USCDI v3 Data Elements: Full List and FHIR Mapping (2026)

March 16, 20264 min readUpdated Nov 8, 2026
Written by
Jitendra Choudhary
Jitendra Choudhary

CTO & Co-Founder

CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

USCDI v3 Data Elements: Full List and FHIR Mapping (2026)

As of January 2026, certified health IT systems must support USCDI v3 (United States Core Data for Interoperability, version 3) under the ONC HTI-1 Final Rule. This is not optional for certified products. USCDI v3 is required for health IT certified under the ONC Health IT Certification Program, for the criteria that reference USCDI (for example § 170.315(b)(1), (e)(1), (g)(9) and (g)(10); see 45 CFR 170.315). An app that only connects to a certified EHR is not itself required to support USCDI v3, though it will receive data in that shape.

Short answer: USCDI v3 is the third version of the United States Core Data for Interoperability, a standardized set of health data classes and elements that ONC certification criteria reference. It has 94 data elements in 19 data classes. The HTI-1 Final Rule made it the required USCDI version from January 1, 2026 for the certification criteria that reference USCDI (ONC then gave developers until February 28, 2026 to finish those updates under enforcement discretion notice EDN2025.06), and US Core 6.1.0 is the FHIR guide that maps it. In 2025 ONC released USCDI v3.1, which removes the Sexual Orientation and Gender Identity elements and changes Sex; the section on v3.1 below explains what that means for certification.

USCDI v3 adds two new data classes, Health Insurance Information and Health Status/Assessments, and new data elements in Laboratory, Medications, Patient Demographics and Procedures. Many organizations are discovering that while their systems handle v2 data elements well, the v3 additions expose significant gaps in their data capture, storage, and API exposure.

For a gap assessment against USCDI v3, see our healthcare compliance engineering services.

This guide maps every USCDI v3 data class to its corresponding FHIR US Core profile, identifies the most common compliance gaps, and provides a testing approach using the Inferno US Core test suite. If you also support older or newer USCDI releases, our USCDI vs US Core version map shows which US Core release lines up with each one.

What Changed from USCDI v2 to v3

USCDI v3 contains 94 data elements in 19 data classes, up from 52 elements in 16 classes in v1. Compared with v2, it adds two new data classes and 24 new data elements (source: ONC Standards Bulletin 2022-2).

USCDI v3 builds on v2 by adding two new data classes and new data elements within existing classes. The changes below follow the ONC Standards Bulletin.

New Data Classes in v3

  • Health Insurance Information: Coverage Status, Coverage Type, Relationship to Subscriber, Member Identifier, Subscriber Identifier, Group Number and Payer Identifier. Most EHRs capture insurance data for billing but do not expose it through standardized FHIR APIs.
  • Health Status/Assessments: Functional Status, Disability Status, Mental/Cognitive Status and Pregnancy Status.

New Data Elements in Existing Classes

  • Laboratory: Specimen Type and Result Status
  • Medications: Dose, Dose Unit of Measure, Indication and Fill Status
  • Patient Demographics/Information: Date of Death, Tribal Affiliation, Related Person's Name, Related Person's Relationship, Occupation and Occupation Industry
  • Procedures: Reason for Referral

Classes Carried Over from v2

Encounter Information, Clinical Tests and Diagnostic Imaging were added in USCDI v2, not v3. They remain required in v3. Systems moving straight from USCDI v1 to v3 meet them for the first time, which is why they still show up as gaps.

Complete USCDI v3 to FHIR Mapping

US Core 6.1.0 is the FHIR implementation guide built for USCDI v3, and HTI-1 adopted it for the certification API criterion. The table below lists all 19 USCDI v3 data classes, their data elements, and the US Core 6.1.0 profiles that carry them, following the official US Core 6.1.0 USCDI mapping. "Carried over" means the class existed before v2; the other labels show what changed.

