FHIR

FHIR implementation guides explained: US Core, the IPS and national profiles

Base FHIR is deliberately broad; implementation guides (IGs) narrow it for a country or use case with profiles, must-support elements and terminology bindings. What an IG contains, how US Core and the International Patient Summary differ, and how to validate against them.

by Published 2 min read

Short answer: Base FHIR defines resources broadly so that every country and use case can use them. An implementation guide (IG) narrows them for a context: which elements are required or must-support, which code systems are bound to which elements, which extensions are allowed, with examples and tests. US Core defines the minimum for US health data exchange (aligned with USCDI); the International Patient Summary (IPS) defines a short cross-border summary; many countries publish their own base profiles.

What an IG contains

  • Profiles (StructureDefinitions) that constrain resources, for example an Observation that must have a LOINC code and a UCUM unit.
  • Value set bindings: which codes are allowed for an element.
  • Extensions for data the base resource does not have.
  • CapabilityStatements, examples, search requirements.

A resource "conforms" to an IG when it validates against its profiles; the HL7 validator checks this.

US Core vs IPS

US Core covers the data US systems exchange day to day (patients, problems, medications, labs, vital signs and more). The IPS covers what a doctor anywhere needs in an unplanned visit: allergies, medications, problems, immunizations and some more, packed in one document bundle, coded with international terminologies (SNOMED CT, LOINC). A system can support both. See our patient guide on the International Patient Summary.

In Anpheros

Anpheros generates an International Patient Summary for each person, validated with the HL7 validator against the IPS profiles. Developers: the International Patient Summary in FHIR and FHIR code systems.

Sources

Frequently asked questions

What is a FHIR implementation guide?

A specification that narrows base FHIR for a country or use case with profiles, bindings and examples.

What does must-support mean?

That a system must be able to handle the element when the data exists; the exact meaning is defined by each IG.

What is the difference between US Core and the IPS?

US Core covers everyday US exchange; the IPS a short international summary for unplanned care.

How do I check that my resources conform?

Validate them against the IG's profiles, for example with the HL7 FHIR validator.

Anpheros Platform

Try it free in the sandbox

Your first FHIR call in 5 minutes. An HL7 FHIR R4 API with the patient's consent built in: try it in the sandbox, then connect your own app or clinic system.

Free · 30 synthetic patients · no card

This guide is for information and does not replace medical advice. For decisions about your health, talk to your doctor. In an emergency, call your local emergency number (112 in Europe).
Written by
The Anpheros team

Anpheros builds a medical record that the patient controls and can share with any clinic, on an HL7 FHIR R4 platform, based in the EU. These guides help you understand and organise your health; they do not replace your doctor.

About Anpheros →
Anpheros

The more you log, the clearer your record

Your health history in one place, under your control.

Symptom diaryPatterns show over time
Emergency cardQR in your phone's Wallet
All your resultsLabs and reports together
You decideWho sees what, and for how long
Create your free account

Free · Works in your browser · No card