White papers
HL7 FHIR Primer
HL7 FHIR Primer. By Dave Shaver, Co-Chair of the HL7 FHIR Governance Committee and Founder of Corepoint Health.
Read More >
Resources
Press releases
Rhapsody Earns Top Integration Engine Award in 2025 Best in KLAS® Report
Industry-Leading Digital Health Enablement and Interoperability Platform Receives Top Recognition for 16th Consecutive Year
Filter by
Market segment
Resource type
Region
Product
Topics
Oops! Look like we don’t have any results. Check this out instead.
Read more >
Blogs
Frequently asked questions about FHIR APIs
FHIR APIs are coming. Will FHIR ensure better consistency? When will major EHRs begin offering FHIR APIs? How will they function?
Read More >
White papers
The Future of Interoperability: Web APIs & HL7 FHIR
Web APIs have the potential to open myriad possibilities for patient care. This whitepaper details how providers can leverage API integration to reap the benefits of APIs alongside HL7 FHIR, the standard that is being employed as the data standard of choice for APIs by all major EHR vendors.
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 >
Blogs
HL7 publishes Release 3 of FHIR
HL7 FHIR takes one last step before becoming a 'finished' product. FHIR progress is happening quickly with thousands of proposals and three key focus areas.
Read More >
Blogs
What is a FHIR® Connectathon? And how do these events evolve this health IT standard?
What's the Purpose of a Connectathon?
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 >