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.
Push new observations from a device to a patient's chart.
One message may include multiple observations.
Patient and visit information may be included. However, the EHR system usually maps the device ID either to the patient directly or to a room/bed directly. So the EHR system usually ignores the patient and visit information.
Request Body Schema
- Metarequired, object
- DataModelrequired, stringReliable
Device
- EventTyperequired, stringReliable
New
- EventDateTimestring, nullReliable
Displays the UTC date and time that an outgoing request is delivered or an incoming request is received.
ISO 8601 Format - Testboolean, nullReliable
Indicates whether the request is a test or not.
- Sourceobject
Contains the information for the system initiating the message, including the source ID and name.
Included in messages from Redox- IDstring, nullReliable
Identifies the system initiating the message. If you have multiple OAuth API keys per environment type, this value is required. If you have only one OAuth API key per environment type, or you're using legacy API keys, this value is optional.
UUID - Namestring, nullReliable
Displays the name of the system initiating the message.
- DestinationsArray of object
Contains the information for the endpoint(s) receiving the request. A request must contain at least one destination, but asynchronous requests can have more than one destination. Synchronous requests like queries can only support one destination.
Required when sending data to Redox.- IDstring, nullReliable
Identifies the endpoint that the request is directed to.
UUID - Namestring, nullReliable
Displays the name of the endpoint that the request is directed to.
- LogsArray of object
Contains the log identifier(s) for the request.
- IDstring, nullReliable
Identifies the request log(s) that correspond to this request. You can use this value to locate the relevant log in the Redox dashboard for support and reference.
UUID - AttemptIDstring, nullReliable
Identifies the request log attempt value, which is useful when retries are possible.
UUID
- FacilityCodestring, nullPossible
Code for the facility related to the message.
Only use this field if a health system indicates you should. The code is specific to the health system's EHR and might not be unique across health systems. In general, the facility fields within the data models (e.g. OrderingFacility) are more reliable and informative.
- Devicerequired, object
- IDrequired, stringReliable
Identifier for the device.
This ID is used to map the device to the patient in the EMR
- Observationsrequired, Array of object
List of values to be added to the patient's chart
- DateTimerequired, stringReliable
DateTime the value was recorded.
ISO 8601 Format - Coderequired, stringReliable
Code for the metric measured.
This is usually provided by the EMR or you will be asked to provide a list of codes you can send. For example, this is where you would specify "Heart Rate" - Valuerequired, stringReliable
Value to be recorded for corresponding code.
For example, if the code is "Heart Rate", this may be 65 - ValueTyperequired, stringReliableValue Set
Data type for the value
- Unitsstring, nullProbable
Units of the value.
If the code is "Heart Rate", this may be "BPM"
- Patientobject
- IdentifiersArray of object
List of IDs and ID types that identify the patient
- IDstring, nullReliable
ID for the patient
- IDTypestring, nullReliable
Type of ID.
E.g. MRN, EPI
- Demographicsobject
- FirstNamestring, nullReliable
Patient's first name
- MiddleNamestring, nullPossible
Patient's middle name or middle initial. For patients with multiple middle names, all their middle names are included in this field.
- LastNamestring, nullReliable
Patient's last name
- DOBstring, nullReliable
Patient's date of birth.
In ISO 8601 format - SSNstring, nullProbable
Patient's social security number
- Sexstring, nullReliableValue Set
Patient's sex
- Racestring, nullPossibleValue Set
Patient's race
- IsHispanicboolean, nullPossibleValue Set
Indicates if the patient is of hispanic origin.
- Religionstring, nullPossibleValue Set
Patient's religious affiliation
- MaritalStatusstring, nullPossibleValue Set
Patient's marital status
- IsDeceasedboolean, nullPossible
Indicates if the patient is deceased
- DeathDateTimestring, nullPossible
Date and Time the patient was proclaimed deceased.
ISO 8601 Format - PhoneNumberobject
- Homestring, nullProbable
Patient's home phone number.
In E. 164 Format. (e.g. +16085551234) - Officestring, nullProbable
Patient's office phone number.
In E. 164 Format. (e.g. +16085551234) - Mobilestring, nullProbable
Patient's mobile phone number.
In E. 164 Format. (e.g. +16085551234)
- EmailAddressesArray of string
Patient's email address(es)
- Languagestring, nullPossibleValue Set
Patient's primary spoken language.
In ISO 639-1 alpha values (e.g. 'en'). Supported Values - CitizenshipArray of string
Patient's nation(s) of citizenship.
In ISO 3166 alpha 2 format (e.g. 'US'). - Addressobject
Patient's home address
- StreetAddressstring, nullProbable
Street address
- Citystring, nullProbable
City
- Statestring, nullProbable
State
- ZIPstring, nullProbable
ZIP
- Countystring, nullPossible
County
- Countrystring, nullPossibleValue Set
Country
- NotesArray of string
Patient-level notes
- ContactsArray of object
- FirstNamestring, nullPossible
First name of the contact
- MiddleNamestring, nullPossible
Middle name of the contact
- LastNamestring, nullPossible
Last name of the contact
- Addressobject
Address of the contact
- StreetAddressstring, nullPossible
Street address
- Citystring, nullPossible
City
- Statestring, nullPossible
State
- ZIPstring, nullPossible
ZIP
- Countystring, nullPossible
County
- Countrystring, nullPossibleValue Set
Country
- PhoneNumberobject
- Homestring, nullPossible
Home phone number.
In E. 164 Format. (e.g. +16085551234) - Officestring, nullPossible
Office phone number.
In E. 164 Format. (e.g. +16085551234) - Mobilestring, nullProbable
Mobile phone number.
In E. 164 Format. (e.g. +16085551234)
- RelationToPatientstring, nullPossibleValue Set
Personal relationship to the patient.
e.x. Father, Spouse - EmailAddressesArray of string
Email address(es) of the contact person
- RolesArray of string
Role of this contact for the patient.
e.x. Employer, Emergency Contact
- Visitobject
- VisitNumberstring, nullReliable
Number for the visit
- Locationobject
Location of the visit. This may be used for validation or to identify your application/device.
- Typestring, nullProbable
Type of location.
Examples: Clinic, Department, Home, Nursing Unit, Provider's Office, Phone - Facilitystring, nullProbable
Facility.
Example: Community Hospital - FacilityIdentifiersArray of object
List of IDs specific to this facility
- IDstring, nullProbable
An ID specific to this facility
- IDTypestring, nullProbable
The source or system to which this ID pertains.
Could be an OID or a human-readable name
- Departmentstring, nullProbable
Department
- DepartmentIdentifiersArray of object
List of IDs specific to this department
- IDstring, nullProbable
An ID specific to this department
- IDTypestring, nullProbable
The source or system to which this ID pertains.
Could be an OID or a human-readable name
- Roomstring, nullProbable
Room.
Example: 136 - Bedstring, nullProbable
Bed.
Example: B