The US Core Implementation Guide (IG) is a binding FHIR specification that establishes the minimum set of FHIR profiles, RESTful interactions, and terminology constraints required for interoperable patient data exchange in the U.S. It is derived directly from the U.S. Core Data for Interoperability (USCDI) standard, translating mandated clinical data classes—such as allergies, medications, and lab results—into concrete, computable StructureDefinition resources that systems must support.
Glossary
US Core Implementation Guide (IG)
A FHIR specification defining the minimum conformance requirements for accessing patient data in the United States, based on the U.S. Core Data for Interoperability (USCDI) standard.
INTEROPERABILITY STANDARD
What is US Core Implementation Guide (IG)?
The US Core Implementation Guide (IG) is the foundational FHIR specification that defines the minimum conformance requirements for accessing and exchanging patient data across the United States healthcare system.
Published by HL7 International, the US Core IG serves as the base profile layer upon which other specialized implementation guides are built. It defines mandatory CapabilityStatement requirements for servers and clients, specifies which ValueSet bindings apply to coded elements, and mandates support for the SMART on FHIR authorization protocol. Compliance with US Core is a prerequisite for certification under the ONC Health IT Certification Program, making it the technical backbone of nationwide health information networks.
INTEROPERABILITY FOUNDATION
Key Features of US Core IG
The US Core Implementation Guide defines the minimum conformance requirements for accessing patient data in the United States, based on the U.S. Core Data for Interoperability (USCDI) standard. It establishes a baseline for FHIR-based exchange across the healthcare ecosystem.
02
Must Support & Cardinality
Profiles define Must Support flags and strict cardinality constraints on data elements. When an element is marked Must Support, systems must be capable of populating, storing, and returning that data if it exists. This creates a predictable contract between clients and servers:
- Required elements (cardinality 1..1) must always be present
- Must Support elements must be handled if the source system has the data
- Optional elements (cardinality 0..1) may be omitted without breaking conformance
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.
Enterprise searchRAGPermissions
Read more
Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.
AI agentsWorkflow automationGovernance
Read more
Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
AI integrationDecision supportModel routing
Read moreUS CORE IG
Frequently Asked Questions
Clear answers to the most common questions about the US Core Implementation Guide, its relationship to USCDI, and its role in FHIR interoperability.
The US Core Implementation Guide (IG) is a formal FHIR specification that defines the minimum conformance requirements for accessing patient data in the United States. It works by profiling a subset of base FHIR resources—such as Patient, Observation, and MedicationRequest—and constraining them with mandatory elements, specific terminologies, and search parameters that every certified health IT system must support. The guide is built directly on the U.S. Core Data for Interoperability (USCDI) standard, translating its data classes and elements into computable, API-ready definitions. When a FHIR server declares conformance to US Core, it guarantees that a client can reliably query for and receive a predictable set of clinical data elements using standardized RESTful interactions, regardless of the underlying EHR vendor.
About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
LinkedIn
Limited slotsGet a Free AI Consultation
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us