HL7 resources
HL7 Data Types
HL7 data types define the kind of data included in a field used in the HL7 message structure. Examples include a string, text, timestamp, address, or coded element.
Read more >Resources
Press releases
Rhapsody Earns Best in KLAS® Distinction in Integration Engine Category for 15th Consecutive Year
Leading Digital Health Enablement Platform Receives Top Rankings in the 2024 Best in KLAS®: Software & Services Report
Filter by
Market segment
Resource type
Region
Product
Topics
Oops! Look like we don’t have any results. Check this out instead.
HL7 resources
RIM-Reference Information Model
The HL7 Reference Information Model (RIM) represents a static model of healthcare workflows as viewed by the HL7 standards development group.
Read more >HL7 resources
Minimum Layer Protocol – MLP
MLP is how an application should wrap an HL7 message to ensure HL7 compliant applications know where a message starts and stops, and where the next message begins.
Read more >HL7 resources
HL7 NTE Segment
The HL7 NTE segment is used for sending notes and comments in a message. NTE segments often follow OBX segments to provide additional information.
Read more >HL7 resources
HL7 IN1 Segment
The HL7 IN1 segment contains insurance policy coverage information necessary to produce properly pro‑rated and patient and insurance bills.
Read more >HL7 resources
HL7 NK1 Segment
NK1 segments contains information about the patient’s other related parties, and any associated parties. The NK1 attribute fields are as follows:
Read more >HL7 resources
FHIR Resources
FHIR Resources are the data packages used to send or receive data from a FHIR repository. With the STU-3 release 3 of FHIR, there are 92 resources defined.
Read more >HL7 resources
HL7 FHIR Manifesto
Although HL7 International does not have an official FHIR manifesto, the original architects of the FHIR standard created one to guide the early efforts of the standard’s development.
Read more >HL7 resources
HL7 FHIR Extensions
The HL7 FHIR standard makes use of extensions to keep the standard simple. An extension allows for the inclusion of data that does not fit into the standard’s defined data elements.
Read more >