Must Support is not the same as required. In US Core, Must Support means a server must be able to return the element when it has the data. Cardinality (for example 1..1) is what makes an element required in every instance. See our guide to FHIR profiles, extensions and Must Support. Some USCDI elements map to more than one profile or to an extension, for example Sex, Gender Identity and Tribal Affiliation on US Core Patient; the US Core 6.1.0 USCDI page lists each one.

USCDI v3 Data ClassData ElementsUS Core 6.1.0 Profile(s)Status in v3
Allergies and IntolerancesSubstance (Medication), Substance (Drug Class), ReactionUS Core AllergyIntoleranceCarried over
Assessment and Plan of TreatmentAssessment and Plan of Treatment, SDOH AssessmentUS Core CarePlan; for SDOH assessments: US Core Simple Observation, US Core Observation Screening Assessment, US Core QuestionnaireResponseCarried over
Care Team MembersName, Identifier, Location, Telecom, RoleUS Core CareTeamCarried over
Clinical NotesConsultation Note, Discharge Summary Note, History & Physical, Imaging Narrative, Laboratory Report Narrative, Pathology Report Narrative, Procedure Note, Progress NoteUS Core DocumentReference; US Core DiagnosticReport Profile for Report and Note ExchangeCarried over
Clinical TestsClinical Test, Clinical Test Result/ReportUS Core Observation Clinical Result; US Core DiagnosticReport Profile for Report and Note ExchangeAdded in v2
Diagnostic ImagingDiagnostic Imaging Test, Diagnostic Imaging ReportUS Core Observation Clinical Result; US Core DiagnosticReport Profile for Report and Note ExchangeAdded in v2
Encounter InformationEncounter Type, Encounter Diagnosis, Encounter Time, Encounter Location, Encounter DispositionUS Core Encounter; Encounter Diagnosis uses US Core Condition Encounter DiagnosisAdded in v2
GoalsPatient Goals, SDOH GoalsUS Core GoalCarried over
Health Insurance InformationCoverage Status, Coverage Type, Relationship to Subscriber, Member Identifier, Subscriber Identifier, Group Number, Payer IdentifierUS Core Coverage (payer as US Core Organization)New class in v3
Health Status/AssessmentsNew in v3: Functional Status, Disability Status, Mental/Cognitive Status, Pregnancy Status. Also in this class: Health Concerns, Smoking StatusUS Core Simple Observation, US Core Observation Screening Assessment, US Core QuestionnaireResponse, US Core Condition Problems and Health Concerns, US Core Observation Pregnancy Status, US Core Observation Pregnancy Intent, US Core Smoking Status ObservationNew class in v3
ImmunizationsImmunizationsUS Core ImmunizationCarried over
LaboratoryTests, Values/Results, plus new in v3: Specimen Type, Result StatusUS Core Laboratory Result Observation; US Core DiagnosticReport Profile for Laboratory Results Reporting; US Core SpecimenNew elements in v3
MedicationsMedications, plus new in v3: Dose, Dose Unit of Measure, Indication, Fill StatusUS Core MedicationRequest; US Core Medication; US Core MedicationDispense (Fill Status)New elements in v3
Patient Demographics/InformationFirst, Last, Middle and Previous Name, Suffix, Sex, Date of Birth, Race, Ethnicity, Gender Identity, Sexual Orientation, Preferred Language, Address, Previous Address, Phone Number, Email, plus new in v3: Date of Death, Tribal Affiliation, Related Person's Name, Related Person's Relationship, Occupation, Occupation IndustryUS Core Patient (with Race, Ethnicity, Sex, Tribal Affiliation and Gender Identity extensions); US Core Observation Sexual Orientation; US Core RelatedPerson; US Core Observation OccupationNew elements in v3
ProblemsProblems, Date of Diagnosis, Date of Resolution, SDOH Problems/Health ConcernsUS Core Condition Problems and Health ConcernsCarried over
ProceduresProcedure, SDOH Interventions, plus new in v3: Reason for ReferralUS Core Procedure; US Core ServiceRequest (Reason for Referral, SDOH Interventions)New element in v3
ProvenanceAuthor Time Stamp, Author OrganizationUS Core ProvenanceCarried over
Unique Device Identifier(s) for a Patient's Implantable Device(s)Unique Device Identifier(s)US Core Implantable DeviceCarried over
Vital SignsSystolic and diastolic blood pressure, body height, body weight, heart rate, respiratory rate, body temperature, pulse oximetry, inhaled oxygen concentration, BMI percentile (2 to 20 years), weight-for-length percentile (birth to 36 months), head circumference percentile (birth to 36 months)US Core Vital Signs and its specific profiles: Blood Pressure, Body Height, Body Weight, Heart Rate, Respiratory Rate, Body Temperature, Pulse Oximetry, Pediatric BMI for Age, Pediatric Weight for Height, Pediatric Head Occipital Frontal Circumference PercentileCarried over

