US Core is a standardized FHIR Implementation Guide that defines the minimum conformance requirements for accessing and exchanging patient data in the United States. Mandated by the ONC Cures Act Final Rule, it specifies a core set of FHIR profiles—including Patient, Observation, and MedicationRequest—that certified health IT systems must support to ensure foundational interoperability.
Glossary
US Core
A standardized FHIR Implementation Guide defining the minimum conformance requirements for accessing patient data in the United States, as mandated by the Office of the National Coordinator for Health IT (ONC).
INTEROPERABILITY STANDARD
What is US Core?
The mandatory baseline specification for FHIR-based data exchange in the United States, defining the minimum set of profiles and rules for accessing patient data.
This guide constrains base FHIR resources to meet U.S.-specific terminologies like LOINC and RxNorm, and it establishes the required RESTful API interactions for querying clinical data. By serving as a universal floor rather than a ceiling, US Core ensures that diverse systems can reliably share essential demographic, medication, and laboratory information without custom point-to-point interfaces.
INTEROPERABILITY STANDARD
Key Features of US Core
The US Core Implementation Guide defines the minimum conformance requirements for accessing patient data, establishing a foundational standard for nationwide interoperability as mandated by the ONC Cures Act.
01
Mandated Conformance Baseline
Establishes the minimum set of FHIR resources and profiles that certified health IT systems must support. This creates a universal floor for interoperability, ensuring that every certified EHR can expose and consume a common set of patient data elements. The guide specifies exact search parameters, terminology bindings, and cardinality constraints that systems must implement to achieve certification.
ONC Mandated
Certification Requirement
30+
Profiled Resources
03
Clinical Summary & Document Exchange
Defines the US Core DocumentReference Profile for accessing clinical notes and the Composition Profile for structured clinical summaries. Supports the retrieval of CCDs and other C-CDA documents as FHIR resources. Enables the seamless exchange of encounter summaries, discharge instructions, and progress notes between referring physicians and care teams.
04
Laboratory Results & Vital Signs
Standardizes the representation of quantitative clinical measurements through the Observation resource. Mandates specific LOINC codes for common vital signs like blood pressure, heart rate, and BMI. Profiles the DiagnosticReport resource for lab results and radiology reports, ensuring structured and coded data flows from lab systems to clinical repositories.
LOINC
Primary Code System
05
Medication & Allergy Reconciliation
Profiles the MedicationRequest resource for prescribed medications and the AllergyIntolerance resource for adverse reactions. Requires RxNorm coding for medications and SNOMED CT or RxNorm for allergy substances. Supports the _revinclude parameter to efficiently retrieve a patient's complete medication list and allergy profile in a single query for reconciliation workflows.
06
Problem List & Encounter Context
Defines the Condition profile for capturing a patient's active problem list and medical history using SNOMED CT codes. Profiles the Encounter resource to provide the clinical context—such as location, type, and period—in which observations were made and procedures were performed. Links clinical facts to their originating care event.
US CORE CLARIFIED
Frequently Asked Questions
Clear, technically precise answers to the most common questions about the US Core Implementation Guide, its conformance requirements, and its role in achieving nationwide interoperability.
US Core is a standardized FHIR Implementation Guide that defines the minimum conformance requirements for accessing patient data in the United States. It works by profiling a specific subset of base FHIR resources—such as Patient, Observation, and MedicationRequest—and constraining them to meet U.S. regulatory and clinical needs. These profiles mandate which data elements must be supported, what terminology bindings are required, and how servers must respond to RESTful queries. The guide is published by HL7 and is mandated by the ONC Cures Act Final Rule for certified health IT modules. In practice, a FHIR server claiming US Core conformance must be able to return a patient's demographic data, vital signs, lab results, medications, allergies, and clinical notes in the exact structure defined by the profiles, ensuring that any conformant application can reliably consume and understand the data without custom integration work.
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 more
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