http://wiki.cas.mcmaster.ca/index.php?title=Special:Contributions&feed=atom&target=LawfordComputing and Software Wiki - User contributions [en]2024-03-28T22:44:59ZFrom Computing and Software WikiMediaWiki 1.15.1http://wiki.cas.mcmaster.ca/index.php/Tabular_ExpressionsTabular Expressions2012-11-08T20:54:02Z<p>Lawford: Tabular Expressions wiki page</p>
<hr />
<div>This is a placeholder page for a wiki on tabular expression.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_FAQPacemaker FAQ2012-05-08T11:37:15Z<p>Lawford: Adding link to specification document</p>
<hr />
<div>= Introduction =<br />
<br />
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.<br />
<br />
= Q&A =<br />
<br />
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.<br />
<br />
== General Questions ==<br />
<br />
* 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. <br />
<br />
Furthermore, the spec presumes the reader has domain knowledge to achieve its perspicuousness. This domain knowledge has been superbly summarized in a "cartoon" book, Step-by-Step (SbS), obviously derived from slides for a course for electrophysiologists who (will) use pacemakers to treat bradycardia. Many frequently-asked-questions reveal that the questioner has not read SbS, because the answers are contained therein. <br />
<br />
As much as possible, the spec defines requirements, not design. Requirements define '''''what''''' a system should do; designs define '''''how''''' the system does it. Verification asserts the '''''how''''' meets the '''''what'''''.<br />
<br />
* Why was the spec created?<br>'''A:''' The impetus for creating the spec was to provide a subject for the demonstration of formal methodologies on a real-world problem of tractable size. The properties demanded in Section 5 would be translated into a mathematically-precise notation (requirements); a mathematically-precise implementation would be claimed to uphold those properties (design), and some formal verification method (model-checking, proof, etc.) that the design meets its requirements.<br>During the arduous process of sanitizing a Company Confidential document to get approval for public release, no alternative uses of the spec were envisioned. That the spec would be used as subject of senior EE hardware design projects, senior software engineering projects, IEC62304 tutorial, or student contest at ICSE was unanticipated. Let SQRL know if you use the spec for some other purpose.<br />
<br />
== Section 2.5.2 Implant Phase (page 11)==<br />
7. Testing the system sensing and pacing efficacy.<br />
* What kind of test is made? <br />
* Which of these parameters are evaluated?<br>'''A:''' See #6 in the section above 2.5.2<br />
<br />
== Section 2.5.3 Predischarge Follow-up (Page 12) ==<br />
2. Reprogramming to final pre-discharge value<br />
* Is there any special values for parameters?<br>'''A.''' No. This just means that the doctor can change parameters after implant, but before the patient leaves the hospital.<br />
<br />
== Section 3.2.4 Printed Reports (page 14)==<br />
1. A Trending Report shall be available.<br />
* What is a trending report?<br>'''A.''' A trending report summarizes heart history since the last follow-up, typically three months. It will include histograms and sensor trending. Lead impedance and sense amplitude may also be included. SbS has other examples of data accumulated and reported. This is an area of implementer's discretion.<br />
<br />
== Section 3.4.3 Rate Sensing (page 16)==<br />
* What exactly is a rate sensing?<br>'''A.''' Rate sensing converts an analog voltage to a discrete sense event when that voltage exceeds a programmed threshold; the time between sense events determines the patient's heart rate. <br />
<br />
* How are cardiac cycle lengths measured?<br>'''A.''' The time between ventricular events is the cardiac cycle length, except for atrium-only pacing modes which uses the time between atrial events.<br />
<br />
* Based on the event markers?<br>'''A.''' Yes. VS/AS indicates an intrinsic contraction; VP/AP indicates a contraction caused by a pace.<br />
<br />
* What is a rate detection decision?<br>'''A.''' Choice of event marker. The timing of event markers determines heart rate in beats per minute.<br />
<br />
* How do rate detection decisions affect the pacemaker behavior?<br>'''A.''' Fundamentally. It determines how the device responds based on mode (DDD, VVIR, etc.) and the programmed timing parameters. <br />
<br />
* “Rate shall be evaluated on an interval-by-interval basis.” Is there any defined interval for this measurement?<br>'''A.''' The cardiac cycle interval.<br />
<br />
== Section 3.6.1 Permanent State (Page 17) ==<br />
The normal pacing parameters programmed shall be used in the permanent brady state. <br />
* Which are these normal pacing parameters?<br>'''A.''' The ones that are currently programmed.<br />
<br />
== Section 3.6.2 Temporary Bradycardia Pacing (page 17)==<br />
The temporary brady parameters programmed shall be used in the temporary brady state. <br />
* Which are these temporary brady parameters?<br>'''A.''' An identical set of parameters to the permanent parameters, but changes in temporary parameters do not affect permanent parameters.<br><br />
The temporary state shall be capable of being used to temporarily test various system parameters or provide patient diagnostic testing.<br />
* Which parameters are tested? <br>'''A.''' Any or all parameters that the physician wishes to try temporarily.<br />
* What is the "patient diagnostic testing".<br>'''A.''' Testing impedance/amplitude/threshold.<br />
<br />
==3.6.3 Pace-Now State (page 18)==<br />
<br />
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.<br />
<br />
* 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.<br />
<br />
==3.6.5 Power-On Reset (POR) State (page 18)==<br />
<br />
All functions shall be disabled until the battery voltage exceeds the''' POR trip voltage.'''<br />
<br />
* What is a POR trip voltage?<br>'''A.''' The minimum battery voltage necessary to pace.<br />
<br />
==3.7 Magnet Test (page 19)==<br />
<br />
3. When the magnet is removed, the device shall automatically assume PRETEST OPERATION. <br />
<br />
* What is the “PRETEST OPERATION“? <br>'''A.''' Whatever the PG was doing immediately prior to the application of the magnet.<br />
<br />
* What is changed in the pulse generator (PG)? <br>'''A.''' Nothing.<br />
<br />
* Do you have any more details for the Magnet Test? <br>'''A.''' Putting a magnet causes a pacing rate indicating energy left (voltage) in the battery:<br />
** 100 ppm => beginning of life (new) (no batt voltage stated)<br />
** 85 ppm => elective replacement indicated (old) batt=2.654 V<br />
<br />
==4.4 Battery Status (page 21) ==<br />
<br />
1. Monitoring voltage information shall be provided <br />
<br />
* How is this made? What kind of information shall be provided?<br>'''A.''' There is an on-board voltmeter. The information provided shall be battery voltage.<br />
<br />
2. Battery Status indicator information shall be provided. <br />
<br />
* What is this information?<br>'''A.''' How much energy is left in the battery. A typical visual representation is a “gas gauge”.<br />
<br />
==Section 4.5 Threshold Test (page 22) ==<br />
<br />
* How does it happen?<br>'''A.''' Loss of capture is observed by the change in shape of the ECG PQRS complex. See SbS 27.<br />
<br />
* Which parameters are evaluated?<br>'''A.''' Pace voltages and pulse widths.<br />
<br />
* During this test, should the pacemaker change its current bradycardia state?<br>'''A.''' Temporarily pace faster than the intrinsic rate (at which the heart beats unassisted).<br />
<br />
==Section 4.6 - Bradycardia History (page 22) ==<br />
<br />
* Which parameters are adjusted in this case? <br>'''A.''' All.<br />
<br />
==Section 4.6.1 Rate Histograms (page 22)==<br />
<br />
* I can’t understand what does mean: "Distributions shall be recorded for all ..." <br>'''A.''' A histogram<br />
<br />
* What is a paced event? And a sensed event?<br>'''A.''' A paced event is the issuing of a pacing pulse. A sensed event is the detection of an atrial or ventricular contraction.<br>Examples of histograms can be found on SbS 279-281.<br />
<br />
==Section 4.6.2 Rate Trending (Page 23) ==<br />
<br />
The system shall be configurable to record and display the following data items separately or concurrently over a programmable duration and storage method: 1. Pacing rate 2. sensor data. <br />
* Could it be explained in another way?<br>'''A.''' Device records pacing rate and acceleration (in milliG); DCM displays charts with time on horizontal axis, rate and XL on vertical axis.<br />
<br />
==Section 4.6.4 Sensor Trending (page 24)==<br />
<br />
The system shall provide off-line prediction analysis of sensor indicated rate with or without intrinsic rate for the synchronized data collected. <br />
<br />
* Can you explain this to me, please?<br>'''A.''' Sensor trending displays the motion detected by the accelerometer, and the corresponding rate paced. XL and rate are sampled periodically, and displayed together to help the physician adjust a patient's rate response parameters.<br />
<br />
==Section 4.7 Real-time Electrograms (page 24)==<br />
<br />
* 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.<br />
<br />
==Section 4.9 Faults and Error Handling (page 27) ==<br />
<br />
* 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.<br />
<br />
==Section 5 Bradycardia Therapy (page 28) ==<br />
<br />
* 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.<br />
<br />
In VOO mode with LRL=60 bpm, the only rule is to pace each second.<br />
In VVI mode, senses inhibit paces, the rule becomes to pace whenever neither a pace nor a (non-refractory) sense has occurred in the past second. <br />
<br />
Rules that say: "inhibit, cause, or delay this action, when that occurs, except when thus" start to pile-up. That's what makes the spec a non-trivial subject for formal methods. Assuring that the device will satisfy any combination of features, is a challenge for validation as well as verification. <br />
<br />
Time is what makes embedded systems fundamentally different from mere state transformation. <br />
<br />
Section 5 defines all the timing behavior declaratively. It says what should result, not how to achieve it. Read them as invariants over the life of the device:<br />
LRL - there will be no duration of time longer than the LRL period without a heart beat (except for hysteresis pacing).<br />
URL - no paces will be faster than the upper rate limit.<br />
VRP - ventricular senses soon after ventricular paces or senses will be ignored<br />
<br />
SbS has many examples, sometimes using slightly different names (AV interval instead of AV delay). Read the text starting at SbS 291 first, then read all of SbS from the beginning.<br />
<br />
'''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.'''<br />
<br />
==Section 5.2 Upper Rate Limit (URL) (page 29)== <br />
<br />
This section said URI is the min time between a ventricular event and the next ventricular pace. <br />
* Why is URI effective in modes without ventricular pacing nor sensing, such as AAT, AOO (Table 6, page 28)?<br>'''A:''' “URI” should be “URL interval” in the question. For AAT, trigger paces must not be faster than URL. AOO is constant rate pacing at LRL. So long as LRL < URL (one of many implicit parameter constraints) AOO will pace slower than URL.<br> The requirement could have been broadened to atrial-only modes. Alternatively, strict reading that URL does not apply to atrial-only modes is acceptable as well.<br />
<br />
== Section 5.3.3 Dynamic AV Delay (page 29) ==<br />
<br />
When using Dynamic AV delay, the delay should stay<br />
between a max and a min value. In section 5.3.3, it says the way the new<br />
AV delay is calculated as follows:<br />
<br />
"The previous cardiac cycle length is multiplied by a factor stored in<br />
device memory to create the dynamic AV delay."<br />
<br />
* The range of values that such a factor can take is not specified in the<br />
document. What happens if we multiply the cardiac cycle length by<br />
the factor and get a value outside the max/min range for the dynamic AV?<br>''A.'' The factor must be calculated to stay within min-max. Hint:<br />
consider intervals at LRL and URL.<br />
<br />
== Section 5.5 Noise Response (page 31) ==<br />
<br />
* 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.<br />
<br />
== Section 5.6 Atrial Tachycardia Response (ATR) (page 31) ==<br />
<br />
In section 5.6.1 of the document, explaining the AT detection algorithm,<br />
points 1 and 2 do not clearly define the start and stop of AT.<br />
<br />
"1. AT onset shall be detected when the intervals between atrial senses are <br />
predominately, but not exclusively, faster than URL.<br> <br />
2. AT cessation shall be detected when the intervals between atrial senses <br />
are mostly, but not exclusively, faster than URL. "<br />
<br />
The only difference between start/stop is "predominately" vs. "mostly". <br />
<br />
*What is the interpretation of these statements?<br>'''A.''' Both of those def'ns for ATR were deliberately fudged to hide the actual algorithm. In essence, the algorithm allows some slow beats among the fast ones to enter ATR, to leave it's the opposite. "predominately" and "mostly" were carefully chosen. <br>The implementer gets to define the implementation, but it must be fast. 30s tracking Afib at MTR is really hard on sick patients.<br />
<br />
* The definition of what the device should do for Atrial Tachycardia Response (ATR) leaves the algorithm for deciding when to mode switch loosely defined. Please explain why a physician would prescribe ATR to help me devise an algorithm that meets the requirement.<br>'''A.''' In DDD mode, ventricular paces track atrial senses after a sensed AV delay. When the atrium naturally beats faster with exercise, ventricular contractions due to paces quicken in lockstep. For patients whose problem is poor conduction, this prescription restores people who could barely walk across a room, to normal life. Immediately. Many patients who got the real device felt like kids again, the day after implant.<br />
<br />
Unfortunately, some patients can get electrical "storms" in their right-atria which if tracked, would inappropriately pace sick hearts at URL. Therefore, when the atrial rate is "too fast", ATR switches to a non-tracking mode, VVI. When the storm subsides, no longer "too fast", ATR switches back to DDD mode.<br />
<br />
To prevent mode switching except for sustained atrial storms, the spec requires that the rate of recent atrial senses be "predominantly" faster than URL to switch from DDD to VVI, and "mostly" faster to stay in VVI. A possible, but not very good, algorithm for deciding when to mode switch, would be:<br />
<br />
When at least 4 of the last 5 atrial senses have periods shorter than the URL interval (in ms), then ATR mode switch from DDD to VVI.<br />
When no more than 2 of the last 5 atrial senses have periods shorter than the URL interval, then ATR mode switch from VVI back to DDD.<br />
<br />
All manufacturers of pacemakers use different criteria for ATR mode switching; all claim their criteria work the best, certainly better that the one above; and all meet the requirement as stated in the spec. <br />
<br />
Sudden drops in pacing rate from URL to LRL are unpleasant for patients. Rate smoothing is often used in conjunction with ATR to moderate pacing rate changes arising from pacing mode changes.<br />
<br />
<br />
== Section 5.9 Rate Smoothing (page 33) ==<br />
<br />
One of the questions we had for the pacemaker was<br />
regarding<br />
the rate smoothing algorithm. We were wondering if the pacing rate was<br />
suppose to increase based on a percentage of the current pacing rate or<br />
the rate we are suppose to be pacing at (Lower rate Limit).<br />
<br />
'''A.''' The percentage is applied to the previous cardiac cycle. Although<br />
the physician may define up-rate smoothing of 3%, the period must<br />
decrease so that the rate is 1.03x faster => divide by 1.03 instead of<br />
multiply by 0.97. Rate smoothing is VERY important, trumping all other<br />
rate modifiers.<br />
<br />
= Hardware Reference Platform =<br />
<br />
==Availability and Cost==<br />
* When will the pacemaker boards be available for purchase?<br>'''A.''' There are a limited number of boards (43) available right now!<br />
* How much do pacemaker boards cost?<br>'''A.''' $350 (CDN) plus shipping. This includes programming cables compatible with the Microchip ICD2 and the PICKit2 programmer. We are selling these boards at cost. You are welcome to try to build your own but be forewarned that they use a lot of surface mount parts!<br />
<br />
==Getting Started==<br />
* What else do I need to get started?<br>'''A.''' You need the following:<br />
** A power supply, <br />
** serial cable or USB/Serial cable, <br />
** a compiler or assembler that supports the PIC18F4520 microcontroller (e.g. Microchip's [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010014 MPLAB C18] Compiler or the Small Device C Compiler ([http://sdcc.sourceforge.net/ SDCC])),<br />
** and a PIC programmer/debugger such as the Microchip ICD2 or PICKit2. <br />
** We'd also recommend an oscilloscope and signal generator or computer with and A/D card and some software such as Labview. These are helpful for debugging and generating input signals.<br />
* What are the power supply requirements?<br>'''A.''' We recommend a 12V 150+ mA power supply with a standard 2mm jack. We have also run the boards off of a 9V 200mA adapter and a standard 9V ([http://en.wikipedia.org/wiki/PP3_battery | PP3]) battery without any problems. <br />
<br />
<br />
== How do I order pacemaker boards?==<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford].</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2009-10-31T14:51:53Z<p>Lawford: /* What's New? */ Added pre-FM2009 workshop</p>
<hr />
<div>= Pacemaker Formal Methods Challenge =<br />
<br />
See the [[Pacemaker FAQ]] for detailed questions about the requirements, hardware or pacemakers in general. <br />
<br />
See below for What's New, an Intro, etc.<br />
<br />
= What's New? =<br />
* '''Nov. 1, 2009:''' A pre-FM2009 workshop on the paceamaker challenge is being held in Eindhoven, NL to review the present state of the Pacemaker challenge and prepare to make it a major part of FM2011. The workshop is in the main auditorium building on the TU Eindhoven Campus, room Room 11. <br />
* '''Oct 22, 2008:''' A web page has been set up containing updates on the [http://www.vdmportal.org/twiki/bin/view/Main/PacemakerCaseStudy VDM work on the Pacemaker]. <br />
* '''Oct 6, 2008:''' Of the initial run of 50 hardware reference platform, 17 remain available for purchase. Get yours while they are still available, otherwise you'll have to make your own or hope for a 2nd production run.<br />
* '''Sept 15, 2008:''' John Fitzgerald gave an invited talk about the Pacemaker Challenge to the [http://www.abz2008.org/VsrNetProgramme.pdf VSR-net day] held at the [http://www.abz2008.org/ ABZ conference] in London. John's slides are available [http://www.vdmportal.org/twiki/pub/Main/PacemakerCaseStudy/FitzgeraldPacemaker.pdf Here]. There was a positive response to the talk (plus a discussion about certification evidence) and John hope to arrange a workshop for those wanting to contribute at the latest early in 2009, probably at Newcastle University, UK. <br />
* '''Sept 15, 2008:''' The pacemaker challenge has been adopted by Alan Wassyng of McMaster's Department of Computing and Software for the course ''SFWR ENG 3K04 SOFTWARE DEVELOPMENT'' that is taught to 3rd year undergraduate Mechatronics Engineering and Electrical Engineering students.<br />
* '''Aug 20, 2008:''' Hardware Reference Platform boards are now available at a cost of $350/board + shipping. Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.<br />
* '''July 22, 2008:''' Mark Lawford presented "The Pace Maker Challenge" at the Real-time and Embedded System Forum (RTES) [http://www.opengroup.org/chicago2008/member-meetings-index.htm Member Meeting] of the [http://www.opengroup.org/chicago2008/venue.htm Open Group Conference], Chicago, IL. This presentation documents the experience from using the Pacemaker Challenge in the senior thesis course for the Undergraduate Software Engineering Students at McMaster University.<br />
* '''May 29, 2008:''' At ''[http://www.fm2008.abo.fi/ FM2008]'' the paper "Incremental Development of a Distributed Real-Time Model of a Cardiac Pacing System using VDM" by Hugo Daniel Macedo, Peter Gorm Larsen and John Fitzgerald was presented. The paper documents the authors progress on Pacemaker Challenge. The full paper is available [http://dx.doi.org/10.1007/978-3-540-68237-0_14 here].<br />
* '''Nov 23, 2007:''' Pacemaker chosen as one of the ICSE 2009 Student COntest in softwaRe Engineering (SCORE 2009) problems. See http://score.elet.polimi.it for details!<br />
<br />
= Introduction =<br />
The Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
== Who's Involved in the Pacemaker Challenge ==<br />
<br />
The [[Software Certification Consortium]] has formed a panel to create submission guidelines and judge submission. Current panel members are:<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Panelist<br />
!Position<br />
!Institution<br />
|-<br />
|Rick Chapman<br />
|General Engineer<br />
|Division of Electrical and Software Engineering Office of Science & Engineering Laboratories, [http://www.fda.gov/cdrh/index.html Center for Devices & Radiological Health, U.S. Food and Drug Administration]<br />
|-<br />
|Brian Larson<br />
|Research Scientist<br />
|[http://www.bostonscientific.com/ Boston Scientific]<br />
|-<br />
|Mark Lawford<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|-<br />
|David Tremaine<br />
|CEO<br />
|[http://www.swi.com/ Systemware Innovation] (SWI)<br />
|-<br />
|Alan Wassyng<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|}<br />
<br />
<br />
People who are known to be working on the Pacemaker Challenge:<br />
<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Researcher<br />
!Institution<br />
!Country<br />
!Involvement<br />
|-<br />
|[http://homepages.cs.ncl.ac.uk/john.fitzgerald/ John Fitzgerald]<br />
|School of Computing Science, Newcastle University<br />
|UK<br />
|Purchased board, Wrote paper about the pacemaker at FM2008<br />
|-<br />
|[http://www.cis.upenn.edu/~lee/home/home.html Insup Lee]<br />
|Electrical and Computer Engineering, University of Pennsylvania<br />
|USA<br />
|Purchased boards, member of SCC<br />
|-<br />
|[http://www.engr.mun.ca/~dpeters/ Dennis Peters]<br />
|Electrical and Computer Engineering, Memorial University of Newfoundland<br />
|Canada<br />
|Purchased boards<br />
|}<br />
<br />
= Pacemaker Hardware Reference Platform =<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. We have now produced an additional 45 board for sale at cost (approx. $350 CDN + shipping) to interested students, researchers and industry people. The boards come with cables to connect directly to a Microchip ICD2 or PICKit2 programmer. You will need to supply your own 12V DC/150+mA Power supply and serial cable.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-12-08T15:49:24Z<p>Lawford: Undo revision 3605 by Special:Contributions/194.165.42.59 (User talk:194.165.42.59)</p>
<hr />
<div>= Pacemaker Formal Methods Challenge =<br />
<br />
See the [[Pacemaker FAQ]] for detailed questions about the requirements, hardware or pacemakers in general. <br />
<br />
See below for What's New, an Intro, etc.<br />
<br />
= What's New? =<br />
* '''Oct 22, 2008:''' A web page has been set up containing updates on the [http://www.vdmportal.org/twiki/bin/view/Main/PacemakerCaseStudy VDM work on the Pacemaker]. <br />
* '''Oct 6, 2008:''' Of the initial run of 50 hardware reference platform, 17 remain available for purchase. Get yours while they are still available, otherwise you'll have to make your own or hope for a 2nd production run.<br />
* '''Sept 15, 2008:''' John Fitzgerald gave an invited talk about the Pacemaker Challenge to the [http://www.abz2008.org/VsrNetProgramme.pdf VSR-net day] held at the [http://www.abz2008.org/ ABZ conference] in London. John's slides are available [http://www.vdmportal.org/twiki/pub/Main/PacemakerCaseStudy/FitzgeraldPacemaker.pdf Here]. There was a positive response to the talk (plus a discussion about certification evidence) and John hope to arrange a workshop for those wanting to contribute at the latest early in 2009, probably at Newcastle University, UK. <br />
* '''Sept 15, 2008:''' The pacemaker challenge has been adopted by Alan Wassyng of McMaster's Department of Computing and Software for the course ''SFWR ENG 3K04 SOFTWARE DEVELOPMENT'' that is taught to 3rd year undergraduate Mechatronics Engineering and Electrical Engineering students.<br />
* '''Aug 20, 2008:''' Hardware Reference Platform boards are now available at a cost of $350/board + shipping. Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.<br />
* '''July 22, 2008:''' Mark Lawford presented "The Pace Maker Challenge" at the Real-time and Embedded System Forum (RTES) [http://www.opengroup.org/chicago2008/member-meetings-index.htm Member Meeting] of the [http://www.opengroup.org/chicago2008/venue.htm Open Group Conference], Chicago, IL. This presentation documents the experience from using the Pacemaker Challenge in the senior thesis course for the Undergraduate Software Engineering Students at McMaster University.<br />
* '''May 29, 2008:''' At ''[http://www.fm2008.abo.fi/ FM2008]'' the paper "Incremental Development of a Distributed Real-Time Model of a Cardiac Pacing System using VDM" by Hugo Daniel Macedo, Peter Gorm Larsen and John Fitzgerald was presented. The paper documents the authors progress on Pacemaker Challenge. The full paper is available [http://dx.doi.org/10.1007/978-3-540-68237-0_14 here].<br />
* '''Nov 23, 2007:''' Pacemaker chosen as one of the ICSE 2009 Student COntest in softwaRe Engineering (SCORE 2009) problems. See http://score.elet.polimi.it for details!<br />
<br />
= Introduction =<br />
The Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
== Who's Involved in the Pacemaker Challenge ==<br />
<br />
The [[Software Certification Consortium]] has formed a panel to create submission guidelines and judge submission. Current panel members are:<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Panelist<br />
!Position<br />
!Institution<br />
|-<br />
|Rick Chapman<br />
|General Engineer<br />
|Division of Electrical and Software Engineering Office of Science & Engineering Laboratories, [http://www.fda.gov/cdrh/index.html Center for Devices & Radiological Health, U.S. Food and Drug Administration]<br />
|-<br />
|Brian Larson<br />
|Research Scientist<br />
|[http://www.bostonscientific.com/ Boston Scientific]<br />
|-<br />
|Mark Lawford<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|-<br />
|David Tremaine<br />
|CEO<br />
|[http://www.swi.com/ Systemware Innovation] (SWI)<br />
|-<br />
|Alan Wassyng<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|}<br />
<br />
<br />
People who are known to be working on the Pacemaker Challenge:<br />
<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Researcher<br />
!Institution<br />
!Country<br />
!Involvement<br />
|-<br />
|[http://homepages.cs.ncl.ac.uk/john.fitzgerald/ John Fitzgerald]<br />
|School of Computing Science, Newcastle University<br />
|UK<br />
|Purchased board, Wrote paper about the pacemaker at FM2008<br />
|-<br />
|[http://www.cis.upenn.edu/~lee/home/home.html Insup Lee]<br />
|Electrical and Computer Engineering, University of Pennsylvania<br />
|USA<br />
|Purchased boards, member of SCC<br />
|-<br />
|[http://www.engr.mun.ca/~dpeters/ Dennis Peters]<br />
|Electrical and Computer Engineering, Memorial University of Newfoundland<br />
|Canada<br />
|Purchased boards<br />
|}<br />
<br />
= Pacemaker Hardware Reference Platform =<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. We have now produced an additional 45 board for sale at cost (approx. $350 CDN + shipping) to interested students, researchers and industry people. The boards come with cables to connect directly to a Microchip ICD2 or PICKit2 programmer. You will need to supply your own 12V DC/150+mA Power supply and serial cable.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-12-08T15:20:22Z<p>Lawford: Trying to undo spammer's work.</p>
<hr />
<div>= Pacemaker Formal Methods Challenge =<br />
<br />
See the [[Pacemaker FAQ]] for detailed questions about the requirements, hardware or pacemakers in general. <br />
<br />
See below for What's New, an Intro, etc.<br />
<br />
= What's New? =<br />
* '''Oct 22, 2008:''' A web page has been set up containing updates on the [http://www.vdmportal.org/twiki/bin/view/Main/PacemakerCaseStudy VDM work on the Pacemaker]. <br />
* '''Oct 6, 2008:''' Of the initial run of 50 hardware reference platform, 17 remain available for purchase. Get yours while they are still available, otherwise you'll have to make your own or hope for a 2nd production run.<br />
* '''Sept 15, 2008:''' John Fitzgerald gave an invited talk about the Pacemaker Challenge to the [http://www.abz2008.org/VsrNetProgramme.pdf VSR-net day] held at the [http://www.abz2008.org/ ABZ conference] in London. John's slides are available [http://www.vdmportal.org/twiki/pub/Main/PacemakerCaseStudy/FitzgeraldPacemaker.pdf Here]. There was a positive response to the talk (plus a discussion about certification evidence) and John hope to arrange a workshop for those wanting to contribute at the latest early in 2009, probably at Newcastle University, UK. <br />
* '''Sept 15, 2008:''' The pacemaker challenge has been adopted by Alan Wassyng of McMaster's Department of Computing and Software for the course ''SFWR ENG 3K04 SOFTWARE DEVELOPMENT'' that is taught to 3rd year undergraduate Mechatronics Engineering and Electrical Engineering students.<br />
* '''Aug 20, 2008:''' Hardware Reference Platform boards are now available at a cost of $350/board + shipping. Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.<br />
* '''July 22, 2008:''' Mark Lawford presented "The Pace Maker Challenge" at the Real-time and Embedded System Forum (RTES) [http://www.opengroup.org/chicago2008/member-meetings-index.htm Member Meeting] of the [http://www.opengroup.org/chicago2008/venue.htm Open Group Conference], Chicago, IL. This presentation documents the experience from using the Pacemaker Challenge in the senior thesis course for the Undergraduate Software Engineering Students at McMaster University.<br />
* '''May 29, 2008:''' At ''[http://www.fm2008.abo.fi/ FM2008]'' the paper "Incremental Development of a Distributed Real-Time Model of a Cardiac Pacing System using VDM" by Hugo Daniel Macedo, Peter Gorm Larsen and John Fitzgerald was presented. The paper documents the authors progress on Pacemaker Challenge. The full paper is available [http://dx.doi.org/10.1007/978-3-540-68237-0_14 here].<br />
* '''Nov 23, 2007:''' Pacemaker chosen as one of the ICSE 2009 Student COntest in softwaRe Engineering (SCORE 2009) problems. See http://score.elet.polimi.it for details!<br />
<br />
= Introduction =<br />
The Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
== Who's Involved in the Pacemaker Challenge ==<br />
<br />
The [[Software Certification Consortium]] has formed a panel to create submission guidelines and judge submission. Current panel members are:<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Panelist<br />
!Position<br />
!Institution<br />
|-<br />
|Rick Chapman<br />
|General Engineer<br />
|Division of Electrical and Software Engineering Office of Science & Engineering Laboratories, [http://www.fda.gov/cdrh/index.html Center for Devices & Radiological Health, U.S. Food and Drug Administration]<br />
|-<br />
|Brian Larson<br />
|Research Scientist<br />
|[http://www.bostonscientific.com/ Boston Scientific]<br />
|-<br />
|Mark Lawford<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|-<br />
|David Tremaine<br />
|CEO<br />
|[http://www.swi.com/ Systemware Innovation] (SWI)<br />
|-<br />
|Alan Wassyng<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|}<br />
<br />
<br />
People who are known to be working on the Pacemaker Challenge:<br />
<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Researcher<br />
!Institution<br />
!Country<br />
!Involvement<br />
|-<br />
|[http://homepages.cs.ncl.ac.uk/john.fitzgerald/ John Fitzgerald]<br />
|School of Computing Science, Newcastle University<br />
|UK<br />
|Purchased board, Wrote paper about the pacemaker at FM2008<br />
|-<br />
|[http://www.cis.upenn.edu/~lee/home/home.html Insup Lee]<br />
|Electrical and Computer Engineering, University of Pennsylvania<br />
|USA<br />
|Purchased boards, member of SCC<br />
|-<br />
|[http://www.engr.mun.ca/~dpeters/ Dennis Peters]<br />
|Electrical and Computer Engineering, Memorial University of Newfoundland<br />
|Canada<br />
|Purchased boards<br />
|}<br />
<br />
= Pacemaker Hardware Reference Platform =<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. We have now produced an additional 45 board for sale at cost (approx. $350 CDN + shipping) to interested students, researchers and industry people. The boards come with cables to connect directly to a Microchip ICD2 or PICKit2 programmer. You will need to supply your own 12V DC/150+mA Power supply and serial cable.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-10-13T12:54:19Z<p>Lawford: Put link to FAQ at the top</p>
<hr />
<div>= Pacemaker Formal Methods Challenge =<br />
<br />
See the [[Pacemaker FAQ]] for detailed questions about the requirements, hardware or pacemakers in general. <br />
<br />
See below for What's New, an Intro, etc.<br />
<br />
= What's New? =<br />
<br />
* '''Oct 6, 2008:''' Of the initial run of 50 hardware reference platform, 17 remain available for purchase. Get yours while they are still available, otherwise you'll have to make your own or hope for a 2nd production run.<br />
* '''Sept 15, 2008:''' The pacemaker challenge has been adopted by Alan Wassyng of McMaster's Department of Computing and Software for the course ''SFWR ENG 3K04 SOFTWARE DEVELOPMENT'' that is taught to 3rd year undergraduate Mechatronics Engineering and Electrical Engineering students.<br />
* '''Aug 20, 2008:''' Hardware Reference Platform boards are now available at a cost of $350/board + shipping. Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.<br />
* '''July 22, 2008:''' Mark Lawford presented "The Pace Maker Challenge" at the Real-time and Embedded System Forum (RTES) [http://www.opengroup.org/chicago2008/member-meetings-index.htm Member Meeting] of the [http://www.opengroup.org/chicago2008/venue.htm Open Group Conference], Chicago, IL. This presentation documents the experience from using the Pacemaker Challenge in the senior thesis course for the Undergraduate Software Engineering Students at McMaster University.<br />
* '''May 29, 2008:''' At ''[http://www.fm2008.abo.fi/ FM2008]'' the paper "Incremental Development of a Distributed Real-Time Model of a Cardiac Pacing System using VDM" by Hugo Daniel Macedo, Peter Gorm Larsen and John Fitzgerald was presented. The paper documents the authors progress on Pacemaker Challenge. The full paper is available [http://dx.doi.org/10.1007/978-3-540-68237-0_14 here].<br />
* '''Nov 23, 2007:''' Pacemaker chosen as one of the ICSE 2009 Student COntest in softwaRe Engineering (SCORE 2009) problems. See http://score.elet.polimi.it for details!<br />
<br />
= Introduction =<br />
The Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
== Who's Involved in the Pacemaker Challenge ==<br />
<br />
The [[Software Certification Consortium]] has formed a panel to create submission guidelines and judge submission. Current panel members are:<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Panelist<br />
!Position<br />
!Institution<br />
|-<br />
|Rick Chapman<br />
|General Engineer<br />
|Division of Electrical and Software Engineering Office of Science & Engineering Laboratories, [http://www.fda.gov/cdrh/index.html Center for Devices & Radiological Health, U.S. Food and Drug Administration]<br />
|-<br />
|Brian Larson<br />
|Research Scientist<br />
|[http://www.bostonscientific.com/ Boston Scientific]<br />
|-<br />
|Mark Lawford<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|-<br />
|David Tremaine<br />
|CEO<br />
|[http://www.swi.com/ Systemware Innovation] (SWI)<br />
|-<br />
|Alan Wassyng<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|}<br />
<br />
<br />
People who are known to be working on the Pacemaker Challenge:<br />
<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Researcher<br />
!Institution<br />
!Country<br />
!Involvement<br />
|-<br />
|[http://www.cs.ncl.ac.uk/people/john.fitzgerald John Fitzgerald]<br />
|School of Computing Science, Newcastle University<br />
|UK<br />
|Purchased board, Wrote paper about the pacemaker at FM2008<br />
|-<br />
|[http://www.cis.upenn.edu/~lee/home/home.html Insup Lee]<br />
|Electrical and Computer Engineering, University of Pennsylvania<br />
|USA<br />
|Purchased boards, member of SCC<br />
|-<br />
|[http://www.engr.mun.ca/~dpeters/ Dennis Peters]<br />
|Electrical and Computer Engineering, Memorial University of Newfoundland<br />
|Canada<br />
|Purchased boards<br />
|}<br />
<br />
= Pacemaker Hardware Reference Platform =<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. We have now produced an additional 45 board for sale at cost (approx. $350 CDN + shipping) to interested students, researchers and industry people. The boards come with cables to connect directly to a Microchip ICD2 or PICKit2 programmer. You will need to supply your own 12V DC/150+mA Power supply and serial cable.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-10-06T17:44:26Z<p>Lawford: Added list of review panel and people working on the pacemaker.</p>
<hr />
<div>= Pacemaker Formal Methods Challenge =<br />
<br />
= What's New? =<br />
<br />
* '''Oct 6, 2008:''' Of the initial run of 50 hardware reference platform, 17 remain available for purchase. Get yours while they are still available, otherwise you'll have to make your own or hope for a 2nd production run.<br />
* '''Sept 15, 2008:''' The pacemaker challenge has been adopted by Alan Wassyng of McMaster's Department of Computing and Software for the course ''SFWR ENG 3K04 SOFTWARE DEVELOPMENT'' that is taught to 3rd year undergraduate Mechatronics Engineering and Electrical Engineering students.<br />
* '''Aug 20, 2008:''' Hardware Reference Platform boards are now available at a cost of $350/board + shipping. Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.<br />
* '''July 22, 2008:''' Mark Lawford presented "The Pace Maker Challenge" at the Real-time and Embedded System Forum (RTES) [http://www.opengroup.org/chicago2008/member-meetings-index.htm Member Meeting] of the [http://www.opengroup.org/chicago2008/venue.htm Open Group Conference], Chicago, IL. This presentation documents the experience from using the Pacemaker Challenge in the senior thesis course for the Undergraduate Software Engineering Students at McMaster University.<br />
* '''May 29, 2008:''' At ''[http://www.fm2008.abo.fi/ FM2008]'' the paper "Incremental Development of a Distributed Real-Time Model of a Cardiac Pacing System using VDM" by Hugo Daniel Macedo, Peter Gorm Larsen and John Fitzgerald was presented. The paper documents the authors progress on Pacemaker Challenge. The full paper is available [http://dx.doi.org/10.1007/978-3-540-68237-0_14 here].<br />
* '''Nov 23, 2007:''' Pacemaker chosen as one of the ICSE 2009 Student COntest in softwaRe Engineering (SCORE 2009) problems. See http://score.elet.polimi.it for details!<br />
<br />
= Introduction =<br />
The Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
== Who's Involved in the Pacemaker Challenge ==<br />
<br />
The [[Software Certification Consortium]] has formed a panel to create submission guidelines and judge submission. Current panel members are:<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Panelist<br />
!Position<br />
!Institution<br />
|-<br />
|Rick Chapman<br />
|General Engineer<br />
|Division of Electrical and Software Engineering Office of Science & Engineering Laboratories, [http://www.fda.gov/cdrh/index.html Center for Devices & Radiological Health, U.S. Food and Drug Administration]<br />
|-<br />
|Brian Larson<br />
|Research Scientist<br />
|[http://www.bostonscientific.com/ Boston Scientific]<br />
|-<br />
|Mark Lawford<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|-<br />
|David Tremaine<br />
|CEO<br />
|[http://www.swi.com/ Systemware Innovation] (SWI)<br />
|-<br />
|Alan Wassyng<br />
|Associate Professor<br />
|[http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL), McMaster University<br />
|}<br />
<br />
<br />
People who are known to be working on the Pacemaker Challenge:<br />
<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
!Researcher<br />
!Institution<br />
!Country<br />
!Involvement<br />
|-<br />
|[http://www.cs.ncl.ac.uk/people/john.fitzgerald John Fitzgerald]<br />
|School of Computing Science, Newcastle University<br />
|UK<br />
|Purchased board, Wrote paper about the pacemaker at FM2008<br />
|-<br />
|[http://www.cis.upenn.edu/~lee/home/home.html Insup Lee]<br />
|Electrical and Computer Engineering, University of Pennsylvania<br />
|USA<br />
|Purchased boards, member of SCC<br />
|-<br />
|[http://www.engr.mun.ca/~dpeters/ Dennis Peters]<br />
|Electrical and Computer Engineering, Memorial University of Newfoundland<br />
|Canada<br />
|Purchased boards<br />
|}<br />
<br />
Detailed questions about the requirements, hardware or pacemakers in general can be found in the [[Pacemaker FAQ]].<br />
<br />
= Pacemaker Hardware Reference Platform =<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. We have now produced an additional 45 board for sale at cost (approx. $350 CDN + shipping) to interested students, researchers and industry people. The boards come with cables to connect directly to a Microchip ICD2 or PICKit2 programmer. You will need to supply your own 12V DC/150+mA Power supply and serial cable.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-10-06T15:41:33Z<p>Lawford: Added 3K04 news</p>
<hr />
<div>= Pacemaker Formal Methods Challenge =<br />
<br />
= What's New? =<br />
<br />
* '''Sept 15, 2008:''' The pacemaker challenge has been adopted by McMaster's Department of Computing and Software for the course ''SFWR ENG 3K04 SOFTWARE DEVELOPMENT'' that is taught to 3rd year undergraduate Mechatronics Engineering and Electrical Engineering students.<br />
* '''Aug 20, 2008:''' Hardware Reference Platform boards are now available at a cost of $350/board + shipping. Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.<br />
* '''July 22, 2008:''' Mark Lawford presented "The Pace Maker Challenge" at the Real-time and Embedded System Forum (RTES) [http://www.opengroup.org/chicago2008/member-meetings-index.htm Member Meeting] of the [http://www.opengroup.org/chicago2008/venue.htm Open Group Conference], Chicago, IL. This presentation documents the experience from using the Pacemaker Challenge in the senior thesis course for the Undergraduate Software Engineering Students at McMaster University.<br />
* '''May 29, 2008:''' At ''[http://www.fm2008.abo.fi/ FM2008]'' the paper "Incremental Development of a Distributed Real-Time Model of a Cardiac Pacing System using VDM" by Hugo Daniel Macedo, Peter Gorm Larsen and John Fitzgerald was presented. The paper documents the authors progress on Pacemaker Challenge. The full paper is available [http://dx.doi.org/10.1007/978-3-540-68237-0_14 here].<br />
* '''Nov 23, 2007:''' Pacemaker chosen as one of the ICSE 2009 Student COntest in softwaRe Engineering (SCORE 2009) problems. See http://score.elet.polimi.it for details!<br />
<br />
= Introduction =<br />
The Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
Detailed questions about the requirements, hardware or pacemakers in general can be found in the [[Pacemaker FAQ]].<br />
<br />
= Pacemaker Hardware Reference Platform =<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. We have now produced an additional 45 board for sale at cost (approx. $350 CDN + shipping) to interested students, researchers and industry people. The boards come with cables to connect directly to a Microchip ICD2 or PICKit2 programmer. You will need to supply your own 12V DC/150+mA Power supply and serial cable.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_FAQPacemaker FAQ2008-09-11T19:00:07Z<p>Lawford: Added ISBN and amazon link to book.</p>
<hr />
<div>= Introduction =<br />
<br />
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.<br />
<br />
<br />
<br />
= Requirements =<br />
<br />
The basis of the system requirements are the following Design Input Documents (DID):<br />
<br />
# 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.<br />
# 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<br />
# The [[Pacemaker Hardware Reference Platform Details]] - including the general overview document of the hardware reference platform, the circuit schematic and Bill of Materials (BOM). <br />
<br />
<br />
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.<br />
<br />
== Section 2.5.2 Implant Phase ==<br />
7. Testing the system sensing and pacing efficacy.<br />
* What kind of test is made? <br />
* Which of these parameters are evaluated?<br>'''A:''' See #6 in the section above 2.5.2<br />
<br />
== Section 2.5.3 Predischarge Follow-up (Page 12) ==<br />
2. Reprogramming to final pre-discharge value<br />
* Is there any special values for parameters?<br>'''A.''' No. This just means that the doctor can change parameters after implant, but before the patient leaves the hospital.<br />
<br />
== Section 3.6.1 Permanent State (Page 17) ==<br />
The normal pacing parameters programmed shall be used in the permanent brady state. <br />
* Which are these normal pacing parameters?<br>'''A.''' The ones that are currently programmed.<br />
<br />
== Section 3.6.2 Temporary Bradycardia Pacing ==<br />
The temporary brady parameters programmed shall be used in the temporary brady state. <br />
* Which are these temporary brady parameters?<br>'''A.''' An identical set of parameters to the permanent parameters, but changes in temporary parameters do not affect permanent parameters.<br><br />
The temporary state shall be capable of being used to temporarily test various system parameters or provide patient diagnostic testing.<br />
* Which parameters are tested? <br>'''A.''' Any or all parameters that the physician wishes to try temporarily.<br />
* What is the "patient diagnostic testing".<br>'''A.''' Testing impedance/amplitude/threshold.<br />
<br />
==3.6.3 Pace-Now State==<br />
<br />
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.<br />
<br />
* 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.<br />
<br />
<br />
==3.6.5 Power-On Reset (POR) State==<br />
<br />
All functions shall be disabled until the battery voltage exceeds the''' POR trip voltage.'''<br />
<br />
* What is a POR trip voltage?<br>'''A.''' The minimum battery voltage necessary to pace.<br />
<br />
<br />
==3.7 Magnet Test ==<br />
<br />
3. When the magnet is removed, the device shall automatically assume PRETEST OPERATION. <br />
<br />
* What is the “PRETEST OPERATION“? <br>'''A.''' Whatever the PG was doing immediately prior to the application of the magnet.<br />
<br />
* What is changed in the pulse generator (PG)? <br>'''A.''' Nothing.<br />
<br />
* Do you have any more details for the Magnet Test? <br>'''A.''' Putting a magnet causes a pacing rate indicating energy left (voltage) in the battery:<br />
** 100 ppm => beginning of life (new) (no batt voltage stated)<br />
** 85 ppm => elective replacement indicated (old) batt=2.654 V<br />
<br />
==4.4 Battery Status (Page 21) ==<br />
<br />
1. Monitoring voltage information shall be provided <br />
<br />
<br />
* How is this made? What kind of information shall be provided?<br>'''A.''' There is an on-board voltmeter. The information provided shall be battery voltage.<br />
<br />
<br />
2. Battery Status indicator information shall be provided. <br />
<br />
* What is this information?<br>'''A.''' How much energy is left in the battery. A typical visual representation is a “gas gauge”.<br />
<br />
<br />
==Section 4.5 Automatic threshold testing ==<br />
<br />
* How does it happen?<br>'''A.''' Loss of capture is observed by the change in shape of the ECG PQRS complex.<br />
<br />
<br />
==Section 4.6 - Bradycardia History (Page 22) ==<br />
<br />
* Which parameters are adjusted in this case? <br>'''A.''' All.<br />
<br />
<br />
==Section 4.6.1 Rate Histograms ==<br />
<br />
* I can’t understand what does mean: "Distributions shall be recorded for all ..." <br>'''A.''' A histogram<br />
<br />
<br />
* What is a paced event? And a sensed event?<br>'''A.''' A paced event is the issuing of a pacing pulse. A sensed event is the detection of an atrial or ventricular contraction.<br />
<br />
<br />
==Section 4.6.4 Sensor Trending ==<br />
<br />
The system shall provide off-line prediction analysis of sensor indicated rate with or withoutintrisic rate for the synchronized data collected. <br />
<br />
* Can you explain this to me, please?<br><br />
'''A.''' Show XL and/or pacing rate derived from it. <br />
<br />
==Section 5.2 Upper Rate Limit (URL) (page 29)== <br />
<br />
This section said URI is the min time between a ventricular event and the next ventricular pace. <br />
* Why is URI effective in modes without ventricular pacing nor sensing, such as AAT, AOO (Table 6, page 28)?<br>'''A:''' “URI” should be “URL interval” in the question. For AAT, trigger paces must not be faster than URL. AOO is constant rate pacing at LRL. So long as LRL < URL (one of many implicit parameter constraints) AOO will pace slower than URL.<br> The requirement could have been broadened to atrial-only modes. Alternatively, strict reading that URL does not apply to atrial-only modes is acceptable as well.<br />
<br />
== Section 5.3.3 Dynamic AV Delay (page 29) ==<br />
<br />
When using Dynamic AV delay, the delay should stay<br />
between a max and a min value. In section 5.3.3, it says the way the new<br />
AV delay is calculated as follows:<br />
<br />
"The previous cardiac cycle length is multiplied by a factor stored in<br />
device memory to create the dynamic AV delay."<br />
<br />
The range of values that such a factor can take is not specified in the<br />
document. And what happens if we multiply the cardiac cycle length by<br />
the factor and get a value outside the max/min range for the dynamic AV.<br />
<br />
''A.'' The factor must be calculated to stay within min-max. Hint:<br />
consider intervals at LRL and URL.<br />
<br />
== Section 5.6 Atrial Tachycardia Response (ATR) (page 31) ==<br />
<br />
In section 5.6.1 of the document, explaining the AT detection algorithm,<br />
points 1 and 2 do not clearly define the start and stop of AT.<br />
<br />
"1. AT onset shall be detected when the intervals between atrial senses are <br />
predominately, but not exclusively, faster than URL.<br> <br />
2. AT cessation shall be detected when the intervals between atrial senses <br />
are mostly, but not exclusively, faster than URL. "<br />
<br />
The only difference between start/stop is "predominately" vs. "mostly". <br />
<br />
*What is the interpretation of these statements?<br>'''A.''' Both of those def'ns for ATR were deliberately fudged to hide the actual algorithm. In essence, the algorithm allows some slow beats among the fast ones to enter ATR, to leave it's the opposite. "predominately" and "mostly" were carefully chosen. <br>The implementer gets to define the implementation, but it must be fast. 30s tracking Afib at MTR is really hard on sick patients.<br />
<br />
== Section 5.9 Rate Smoothing (page 35) ==<br />
<br />
One of the questions we had for the pacemaker was<br />
regarding<br />
the rate smoothing algorithm. We were wondering if the pacing rate was<br />
suppose to increase based on a percentage of the current pacing rate or<br />
the rate we are suppose to be pacing at (Lower rate Limit)<br />
<br />
'''A.''' The percentage is applied to the previous cardiac cycle. Although<br />
the physician may define up-rate smoothing of 3%, the period must<br />
decrease so that the rate is 1.03x faster => divide by 1.03 instead of<br />
multiply by 0.97. Rate smoothing is VERY important, trumping all other<br />
rate modifiers.<br />
<br />
= Hardware Reference Platform =<br />
<br />
==Availability and Cost==<br />
* When will the pacemaker boards be available for purchase?<br>'''A.''' There are a limited number of boards (43) available right now!<br />
* How much do pacemaker boards cost?<br>'''A.''' $350 (CDN) plus shipping. This includes programming cables compatible with the Microchip ICD2 and the PICKit2 programmer. We are selling these boards at cost. You are welcome to try to build your own but be forewarned that they use a lot of surface mount parts!<br />
<br />
==Getting Started==<br />
* What else do I need to get started?<br>'''A.''' You need the following:<br />
** A power supply, <br />
** serial cable or USB/Serial cable, <br />
** a compiler or assembler that supports the PIC18F4520 microcontroller (e.g. Microchip's [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010014 MPLAB C18] Compiler or the Small Device C Compiler ([http://sdcc.sourceforge.net/ SDCC])),<br />
** and a PIC programmer/debugger such as the Microchip ICD2 or PICKit2. <br />
** We'd also recommend an oscilloscope and signal generator or computer with and A/D card and some software such as Labview. These are helpful for debugging and generating input signals.<br />
* What are the power supply requirements?<br>'''A.''' We recommend a 12V 150+ mA power supply with a standard 2mm jack. We have also run the boards off of a 9V 200mA adapter and a standard 9V ([http://en.wikipedia.org/wiki/PP3_battery | PP3]) battery without any problems. <br />
<br />
<br />
== How do I order pacemaker boards?==<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford].</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-08-22T17:54:38Z<p>Lawford: Added RTES Forum talk and link to Fitzgerald paper in What's New.</p>
<hr />
<div>= Pacemaker Formal Methods Challenge =<br />
<br />
= What's New? =<br />
<br />
* '''Aug 20, 2008:''' Hardware Reference Platform boards are now available at a cost of $350/board + shipping. Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.<br />
* '''July 22, 2008:''' Mark Lawford presented "The Pace Maker Challenge" at the Real-time and Embedded System Forum (RTES) [http://www.opengroup.org/chicago2008/member-meetings-index.htm Member Meeting] of the [http://www.opengroup.org/chicago2008/venue.htm Open Group Conference], Chicago, IL. This presentation documents the experience from using the Pacemaker Challenge in the senior thesis course for the Undergraduate Software Engineering Students at McMaster University.<br />
* '''May 29, 2008:''' At ''[http://www.fm2008.abo.fi/ FM2008]'' the paper "Incremental Development of a Distributed Real-Time Model of a Cardiac Pacing System using VDM" by Hugo Daniel Macedo, Peter Gorm Larsen and John Fitzgerald was presented. The paper documents the authors progress on Pacemaker Challenge. The full paper is available [http://dx.doi.org/10.1007/978-3-540-68237-0_14 here].<br />
* '''Nov 23, 2007:''' Pacemaker chosen as one of the ICSE 2009 Student COntest in softwaRe Engineering (SCORE 2009) problems. See http://score.elet.polimi.it for details!<br />
<br />
= Introduction =<br />
The Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
Detailed questions about the requirements, hardware or pacemakers in general can be found in the [[Pacemaker FAQ]].<br />
<br />
= Pacemaker Hardware Reference Platform =<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. We have now produced an additional 45 board for sale at cost (approx. $350 CDN + shipping) to interested students, researchers and industry people. The boards come with cables to connect directly to a Microchip ICD2 or PICKit2 programmer. You will need to supply your own 12V DC/150+mA Power supply and serial cable.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-08-20T20:52:23Z<p>Lawford: /* Pacemaker Formal Methods Challenge */</p>
<hr />
<div>= Pacemaker Formal Methods Challenge =<br />
<br />
= What's New? =<br />
<br />
* '''Aug 20, 2008:''' Hardware Reference Platform boards are now available at a cost of $350/board + shipping. Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.<br />
* '''Nov 23, 2007:''' Pacemaker chosen as one of the ICSE 2009 Student COntest in softwaRe Engineering (SCORE 2009) problems. See http://score.elet.polimi.it for details!<br />
<br />
= Introduction =<br />
The Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
Detailed questions about the requirements, hardware or pacemakers in general can be found in the [[Pacemaker FAQ]].<br />
<br />
= Pacemaker Hardware Reference Platform =<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. We have now produced an additional 45 board for sale at cost (approx. $350 CDN + shipping) to interested students, researchers and industry people. The boards come with cables to connect directly to a Microchip ICD2 or PICKit2 programmer. You will need to supply your own 12V DC/150+mA Power supply and serial cable.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford] to request boards.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_FAQPacemaker FAQ2008-08-20T20:52:12Z<p>Lawford: Added more details on hardware platform including now available!</p>
<hr />
<div>= Introduction =<br />
<br />
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 ''Cardiac Pacemakers Step by Step, An Illustrated Guide''.<br />
<br />
<br />
<br />
= Requirements =<br />
<br />
The basis of the system requirements are the following Design Input Documents (DID):<br />
<br />
# 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.<br />
# 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<br />
# The [[Pacemaker Hardware Reference Platform Details]] - including the general overview document of the hardware reference platform, the circuit schematic and Bill of Materials (BOM). <br />
<br />
<br />
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.<br />
<br />
== Section 2.5.2 Implant Phase ==<br />
7. Testing the system sensing and pacing efficacy.<br />
* What kind of test is made? <br />
* Which of these parameters are evaluated?<br>'''A:''' See #6 in the section above 2.5.2<br />
<br />
== Section 2.5.3 Predischarge Follow-up (Page 12) ==<br />
2. Reprogramming to final pre-discharge value<br />
* Is there any special values for parameters?<br>'''A.''' No. This just means that the doctor can change parameters after implant, but before the patient leaves the hospital.<br />
<br />
== Section 3.6.1 Permanent State (Page 17) ==<br />
The normal pacing parameters programmed shall be used in the permanent brady state. <br />
* Which are these normal pacing parameters?<br>'''A.''' The ones that are currently programmed.<br />
<br />
== Section 3.6.2 Temporary Bradycardia Pacing ==<br />
The temporary brady parameters programmed shall be used in the temporary brady state. <br />
* Which are these temporary brady parameters?<br>'''A.''' An identical set of parameters to the permanent parameters, but changes in temporary parameters do not affect permanent parameters.<br><br />
The temporary state shall be capable of being used to temporarily test various system parameters or provide patient diagnostic testing.<br />
* Which parameters are tested? <br>'''A.''' Any or all parameters that the physician wishes to try temporarily.<br />
* What is the "patient diagnostic testing".<br>'''A.''' Testing impedance/amplitude/threshold.<br />
<br />
==3.6.3 Pace-Now State==<br />
<br />
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.<br />
<br />
* 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.<br />
<br />
<br />
==3.6.5 Power-On Reset (POR) State==<br />
<br />
All functions shall be disabled until the battery voltage exceeds the''' POR trip voltage.'''<br />
<br />
* What is a POR trip voltage?<br>'''A.''' The minimum battery voltage necessary to pace.<br />
<br />
<br />
==3.7 Magnet Test ==<br />
<br />
3. When the magnet is removed, the device shall automatically assume PRETEST OPERATION. <br />
<br />
* What is the “PRETEST OPERATION“? <br>'''A.''' Whatever the PG was doing immediately prior to the application of the magnet.<br />
<br />
* What is changed in the pulse generator (PG)? <br>'''A.''' Nothing.<br />
<br />
* Do you have any more details for the Magnet Test? <br>'''A.''' Putting a magnet causes a pacing rate indicating energy left (voltage) in the battery:<br />
** 100 ppm => beginning of life (new) (no batt voltage stated)<br />
** 85 ppm => elective replacement indicated (old) batt=2.654 V<br />
<br />
==4.4 Battery Status (Page 21) ==<br />
<br />
1. Monitoring voltage information shall be provided <br />
<br />
<br />
* How is this made? What kind of information shall be provided?<br>'''A.''' There is an on-board voltmeter. The information provided shall be battery voltage.<br />
<br />
<br />
2. Battery Status indicator information shall be provided. <br />
<br />
* What is this information?<br>'''A.''' How much energy is left in the battery. A typical visual representation is a “gas gauge”.<br />
<br />
<br />
==Section 4.5 Automatic threshold testing ==<br />
<br />
* How does it happen?<br>'''A.''' Loss of capture is observed by the change in shape of the ECG PQRS complex.<br />
<br />
<br />
==Section 4.6 - Bradycardia History (Page 22) ==<br />
<br />
* Which parameters are adjusted in this case? <br>'''A.''' All.<br />
<br />
<br />
==Section 4.6.1 Rate Histograms ==<br />
<br />
* I can’t understand what does mean: "Distributions shall be recorded for all ..." <br>'''A.''' A histogram<br />
<br />
<br />
* What is a paced event? And a sensed event?<br>'''A.''' A paced event is the issuing of a pacing pulse. A sensed event is the detection of an atrial or ventricular contraction.<br />
<br />
<br />
==Section 4.6.4 Sensor Trending ==<br />
<br />
The system shall provide off-line prediction analysis of sensor indicated rate with or withoutintrisic rate for the synchronized data collected. <br />
<br />
* Can you explain this to me, please?<br><br />
'''A.''' Show XL and/or pacing rate derived from it. <br />
<br />
==Section 5.2 Upper Rate Limit (URL) (page 29)== <br />
<br />
This section said URI is the min time between a ventricular event and the next ventricular pace. <br />
* Why is URI effective in modes without ventricular pacing nor sensing, such as AAT, AOO (Table 6, page 28)?<br>'''A:''' “URI” should be “URL interval” in the question. For AAT, trigger paces must not be faster than URL. AOO is constant rate pacing at LRL. So long as LRL < URL (one of many implicit parameter constraints) AOO will pace slower than URL.<br> The requirement could have been broadened to atrial-only modes. Alternatively, strict reading that URL does not apply to atrial-only modes is acceptable as well.<br />
<br />
== Section 5.3.3 Dynamic AV Delay (page 29) ==<br />
<br />
When using Dynamic AV delay, the delay should stay<br />
between a max and a min value. In section 5.3.3, it says the way the new<br />
AV delay is calculated as follows:<br />
<br />
"The previous cardiac cycle length is multiplied by a factor stored in<br />
device memory to create the dynamic AV delay."<br />
<br />
The range of values that such a factor can take is not specified in the<br />
document. And what happens if we multiply the cardiac cycle length by<br />
the factor and get a value outside the max/min range for the dynamic AV.<br />
<br />
''A.'' The factor must be calculated to stay within min-max. Hint:<br />
consider intervals at LRL and URL.<br />
<br />
== Section 5.6 Atrial Tachycardia Response (ATR) (page 31) ==<br />
<br />
In section 5.6.1 of the document, explaining the AT detection algorithm,<br />
points 1 and 2 do not clearly define the start and stop of AT.<br />
<br />
"1. AT onset shall be detected when the intervals between atrial senses are <br />
predominately, but not exclusively, faster than URL.<br> <br />
2. AT cessation shall be detected when the intervals between atrial senses <br />
are mostly, but not exclusively, faster than URL. "<br />
<br />
The only difference between start/stop is "predominately" vs. "mostly". <br />
<br />
*What is the interpretation of these statements?<br>'''A.''' Both of those def'ns for ATR were deliberately fudged to hide the actual algorithm. In essence, the algorithm allows some slow beats among the fast ones to enter ATR, to leave it's the opposite. "predominately" and "mostly" were carefully chosen. <br>The implementer gets to define the implementation, but it must be fast. 30s tracking Afib at MTR is really hard on sick patients.<br />
<br />
== Section 5.9 Rate Smoothing (page 35) ==<br />
<br />
One of the questions we had for the pacemaker was<br />
regarding<br />
the rate smoothing algorithm. We were wondering if the pacing rate was<br />
suppose to increase based on a percentage of the current pacing rate or<br />
the rate we are suppose to be pacing at (Lower rate Limit)<br />
<br />
'''A.''' The percentage is applied to the previous cardiac cycle. Although<br />
the physician may define up-rate smoothing of 3%, the period must<br />
decrease so that the rate is 1.03x faster => divide by 1.03 instead of<br />
multiply by 0.97. Rate smoothing is VERY important, trumping all other<br />
rate modifiers.<br />
<br />
= Hardware Reference Platform =<br />
<br />
==Availability and Cost==<br />
* When will the pacemaker boards be available for purchase?<br>'''A.''' There are a limited number of boards (43) available right now!<br />
* How much do pacemaker boards cost?<br>'''A.''' $350 (CDN) plus shipping. This includes programming cables compatible with the Microchip ICD2 and the PICKit2 programmer. We are selling these boards at cost. You are welcome to try to build your own but be forewarned that they use a lot of surface mount parts!<br />
<br />
==Getting Started==<br />
* What else do I need to get started?<br>'''A.''' You need the following:<br />
** A power supply, <br />
** serial cable or USB/Serial cable, <br />
** a compiler or assembler that supports the PIC18F4520 microcontroller (e.g. Microchip's [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010014 MPLAB C18] Compiler or the Small Device C Compiler ([http://sdcc.sourceforge.net/ SDCC])),<br />
** and a PIC programmer/debugger such as the Microchip ICD2 or PICKit2. <br />
** We'd also recommend an oscilloscope and signal generator or computer with and A/D card and some software such as Labview. These are helpful for debugging and generating input signals.<br />
* What are the power supply requirements?<br>'''A.''' We recommend a 12V 150+ mA power supply with a standard 2mm jack. We have also run the boards off of a 9V 200mA adapter and a standard 9V ([http://en.wikipedia.org/wiki/PP3_battery | PP3]) battery without any problems. <br />
<br />
<br />
== How do I order pacemaker boards?==<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford].</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-06-11T18:19:38Z<p>Lawford: </p>
<hr />
<div>= Pacemaker Formal Methods Challenge =<br />
<br />
== Introduction ==<br />
The Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
Detailed questions about the requirements, hardware or pacemakers in general can be found in the [[Pacemaker FAQ]].<br />
<br />
== Pacemaker Hardware Reference Platform ==<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. Once we have finished debugging the revised design we will be producing an additional 45 board for sale at cost (approx. $350 CDN) to interested students, researchers and industry people.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Software_Certification_ConsortiumSoftware Certification Consortium2008-06-11T18:18:22Z<p>Lawford: </p>
<hr />
<div>= The Software Certification Consortium (SCC) =<br />
<br />
== Objectives of SCC ==<br />
<br />
# To promote the scientific understanding of software certification and the standards on which it is based;<br />
# To promote the effective deployment of software certification standards;<br />
# To promote public, government and industrial understanding of the concept of software certification and the acceptance of the need for certification standards for software related products;<br />
# To co-ordinate software certification initiatives and activities to further objectives 1-3 above.<br />
<br />
<br />
== Definition of Certification ==<br />
<br />
;Definition <br />
<br />
: ''Certification'' is the process of systematically determining, based on the principles of science, engineering and measurement theory, whether an artifact satisfies accepted, well defined and measurable criteria.<br />
<br />
== The Goal of Software Certification ==<br />
<br />
The goal of certification is to systematically determine, based<br />
on the principles of science, engineering and measurement<br />
theory, whether an artefact satisfies accepted, well defined<br />
and measurable criteria.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_FAQPacemaker FAQ2008-05-21T18:35:48Z<p>Lawford: </p>
<hr />
<div>= Introduction =<br />
<br />
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 ''Cardiac Pacemakers Step by Step, An Illustrated Guide''.<br />
<br />
<br />
<br />
= Requirements =<br />
<br />
The basis of the system requirements are the following Design Input Documents (DID):<br />
<br />
# 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.<br />
# 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<br />
# The [[Pacemaker Hardware Reference Platform Details]] - including the general overview document of the hardware reference platform, the circuit schematic and Bill of Materials (BOM). <br />
<br />
<br />
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.<br />
<br />
== Section 2.5.2 Implant Phase ==<br />
7. Testing the system sensing and pacing efficacy.<br />
* What kind of test is made? <br />
* Which of these parameters are evaluated?<br>'''A:''' See #6 in the section above 2.5.2<br />
<br />
== Section 2.5.3 Predischarge Follow-up (Page 12) ==<br />
2. Reprogramming to final pre-discharge value<br />
* Is there any special values for parameters?<br>'''A.''' No. This just means that the doctor can change parameters after implant, but before the patient leaves the hospital.<br />
<br />
== Section 3.6.1 Permanent State (Page 17) ==<br />
The normal pacing parameters programmed shall be used in the permanent brady state. <br />
* Which are these normal pacing parameters?<br>'''A.''' The ones that are currently programmed.<br />
<br />
== Section 3.6.2 Temporary Bradycardia Pacing ==<br />
The temporary brady parameters programmed shall be used in the temporary brady state. <br />
* Which are these temporary brady parameters?<br>'''A.''' An identical set of parameters to the permanent parameters, but changes in temporary parameters do not affect permanent parameters.<br><br />
The temporary state shall be capable of being used to temporarily test various system parameters or provide patient diagnostic testing.<br />
* Which parameters are tested? <br>'''A.''' Any or all parameters that the physician wishes to try temporarily.<br />
* What is the "patient diagnostic testing".<br>'''A.''' Testing impedance/amplitude/threshold.<br />
<br />
==3.6.3 Pace-Now State==<br />
<br />
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.<br />
<br />
* 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.<br />
<br />
<br />
==3.6.5 Power-On Reset (POR) State==<br />
<br />
All functions shall be disabled until the battery voltage exceeds the''' POR trip voltage.'''<br />
<br />
* What is a POR trip voltage?<br>'''A.''' The minimum battery voltage necessary to pace.<br />
<br />
<br />
==3.7 Magnet Test ==<br />
<br />
3. When the magnet is removed, the device shall automatically assume PRETEST OPERATION. <br />
<br />
* What is the “PRETEST OPERATION“? <br>'''A.''' Whatever the PG was doing immediately prior to the application of the magnet.<br />
<br />
<br />
* What is changed in the pulse generator (PG)? <br>'''A.''' Nothing.<br />
<br />
<br />
==4.4 Battery Status (Page 21) ==<br />
<br />
1. Monitoring voltage information shall be provided <br />
<br />
<br />
* How is this made? What kind of information shall be provided?<br>'''A.''' There is an on-board voltmeter. The information provided shall be battery voltage.<br />
<br />
<br />
2. Battery Status indicator information shall be provided. <br />
<br />
* What is this information?<br>'''A.''' How much energy is left in the battery. A typical visual representation is a “gas gauge”.<br />
<br />
<br />
==Section 4.5 Automatic threshold testing ==<br />
<br />
* How does it happen?<br>'''A.''' Loss of capture is observed by the change in shape of the ECG PQRS complex.<br />
<br />
<br />
==Section 4.6 - Bradycardia History (Page 22) ==<br />
<br />
* Which parameters are adjusted in this case? <br>'''A.''' All.<br />
<br />
<br />
==Section 4.6.1 Rate Histograms ==<br />
<br />
* I can’t understand what does mean: "Distributions shall be recorded for all ..." <br>'''A.''' A histogram<br />
<br />
<br />
* What is a paced event? And a sensed event?<br>'''A.''' A paced event is the issuing of a pacing pulse. A sensed event is the detection of an atrial or ventricular contraction.<br />
<br />
<br />
==Section 4.6.4 Sensor Trending ==<br />
<br />
The system shall provide off-line prediction analysis of sensor indicated rate with or withoutintrisic rate for the synchronized data collected. <br />
<br />
* Can you explain this to me, please?<br><br />
'''A.''' Show XL and/or pacing rate derived from it. <br />
<br />
==Section 5.2 Upper Rate Limit (URL) (page 29)== <br />
<br />
This section said URI is the min time between a ventricular event and the next ventricular pace. <br />
* Why is URI effective in modes without ventricular pacing nor sensing, such as AAT, AOO (Table 6, page 28)?<br>'''A:''' “URI” should be “URL interval” in the question. For AAT, trigger paces must not be faster than URL. AOO is constant rate pacing at LRL. So long as LRL < URL (one of many implicit parameter constraints) AOO will pace slower than URL.<br> The requirement could have been broadened to atrial-only modes. Alternatively, strict reading that URL does not apply to atrial-only modes is acceptable as well.<br />
<br />
== Section 5.3.3 Dynamic AV Delay (page 29) ==<br />
<br />
When using Dynamic AV delay, the delay should stay<br />
between a max and a min value. In section 5.3.3, it says the way the new<br />
AV delay is calculated as follows:<br />
<br />
"The previous cardiac cycle length is multiplied by a factor stored in<br />
device memory to create the dynamic AV delay."<br />
<br />
The range of values that such a factor can take is not specified in the<br />
document. And what happens if we multiply the cardiac cycle length by<br />
the factor and get a value outside the max/min range for the dynamic AV.<br />
<br />
''A.'' The factor must be calculated to stay within min-max. Hint:<br />
consider intervals at LRL and URL.<br />
<br />
== Section 5.6 Atrial Tachycardia Response (ATR) (page 31) ==<br />
<br />
In section 5.6.1 of the document, explaining the AT detection algorithm,<br />
points 1 and 2 do not clearly define the start and stop of AT.<br />
<br />
"1. AT onset shall be detected when the intervals between atrial senses are <br />
predominately, but not exclusively, faster than URL.<br> <br />
2. AT cessation shall be detected when the intervals between atrial senses <br />
are mostly, but not exclusively, faster than URL. "<br />
<br />
The only difference between start/stop is "predominately" vs. "mostly". <br />
<br />
*What is the interpretation of these statements?<br>'''A.''' Both of those def'ns for ATR were deliberately fudged to hide the actual algorithm. In essence, the algorithm allows some slow beats among the fast ones to enter ATR, to leave it's the opposite. "predominately" and "mostly" were carefully chosen. <br>The implementer gets to define the implementation, but it must be fast. 30s tracking Afib at MTR is really hard on sick patients.<br />
<br />
== Section 5.9 Rate Smoothing (page 35) ==<br />
<br />
One of the questions we had for the pacemaker was<br />
regarding<br />
the rate smoothing algorithm. We were wondering if the pacing rate was<br />
suppose to increase based on a percentage of the current pacing rate or<br />
the rate we are suppose to be pacing at (Lower rate Limit)<br />
<br />
'''A.''' The percentage is applied to the previous cardiac cycle. Although<br />
the physician may define up-rate smoothing of 3%, the period must<br />
decrease so that the rate is 1.03x faster => divide by 1.03 instead of<br />
multiply by 0.97. Rate smoothing is VERY important, trumping all other<br />
rate modifiers.<br />
<br />
= Hardware Reference Platform =<br />
<br />
==Availability and Cost==<br />
* When will the pacemaker boards be available for purchase?<br>'''A.''' Soon!<br />
* How much will a pacemaker board cost?<br>'''A.''' Approximately $350 (CDN) plus shipping. We are selling these boards at cost. You are welcome to try to build your own but be forewarned that they use a lot of surface mount parts!<br />
<br />
== How do I order pacemaker boards?==<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford].</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_FAQPacemaker FAQ2008-05-21T14:27:17Z<p>Lawford: Added all questions and Answers from Alan and some from 4G06.</p>
<hr />
<div>= Introduction =<br />
<br />
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 ''Cardiac Pacemakers Step by Step, An Illustrated Guide''.<br />
<br />
<br />
<br />
= Requirements =<br />
<br />
The basis of the system requirements are the following Design Input Documents (DID):<br />
<br />
# 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.<br />
# 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<br />
# The [[Pacemaker Hardware Reference Platform Details]] - including the general overview document of the hardware reference platform, the circuit schematic and Bill of Materials (BOM). <br />
<br />
<br />
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.<br />
<br />
== Section 2.5.2 – Implant Phase ==<br />
7. Testing the system sensing and pacing efficacy.<br />
* What kind of test is made? <br />
* Which of these parameters are evaluated?<br>'''A:''' See #6 in the section above 2.5.2<br />
<br />
== Section 2.5.3 - Predischarge Follow-up (Page 12) ==<br />
2. Reprogramming to final pre-discharge value<br />
* Is there any special values for parameters?<br>'''A.''' No. This just means that the doctor can change parameters after implant, but before the patient leaves the hospital.<br />
<br />
== Section 3.6.1 - Permanent State (Page 17) ==<br />
The normal pacing parameters programmed shall be used in the permanent brady state. <br />
* Which are these normal pacing parameters?<br>'''A.''' The ones that are currently programmed.<br />
<br />
== Section 3.6.2 - Temporary Bradycardia Pacing ==<br />
The temporary brady parameters programmed shall be used in the temporary brady state. <br />
* Which are these temporary brady parameters?<br>'''A.''' An identical set of parameters to the permanent parameters, but changes in temporary parameters do not affect permanent parameters.<br><br />
The temporary state shall be capable of being used to temporarily test various system parameters or provide patient diagnostic testing.<br />
* Which parameters are tested? <br>'''A.''' Any or all parameters that the physician wishes to try temporarily.<br />
* What is the "patient diagnostic testing".<br>'''A.''' Testing impedance/amplitude/threshold.<br />
<br />
==3.6.3 – Pace-Now State==<br />
<br />
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.<br />
<br />
* 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.<br />
<br />
<br />
==3.6.5 – Power-On Reset (POR) State==<br />
<br />
All functions shall be disabled until the battery voltage exceeds the''' POR trip voltage.'''<br />
<br />
* What is a POR trip voltage?<br>'''A.''' The minimum battery voltage necessary to pace.<br />
<br />
<br />
==3.7 - Magnet Test ==<br />
<br />
3. When the magnet is removed, the device shall automatically assume PRETEST OPERATION. <br />
<br />
* What is the “PRETEST OPERATION“? <br>'''A.''' Whatever the PG was doing immediately prior to the application of the magnet.<br />
<br />
<br />
* What is changed in the pulse generator (PG)? <br>'''A.''' Nothing.<br />
<br />
<br />
==4.4 - Battery Status (Page 21) ==<br />
<br />
1. Monitoring voltage information shall be provided <br />
<br />
<br />
* How is this made? What kind of information shall be provided?<br>'''A.''' There is an on-board voltmeter. The information provided shall be battery voltage.<br />
<br />
<br />
2. Battery Status indicator information shall be provided. <br />
<br />
* What is this information?<br>'''A.''' How much energy is left in the battery. A typical visual representation is a “gas gauge”.<br />
<br />
<br />
==4.5 - Automatic threshold testing ==<br />
<br />
* How does it happen?<br>'''A.''' Loss of capture is observed by the change in shape of the ECG PQRS complex.<br />
<br />
<br />
==4.6 - Bradycardia History (Page 22) ==<br />
<br />
* Which parameters are adjusted in this case? <br>'''A.''' All.<br />
<br />
<br />
==4.6.1 - Rate Histograms ==<br />
<br />
* I can’t understand what does mean: "Distributions shall be recorded for all ..." <br>'''A.''' A histogram<br />
<br />
<br />
* What is a paced event? And a sensed event?<br>'''A.''' A paced event is the issuing of a pacing pulse. A sensed event is the detection of an atrial or ventricular contraction.<br />
<br />
<br />
==4.6.4 - Sensor Trending ==<br />
<br />
The system shall provide off-line prediction analysis of sensor indicated rate with or withoutintrisic rate for the synchronized data collected. <br />
<br />
* Can you explain this to me, please?<br><br />
'''A.''' Show XL and/or pacing rate derived from it. <br />
<br />
== Section 5.2 - Upper Rate Limit (URL) (page 29)== <br />
<br />
This section said URI is the min time between a ventricular event and the next ventricular pace. <br />
* Why is URI effective in modes without ventricular pacing nor sensing, such as AAT, AOO (Table 6, page 28)?<br>'''A:''' “URI” should be “URL interval” in the question. For AAT, trigger paces must not be faster than URL. AOO is constant rate pacing at LRL. So long as LRL < URL (one of many implicit parameter constraints) AOO will pace slower than URL.<br> The requirement could have been broadened to atrial-only modes. Alternatively, strict reading that URL does not apply to atrial-only modes is acceptable as well.<br />
<br />
== Section - 5.3.3 Dynamic AV Delay (page 29) ==<br />
<br />
When using Dynamic AV delay, the delay should stay<br />
between a max and a min value. In section 5.3.3, it says the way the new<br />
AV delay is calculated as follows:<br />
<br />
"The previous cardiac cycle length is multiplied by a factor stored in<br />
device memory to create the dynamic AV delay."<br />
<br />
The range of values that such a factor can take is not specified in the<br />
document. And what happens if we multiply the cardiac cycle length by<br />
the factor and get a value outside the max/min range for the dynamic AV.<br />
<br />
''A.'' The factor must be calculated to stay within min-max. Hint:<br />
consider intervals at LRL and URL.<br />
<br />
== Section - 5.6 Atrial Tachycardia Response (ATR) (page 31) ==<br />
<br />
In section 5.6.1 of the document, explaining the AT detection algorithm,<br />
points 1 and 2 do not clearly define the start and stop of AT.<br />
<br />
"1. AT onset shall be detected when the intervals between atrial senses are <br />
predominately, but not exclusively, faster than URL.<br> <br />
2. AT cessation shall be detected when the intervals between atrial senses <br />
are mostly, but not exclusively, faster than URL. "<br />
<br />
The only difference between start/stop is "predominately" vs. "mostly". <br />
<br />
*What is the interpretation of these statements?<br>'''A.''' Both of those def'ns for ATR were deliberately fudged to hide the actual algorithm. In essence, the algorithm allows some slow beats among the fast ones to enter ATR, to leave it's the opposite. "predominately" and "mostly" were carefully chosen. <br>The implementer gets to define the implementation, but it must be fast. 30s tracking Afib at MTR is really hard on sick patients.<br />
<br />
== Section 5.9 - Rate Smoothing (page 35) ==<br />
<br />
One of the questions we had for the pacemaker was<br />
regarding<br />
the rate smoothing algorithm. We were wondering if the pacing rate was<br />
suppose to increase based on a percentage of the current pacing rate or<br />
the rate we are suppose to be pacing at (Lower rate Limit)<br />
<br />
'''A.''' The percentage is applied to the previous cardiac cycle. Although<br />
the physician may define up-rate smoothing of 3%, the period must<br />
decrease so that the rate is 1.03x faster => divide by 1.03 instead of<br />
multiply by 0.97. Rate smoothing is VERY important, trumping all other<br />
rate modifiers.<br />
<br />
= Hardware Reference Platform =<br />
<br />
==Availability and Cost==<br />
* When will the pacemaker boards be available for purchase?<br>'''A.''' Soon!<br />
* How much will a pacemaker board cost?<br>'''A.''' Approximately $350 (CDN) plus shipping. We are selling these boards at cost. You are welcome to try to build your own but be forewarned that they use a lot of surface mount parts!<br />
<br />
== How do I order pacemaker boards?==<br />
<br />
Send an email to [mailto:lawford@mcmaster.ca Mark Lawford].</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_FAQPacemaker FAQ2008-05-21T02:58:35Z<p>Lawford: Format change</p>
<hr />
<div>This page contains answers to the Frequently Asked Questions about the Pacemaker.<br />
<br />
= Requirements =<br />
<br />
== Section 2.5.2 – Implant Phase ==<br />
7. Testing the system sensing and pacing efficacy.<br />
* What kind of test is made? <br />
* Which of these parameters are evaluated?<br>'''A:''' See #6 in the section above 2.5.2<br />
== Section 2.5.3 - Predischarge Follow-up (Page 12) ==<br />
2. Reprogramming to final pre-discharge value<br />
* Is there any special values for parameters?<br>'''A.''' No. This just means that the doctor can change parameters after implant, but before the patient leaves the hospital.<br />
== Section 3.6.1 - Permanent State (Page 17) ==<br />
The normal pacing parameters programmed shall be used in the permanent brady state. <br />
* Which are these normal pacing parameters?<br>'''A.''' The ones that are currently programmed.<br />
== Section 3.6.2 - Temporary Bradycardia Pacing ==<br />
The temporary brady parameters programmed shall be used in the temporary brady state. <br />
* Which are these temporary brady parameters?<br>'''A.''' An identical set of parameters to the permanent parameters, but changes in temporary parameters do not affect permanent parameters.<br><br />
<br />
The temporary state shall be capable of being used to temporarily test various system parameters or provide patient diagnostic testing.<br />
* Which parameters are tested? <br>'''A.''' Any or all parameters that the physician wishes to try temporarily.<br />
* What is the "patient diagnostic testing".<br>'''A.''' Testing impedance/amplitude/threshold.<br />
== Section 5.2 == <br />
This section said URI is the min time between a ventricular event and the next ventricular pace. Then why is URI effective in modes without ventricular pacing nor sensing, such as AAT, AOO (Table 6, page 28)?<br>'''A:''' “URI” should be “URL interval” in the question. For AAT, trigger paces must not be faster than URL. AOO is constant rate pacing at LRL. So long as LRL < URL (one of many implicit parameter constraints) AOO will pace slower than URL.<br> The requirement could have been broadened to atrial-only modes. Alternatively, strict reading that URL does not apply to atrial-only modes is acceptable as well.<br />
<br />
<br />
<br />
== Hardware Reference Platform ==<br />
* When will boards be available for purchase?<br>'''A.''' Soon!</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_FAQPacemaker FAQ2008-05-21T02:23:12Z<p>Lawford: Added more parts of the FAQ.</p>
<hr />
<div>This page contains answers to the Frequently Asked Questions about the Pacemaker.<br />
<br />
== Requirements ==<br />
<br />
# Section 2.5.2 – Implant Phase<br>7. Testing the system sensing and pacing efficacy.<br />
#* What kind of test is made? <br />
#* Which of these parameters are evaluated?<br>'''A:''' See #6 in the section above 2.5.2<br />
# Part 5.2 said URI is the min time between a ventricular event and the next ventricular pace. Then why is URI effective in modes without ventricular pacing nor sensing, such as AAT, AOO (Table 6, page 28)?<br>'''A:''' “URI” should be “URL interval” in the question. For AAT, trigger paces must not be faster than URL. AOO is constant rate pacing at LRL. So long as LRL < URL (one of many implicit parameter constraints) AOO will pace slower than URL.<br> The requirement could have been broadened to atrial-only modes. Alternatively, strict reading that URL does not apply to atrial-only modes is acceptable as well.<br />
# 2.5.3 - Predischarge Follow-up (Page 12)<br>2. Reprogramming to final pre-discharge value<br />
#* Is there any special values for parameters?<br>'''A.''' No. This just means that the doctor can change parameters after implant, but before the patient leaves the hospital.<br />
# 3.6.1 - Permanent State (Page 17)<br>The normal pacing parameters programmed shall be used in the permanent brady state. <br />
#* Which are these normal pacing parameters?<br>'''A.''' The ones that are currently programmed.<br />
# 3.6.2 - Temporary Bradycardia Pacing<br>The temporary brady parameters programmed shall be used in the temporary brady state. <br />
#* Which are these temporary brady parameters?<br>'''A.''' An identical set of parameters to the permanent parameters, but changes in temporary parameters do not affect permanent parameters.<br><br />
The temporary state shall be capable of being used to temporarily test various system parameters or provide patient diagnostic testing.<br />
#* Which parameters are tested? <br>'''A.''' Any or all parameters that the physician wishes to try temporarily.<br />
#* What is the "patient diagnostic testing".<br>'''A.''' Testing impedance/amplitude/threshold.<br />
<br />
<br />
<br />
<br />
== Hardware Reference Platform ==</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_FAQPacemaker FAQ2008-05-20T20:46:32Z<p>Lawford: Started entering FAQ contents.</p>
<hr />
<div>This page contains answers to the Frequently Asked Questions about the Pacemaker.<br />
<br />
== Requirements ==<br />
<br />
# Section 2.5.2 – Implant Phase<br>7. Testing the system sensing and pacing efficacy.<br />
#* What kind of test is made? <br />
#* Which of these parameters are evaluated?<br>'''A:''' See #6 in the section above 2.5.2<br />
# Part 5.2 said URI is the min time between a ventricular event and the next ventricular pace. Then why is URI effective in modes without ventricular pacing nor sensing, such as AAT, AOO (Table 6, page 28)?<br>'''A:''' “URI” should be “URL interval” in the question. For AAT, trigger paces must not be faster than URL. AOO is constant rate pacing at LRL. So long as LRL < URL (one of many implicit parameter constraints) AOO will pace slower than URL.<br> The requirement could have been broadened to atrial-only modes. Alternatively, strict reading that URL does not apply to atrial-only modes is acceptable as well.<br />
<br />
== Hardware Reference Platform ==</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-05-20T17:00:16Z<p>Lawford: Added link to FAQ.</p>
<hr />
<div>Information on the Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
Detailed questions about the requirements, hardware or pacemakers in general can be found in the [[Pacemaker FAQ]].<br />
<br />
=== Pacemaker Hardware Reference Platform ===<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. Once we have finished debugging the revised design we will be producing an additional 45 board for sale at cost (approx. $350 CDN) to interested students, researchers and industry people.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_Hardware_Reference_Platform_DetailsPacemaker Hardware Reference Platform Details2008-05-03T01:46:38Z<p>Lawford: /* Bill Of Materials (BOM) */</p>
<hr />
<div>= Pacemaker Hardware Reference Platform Details =<br />
<br />
== Introduction ==<br />
<br />
<br />
Here are some photos of the prototype hardware reference platform that we have produced.<br />
<br />
<br />
[[Image:PacemakerTop.png]]<br />
<br />
The side photo show the standard 2mm power jack. A 9-12V adapter providing 300mA should suffice. You can even run the board off of a 9V battery for some time<br />
.<br />
<br />
[[Image:PacemakerSide.png]]<br />
<br />
The next photo shows the BNC and binding post connectors that we have put on so allow the boards to be easily connected to a PC running Labview or some other software to simulate a heart and facilitate testing and debugging.<br />
<br />
[[Image:PacemakerIOConnectors.png]]<br />
<br />
Here is the originial design of the Pacemaker Hardware Reference Platform.<br />
<br />
<br />
== Bill Of Materials (BOM) ==<br />
<br />
We will be releasing the Bill Of Materials (BOM) and the schematics for the hardware once the design is finalized so that you can also produce your own boards if you would prefer to do that. <br />
<br />
{| border="1" cellpadding="20" cellspacing="0"<br />
|Qty<br />
|Reference<br />
|Description<br />
|MFR PART NUMBER<br />
|MFR<br />
|DIGI-KEY PART # <br />
|COST <1000 <br />
|Total Cost $<br />
|-<br />
|4<br />
|C1-2 C67 C68<br />
|CAP 10UF 25V ELECT PW RADIAL<br />
|UVX1H100M<br />
|NICHICON AMERICA<br />
|UPW1E100MDH-ND<br />
| $0.07 <br />
| $0.26 <br />
|-<br />
|13<br />
|C14-15 C33 C45 C50 C9 C58-63 C84<br />
|CAP 1.5UF 10V CERAMIC X7R 1206<br />
|ECJ-3YB1A155K<br />
|Panasonic - ECG<br />
|PCC1867CT-ND<br />
| $0.29 <br />
| $3.72<br />
|-<br />
|2<br />
|C21-22<br />
|"CAP, CERAM-CHIP, 22PF, 50V, COG, 1206"<br />
|CC1206JRNP09BN220<br />
|Yageo Corporation<br />
|311-1154-1-ND<br />
| $0.10 <br />
| $0.19 <br />
|-<br />
|4<br />
|C3 C5 C28 C30<br />
|"CAP, ALUM, 6.8 uF, 20%, 25V, 85C, RAD"<br />
|ECE-A1EKG6R8<br />
|NIC COMPONENTS CORP<br />
|P915-ND<br />
| $0.19 <br />
| $0.76 <br />
|-<br />
|18<br />
|C32 C35 C11 C26 C37-38 C55 C70 C71 C78 C80 C82 C87 C93 C99 C101 C106 C113<br />
|"CAP, CERAM-CHIP, .01uF HI DIALECTRIC"<br />
|CC1206KRX7R9BB103<br />
|Yageo Corporation<br />
|311-1174-1-ND<br />
| $0.08 <br />
| $1.51 <br />
|-<br />
|4<br />
|C39 C66 C72 C73<br />
|"CAP, ALUM, 1 uF, 20%, 50V, 85C, RAD"<br />
|EKMG500ELL1R0ME11D<br />
|United Chemi-Con<br />
|565-1332-ND<br />
| $0.27 <br />
| $1.08 <br />
|-<br />
|37<br />
|C4 C6 C12 C13 C16-20 C23 C24 C27 C29 C34 C36 C49 C54 C56 C74-77 C83 C88 C91 C92 C96 C97 C100 C105 C110 C111 C114 C116-119<br />
|"CAP, CERAM-CHIP, .1 uF, 50V, X7R, 1206"<br />
|C1206C104K5RACTU<br />
|Kemet<br />
|399-1249-1-ND<br />
| $0.07 <br />
| $2.66 <br />
|-<br />
|9<br />
|C40-43 C94 C107-109 C51<br />
|CAP 1.0UF 25V CERAMIC X7R 1206<br />
|C1206C105K3RACTU<br />
|Kemet<br />
|399-1255-1-ND<br />
| $0.19 <br />
| $1.69 <br />
|-<br />
|1<br />
|C52<br />
|"CAP, CERAM-CHIP, .22 uF, 25V, X7R, 1206"<br />
|GRM319F51E224ZA01D<br />
|MURATA ELECTRONICS<br />
|490-1829-1-ND<br />
| $0.21 <br />
| $0.21 <br />
|-<br />
|1<br />
|C53<br />
|CAP CER 2.2UF 16V 10% X7R 1206<br />
|GRM31MR71C225KA35L<br />
|MURATA ELECTRONICS<br />
|490-1799-1-ND<br />
| $0.43 <br />
| $0.43 <br />
|-<br />
|1<br />
|C64<br />
|CAP CERM .68UF 10% 25V X7R 1206<br />
|12063C684KAT2A<br />
|AVX Corporation<br />
|478-1565-1-ND<br />
| $0.11 <br />
| $0.11 <br />
|-<br />
|1<br />
|C65<br />
|CAP .15UF 16V CERAMIC X7R 1206<br />
|ECJ-3VB1C154K<br />
|Panasonic - ECG<br />
|PCC1872CT-ND<br />
| $0.19 <br />
| $0.19 <br />
|-<br />
|14<br />
|C7 C10 C25 C31 C44 C46-48 C69 C79 C81 C86 C90 C98<br />
|"CAP, CERAM-CHIP, .001 uF,5%,50V,COG 1206"<br />
|CC1206KRX7R9BB102<br />
|Yageo Corporation<br />
|311-1170-1-ND<br />
| $0.08 <br />
| $1.18 <br />
|-<br />
|2<br />
|C8 C57<br />
|CAP CER 4.7UF 10V X5R 1206<br />
|LMK316BJ475KD-T<br />
|Taiyo Yuden<br />
|587-1340-1-ND<br />
| $0.34 <br />
| $0.68 <br />
|-<br />
|1<br />
|C85<br />
|CAP CER 68000PF 100V X7R 1206<br />
|GRM31MR72A683KA01L<br />
|MURATA ELECTRONICS<br />
|490-3363-1-ND<br />
| $0.22 <br />
| $0.22 <br />
|-<br />
|2<br />
|C89 C95<br />
|CAP CER 10UF 10V X5R 1206<br />
|LMK316BJ106KL-T<br />
|Taiyo Yuden<br />
|587-1342-1-ND<br />
| $0.39 <br />
| $0.77 <br />
|-<br />
|4<br />
|D1-4<br />
|"DIODE, SCHOTTKY, L1, SOT-523"<br />
|BAT54T-7<br />
|DIODES INC (VISHAY)<br />
|BAT54TDITR-ND<br />
| $0.15 <br />
| $0.60 <br />
|-<br />
|1<br />
|J1<br />
|"CONNECTOR, D-SUBMIN. 9 SOCKETS FEMALE"<br />
|617-C0095-BF220<br />
|AMPHENOL BENDIX CONNECTOR OP<br />
|<br />
| $3.24 <br />
| $3.24 <br />
|-<br />
|1<br />
|J10<br />
|"CONNECTOR, HEADER, MALE, 5 POS, .098 CTR"<br />
|B 5B-XH-A<br />
|J.S.T. CORPORATION<br />
|<br />
| $0.18 <br />
| $0.18 <br />
|-<br />
|1<br />
|J8<br />
|2mm DC Power<br />
|PJ-014C-SMT<br />
|CUI<br />
|CP-014CPJTR-ND<br />
| $0.42 <br />
| $0.42 <br />
|-<br />
|2<br />
|R11 R16<br />
|RES 52.3K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF6491<br />
|Rohm<br />
|RHM52.3KFCT-ND<br />
| $0.05 <br />
| $0.09 <br />
|-<br />
|2<br />
|R1-2<br />
|"RES, CHIP, 1.0M, 5%, 1/8W, 1206"<br />
|CRCW12061M00FKEA<br />
|Vishay/Dale<br />
|541-1.00MFCT-ND<br />
| $0.05 <br />
| $0.10 <br />
|-<br />
|6<br />
|R12 R15 R17 R50 R68 R69<br />
|RES 6.49K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF6491<br />
|Rohm<br />
|RHM6.49KFCT-ND<br />
| $0.05 <br />
| $0.28 <br />
|-<br />
|4<br />
|R18-21<br />
|RES 15.8K OHM 1/4W 1% 1206 SMD<br />
|CRCW120615K8FKEA<br />
|Vishay/Dale<br />
|541-15.8KFCT-ND<br />
| $0.05 <br />
| $0.19 <br />
|-<br />
|4<br />
|R22-23 R32 R33<br />
|"RES, CHIP, 1K, 5%, 1/8W, 1206"<br />
|CRCW12061K00JNEA<br />
|Vishay/Dale<br />
|541-1.0KECT-ND<br />
| $0.04 <br />
| $0.16 <br />
|-<br />
|8<br />
|R24-27 R30 R31 R66 R67<br />
|"RES, CHIP, 249K 1%, 1206"<br />
|RC1206FR-07249KL<br />
|Yageo Corporation<br />
|311-249KFRCT-ND<br />
| $0.09 <br />
| $0.70 <br />
|-<br />
|5<br />
|R28 R64 R65 R71 R72<br />
|"RES, CHIP, 0 OHM, 5%, 1/8w, 1206"<br />
|RC1206JR-070RL<br />
|Yageo Corporation<br />
|311-0.0ERCT-ND<br />
| $0.08 <br />
| $0.39 <br />
|-<br />
|1<br />
|R34<br />
|"RES, CHIP, 620Kohm, 5%, 1/8 WATT, 1206"<br />
|9C12063A6203JLHFT<br />
|Yageo Corporation<br />
|311-620KECT-ND<br />
| $0.08 <br />
| $0.08 <br />
|-<br />
|1<br />
|R35<br />
|"RES, CHIP, 100, 5%, 1/8W, 1206"<br />
|MCR18EZHJ101<br />
|Rohm<br />
|RHM100ECT-ND<br />
| $0.09 <br />
| $0.09 <br />
|-<br />
|1<br />
|R36<br />
|RES 14.0K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF1402<br />
|Rohm<br />
|RHM14.0KFCT-ND<br />
| $0.05 <br />
| $0.05 <br />
|-<br />
|4<br />
|R3-6<br />
|"RES, CHIP, 240 OHM, 5% 1/8W, 1206"<br />
|MCR18EZPJ241<br />
|Rohm<br />
|RHM240ERCT-ND<br />
| $0.05 <br />
| $0.20 <br />
|-<br />
|8<br />
|R37 R38 R42-44 R57-59<br />
|RES 4.99K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF4991<br />
|Rohm<br />
|RHM4.99KFRCT-ND<br />
| $0.05 <br />
| $0.37 <br />
|-<br />
|1<br />
|R40<br />
|"RES, CHIP, 12 KOHM, 1/8W, 5%, 1206"<br />
|MCR18EZHJ123<br />
|Rohm<br />
|RHM12KECT-ND<br />
| $0.09 <br />
| $0.09 <br />
|-<br />
|2<br />
|R41 R39<br />
|RES 5.90K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF5901<br />
|Rohm<br />
|RHM5.90KFCT-ND<br />
| $0.05 <br />
| $0.09 <br />
|-=<br />
|2<br />
|R47 R62<br />
|"RES, CHIP, 47K, 5%, 1/8W, 1206"<br />
|MCR18EZPJ473<br />
|Rohm<br />
|RHM47KERCT-ND<br />
| $0.04 <br />
| $0.08 <br />
|-<br />
|2<br />
|R48 R13<br />
|RES 17.4K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF1742<br />
|Rohm<br />
|RHM17.4KFCT-ND<br />
| $0.05 <br />
| $0.09 <br />
|-<br />
|2<br />
|R49 R14<br />
|RES 41.2K OHM 1/4W 1% 1206 SMD<br />
|9C12063A4122FKHFT<br />
|Yageo Corporation<br />
|311-41.2KFCT-ND<br />
| $0.09 <br />
| $0.18 <br />
|-<br />
|1<br />
|R51<br />
|RES 11.8K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF1182<br />
|Rohm<br />
|RHM11.8KFCT-ND<br />
| $0.05 <br />
| $0.05 <br />
|-<br />
|2<br />
|R53 R52<br />
|RES 4.32K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF4321<br />
|Rohm<br />
|RHM4.32KFCT-ND<br />
| $0.05 <br />
| $0.09 <br />
|-<br />
|2<br />
|R54 R56<br />
|RES 4.87K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF4871<br />
|Rohm<br />
|RHM4.87KFCT-ND<br />
| $0.05 <br />
| $0.09 <br />
|-<br />
|1<br />
|R55<br />
|RES 10.5K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF1052<br />
|Rohm<br />
|RHM10.5KFCT-ND<br />
| $0.05 <br />
| $0.05 <br />
|-<br />
|2<br />
|R61 R46<br />
|RES 60.4K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF6042<br />
|Rohm<br />
|RHM60.4KFCT-ND<br />
| $0.05 <br />
| $0.09 <br />
|-<br />
|5<br />
|R7 R29 R70 R45 R60<br />
|"RES, CHIP, 10K OHM, 5%, 1/8 W, 1206"<br />
|CRCW120610K0JNEA<br />
|Vishay/Dale<br />
|541-10KECT-ND<br />
| $0.04 <br />
| $0.20 <br />
|-<br />
|2<br />
|R8 R10<br />
|RES 3.16K OHM 1/4W 1% 1206 SMD<br />
|MCR18EZHF3161<br />
|Rohm<br />
|RHM3.16KFCT-ND<br />
| $0.05 <br />
| $0.09 <br />
|-<br />
|2<br />
|R9 R63<br />
|"RES, CHIP, 20K OHM, 5%, 1/8 W, 1206"<br />
|CRCW120620K0JNEA<br />
|Vishay/Dale<br />
|541-20KECT-ND<br />
| $0.04 <br />
| $0.08 <br />
|-<br />
|1<br />
|S1<br />
|"SWITCH, REED, AXIAL LEAD"<br />
|ORD9215<br />
|"HASCO COMPONENTS,INC"<br />
|<br />
| $0.15 <br />
| $0.15 <br />
|-<br />
|2<br />
|U1 U26<br />
|"VOLTAGE REG, 5V, 500mA, 78M05 SMT TO-252"<br />
|MC78MO5CDTRK<br />
|MOTOROLA SEMICONDUCTOR<br />
|<br />
| $0.36 <br />
| $0.72 <br />
|-<br />
|2<br />
|U13 U16<br />
|IC SW DUAL DPDT 1.8-5.5V 16TSSOP<br />
|ADG888YRUZ<br />
|ANALOG DEVICES<br />
|ADG888YRUZ-ND<br />
| $1.86 <br />
| $3.72 <br />
|-<br />
|2<br />
|U14 U17<br />
|IC AMP INSTRUMENTATION LP 8-SOIC<br />
|AD620AR<br />
|ANALOG DEVICES<br />
|AD620AR-ND<br />
| $4.14 <br />
| $8.27 <br />
|-<br />
|2<br />
|U19 U36<br />
|IC REF VOLT HI PSRR 1.2V SOT-23<br />
|ADR280ART-R2<br />
|ANALOG DEVICES<br />
|ADR280ART-R2TR-ND<br />
| $0.77 <br />
| $1.54 <br />
|-<br />
|2<br />
|U20 U37<br />
|IC OPAMP SNGL R-R I/O SOT23-5<br />
|AD8601ART-R2<br />
|ANALOG DEVICES<br />
|AD8601ART-R2-ND<br />
| $0.94 <br />
| $1.88 <br />
|-<br />
|3<br />
|U22 U27 U28<br />
|2.5V REF<br />
|MAX6102<br />
|MAXIM SEMI<br />
|MAX6102EUR+T-ND<br />
| $0.42 <br />
| $1.26 <br />
|-<br />
|2<br />
|U2-3<br />
|"VOLTAGE REG, LM317LZM TO-92 T/R VOLT REG"<br />
|LM317LZ<br />
|ON SEMICONDUCTOR<br />
|LM317LZOS-ND<br />
| $0.15 <br />
| $0.31 <br />
|-<br />
|2<br />
|U23 U30<br />
|IC ADC 16BIT PSEUDO-DIFF 10MSOP<br />
|AD7685ARMZRL7<br />
|ANALOG DEVICES<br />
|AD7685ARMZRL7-ND<br />
| $7.63 <br />
| $15.26 <br />
|-<br />
|2<br />
|U31-32<br />
|IC OPAMP SGL R-R PREC 5TSOT<br />
|AD8615AUJZ-R2<br />
|ANALOG DEVICES<br />
|AD8615AUJZ-R2-ND<br />
| $1.37 <br />
| $2.74 <br />
|-<br />
|1<br />
|U33<br />
|ADXL202E<br />
|ADXL202EB-232<br />
|ANALOG DEVICES<br />
|ADXL202EB-232-ND<br />
|<br />
| $- <br />
|-<br />
|2<br />
|U11 U35<br />
|IC DGTL POT DUAL 50K I2C 10-MSOP<br />
|AD5248BRM50<br />
|ANALOG DEVICES<br />
|AD5248BRM50-ND<br />
| $2.38 <br />
| $4.76 <br />
|-<br />
|1<br />
|u4<br />
|IC DGTL POT DUAL 2.5K I2C 10MSOP<br />
|AD5248BRMZ2.5<br />
|ANALOG DEVICES<br />
|AD5248BRM2.5-ND<br />
| $2.38 <br />
| $2.38 <br />
|-<br />
|2<br />
|U5 U15<br />
|MAX4662<br />
|MAX4662CAE<br />
|MAXIM SEMI<br />
|<br />
| $0.50 <br />
| $1.00 <br />
|-<br />
|5<br />
|U6-7 U10 U12 U24<br />
|IC OP AMP QUAD LOW V R-R 14-SOIC<br />
|LMV324M/NOPB<br />
|National Semiconductor<br />
|LMV324M-ND<br />
| $0.96 <br />
| $4.80 <br />
|-<br />
|1<br />
|U8<br />
|PIC18F452-I/P<br />
|PIC18F452-I/P<br />
|MICROCHIP<br />
|PIC18F452-I/P-ND<br />
| $6.82 <br />
| $6.82 <br />
|-<br />
|1<br />
|U9<br />
|MAX232<br />
|MAX232ACSE<br />
|MAXIM SEMI<br />
|MAX232ACSE+-ND<br />
| $0.90 <br />
| $0.90 <br />
|-<br />
|1<br />
|XTAL1<br />
|4.0MHZ<br />
|<br />
|PDI CRYSTALS<br />
|<br />
| $0.21 <br />
| $0.21 <br />
|}<br />
<br />
== Scematic ==<br />
<br />
=== Page 1 ===<br />
<br />
[[Image:Pacemaker_Rev10a_schematic_Page_1.png]]<br />
<br />
=== Page 2 ===<br />
<br />
[[Image:Pacemaker_Rev10a_schematic_Page_2.png]]<br />
<br />
=== Page 3 ===<br />
<br />
[[Image:Pacemaker_Rev10a_schematic_Page_3.png]]</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_Hardware_Reference_Platform_DetailsPacemaker Hardware Reference Platform Details2008-05-02T20:53:42Z<p>Lawford: Started adding BOM</p>
<hr />
<div>= Pacemaker Hardware Reference Platform Details =<br />
<br />
== Introduction ==<br />
<br />
<br />
Here are some photos of the prototype hardware reference platform that we have produced.<br />
<br />
<br />
[[Image:PacemakerTop.png]]<br />
<br />
The side photo show the standard 2mm power jack. A 9-12V adapter providing 300mA should suffice. You can even run the board off of a 9V battery for some time<br />
.<br />
<br />
[[Image:PacemakerSide.png]]<br />
<br />
The next photo shows the BNC and binding post connectors that we have put on so allow the boards to be easily connected to a PC running Labview or some other software to simulate a heart and facilitate testing and debugging.<br />
<br />
[[Image:PacemakerIOConnectors.png]]<br />
<br />
Here is the originial design of the Pacemaker Hardware Reference Platform.<br />
<br />
<br />
== Bill Of Materials (BOM) ==<br />
<br />
We will be releasing the Bill Of Materials (BOM) and the schematics for the hardware once the design is finalized so that you can also produce your own boards if you would prefer to do that. <br />
<br />
{| border="1" cellpadding="20" cellspacing="0"<br />
|Qty<br />
|Reference<br />
|Description<br />
|MFR PART NUMBER<br />
|MFR<br />
|DIGI-KEY PART # <br />
|COST <1000 <br />
|Total Cost $<br />
|-<br />
|4<br />
|C1-2 C67 C68<br />
|CAP 10UF 25V ELECT PW RADIAL<br />
|UVX1H100M<br />
|NICHICON AMERICA<br />
|UPW1E100MDH-ND<br />
| $0.07 <br />
| $0.26 <br />
|-<br />
|13<br />
|C14-15 C33 C45 C50 C9 C58-63 C84<br />
|CAP 1.5UF 10V CERAMIC X7R 1206<br />
|ECJ-3YB1A155K<br />
|Panasonic - ECG<br />
|PCC1867CT-ND<br />
| $0.29 <br />
| $3.72<br />
|-<br />
|More<br />
|To<br />
|Come<br />
|}<br />
<br />
== Scematic ==<br />
<br />
=== Page 1 ===<br />
<br />
[[Image:Pacemaker_Rev10a_schematic_Page_1.png]]<br />
<br />
=== Page 2 ===<br />
<br />
[[Image:Pacemaker_Rev10a_schematic_Page_2.png]]<br />
<br />
=== Page 3 ===<br />
<br />
[[Image:Pacemaker_Rev10a_schematic_Page_3.png]]</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/File:PacemakerSide.pngFile:PacemakerSide.png2008-05-02T13:58:24Z<p>Lawford: Pacemaker Rev. 11 side photo</p>
<hr />
<div>Pacemaker Rev. 11 side photo</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/File:PacemakerTop.pngFile:PacemakerTop.png2008-05-02T13:57:55Z<p>Lawford: Pacemaker board Rev. 11 top photo</p>
<hr />
<div>Pacemaker board Rev. 11 top photo</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/File:PacemakerIOConnectors.pngFile:PacemakerIOConnectors.png2008-05-02T13:56:42Z<p>Lawford: Pacemaker IO Connector Photos</p>
<hr />
<div>Pacemaker IO Connector Photos</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/File:Pacemaker_Rev10a_schematic_Page_3.pngFile:Pacemaker Rev10a schematic Page 3.png2008-05-01T18:36:51Z<p>Lawford: Pacemaker Hardware Reference Platform Rev. 10a Schematic page 3</p>
<hr />
<div>Pacemaker Hardware Reference Platform Rev. 10a Schematic page 3</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/File:Pacemaker_Rev10a_schematic_Page_2.pngFile:Pacemaker Rev10a schematic Page 2.png2008-05-01T18:36:00Z<p>Lawford: Pacemaker Hardware Reference Platform Rev. 10a Schematic page 2.</p>
<hr />
<div>Pacemaker Hardware Reference Platform Rev. 10a Schematic page 2.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Pacemaker_Hardware_Reference_Platform_DetailsPacemaker Hardware Reference Platform Details2008-05-01T18:34:05Z<p>Lawford: Created pacemaker hardware details page.</p>
<hr />
<div>= Pacemaker Hardware Reference Platform Details =<br />
<br />
== Introduction ==<br />
<br />
Here is the originial design of the Pacemaker Hardware Reference Platform.<br />
<br />
<br />
== Bill Of Materials (BOM) ==<br />
<br />
We will be releasing the Bill Of Materials (BOM) and the schematics for the hardware once the design is finalized so that you can also produce your own boards if you would prefer to do that. <br />
<br />
== Scematic ==<br />
<br />
=== Page 1 ===<br />
<br />
[[Image:Pacemaker_Rev10a_schematic_Page_1.png]]<br />
<br />
=== Page 2 ===<br />
<br />
[[Image:Pacemaker_Rev10a_schematic_Page_2.png]]<br />
<br />
=== Page 3 ===<br />
<br />
[[Image:Pacemaker_Rev10a_schematic_Page_3.png]]</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-05-01T18:21:09Z<p>Lawford: </p>
<hr />
<div>= Pacemaker Grand Challenge =<br />
<br />
Information on the Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
=== Pacemaker Hardware Reference Platform ===<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. Once we have finished debugging the revised design we will be producing an additional 45 board for sale at cost (approx. $350 CDN) to interested students, researchers and industry people.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details]] for schematic, Bill Of Materials (BOM) and other details.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-05-01T18:20:53Z<p>Lawford: </p>
<hr />
<div>= Pacemaker Grand Challenge =<br />
<br />
Information on the Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
=== Pacemaker Hardware Reference Platform ===<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. Once we have finished debugging the revised design we will be producing an additional 45 board for sale at cost (approx. $350 CDN) to interested students, researchers and industry people.<br />
<br />
See the [[Pacemaker Hardware Reference Platform Details] for schematic, Bill Of Materials (BOM) and other details.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/File:Pacemaker_Rev10a_schematic_Page_1.pngFile:Pacemaker Rev10a schematic Page 1.png2008-05-01T18:04:23Z<p>Lawford: Pacemaker Hardware Reference Platform Rev. 10a Schematic page 1</p>
<hr />
<div>Pacemaker Hardware Reference Platform Rev. 10a Schematic page 1</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/Software_Certification_ConsortiumSoftware Certification Consortium2008-05-01T17:48:29Z<p>Lawford: New page: = The Software Certification Consortium (SCC) = == Objectives of SCC == # To promote the scientific understanding of software certification and the standards on which it is based; # To p...</p>
<hr />
<div>= The Software Certification Consortium (SCC) =<br />
<br />
== Objectives of SCC ==<br />
<br />
# To promote the scientific understanding of software certification and the standards on which it is based;<br />
# To promote the effective deployment of software certification standards;<br />
# To promote public, government and industrial understanding of the concept of software certification and the acceptance of the need for certification standards for software related products;<br />
# To co-ordinate software certification initiatives and activities to further objectives 1-3 above.<br />
<br />
<br />
== Definition of Certification ==<br />
<br />
;Definition <br />
<br />
: ''Certification'' is the process of systematically determining, based on the principles of science, engineering and measurement theory, whether an artifact satisfies accepted, well defined and measurable criteria.<br />
<br />
== The Goal of Software Certification ==<br />
<br />
The goal of certification is to systematically determine, based<br />
on the principles of science, engineering and measurement<br />
theory, whether an artifact satisfies accepted, well defined<br />
and measurable criteria.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-05-01T17:31:37Z<p>Lawford: </p>
<hr />
<div>== Pacemaker Grand Challenge ==<br />
<br />
Information on the Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
=== Pacemaker Hardware Reference Platform ===<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. Once we have finished debugging the revised design we will be producing an additional 45 board for sale at cost (approx. $350 CDN) to interested students, researchers and industry people.<br />
<br />
We will be releasing the Bill Of Materials (BOM) and the schematics for the hardware once the design is finalized so that you can also produce your own boards if you would prefer to do that.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-05-01T13:18:44Z<p>Lawford: </p>
<hr />
<div>== Pacemaker Grand Challenge ==<br />
<br />
Information on the Pacemaker Grand Challenge is the first certification challenge problem issued by the [[Software Certification Consortium]] (SCC). It is being hosted by the McMaster University's [http://sqrl.mcmaster.ca Software Quality Research Lab] (SQRL). More detailed documentation on the Pacemaker Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
=== Pacemaker Hardware Reference Platform ===<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. Once we have finished debugging the revised design we will be producing an additional 45 board for sale at cost (approx. $350 CDN) to interested students, researchers and industry people.<br />
<br />
We will be releasing the Bill Of Materials (BOM) and the schematics for the hardware once the design is finalized so that you can also produce your own boards if you would prefer to do that. The</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-04-28T12:48:09Z<p>Lawford: </p>
<hr />
<div>== Pacemaker Grand Challenge ==<br />
<br />
Information on the Pacemaker Grand Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].<br />
<br />
=== Pacemaker Hardware Reference Platform ===<br />
<br />
The hardware reference platform, developed by students at the University of Minnesota, is based upon an 8-bit PIC18F4520 microcontroller. It include analog filtering for the input signals from the atrial and ventricle as well as programmable resistors to set the sense thresholds and pace amplitude, external 16 bit A/D converters to allow real-time ECG data to be transmitted from the board, a magnetic reed switch (for magnet mode) , a MAX232 for RS-232 serial communication with a PC acting as a Device Controller-Monitor (DCM) and an accelerometer for rate adaptive modes. <br />
<br />
A number of the parts used in the original design are not readliy available so we have update the design and produced 5 prototype boards for testing that were used at McMaster University for the Software Engineering Senior Thesis course. Once we have finished debugging the revised design we will be producing an additional 45 board for sale at cost (approx. $350 CDN) to interested students, researchers and industry people.<br />
<br />
We will be releasing the Bill Of Materials (BOM) and the schematics for the hardware once the design is finalized so that you can also produce your own boards if you would prefer to do that.</div>Lawfordhttp://wiki.cas.mcmaster.ca/index.php/PacemakerPacemaker2008-04-25T22:24:53Z<p>Lawford: New page: == Pacemaker Grand Challenge == Information on the Pacemaker Grand Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].</p>
<hr />
<div>== Pacemaker Grand Challenge ==<br />
<br />
Information on the Pacemaker Grand Challenge can be found at [http://sqrl.mcmaster.ca/pacemaker.htm SQRL].</div>Lawford