Rhapsody site logo

HL7 resources

FHIR Resources

FHIR Resources are the data packages used to send or receive data from a FHIR repository. With STU-3, Standard for Trial Use, release 3 of FHIR, there are currently 92 resources defined. The HL7 organization wants enough resources to handle 80% of the healthcare workflows but does not want so many that the standard would become too complex.

Optimize resource productivity with the most trusted and flexible HL7 and API integration tools in the market

Resources are meant to capture a meaningful amount of data. For example, the following table provides examples of what would be, and would not be, a FHIR resource. Things like patient demographic data or allergies provide the perfect amount of data. For those familiar with HL7 V2 messaging, a resource would typically contain about the same amount of data as a segment in a HL7 V2 message.

The data housed within resources is broken out into four parts, in the following order:

  • Metadata – Contains details about the resource, such as when it was last updated.
  • Narrative – Contains XHTML so that the resource can be read in browsers without having to parse apart all the data
  • Extensions – Used to include data that is not part of the defined structure of the resource
  • Elements – Contains the structured data of the resource

Want to learn more about HL7? Enroll in the Academy’s HL7 training course now!

For further reading:

You might also like

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 >

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 >