<aside> 💡 The goal of this template is to provide RIS manufacturers and partners with standard HL7 profiles that follows the IHE norm, allowing for interoperability between systems
</aside>
https://www.vico.org/HL7_V2_5/v251/std251/hl7.html
https://hl7-definition.caristix.com/v2/HL7v2.5.1/Segments
The HL7 (Health Level 7) format is a set of standards for the exchange, integration, sharing, and retrieval of electronic health information. It specifies a framework for structuring, encoding, and transmitting various types of healthcare data, such as patient demographics, clinical observations, laboratory results, and more. It is used together with the DICOM format that was designed specifically for the management and exchange of medical images rather than “administrative” information
We call each different line a segment, that has a specific purpose. They are all structured with a similar syntax, and depending on the type of segment (MSH, PID, OBR, OBX…) each field of the segment should hold specific information. For example, the information about the provider in MSH is always in field 3 : it is not random and follows a set structure defined by the HL7 standard
| CHARACTER | NAME | PURPOSE |
|---|---|---|
| Field separator (pipe) | ||
| ^ | Component separator (hat) | Separates components in a field |
| ~ | Field repeat separator | Separates repeated fields in a segment |
| & | Sub-component separator | Separates components within components |
<aside> 💡 A segment in an HL7 message is a fundamental unit of data within the message. It represents a specific type of information or a group of related data elements. Each segment is identified by a three-letter code that indicates its type, and it contains a set of fields, each separated by a specific delimiter.
</aside>
Each page contains the information details and sources, of why each specific segment is constructed this way. For clarity purposes, we’re not detailing each optional field that can be provided to a segment but only those that are needed to communicate AI Results.
# In {} are variables, the rest is fixed
MSH|^~\\&|Rayvolve|AZMED|RIS|{InstitutionName}|{YYYYMMDDHHMMSS}||ORU^R01|{UniqueIdentifier}|P|2.5.1
PID - the patient identification segment
# In {} are variables, the rest is fixed
PID|||{PatientID}||{LastName}^{FirstName}||{PatientBirthDate}|{PatientSex}