Written and maintained by CASRAI Editorial Board
Last updated
Short answer: CommonWell Health Alliance (often referred to simply as CommonWell) is a vendor-neutral, non-profit 501(c)(6) health information exchange trade association and a federally designated Qualified Health Information Network (QHIN) under the Trusted Exchange Framework and Common Agreement (TEFCA). Embedded natively inside major Electronic Health Record (EHR) systems—including Oracle Health (Cerner) EHR, MEDITECH EHR, athenahealth, Greenway Health, and Altera Digital Health—CommonWell provides centralized patient identity matching, an automated Record Locator Service (RLS), and clinical data brokering across all 50 U.S. states.
What Is CommonWell? Founding Governance and TEFCA QHIN Status
Established in 2013 by a coalition of competing EHR vendors to solve cross-vendor clinical record fragmentation, CommonWell Health Alliance was built on the premise that health data exchange services should be embedded directly inside the clinician’s native EHR workflow at negligible incremental cost rather than requiring custom point-to-point hospital interfaces.
In February 2024, following rigorous technical and governance testing overseen by the Assistant Secretary for Technology Policy / Office of the National Coordinator for Health IT (ASTP/ONC) and the Recognized Coordinating Entity (The Sequoia Project), CommonWell achieved production designation as an official TEFCA Qualified Health Information Network (QHIN). As a QHIN, CommonWell connects its member provider sites directly to the nationwide TEFCA backbone alongside other designated QHINs (such as Health Gorilla, eHealth Exchange, Epic Nexus, KONZA, Kno2, and MedAllies).
How CommonWell Works in Practice: The Four Core Network Services
Unlike pure policy frameworks that leave patient discovery to manual geographic searches, CommonWell operates a centralized cloud-hosted service layer (built with technical infrastructure partner ELLKAY) that executes four sequential functions whenever a patient presents at a participating clinic or hospital:
- Patient Registration & Enterprise Master Person Index (EMPI) Matching: When a patient registers at a CommonWell-enabled EHR site, the EHR transmits core demographic attributes via HL7 v2 / PIX / PDQ or FHIR APIs to CommonWell’s centralized identity service, which performs probabilistic and deterministic matching to link the local medical record number (MRN) to a network-wide CommonWell Person ID.
- Automated Record Locator Service (RLS): CommonWell maintains a centralized pointer directory—the Record Locator Service—that records every participating organization where that matched patient has received care. When a clinician opens the patient’s chart, the RLS automatically returns the complete list of external facilities holding clinical records for that individual, eliminating the need for clinical staff to manually ask or guess which hospitals or states the patient previously visited.
- Governance and Consent Management: Enforces network-wide HIPAA Treatment, Payment, and Health Care Operations (TPO) exchange policies, patient opt-out preferences, and TEFCA Individual Access Services (IAS) patient-directed query rules.
- Trusted Data Broker (Query and Retrieve): When the clinician or an automated pre-visit workflow requests external records, CommonWell’s data broker queries the source EHR gateways using Integrating the Healthcare Enterprise (IHE) Cross-Community Access (XCA) profiles and HL7 FHIR Release 4 (R4) RESTful APIs, retrieving Consolidated Clinical Document Architecture (HL7 C-CDA R2.1) continuity-of-care summaries and discrete USCDI FHIR resources directly into the local EHR reconciliation queue.
CommonWell vs. Carequality vs. TEFCA: Architectural Comparison
Health system informatics architects and clinical data governance officers frequently evaluate how CommonWell interacts with Carequality and TEFCA:
| Architectural Dimension | CommonWell Health Alliance | Carequality (The Sequoia Project) | TEFCA (ONC / 21st Century Cures Act) |
|---|---|---|---|
| Organizational Role | 501(c)(6) non-profit trade association operating centralized network infrastructure AND a designated TEFCA QHIN. | Nationwide network-to-network interoperability legal and technical trust framework connecting “Implementers.” | Federal overarching legal Common Agreement and QHIN Technical Framework (QTF) connecting designated QHINs nationwide. |
| Centralized MPI & Record Locator Service (RLS) | Yes: Operates a centralized EMPI and automated Record Locator Service that discovers all care locations for a patient without manual org selection. | No central RLS: Relies on a shared endpoint directory; querying systems typically query known or geographically proximate organizations unless paired with an RLS aggregator. | Brokered QHIN-to-QHIN discovery: Routes IHE XCPD/XCA and FHIR R4 queries across participating QHINs under QTF rules. |
| Primary Native EHR Footprint | Oracle Health (Cerner), MEDITECH Expanse, athenahealth, Greenway Health, CPSI/TruBridge, Altera Digital Health, eClinicalWorks, and post-acute EHRs. | Epic (Care Everywhere), eHealth Exchange, Surescripts, NextGen, PCC, and CommonWell (as a bridged Carequality Implementer). | All member networks connected through designated QHINs (including CommonWell, Epic Nexus, Health Gorilla, eHealth Exchange, Kno2, KONZA). |
| Technical Transport Standards | IHE PIXv3 / PDQv3 / XCA (SOAP/XML C-CDA R2.1) and HL7 FHIR R4 RESTful APIs. | IHE XCPD / XCA document exchange and Carequality FHIR Implementation Guide. | QHIN Technical Framework (QTF) IHE XCPD/XCA plus TEFCA Facilitated FHIR Implementation Guide. |
Where CommonWell Matters for Clinical Research and Real-World Data (RWD)
- Cross-Network Completeness via the CommonWell–Carequality Bridge and TEFCA: Because CommonWell has operated a bi-directional connectivity bridge with Carequality since 2016 and now exchanges directly as a TEFCA QHIN, a clinician at an Oracle Health or MEDITECH hospital can seamlessly pull longitudinal medication histories, laboratory results, and problem lists from Epic health systems and ambulatory clinics nationwide.
- Permitted Exchange Purposes and Research Governance: Under CommonWell and TEFCA operating policies, routine network queries are strictly bound to authorized Exchange Purposes (primarily Treatment, Individual Access Services [IAS], Public Health, and Healthcare Operations/Payment). Clinical trial sponsors or decentralized clinical trial (DCT) platforms cannot query CommonWell directly for commercial cohort mining under a Treatment purpose code; instead, research data retrieval relies on HIPAA-compliant Individual Access Services (IAS) where consented study participants authenticate and authorize retrieval of their own longitudinal records.
Common Misunderstandings About CommonWell
- “CommonWell permanently stores all of a patient’s clinical notes in a central database”: False. CommonWell’s central infrastructure stores demographic identity attributes and record location pointers in its Record Locator Service (RLS); the actual clinical documents (C-CDAs and FHIR resources) remain stored at the originating healthcare provider’s EHR and are fetched on demand via the Trusted Data Broker when an authorized query occurs.
- “Epic hospitals cannot exchange records with CommonWell members”: False. Through both the Carequality–CommonWell bridge and TEFCA QHIN-to-QHIN exchange (between CommonWell QHIN and Epic Nexus QHIN), Epic organizations and CommonWell member sites exchange millions of clinical documents daily.
Frequently Asked Questions
What is CommonWell?
CommonWell Health Alliance is a vendor-neutral 501(c)(6) non-profit trade association founded in 2013 by leading EHR developers (including Oracle Health/Cerner, MEDITECH, athenahealth, CPSI/TruBridge, Greenway Health, and Altera) and designated as a Qualified Health Information Network (QHIN) under the federal Trusted Exchange Framework and Common Agreement (TEFCA). It provides nationwide patient identity matching, a centralized Record Locator Service (RLS), and clinical document/FHIR data brokering across tens of thousands of U.S. care sites.
How does CommonWell differ from Carequality?
CommonWell operates centralized shared network infrastructure—including a central Master Person Index (EMPI), a centralized Record Locator Service (RLS) that automatically tracks which clinics hold records for a patient, and a central data broker. Carequality is a legal and technical trust framework (without a central MPI/RLS) that connects disparate networks; CommonWell and Carequality maintain a bi-directional bridge and both participate in TEFCA.
Sources
- CommonWell Health Alliance — CommonWell Service Adopter Technical Specifications & Record Locator Service Architecture
- CommonWell Health Alliance — CommonWell–Carequality Bi-Directional Interoperability & TEFCA QHIN Overview
- Assistant Secretary for Technology Policy / ONC — Trusted Exchange Framework and Common Agreement (TEFCA) QHIN Technical Framework
