Generated by GPT-5-mini| United States Core Data for Interoperability | |
|---|---|
| Name | United States Core Data for Interoperability |
| Established | 2020 |
| Jurisdiction | United States Department of Health and Human Services |
| Related | Office of the National Coordinator for Health Information Technology |
United States Core Data for Interoperability is a federal policy and technical specification intended to standardize clinical data exchange in the United States to improve patient access to electronic health information. It was developed to align federal programs, private sector initiatives, and national standards bodies to facilitate interoperability across health systems, payers, and health information exchanges. The initiative sits at the intersection of regulatory action and health information technology innovation, involving stakeholders from federal agencies, standards organizations, and industry consortia.
The program was promulgated under the auspices of the United States Department of Health and Human Services and coordinated with the Office of the National Coordinator for Health Information Technology, drawing on work by Health Level Seven International, National Institute of Standards and Technology, and the Centers for Medicare & Medicaid Services. It defines a core set of data elements and implementation guides to support APIs, align with the 21st Century Cures Act, and integrate with standards maintained by HL7 FHIR, Consolidated Clinical Document Architecture, and related profiles developed by Integrating the Healthcare Enterprise. Stakeholders including American Medical Association, American Hospital Association, Kaiser Permanente, Mayo Clinic, and private vendors such as Epic Systems Corporation and Cerner Corporation have engaged in technical and policy review.
Development began amid policy shifts following passage of the 21st Century Cures Act and regulatory actions by the Centers for Medicare & Medicaid Services and the Office of the National Coordinator for Health Information Technology. Early drafts incorporated recommendations from Health Level Seven International task forces and pilot work led by regional initiatives like CommonWell Health Alliance and Carequality. Federal advisory committees including the Health Information Technology Advisory Committee and stakeholder convenings with organizations such as the American Medical Informatics Association and National Association of Community Health Centers shaped use cases. The specification evolved through public comment periods, interoperability challenges akin to the HITECH Act rollout, and coordination with standards bodies including IHE International and SNOMED International.
The framework leverages core standards including HL7 FHIR resources, terminologies from SNOMED CT, code systems from the Centers for Disease Control and Prevention like ICD-10-CM, and value sets maintained by the National Library of Medicine. Implementation artifacts reference APIs patterned after profiles developed by Argonaut Project and testing suites from IHE International Connectathons. Security is tied to protocols endorsed by National Institute of Standards and Technology guidance and uses authentication models compatible with OAuth 2.0 and OpenID Connect deployments used by healthcare identity providers such as DirectTrust. Terminology bindings incorporate mappings to LOINC and quality measure frameworks influenced by National Quality Forum specifications and Quality Payment Program reporting.
Adoption occurred through rulemaking by the Centers for Medicare & Medicaid Services and certification criteria administered via the Office of the National Coordinator for Health Information Technology certification program, affecting vendors like Allscripts and public health agencies including Centers for Disease Control and Prevention programs. Health systems including Johns Hopkins Hospital, Cleveland Clinic, and regional health information organizations tested interoperability using exchanges established by partners such as Carequality and CommonWell Health Alliance. Payer integration efforts involved entities like UnitedHealth Group and Blue Cross Blue Shield Association, while consumer-facing implementations integrated with platforms from Apple Inc., Google LLC, and patient portals at institutions such as Mount Sinai Health System.
Privacy and security considerations reference federal statutes including the Health Insurance Portability and Accountability Act and coordination with the Federal Trade Commission on data protection oversight. Governance mechanisms rely on multi-stakeholder bodies and testing frameworks similar to those used by Integrating the Healthcare Enterprise and enforcement integrated with rulemaking from the Department of Health and Human Services Office for Civil Rights. Cryptographic and identity standards draw on National Institute of Standards and Technology publications and federated trust models informed by DirectTrust and industry consortia governance used by CommonWell Health Alliance and Carequality.
Proponents cite improved patient access, reduced information blocking, and greater API-driven innovation benefiting organizations like Epic Systems Corporation, Cerner Corporation, and tech entrants including Apple Inc. and Google LLC. Critics argue that gaps remain in semantic interoperability, equitable access for safety-net providers such as Community Health Centers and Indian Health Service sites, and the potential for increased data flow to raise privacy concerns highlighted by consumer advocates and regulators including the Federal Trade Commission. Academic evaluations by institutions like Harvard Medical School and Johns Hopkins University have documented variable implementation fidelity, while policy analysts referencing Congress of the United States hearings and reports from Office of the Inspector General (United States Department of Health and Human Services) have urged stronger enforcement and clearer incentives for longitudinal data exchange.
Category:Health information technology