What is FHIR? Fundamentally, FHIR is a new interoperability data exchange standard being advocated by the HL7® organization. The claim is that this new standard combines the best of HL7 v2, v3, RIM and CDA standards with the latest in web standards (RESTFul web services) in a way that can both coexist with your current standards and be implemented easily.
Video: James and Alex on FHIR
Many organizations are asking if they should be implementing FHIR as a messaging standard among their distributed applications and partners, but not many are asking if they are actually capable or ready to do so.
The following is a short check-list to evaluate whether FHIR is a reasonable alternative for your organization. Any group looking to move to the adoption of this standard should go through the following FHIR Drill, answering honestly whether you have:
- An organizational IT ideology committed to being on the forefront of interoperability and the flexibility to change with the evolving standard.
- An interest from trading partners to engage in FHIR messaging.
- An interfacing team that has both the bandwidth and technical acumen to commit to learning a new framework centered around resources and document exchange vs. purely event-driven messaging.
- A vendor partner committed to supporting and staying up to date with FHIR (like Rhapsody).
- An integration engine that is capable of consuming and producing RESTful web services that end-applications can consume.
- A message standards library within the integration engine capable of both parsing and manipulating XML and JSON data structures.
- A mapping tool capable of translating from other standards into FHIR, such as HL7 v2 to FHIR. These older standards aren’t going away anytime soon and all integrations will need to be able to play in both spaces.
See all of our FHIR Resources here.
®Health Level Seven, HL7, FHIR and the FHIR [FLAME DESIGN] are registered trademarks of Health Level Seven International, registered with the United States Patent and Trademark Office. The use of these trademarks does not reflect HL7’s endorsement.