Where Each New v3 Element Lives in FHIR

This table points to the exact place in US Core 6.1.0 for every element USCDI v3 added, checked against each profile page.

New v3 elementUS Core 6.1.0 profileWhere it goes
Health Insurance Information (7 elements)US Core CoverageSee the Coverage mapping image and example below
Functional, Disability and Mental/Cognitive StatusUS Core Observation Screening Assessment, Simple Observation, QuestionnaireResponseCoded Observation or the questionnaire answers
Pregnancy StatusUS Core Observation Pregnancy StatusObservation.value
Date of DeathUS Core PatientPatient.deceasedDateTime
Tribal AffiliationUS Core PatientUS Core Tribal Affiliation extension
Related Person's Name and RelationshipUS Core RelatedPersonRelatedPerson.name, RelatedPerson.relationship
Occupation and Occupation IndustryUS Core Observation OccupationJob code or text, plus the industry code or text in the same Observation
Dose and Dose Unit of MeasureUS Core MedicationRequestdosageInstruction.doseAndRate
IndicationUS Core MedicationRequestreasonCode or reasonReference
Fill StatusUS Core MedicationDispenseMedicationDispense.status
Specimen TypeUS Core SpecimenSpecimen.type
Result StatusUS Core Laboratory Result Observation, lab DiagnosticReportObservation.status, DiagnosticReport.status
Reason for ReferralUS Core ServiceRequestreasonCode or reasonReference

Profiles Teams Most Often Miss

  • Encounter Diagnosis is a Condition, not a field on Encounter. It uses the US Core Condition Encounter Diagnosis profile.
  • Pregnancy Status has its own profile (US Core Observation Pregnancy Status), and US Core 6.1.0 adds a separate Pregnancy Intent profile.
  • Fill Status comes from MedicationDispense, so a server that only exposes MedicationRequest misses it.
  • Specimen Type needs the US Core Specimen profile alongside lab Observations.
  • Reason for Referral and SDOH interventions use US Core ServiceRequest, not Procedure.
  • Related Person and Occupation need US Core RelatedPerson and the US Core Observation Occupation profile.
  • Clinical notes: US Core requires servers to support at least eight note types (consultation, discharge summary, history and physical, procedure, progress, imaging narrative, laboratory report narrative and pathology report narrative) and three DiagnosticReport categories (cardiology, pathology and radiology).
  • Screening and assessment data (PHQ-9, GAD-7, SDOH screenings) uses the Observation Screening Assessment and QuestionnaireResponse profiles. US Core has a dedicated Screening and Assessments guidance page.

Where Teams Most Often Fall Short

Based on our experience building EHR systems and working with healthcare organizations on compliance, these are the data classes where teams most often fall short.

Health Insurance Information

This is often the hardest new class. Most EHRs capture insurance data for billing, but few expose it through a standard FHIR Coverage API. The challenge is that insurance data is typically stored in billing-specific tables, not in the clinical data model. Building a FHIR facade over billing data requires careful mapping to the US Core Coverage profile:

{
  "resourceType": "Coverage",
  "meta": {
    "profile": ["http://hl7.org/fhir/us/core/StructureDefinition/us-core-coverage"]
  },
  "identifier": [{
    "type": {
      "coding": [{
        "system": "http://terminology.hl7.org/CodeSystem/v2-0203",
        "code": "MB",
        "display": "Member Number"
      }]
    },
    "system": "http://example.org/fhir/memberidentifier",
    "value": "88800933501"
  }],
  "status": "active",
  "type": {
    "coding": [{
      "system": "https://nahdo.org/sopt",
      "code": "3712",
      "display": "PPO"
    }]
  },
  "subscriberId": "888009335",
  "beneficiary": { "reference": "Patient/example" },
  "relationship": {
    "coding": [{
      "system": "http://terminology.hl7.org/CodeSystem/subscriber-relationship",
      "code": "self"
    }]
  },
  "period": { "start": "2026-01-01" },
  "payor": [{
    "reference": "Organization/example-payer",
    "display": "Example Health Plan"
  }],
  "class": [
    {
      "type": { "coding": [{ "system": "http://terminology.hl7.org/CodeSystem/coverage-class", "code": "group" }] },
      "value": "GRP-789",
      "name": "Example Employer Group"
    },
    {
      "type": { "coding": [{ "system": "http://terminology.hl7.org/CodeSystem/coverage-class", "code": "plan" }] },
      "value": "GOLD-2026",
      "name": "Example Gold PPO"
    }
  ]
}

This example follows the official US Core 6.1.0 Coverage example. Member ID goes in identifier with type MB, Coverage Type uses the payer typology codes, Group Number is the group class, and the payer is a US Core Organization, which carries the Payer Identifier.

Encounter Information

Encounter Information was added in v2 and stays required in v3. Its elements for encounter diagnosis, disposition, and location mean that systems which previously stored minimal encounter data must now capture and expose structured encounter contexts. This is particularly challenging for organizations using EHR integration patterns that aggregate encounter data from multiple source systems.

Clinical Tests

Clinical Tests (added in v2) covers tests that are not laboratory tests, such as an electrocardiogram or a visual acuity exam. These results are often captured in clinical notes rather than structured observations. US Core expects them as US Core Observation Clinical Result resources, with a DiagnosticReport for the report. The extraction challenge here overlaps with the 80/20 unstructured data problem.

Health Status/Assessments

Functional status, disability status, mental/cognitive status and pregnancy status are often captured using validated instruments (PHQ-9, GAD-7, PROMIS). US Core represents these with the Observation Screening Assessment, Simple Observation and QuestionnaireResponse profiles, with LOINC codes. Pregnancy Status has its own profile. Many systems store the assessment as a document rather than discrete coded values.

Testing with Inferno

Inferno (inferno.healthit.gov) is the open-source FHIR testing tool used in the ONC Certification Program. For certification, the ONC Certification (g)(10) Standardized API Test Kit is an approved test method for the § 170.315(g)(10) criterion. It tests US Core resources together with SMART App Launch and Bulk Data. Inferno also offers a standalone US Core test kit that is handy during development. Because those tests check profile constraints, it helps to understand how FHIR profiles, extensions and Must Support work before your first run.

Setting Up Inferno Testing

  1. Deploy Inferno: Run Inferno locally using Docker or use the hosted version at inferno.healthit.gov
  2. Configure your FHIR server endpoint: Point Inferno at your FHIR server's base URL
  3. Configure SMART credentials: Inferno needs client credentials for testing authenticated endpoints
  4. Select the test kit and version: Use the (g)(10) test kit for certification and the US Core test kit for day-to-day checks. US Core 6.1.0 is the USCDI v3 baseline. ONC's 2026 Standards Version Advancement Process (SVAP) also approves US Core 9.0.0 as a voluntary newer version for (g)(10).
  5. Run tests incrementally: Start with Patient, then expand to other resource types

What a passing run produces

Keep these artifacts from every passing run, so you can show what was tested and repeat it:

  • The Inferno session export (results for every test)
  • The test kit name and version. The latest ONC Certification (g)(10) Standardized API Test Kit release when we checked on 15 October 2026 was v8.0.7 (released 9 September 2026).
  • The US Core version tested (6.1.0 for the USCDI v3 baseline)
  • The list of skipped or omitted tests, with the reason for each
  • The sample patient bundle used for the run

Common Inferno Failures and Fixes

Failure CategoryCommon CauseFix
Missing Must Support elementsRequired fields not populatedEnsure seed data includes all MS elements
Invalid code systemWrong terminology OID or URLUse exact system URLs from US Core profiles
Search parameter not supportedMissing search implementationImplement all US Core required search params
Incorrect CapabilityStatementServer metadata outdatedRegenerate CapabilityStatement from actual capabilities
SMART auth failuresToken scoping issuesVerify scope handling matches SMART spec
Provenance missingServer does not return Provenance for the resources it exposesSupport US Core Provenance (author, author time stamp, author organization) and let clients fetch it with _revinclude=Provenance:target, as the US Core Basic Provenance guidance shows
Missing profile for a v3 elementFill Status, Specimen Type or Reason for Referral only modelled on the main resourceAdd US Core MedicationDispense, Specimen and ServiceRequest endpoints

Implementation Timeline

For organizations not yet fully compliant, here is a realistic implementation timeline:

Phase 1: Gap Assessment (Month 1)

  • Run Inferno US Core test suite against current implementation
  • Document all failing tests by data class
  • Map failures to USCDI v3 data elements
  • Prioritize the v3 additions first: Health Insurance Information, Health Status/Assessments, and the new Laboratory, Medications, Patient Demographics and Procedures elements. If you are moving up from v1, add the v2 classes (Encounter, Clinical Tests, Diagnostic Imaging) to the list.

Phase 2: Data Model Updates (Month 2-3)

  • Update database schema to support new data elements
  • Build or update FHIR mappings for Coverage, RelatedPerson, Specimen, MedicationDispense, ServiceRequest, and the Occupation, Pregnancy Status and screening Observations
  • Implement terminology bindings (correct LOINC, SNOMED CT, CVX codes)
  • Ensure Provenance resources are generated for all writes

Phase 3: API Development (Month 3-5)

  • Implement or update FHIR endpoints for the new resource types (Coverage, RelatedPerson, Specimen, MedicationDispense, ServiceRequest)
  • Add required search parameters for expanded data classes
  • Update CapabilityStatement to reflect new capabilities
  • Implement proper SMART on FHIR scope handling for new resources

Phase 4: Testing and Validation (Month 5-6)

  • Run the full Inferno (g)(10) test kit -- target zero failures
  • Validate all resource instances against US Core profiles using the HL7 FHIR Validator
  • Conduct integration testing with downstream consumers
  • Perform security review of new endpoints and data access

Phase 5: Certification and Deployment (Month 7+)

  • Submit for ONC certification testing if applicable
  • Deploy to production with monitoring for new data classes
  • Set up observability dashboards for USCDI v3 API usage patterns

USCDI v3 vs USCDI v3.1: What Changed in 2025

USCDI v3.1 is USCDI v3 with a small set of patient demographic elements removed or changed. ONC released it in 2025 after an enforcement discretion notice dated March 21, 2025 (ONC notice EDN2025.01). Everything else in USCDI v3, including the two new data classes and the FHIR mappings in this guide, stays the same.

ItemUSCDI v3USCDI v3.1 and the March 2025 notice
Sexual OrientationData element in Patient Demographics/InformationRemoved. Notice EDN2025.01 gave temporary enforcement relief, so developers could certify without showing support for this element. The notice did not change the regulation.
Gender IdentityData element in Patient Demographics/InformationRemoved, on the same terms as Sexual Orientation.
SexData element in Patient Demographics/InformationChanged. For the § 170.315(a)(5) demographics criterion, the notice accepts recording sex with SNOMED CT 248152002 (Female) and 248153007 (Male).
Sex Parameter for Clinical Use, Name to Use, PronounsPart of the § 170.315(a)(5) demographics criterionIncluded in the same temporary relief for that criterion.
Regulatory statusAdopted by HTI-1 at 45 CFR 170.213The HTI-5 proposed rule of December 2025 proposes to adopt USCDI v3.1 (Federal Register). ONC also lists v3.1 in its SVAP Approved Standards for 2025.

The notice set a term of twelve months from March 21, 2025, or until HHS finished a rule revising the regulations, whichever came first. That twelve-month term ran to March 21, 2026. When we checked ONC's enforcement discretion page on 17 October 2026 it still listed EDN2025.01 but did not say whether the relief was extended, and HTI-5 is still a proposal. Confirm the current position with ONC or your certification body before you plan work around it. For most teams the practical step is the same either way: keep the data you already capture, keep the FHIR profiles working, and confirm with your ONC-Authorized Certification Body which version your test plan uses.

Which USCDI Version Comes After v3

USCDI v3 is still the baseline version named in the certification regulations, and newer versions are optional for now. ONC publishes a draft USCDI each January and a final version each July (ONC Standards Bulletin 2026-1).

  • SVAP: The Standards Version Advancement Process lets certified developers upgrade voluntarily. ONC added USCDI v5 and USCDI v3.1 to the SVAP Approved Standards for 2025, usable from August 29, 2025.
  • Draft USCDI v7: Released January 29, 2026, with 30 proposed data element additions, including Tobacco Use as a revised form of Smoking Status. ONC's normal schedule is a final version each July, so check the ONC Interoperability Standards Platform for the latest final version.
  • Other programs: CMS-0057-F and TEFCA both require the ability to exchange USCDI data elements, so the version your EHR supports shapes what payers and networks can receive.

If you need help moving an EHR or data platform to USCDI v3 or a later version, our EHR integration services team works on the data model, the FHIR API and the test runs together.

The Regulatory Context

Understanding where USCDI v3 fits in the regulatory landscape helps prioritize implementation:

  • ONC HTI-1 Final Rule: ONC released it in December 2023 and it was published in the Federal Register in January 2024 (89 FR 1192). It made USCDI v3 the baseline for the certification program from 1 January 2026, when USCDI v1 expired, and adopted US Core 6.1.0 for the (g)(10) API criterion. This is the primary regulatory driver.
  • CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F): Impacted payers must share claims and encounter data, USCDI data, and prior authorization information through a Provider Access API by 1 January 2027. CMS lists USCDI v3 and US Core 6.1.0 among the standards for these APIs, with USCDI v1 and US Core 3.1.1 marked as expiring.
  • TEFCA (Trusted Exchange Framework and Common Agreement): The national framework for exchange between networks. Data shared through TEFCA usually comes from certified EHRs, so their USCDI v3 support shapes what can be shared.
  • HTI-5 (proposed): A December 2025 proposal to remove 34 certification criteria and revise 7. See our HTI-5 guide.
  • HTI-2 and USCDI v4: The 2024 HTI-2 proposal to require USCDI v4 by 2028 was withdrawn in December 2025, so v3 stays the baseline for now.
  • 21st Century Cures Act: The underlying legislation mandating standardized APIs and prohibiting information blocking. USCDI defines the minimum data set that must be available through these APIs.

Practical Checklist for USCDI v3 Compliance

  1. Baseline: Run the Inferno (g)(10) test kit against US Core 6.1.0 and record every failure by data class
  2. Map v3 gaps: Use the 19-class table above to find elements you cannot yet return through the FHIR API
  3. Health Insurance Information: Expose US Core Coverage with member ID, subscriber ID, relationship, group and payer
  4. Health Status/Assessments: Return functional, disability and mental/cognitive status and pregnancy status as coded Observations
  5. Medications: Add dose, dose unit and indication to MedicationRequest, and expose MedicationDispense for fill status
  6. Laboratory: Add result status and link a US Core Specimen for specimen type
  7. Patient Demographics: Add date of death, tribal affiliation, RelatedPerson and the Occupation Observation
  8. Procedures: Expose ServiceRequest for reason for referral
  9. v2 classes: Confirm Encounter (with Condition Encounter Diagnosis), Clinical Tests and Diagnostic Imaging if you came from v1
  10. CapabilityStatement: Make your server metadata list every new profile and search parameter
  11. Retest and monitor: Rerun Inferno until it passes, then track production API use for the new resources

For step-by-step US Core implementation, see our FHIR US Core implementation guide. Before you apply for certification, a certification readiness review can find the gaps first.

Need help closing USCDI v3 gaps in your FHIR API? Explore our Healthcare Interoperability Solutions, including FHIR integration services and Inferno test readiness. Talk to our team to get started.

Frequently Asked Questions

Is USCDI v3 compliance mandatory for all healthcare organizations?

USCDI v3 compliance is mandatory for ONC-certified health IT. If your EHR or health IT product holds ONC certification (or plans to), you must support USCDI v3. Organizations that use certified health IT (hospitals, clinics) are indirectly affected because their vendor must provide the capabilities. Non-certified applications (analytics tools, patient engagement apps) are not directly regulated but benefit from supporting USCDI v3 for interoperability.

What happens if we are not compliant by January 2026?

For ONC-certified health IT developers, non-compliance risks certification status. For healthcare organizations using certified EHRs, the vendor is responsible for providing USCDI v3 capabilities. If your vendor has not updated, escalate through their product roadmap process. There is no explicit penalty for individual provider organizations, but information blocking regulations require making USCDI data elements available when requested.

How does USCDI v3 relate to US Core profiles?

USCDI defines the data elements (what data). US Core profiles define how to represent those elements in FHIR (the format). US Core is updated each year to follow new USCDI versions. US Core 6.1.0 is the release built for USCDI v3 and the one HTI-1 adopted. Later releases follow later USCDI versions, and ONC's 2026 SVAP approves US Core 9.0.0 as a voluntary option. Always implement against the US Core profiles, not against USCDI data classes directly.

Vendor pages can lag behind what a server declares. In our PointClickCare API guide, the FHIR home page documents US Core 3.1.1 and USCDI v1, while the live CapabilityStatement we read in October 2026 also declares US Core 6.1.0.

Is USCDI v4 coming? Should we wait?

USCDI v4 was published by ONC in July 2023, but no rule currently requires it. The HTI-2 proposed rule (August 2024) would have required v4 by January 1, 2028, and ASTP/ONC withdrew that proposal in December 2025. USCDI v3 therefore remains the required baseline, with no set end date. Do not wait -- implement v3 now and plan for incremental v4 additions later. Each USCDI version builds on the previous one, so v3 work is not wasted.

How do we handle data elements we do not currently capture?

USCDI requires the capability to capture, store, and exchange data elements -- not that every patient record must contain them. If your system can accept and return Health Insurance Information when it exists, you are compliant even if many patient records lack insurance data. The key is capability, not completeness.

Can we use Bulk Data Export for USCDI v3 compliance?

Bulk Data Export ($export) is part of the same ONC criterion, § 170.315(g)(10), which covers both single-patient and population (multi-patient) access, and the Inferno (g)(10) test kit tests it. Certified developers therefore need both. Single-patient access uses (SMART on FHIR patient-level APIs). CMS also lists Bulk Data among the standards for the payer Provider Access API.

Ready to scale?

Talk to our healthcare engineering team about building, integrating, and shipping faster.

Frequently Asked Questions

What is USCDI v3 and why does it matter for EHR compliance?

USCDI v3 (United States Core Data for Interoperability, version 3) is the data standard that certified health IT systems must support as of January 2026 under the ONC HTI-1 Final Rule. It is required for health IT certified under the ONC Health IT Certification Program, for the criteria that reference USCDI, such as § 170.315(b)(1), (e)(1), (g)(9) and (g)(10). An app that only connects to a certified EHR is not itself required to support USCDI v3, though it will receive data in that shape. Every v3 data element maps to a specific FHIR US Core profile for API exposure.

What changed from USCDI v2 to USCDI v3?

USCDI v3 adds two new data classes: Health Insurance Information (coverage status and type, relationship to subscriber, member, subscriber and payer identifiers, and group number) and Health Status/Assessments (functional, disability, mental/cognitive and pregnancy status). It also adds new elements to existing classes: specimen type and result status in Laboratory; dose, dose unit, indication and fill status in Medications; date of death, tribal affiliation, related person, occupation and occupation industry in Patient Demographics; and reason for referral in Procedures. In total v3 has 94 data elements in 19 classes, according to the ONC Standards Bulletin 2022-2.

Which USCDI v3 data class is hardest to implement?

Health Insurance Information is often the hardest. Most EHRs capture insurance data for billing, but few expose it through a standard FHIR Coverage API, because insurance data typically lives in billing tables rather than the clinical data model. Encounter Information (added in v2) is another common gap, because many systems still lack the structured encounter detail USCDI expects.

How do USCDI v3 data elements map to FHIR US Core profiles?

US Core 6.1.0 maps all 19 USCDI v3 data classes to FHIR profiles. Key ones: Health Insurance Information to US Core Coverage; Health Status/Assessments to US Core Simple Observation, Observation Screening Assessment, QuestionnaireResponse and the Pregnancy Status profile; Encounter Information to US Core Encounter, with Encounter Diagnosis in US Core Condition Encounter Diagnosis; Laboratory to Laboratory Result Observation, the lab DiagnosticReport and US Core Specimen; Medications to MedicationRequest and MedicationDispense; Patient Demographics to US Core Patient, RelatedPerson and the Occupation and Sexual Orientation Observations; Procedures to US Core Procedure and ServiceRequest; and Clinical Notes to DocumentReference and DiagnosticReport.

How can a health IT vendor test and close USCDI v3 compliance gaps before certification?

Map every USCDI v3 data element to its FHIR US Core profile, audit where your system fails to capture, store, or expose that data through APIs, and validate using the Inferno ONC Certification (g)(10) Standardized API Test Kit. The most common work involves building a FHIR Coverage facade over billing tables and adding the MedicationDispense, Specimen, RelatedPerson and ServiceRequest profiles. Nirmitee's healthcare engineering teams have done this gap analysis and remediation while building EHR systems and supporting compliance programs.

How does Nirmitee.io approach healthcare software development?

Nirmitee.io follows a healthcare-first engineering approach — every solution is built with HIPAA compliance, HL7/FHIR interoperability standards, and clinical workflow requirements at the core. We combine domain expertise with modern engineering practices to deliver production-ready systems.

What is USCDI v3.1?

USCDI v3.1 is USCDI v3 with the Sexual Orientation and Gender Identity data elements removed and the Sex data element changed. ONC released it in 2025 after an enforcement discretion notice dated March 21, 2025. HTI-5, proposed in December 2025, would adopt it in the regulations. The other data classes and elements are the same as v3.

How many data elements and classes are in USCDI v3?

USCDI v3 has 94 data elements in 19 data classes. Compared with v2 it adds two data classes, Health Insurance Information and Health Status/Assessments, and 24 data elements.

When did USCDI v3 become required?

Under the HTI-1 Final Rule, USCDI v3 is the required version for ONC certification criteria that reference USCDI from January 1, 2026. Before that date developers could certify to v1 or v3. ONC notice EDN2025.06 then gave developers until February 28, 2026 to finish the HTI-1 updates.

Can a health IT developer use USCDI v5 instead of v3?

Yes, on a voluntary basis. ONC added USCDI v5 to the SVAP Approved Standards for 2025, so certified developers may upgrade to it from August 29, 2025. The certification regulations still name v3 as the baseline.

Which FHIR guide supports USCDI v3?

US Core 6.1.0 is the HL7 FHIR implementation guide that maps USCDI v3. The ONC (g)(10) Inferno test kit tests against it.
Share