Receive HL7 formatted messages over HTTPS to your system. Please note that, unlike endpoints using the Stel v2.0 schema, HL7 measurements from Stel will NOT be sent as JSON and instead as a plain text file using the text/plain
content type header:
{
"Content-Type": "text/plain"
}
Additionally, HL7 measurements sent from Stel will NOT use the MLLP protocol to communicate with your system. Stel expects an HTTPS endpoint with a commercially signed SSL certificate that can be reached on the public internet. Please see our integration guide for additional details.
Lastly, since Stel does not store any PHI, no patient information or references to existing ADTs in your system will be included. Only information related to the measurement taken, i.e. measured vitals, hub ID, device information, etc. will be included in the message.
HL7 messages from Stel will always contain at least four segments: MSH, PID, OBR, OBX. Date/times will always be reported in UTC, denoted with a +0000
timezone offset. Each line ends in a carriage return character (/r
) as defined by the standard HL7 spec. See below for a breakdown of the segments included in a Stel HL7 message:
MSH
MSH|^~\\&|stel||||20240226160649+0000||ORU^R01|884bb4de-a7c2-4c99-9e55-3c689924bc44||2.4
Field Number | Field Value | Default Value | Detail |
---|---|---|---|
1 | Field separator | ||
2 | Encoding characters | ^~\& | |
3 | Sending application | stel | |
7 | Date/time of message | The date/time Stel transmitted the message to your system, this is NOT the time of the measurement | |
9 | Message type | ORU^R01 | |
10 | Message control ID | The unique identifier (UUID) associated to the message | |
12 | Version ID | 2.4 |
PID
PID|||0000BE9YKM^^^Stel Life^stel-hub-id
Field Number | Field Value | Detail |
---|---|---|
3 | Hub ID | - PID-3.1: Hub ID associated to the measurement |
OBR
OBR||||bloodpressure|||20240226160646+0000|||||||20240226160646+0000
Field Number | Field Value | Detail |
---|---|---|
4 | Measurement type | The type of measurement, i.e. “bloodpressure” |
7 | Device time | The time reported by the device when the measurement was taken |
14 | Hub time | The time reported by the hub when it received the measurement from the device |
<aside> 💡 It can be more accurate to refer to the device time (OBR-7) as the time the measurement was taken rather than the hub time (OBR-14) because a device may be used outside of the hub’s range and sent only when returned within the range. However, this field may be empty if the device is incapable of tracking time. If that is the case, defer to the hub time.
</aside>
OBX
OBX|1||systolic||173.0|mmHg||||||||||||UA-651BLE^A\\T\\D^14:E3:CC:A4:92:36
OBX|2||diastolic||80.0|mmHg||||||||||||UA-651BLE^A\\T\\D^14:E3:CC:A4:92:36
OBX|3||heartRate||41.0|bpm||||||||||||UA-651BLE^A\\T\\D^14:E3:CC:A4:92:36
<aside> 💡 In the above example, the make name, A&D, has been updated to escape the encoding character “&”. Please see 2.10.1 of the official HL7 v2.4 documentation for the formatting codes used to escape encoding characters.
</aside>