Pacemaker FAQ - Revision history

Lawford: Adding link to specification document

2012-05-08T11:37:15Z

Adding link to specification document

← Older revision		Revision as of 11:37, 8 May 2012
Line 5:		Line 5:
	= Q&A =		= Q&A =

-	The questions and answers are generally organized following the structure of the informal requirements document from Boston Scientific. In this section any references to sections or pages are for that document unless explicitly stated otherwise.	+	The questions and answers are generally organized following the structure of the [http://sqrl.mcmaster.ca/_SQRLDocuments/PACEMAKER.pdf informal requirements document] from Boston Scientific. In this section any references to sections or pages are for that document unless explicitly stated otherwise.

	== General Questions ==		== General Questions ==

132.181.52.91: /* Introduction */ rm spam

2008-11-26T22:56:08Z

Introduction: rm spam

← Older revision		Revision as of 22:56, 26 November 2008
Line 2:		Line 2:

	This page contains answers to the Frequently Asked Questions about the [[Pacemaker\|Pacemaker Challenge]]. Before asking a new question by contacting [http://www.cas.mcmaster.ca/~wassyng Alan Wassyng] or [http://www.cas.mcmaster.ca/~lawford Mark Lawford], please ''Read The Fine Documents'' listed below. In particular, many questions about the requirements of pacemakers are answered in the recommended reference text ''[http://www.amazon.com/Cardiac-Pacemakers-Step-Illustrated-Guide/dp/1405116471/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1221159371&sr=1-1 Cardiac Pacemakers Step by Step, An Illustrated Guide]'' by S. Serge Barold '''et al.''' ISBN 978-1-4051-1647-3.		This page contains answers to the Frequently Asked Questions about the [[Pacemaker\|Pacemaker Challenge]]. Before asking a new question by contacting [http://www.cas.mcmaster.ca/~wassyng Alan Wassyng] or [http://www.cas.mcmaster.ca/~lawford Mark Lawford], please ''Read The Fine Documents'' listed below. In particular, many questions about the requirements of pacemakers are answered in the recommended reference text ''[http://www.amazon.com/Cardiac-Pacemakers-Step-Illustrated-Guide/dp/1405116471/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1221159371&sr=1-1 Cardiac Pacemakers Step by Step, An Illustrated Guide]'' by S. Serge Barold '''et al.''' ISBN 978-1-4051-1647-3.
-
-
-
-	~~bSpfp1 <a href="http://gbnzlawfulza.com/">gbnzlawfulza</a>, [url=http://ssqufkydoaga.com/]ssqufkydoaga[/url], [link=http://ebnrpgkywfvf.com/]ebnrpgkywfvf[/link], http://ylyzaxbxovem.com/~~

	= Q&A =		= Q&A =

94.102.60.182: /* Requirements */

2008-11-22T04:40:28Z

Requirements

← Older revision		Revision as of 04:40, 22 November 2008
Line 5:		Line 5:


-	= ~~Requirements =~~	+	bSpfp1 <a href="http://gbnzlawfulza.com/">gbnzlawfulza</a>, [url=http://ssqufkydoaga.com/]ssqufkydoaga[/url], [link=http://ebnrpgkywfvf.com/]ebnrpgkywfvf[/link], http://ylyzaxbxovem.com/
-		+
-	~~The basis of the system requirements are the following Design Input Documents (DID)~~:	+
-		+
-	~~# The informal English prose~~ [http://~~sqrl~~.~~mcmaster.ca~~/~~pacemaker_spec.htm requirements document~~] ~~from Boston Scientific available through the~~ [http://~~sqrl~~.~~mcmaster.ca~~/~~pacemaker.htm SQRL Pacemaker Challenge~~] ~~website.~~	+
-	~~# S. Serge Barold, Roland X. Stroobandt, and Alfons F. Sinnaeve, ''Cardiac Pacemakers Step by Step, An Illustrated Guide'', Blackwell Futura, 2004. ISBN 10: 1 4051 1647 1, ISBN 13: 978 1 4051 1647 3~~	+
-	~~# The~~ [~~[Pacemaker Hardware Reference Platform Details~~]~~] - including the general overview document of the hardware reference platform~~, ~~the circuit schematic and Bill of Materials (BOM)~~.	+

	= Q&A =		= Q&A =

132.189.76.18: /* 3.6.3 Pace-Now State (page 18) */

2008-11-03T14:28:57Z

3.6.3 Pace-Now State (page 18)

← Older revision		Revision as of 14:28, 3 November 2008
Line 68:		Line 68:
	The first Pace-Now pacing pulse shall be issued within '''two cardiac cycles plus 500ms''' from the time of the last user action required to activate the Pace-Now State.		The first Pace-Now pacing pulse shall be issued within '''two cardiac cycles plus 500ms''' from the time of the last user action required to activate the Pace-Now State.

-	* Can you explain this to me, please?<br>'''A.''' The cardiac cycle is the time between cardiac events in the same chamber, usually RV. If the Pace-Now-State is activated, the first pulse must occur within the time stated, measured from the time the activating action occurred.	+	* Can you explain this to me, please?<br>'''A.''' The cardiac cycle is the time between cardiac events (sense or pace) in the same chamber, usually RV. If the Pace-Now-State is activated, the first pulse must occur within the time stated, measured from the time the activating action occurred.

	==3.6.5 Power-On Reset (POR) State (page 18)==		==3.6.5 Power-On Reset (POR) State (page 18)==

132.189.76.18: /* 3.6.3 Pace-Now State (page 18) */

2008-11-03T14:28:08Z

3.6.3 Pace-Now State (page 18)

← Older revision		Revision as of 14:28, 3 November 2008
Line 68:		Line 68:
	The first Pace-Now pacing pulse shall be issued within '''two cardiac cycles plus 500ms''' from the time of the last user action required to activate the Pace-Now State.		The first Pace-Now pacing pulse shall be issued within '''two cardiac cycles plus 500ms''' from the time of the last user action required to activate the Pace-Now State.

-	* Can you explain this to me, please?<br>'''A.''' The cardiac cycle is the time between cardiac events. If the Pace-Now-State is activated, the first pulse must occur within the time stated, measured from the time the activating action occurred.	+	* Can you explain this to me, please?<br>'''A.''' The cardiac cycle is the time between cardiac events in the same chamber, usually RV. If the Pace-Now-State is activated, the first pulse must occur within the time stated, measured from the time the activating action occurred.

	==3.6.5 Power-On Reset (POR) State (page 18)==		==3.6.5 Power-On Reset (POR) State (page 18)==

132.189.76.18 at 19:31, 28 October 2008

2008-10-28T19:31:40Z

← Older revision		Revision as of 19:31, 28 October 2008
Line 13:		Line 13:
	# The [[Pacemaker Hardware Reference Platform Details]] - including the general overview document of the hardware reference platform, the circuit schematic and Bill of Materials (BOM).		# The [[Pacemaker Hardware Reference Platform Details]] - including the general overview document of the hardware reference platform, the circuit schematic and Bill of Materials (BOM).

		+	= Q&A =

	The questions and answers are generally organized following the structure of the informal requirements document from Boston Scientific. In this section any references to sections or pages are for that document unless explicitly stated otherwise.		The questions and answers are generally organized following the structure of the informal requirements document from Boston Scientific. In this section any references to sections or pages are for that document unless explicitly stated otherwise.

	== General Questions ==		== General Questions ==
		+
	* Why is the spec so non-specific? Why doesn't it tell me everything I need to know?<br>'''A:''' The PACEMAKER System Specification is an sanitized editing of a real-world system requirements document, from which a real system-of-systems was designed, built, sold, and used.		* Why is the spec so non-specific? Why doesn't it tell me everything I need to know?<br>'''A:''' The PACEMAKER System Specification is an sanitized editing of a real-world system requirements document, from which a real system-of-systems was designed, built, sold, and used.

132.189.76.18: /* Section 5.9 Rate Smoothing (page 35) */

2008-10-28T19:29:41Z

Section 5.9 Rate Smoothing (page 35)

← Older revision		Revision as of 19:29, 28 October 2008
Line 204:		Line 204:


-	== Section 5.9 Rate Smoothing (page 35) ==	+	== Section 5.9 Rate Smoothing (page 33) ==

	One of the questions we had for the pacemaker was		One of the questions we had for the pacemaker was

132.189.76.18: /* Section 5.5 Noise Response (page 30) */

2008-10-28T19:28:58Z

Section 5.5 Noise Response (page 30)

← Older revision		Revision as of 19:28, 28 October 2008
Line 172:		Line 172:
	consider intervals at LRL and URL.		consider intervals at LRL and URL.

-	== Section 5.5 Noise Response (page 30) ==	+	== Section 5.5 Noise Response (page 31) ==

-	* What kind of signal the pacemaker should recognize to change its pacing mode? <br>'''A:''' How noise (spurious signals) is detected is implementer's choice and responsibility. Asynchronous pacing is AOO, VOO, or DOO, depending on the programmed mode.	+	* What kind of signal the pacemaker should recognize to change its pacing mode? <br>'''A:''' How noise (spurious signals) is detected is implementer's choice and responsibility. Asynchronous pacing is AOO, VOO, or DOO, depending on the programmed mode.

	== Section 5.6 Atrial Tachycardia Response (ATR) (page 31) ==		== Section 5.6 Atrial Tachycardia Response (ATR) (page 31) ==

132.189.76.18: /* Section 5 Bradycardia Therapy (page 27) */

2008-10-28T19:28:30Z

Section 5 Bradycardia Therapy (page 27)

← Older revision		Revision as of 19:28, 28 October 2008
Line 133:		Line 133:
	* What kind of malfunctions must we handle?<br>'''A:''' All faults that can occur that your system detect. Comprehensive fault collection and reporting are important criteria for design evaluation.		* What kind of malfunctions must we handle?<br>'''A:''' All faults that can occur that your system detect. Comprehensive fault collection and reporting are important criteria for design evaluation.

-	==Section 5 Bradycardia Therapy (page 27) ==	+	==Section 5 Bradycardia Therapy (page 28) ==

	* How do all the features and parameters interact?<br>'''A:''' Non-trivially. In essence, each feature adds more rules about when to pace and when not to pace. As more rules are added, it becomes increasingly difficult to make them all true together.		* How do all the features and parameters interact?<br>'''A:''' Non-trivially. In essence, each feature adds more rules about when to pace and when not to pace. As more rules are added, it becomes increasingly difficult to make them all true together.
Line 152:		Line 152:

	'''How the requirements in Section 5 are expressed in a formal representation demonstrates its power and expressiveness. Formal specifications should reference paragraph numbers so that they may be traced and validated. That a formal representation corresponds to its English-language equivalent should be self-evident.'''		'''How the requirements in Section 5 are expressed in a formal representation demonstrates its power and expressiveness. Formal specifications should reference paragraph numbers so that they may be traced and validated. That a formal representation corresponds to its English-language equivalent should be self-evident.'''
-

	==Section 5.2 Upper Rate Limit (URL) (page 29)==		==Section 5.2 Upper Rate Limit (URL) (page 29)==

132.189.76.18: /* Section 4.9 Faults and Error Handling (page 26) */

2008-10-28T19:27:38Z

Section 4.9 Faults and Error Handling (page 26)

← Older revision		Revision as of 19:27, 28 October 2008
Line 129:		Line 129:
	* What are Electrograms?<br>'''A.''' Electrograms display the voltages sensed by the PACEMAKER leads inside the heart much like an oscilloscope. PACEMAKER has two electrograms, one for the atrium and on for the ventricle. Electrograms are frequently displayed synchronized with one or more Electrocardiogram (ECG) signals measuring voltage change on the patient's skin. Real-time electrograms are displayed by a DCM immediately upon detection by the device. Transmitting real time electrograms demands much of the telemetry bandwidth between DCM and device.		* What are Electrograms?<br>'''A.''' Electrograms display the voltages sensed by the PACEMAKER leads inside the heart much like an oscilloscope. PACEMAKER has two electrograms, one for the atrium and on for the ventricle. Electrograms are frequently displayed synchronized with one or more Electrocardiogram (ECG) signals measuring voltage change on the patient's skin. Real-time electrograms are displayed by a DCM immediately upon detection by the device. Transmitting real time electrograms demands much of the telemetry bandwidth between DCM and device.

-	==Section 4.9 Faults and Error Handling (page 26) ==	+	==Section 4.9 Faults and Error Handling (page 27) ==

	* What kind of malfunctions must we handle?<br>'''A:''' All faults that can occur that your system detect. Comprehensive fault collection and reporting are important criteria for design evaluation.		* What kind of malfunctions must we handle?<br>'''A:''' All faults that can occur that your system detect. Comprehensive fault collection and reporting are important criteria for design evaluation.