Also Carequality framework, Carequality implementer
Carequality is not a network a provider joins. It is the agreement between networks. An EHR vendor, a health information exchange or a records service becomes an implementer, signs the framework’s connected agreement, and from then on its participants can query, and be queried by, the participants of every other implementer. Epic, Oracle Health, athenahealth, eClinicalWorks and most of the large vendors connect their customers this way, which is why a single query can reach hospitals and practices that have never heard of the organization asking.
The framework fixes three things that otherwise have to be negotiated one hospital at a time:
- The legal terms. One agreement, with the same obligations for everyone, in place of a data-sharing contract per pair of organizations. This is what EpicCare Link does not solve: each health system still signs its own agreement with each agency.
- The permitted purposes. Treatment is the purpose nearly every participant responds to. The framework’s policies name others, with narrower response obligations, and a query must state which one it is made under; see treatment purpose of use.
- The technical standard. Patient discovery and document query over the IHE profiles, returning C-CDA documents. The same request works against every responder.
For an agency the practical consequence is the one described under network query: a treating provider can ask every connected organization for a patient’s documents at once, and receive them, without a portal account at any of them. The framework is also how CommonWell participants and Carequality participants reach each other, and it sits alongside TEFCA, the federal framework that is growing beside it.
