When do I need to use the Device Data Model?
The Redox Device Data Model is used to transmit discrete continuous physiological monitoring data to an EHR. The Device Data Model is useful for workflows where an EHR is maintaining the link from the device to the patient. Given the EHR can match the device ID to the patient record, the application sending the device data back to the chart only needs to include the device identifier. Typically, EHRs that support device data offer an HL7v2 ORU interface or API to file the data.
How is the Redox Device Data Model different from the Flowsheets model?
The Redox Flowsheets and Device models are almost identical save for one key difference: the Device model requires a device identifier to match the results with the patient’s chart while the Flowsheets model (and almost every other Redox data model) requires a patient identifier.
How can an EHR match the Redox Device Data Model to the right patient?
There are two types of device patient association in the EHR:
- Static: If a device is not movable and is set in a single patient room, it can be assumed that any patient in that room is using the device when data comes back for it. No manual step is needed for association of the device to the patient, only validation of the data by a nurse to file it to the chart.
- Dynamic: If a device is mobile and moves from room to room, typically a user will generally manually associate the device with a patient in the EHR before data flows to that chart and can be validated.
How is the Redox Device data model different from the Results model?
While both Data Models deal with diagnostic machines in the hospital producing information, the Redox Device Data Model differs from the Results data model in that the values are continuous (i.e. they are measured repeatedly over an extended period of time) and are not the one-time outcome of an order. Examples include ventilators, pumps or Sp02 monitors. Things that are diagnostic tests (labs, imaging, etc) are also devices of sorts, but do not measure continuously and better served over the Results data model.