2012-02-27 PCD Pulse Oximetry Project Meeting: Difference between revisions
Jump to navigation
Jump to search
| Line 35: | Line 35: | ||
==Links== | ==Links== | ||
* | * Use case analysis: actors and main business use cases" | ||
[[File:PulseOx UseCaseAnalysis,v1.png]] | |||
[[File:PulseOx Workflow,v1.png]] | |||
Workflow description for business use cases for Pulse Oximetry | |||
* Our data analysis identifies the core data elements required to support the use cases. '''Optional''' data elements are indicated by the '''[0..*] cardinality''' notation and '''repeating''' element are specified as '''[1..*]'''. | |||
[[File:PulseOx_DataAnalysis,v1.png]] | |||
==Action Items== | ==Action Items== | ||
Revision as of 18:25, 23 February 2012
Weekly Conference Call
Date: Monday, February 27th, 2012 Meeting will at 1 pm.
Attendees
- expected
- John Rhoads - PCD TC co-chair
- Leah Krynicky
- Greg Staudenmaier
- Nelson S. Hsing
- Ioana Singureanu
- Ken Fuchs, PCD PC co-chair
- Catherine Hoang
- Sean McFarland
- Tamara Diltz-Andary
- Tom Bauld
- Toni Philips
- Tocher Kellom
- Susan Whitehead, MDPNP, CIMIT
- Dr. Julian Goldman
- Lee Winslow
Agenda
- draft
- (05 min) Roll call and meeting minutes approval
- (25 min) Use case discussion: this will include a discussion of the trigger events that initiate an exchange of pulse oximeter results from a device. We need to reach consensus on the distinction between the probe and the device that intended to exchange information. We will also discuss aspects of the workflow to clarify how and where the device data is validated for each use cases. We need to clarify whether the Anesthesia Record will contain validated results, raw device results, or a combination of the two.
- (25 min) Data Requirements Analysis: The information exchanged along with the results for pulse and oxygen saturation. This may include: device allowable ranges, patient-type (e.g. adult, pediatric) reference ranges (from device, from device manager, or added in the receiving system), verification indicator specifying the clinicians validated a result, operator identity - for verified results. We will also discuss alarm conditions intended to be reported to the clinical information system - primarily for those results that were not validated at the point of care.
- (5 min) Action item update
Meeting Notes
Links
- Use case analysis: actors and main business use cases"
Workflow description for business use cases for Pulse Oximetry
- Our data analysis identifies the core data elements required to support the use cases. Optional data elements are indicated by the [0..*] cardinality notation and repeating element are specified as [1..*].
Action Items
- Item:
- Item: