Device

This data model allows vendors to send discrete continuous physiological monitoring data to a patient's chart (e.g., heart rate, estimated blood loss).

A Device data model is useful when an EHR system is maintaining the link from the device to the patient. The vendor sending device data back to the EHR system should include the device ID to save the data to the patient's chart.

There are two types of device patient association in the EHR system:

Static: If a device isn't movable and is located in a single patient room, we can assume that any patient in that room is using the device when data comes back for it. There's no manual step needed for association of the device to the patient. A nurse validates the data to file it to a patient's chart.
Dynamic: If a device is mobile and moves from room to room, medical staff must manually associate the device with a patient in the EHR system before data flows to that chart and can be validated.

This data model has event types that allow you to:

send new observations from a device to a patient's chart.

EHR support for Device

EHR systems that support device data typically offer an HL7v2 ORU interface or API to file the data.

Device v Flowsheets v Results data models

There's some overlap among these data models, but here's what to expect for each:

Device data is continuous. The Device data model requires a device ID to match results to a patient's chart.
Flowsheet data is continuous. The Flowsheet data model requires a patient ID to match results to a patient's chart.
Results data is discrete data that's usually a one-time outcome of an order. The Results data model requires a patient ID to match results to a patient's chart.

Events in Device

New

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.