Difference between revisions of "DCM4MD:Project Use Cases"

From HL7Wiki
Jump to navigation Jump to search
m (fix typos)
m (typo)
Line 23: Line 23:
 
*[[DCM4MD:Actors#EHR-System|EHR-System]]
 
*[[DCM4MD:Actors#EHR-System|EHR-System]]
 
===Pre-Conditions===
 
===Pre-Conditions===
*The patient is associated with a specific bed/location and the location is tracked by a hospital system. This use case applies only to specific  
+
*The patient is associated with a specific bed/location and the location is tracked by a hospital system. This use case applies only to specific inpatient and ambulatory settings.
inpatient and ambulatory settings.
 
 
*The device is associated with a specific bed/location and it is not moved from that location until its location is recorded in an information system.
 
*The device is associated with a specific bed/location and it is not moved from that location until its location is recorded in an information system.
 
*The device is not capable of acquiring an accurate [[#Synchronize_Device_Time_Across_the_LAN|date/time from a reference server]]. The[[DCM4MD:Actors#Medical_Device_Manager|Device Manager]] provides the time/stamp and, optionally, the location if it's not reported by device itself.
 
*The device is not capable of acquiring an accurate [[#Synchronize_Device_Time_Across_the_LAN|date/time from a reference server]]. The[[DCM4MD:Actors#Medical_Device_Manager|Device Manager]] provides the time/stamp and, optionally, the location if it's not reported by device itself.

Revision as of 03:13, 31 January 2011


Back to: Project Main Page


:: May 2011 Use Cases ::

The following use cases have been identified to be in scope for the May 2011 ballot of the DCM for Medical Devices Project. The focus of this ballot will constitute DCMs that are required to support

  1. patient-to-device association in order to assign the data produced by the device to appropriate patient for charting and,
  2. time consistency across information systems and devices.
  3. operator-to-device association in order to assign the data produced by the device to the attending caregiver for charting [SBP - waiting for peer review of this item before modifying the use cases further accordingly]

Associate the Medical Device with a Patient by Location

This use case is currently implemented by most legacy devices in critical and acute care environments. These legacy devices do not have the ability to record the patient's medical record number or receive patient demographics from hospital information systems.

Actors

Pre-Conditions

  • The patient is associated with a specific bed/location and the location is tracked by a hospital system. This use case applies only to specific inpatient and ambulatory settings.
  • The device is associated with a specific bed/location and it is not moved from that location until its location is recorded in an information system.
  • The device is not capable of acquiring an accurate date/time from a reference server. TheDevice Manager provides the time/stamp and, optionally, the location if it's not reported by device itself.

Main Scenario

The patient is placed at a specific location/bed and the medical devices are used to monitor specific physiological parameters or deliver specific therapies. The information produced by the device reports the location where the device was placed.

Alternate Scenario

Instead of the device, the Device Manager or concentrator is associated with the patient location. The information system or EHR-System- uses the informatoon reported by the device or the configure configuration reported by the device manager along with the known location of the patient to infer whose data/results/therapy needs to be recorded.

Post-Conditions

The information/data produced by the device is added to the patient's medical record based on the device to location to patient assignments perfore the Device Manager and EHR-system respectively. In some cases, the data may need to be validated by a clinician (e.g. nurse) before it is permanently committed to the patient's record.

Dependency

Synchronize Time is used to synchronize the device clock to ensure that the results are reported acurately.

Associate the Medical Device with a Patient by Identifier and Point-of-Care

Both location and patient's identifier are used to determine whehter the device should be associated with a specific location.

This use case may represent a transitional state of interoperability.

Actors

Pre-Conditions

  • The device is able to record the patient's identity

Main Scenario

  • The operator scans or enters the patient's identity into the device using its user interface, bar code reader, etc.
  • The device is used to treat or monitor the patient's condition.
  • Once the device is not longer needed, the operator discontinues the association. This removes the patient's identity from the data produced by the device.

Post-Conditions

When the device is no longer acquiring data for the patient, the association with the medical device is broken. In some cases, the data may need to be validated by a clinician (e.g. nurse) before it is permanently committed to the patient's record.

Dependency

Synchronize Time is used to synchronize the device clock to ensure that the results are reported acurately.

Associate the Medical Device with a Patient by Selecting Patient on Device

This use case is applicable in highly integrated environments. It requires an encounter managment system (ADT) integrated either with the Medical Device directly or through its Device Manager .

Actors

Pre-Conditions

  • The device or its device manager is tracking encounter events (e.g admission) or queries its Device Manager for patients as needed.

Main Scenario

  • The operator enter a set of patient identifier traits into the medical device to loop up the patient's identity.
  • The operator selects the appopriate patient record and associates the device with the patient.
  • When the patient is disconnected from the patient, the association is automatically broken.

Post-Conditions

The information reported by the device while the device was associated with the patient, is charted to the patient's record. In some cases, the data may need to be validated by a clinician (e.g. nurse, respiratory therapits) before it is permanently committed to the patient's record.

Dependency

Synchronize Time is used to synchronize the device clock to ensure that the results are reported acurately.

Associate the Medical Device with a Patient by Patient Identifier Only

This use cases provides the most efficient patient-to-device association provided that the patient's identifier is entered correctly into the device.

Actors

Pre-Conditions

  • The device is able to record the patient's identity.

Main Scenario

The Operator enter the patient's identity using the device input device (e.g. keyboard, bar code scanner). The precision with which the patient's identifier is entered into the device determines how acurate the association between the patient and device and its output data will be equally acurate.

Post-Conditions

The information is received by the destination information system or EHR-System and associated with the patient identified by the their patient identifier. In some cases, the data may need to be validated by a clinician (e.g. nurse) before it is permanently committed to the patient's record.

Security Risk Assessment

  • The date in transit may not require encryption since no identifyable patient information needs to be sent by the device

Dependency

Synchronize Time is used to synchronize the device clock to ensure that the results are reported acurately.

Synchronize Device Time Across the LAN

Actors

Pre-Conditions

Main Scenario

The medical device connects to the Network Time Server to set up its clock to acurate date/time. The device clock is used to timestamp the results or parameters reported by the device to the EHR-System.

Post-Conditions

The device is syncronized with the Network Time Server and implictly with any other information systems or devices.

Synchronize information from patient transport

This use case applies to those scenarios when medical devices are used during patient transport to capture vital signs and the information is uploaded into the hospital information systems

Actors

Pre-Conditions

Main Scenario

The medical device connects to the Network Time Server to set up its clock to acurate date/time. The device clock is used to timestamp the results or parameters reported by the device to the EHR-System.

Post-Conditions

The device is syncronized with the Network Time Server and implictly with any other information systems or devices. EHR-System.