Rhapsody site logo

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. Arguably most important factoid in the manifesto is that the specification is written for one target: implementers.

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

Much of the failure of HL7 V3 was blamed on the complexity that was created for implementers. Rather than starting with data models, FHIR’s architects decided to focus on what was most important to them as implementers: ease of implementation. As seen in the list below, the manifesto is highly focused on implementation:

  1. Focus on implementers
  2. Target support for common scenarios
  3. Leverage cross-industry web technologies
  4. Require human readability as base level of interoperability
  5. Make content freely available
  6. Support multiple paradigms & architectures
  7. Demonstrate best practice governance

Learn more about FHIR

Our HL7 FHIR Primer provides an in-depth look at how FHIR will impact the future of health data exchange, including:

  • What differentiates FHIR from other Health Standards?
  • Where might FHIR be used?
  • Where does FHIR go from here?

Download our HL7 FHIR primer as you plan a modern, integrated healthcare IT environment. Or register for an upcoming FHIR: First Steps training class.

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 >