For most of the past fifteen years, health information exchange has largely meant moving documents. A provider would request, or a system would push, a structured clinical document — typically a Consolidated Clinical Document Architecture (C-CDA) file — that bundled a patient’s summary into one package. That model connected the industry and remains widely used. But a quieter, consequential shift is underway: toward querying discrete data elements rather than whole documents.
What changes with element-level exchange
A document-based request returns a container; the receiving system must then parse it to find the few fields a clinician actually needs — the latest hemoglobin A1c, an active medication list, a recent blood pressure. Element-level exchange, built on FHIR’s resource model, lets a system ask for exactly those items and receive them in a form software can use immediately, without unpacking a larger file.
Why both will coexist
This is not a clean replacement. Document exchange is mature, broadly deployed, and well suited to transferring a comprehensive summary — for example, when a patient changes primary-care practices. Element-level FHIR exchange shines for targeted, real-time needs and for powering applications. For years to come, Arizona organizations will run both patterns side by side, choosing the right tool for each use case.
The governance dimension
The shift is not purely technical. Granular access raises sharper questions about minimum necessary disclosure, about which permitted purposes justify which queries, and about how consent decisions apply to individual data elements rather than whole documents. National frameworks are advancing FHIR-based exchange precisely because the standards have matured enough to support it — but the policy scaffolding has to keep pace.
What to do about it
For Arizona stakeholders, the practical message is to plan for a dual-pattern future rather than betting on a single architecture. Investments in FHIR capability are well placed; so is continued support for document exchange that is already delivering value. AzHeC’s Standards work area explains both patterns in plain language, and our Network coverage addresses how they fit into statewide exchange.