By Eric Andrew Kristof, RN, CAHIMS | Healthcare IT Professional | HIMSS Arkansas Chapter Member
About This Series: The HIMSS Word of The Day is a running blog series drawing from the HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025) — the authoritative reference for healthcare IT professionals and the primary study resource for CAHIMS and CPHIMS certification. Each post paraphrases the term in plain language, grounds it in real-world healthcare IT context, and adds a bedside nursing perspective you won’t find in a textbook.
📖 The Term: DAF (Data Access Framework)
Source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025)
🔍 Plain-Language Definition
The HIMSS Dictionary describes the Data Access Framework (DAF) as an HL7 initiative that recommends standards for representing and transmitting data, organized around a “Query Stack” that separates the layers of data access. It adds that the DAF FHIR Implementation Guide gives requirements for queries, query results, transport, and the security and privacy controls needed for data access.
HL7’s own DAF pages add some context. The introduction page describes DAF as an effort of the ONC Standards and Interoperability (S&I) Framework that uses FHIR-based profiles to standardize how data is queried, returned, transported, and secured. The implementation guide itself calls itself a U.S. Realm specification prepared on behalf of the Office of the National Coordinator for Health IT (ONC), published as a Draft Standard for Trial Use (DSTU) that is based on FHIR DSTU 2. The dictionary’s attribution to HL7 reflects where the guide was published, while the initiative itself was sponsored by ONC. These pages were read through a summarizing fetch tool, so exact wording is worth confirming at the source.
| Item | Detail |
|---|---|
| What it is | An ONC-sponsored initiative and an HL7 FHIR implementation guide for standardized data access |
| Organizing idea | The Query Stack, which separates the layers of a data request |
| Layers | Queries, query results, transport requirements, and security and privacy controls |
| Roles | DAF Requestor (the client) and DAF Responder (the server) |
| FHIR base | FHIR DSTU 2 for the main implementation guide |
| Where it went | HL7 says the Argonaut Data Query guide superseded DAF and that US Core descended from Argonaut |
| Relation to HIMSS | None verified for this post, so none is claimed |
⚠️ Exam Alert: DAF is a data access initiative and implementation guide, not a software product, a data warehouse, or a messaging standard such as HL7 V2. It is also not the same as FHIR, which is the underlying standard, or US Core, which later became the main U.S. FHIR profile set. CAHIMS and CPHIMS come from HIMSS, not from HL7 or ONC.
🌐 Why It Matters: Real-World Healthcare IT Context
There is little peer-reviewed literature that discusses DAF by name, and a PubMed search for the abbreviation returned mostly unrelated papers, so this section relies on HL7 specification pages and an ONC project page found through search, rather than on studies.
The problem it addressed. The HL7 introduction page describes a situation in which many organizations had Meaningful Use Stage 2 systems holding structured data, but access to that data was mostly through predefined paths inside each product. The page says DAF was meant to use FHIR and existing IHE standards to standardize access to that structured information, both inside an organization and between organizations. That framing comes from an older, DSTU 1 version of the introduction, found through search, so the current wording may differ.
The Query Stack. The DSTU 2 introduction lists four layers: the query itself, the results that come back, the transport used to carry them, and the controls that protect access. For the first two layers, the guide also addresses structure, vocabularies, and value sets. Splitting the problem this way lets each layer be specified and tested separately, which is general reasoning about layered designs rather than a finding from the page.
Requestor and Responder. The guide names two actors. The DAF Requestor starts a data access request, much like a client. The DAF Responder answers it, much like a server.
Which data. The implementation guide says its profiles map to conceptual data elements in the ONC 2014 Edition criteria tied to Meaningful Use Stage 2, including allergies, medications, laboratory results, problems, procedures, immunizations, vital signs, smoking status, family history, and basic demographics.
Phases and research use. An ONC project wiki page, found through search, lists a Local Access use case for access within one organization (published December 2013), a Targeted Access use case for access between organizations (published February 2014), and a research-focused phase with pilot requirements. A later HL7 DAF Research guide, version 2.0.0 (STU2) and based on FHIR R3, defines extensions for the data models and query formats a data mart supports, according to its page. The ONC wiki also says HL7 and ONC announced the DAF FHIR guide alongside FHIR DSTU 2 on September 23, 2015. These details come from search excerpts, not from full reads of the pages.
What happened next. HL7’s US Core page says its original requirements were developed under the ONC-sponsored DAF project, that the Argonaut Data Query guide superseded DAF, and that US Core descended directly from the Argonaut guide. The same page showed version 9.0.0 (STU9) when it was read for this post. A reader meeting DAF today is most likely to meet it as history, and as the ancestor of the profiles used in U.S. FHIR work.
A link that no longer works. ONC’s older Data Access Framework page on healthit.gov now redirects to a general interoperability investments page, so it is not listed below. The HL7 pages and the ONC wiki page are the better places to read about DAF.
Common DAF problems:
- Treating DAF as a product that can be bought or installed
- Mixing up DAF, FHIR, Argonaut, and US Core, when they are successive layers of one lineage
- Assuming the DSTU 2 guide reflects current U.S. requirements, when HL7 says later guides superseded it
- Confusing the dictionary’s HL7 attribution with the ONC sponsorship described on the guide
- Overlooking that the security and privacy layer is part of the stack, not an add-on
What supports the DAF approach:
- A layered Query Stack that separates query, results, transport, and security
- Clear client and server roles in the Requestor and Responder model
- Use of FHIR profiles mapped to named data elements
- A public lineage from DAF to Argonaut to US Core, documented by HL7
🏥 The Nurse’s Perspective: Clinical, Bedside, & Workflow
Nurses do not run queries against the EHR in the way a developer does, but many tools they touch rely on exactly this kind of standardized access to chart data.
At the Bedside
Apps that display medications, allergies, vital signs, or problem lists drawn from the record depend on data access that follows agreed structures. When an app shows an out-of-date allergy list or a missing value, the cause may sit in how the data was queried or returned, though finding that out is a job for the technical team. Reporting exactly what appeared on screen and where is useful to them.
In Clinical Workflow
Nurse informaticists often sit between clinicians who want information from the record and the teams who can make it available. Knowing that data access has layers, such as what is asked, what comes back, how it travels, and who may see it, helps these nurses ask sharper questions about requests for reports, dashboards, and integrations.
In EHR Implementation (Go-Live Perspective)
During an Epic Go-Live, analysts at the elbow often hear that a third-party app or report is not showing something that appears in the chart. The Query Stack is a useful way to sort such reports: the request may be wrong, the data may not be returned, the transport may fail, or the access rights may block it. Clear examples, with patient details removed, help the interface and security teams work out which layer to look at.
🎓 CAHIMS / CPHIMS & HIMSS Perspective
CAHIMS Exam Domain Mapping
DAF supports data exchange and standards knowledge:
| CAHIMS Domain | How DAF Appears |
|---|---|
| Healthcare & Technology Environments | Federal initiatives, standards bodies, and the HL7 and ONC roles |
| Clinical Informatics | Which clinical data elements can be queried and returned |
| Healthcare Information & Systems Management | Layers of data access, interfaces, and security controls |
| Management & Leadership | Choosing standards-based access over one-off custom queries |
Key Terms to Know Alongside DAF
- Fast Healthcare Interoperability Resources (FHIR) — an HL7 standard for exchanging health data as resources
- US Core — the HL7 FHIR implementation guide that descended from the DAF and Argonaut work
- Argonaut Project — an industry effort whose data query guide superseded DAF
- Application programming interface (API) — a defined way for one program to request data or services from another
- Structural interoperability — agreement on the format and structure of exchanged data
- Standards and Interoperability (S&I) Framework — the ONC-led initiative that sponsored DAF
HIMSS Organizational Position
HIMSS offers education and research on health information and technology topics through its Resource Center. Members can find related information on the HIMSS Resource Center page.
🔗 Explore Further: External References
- HL7 — FHIR DSTU 2, DAF Introduction https://www.hl7.org/fhir/DSTU2/daf/daf-intro.html
- HL7 — U.S. Data Access Framework (DAF) FHIR Implementation Guide (DSTU 2) https://www.hl7.org/fhir/DSTU2/daf/daf.html
- HL7 — US Core Implementation Guide, Background https://www.hl7.org/fhir/us/core/
- HL7 — DAF Research Implementation Guide v2.0.0 (STU2), Extensions https://hl7.org/fhir/us/daf-research/STU2/extensions.html
- ONC Tech Lab wiki — DAF Data Element Based Queries (HL7) https://oncprojectracking.healthit.gov/wiki/spaces/TechLabSC/pages/16123310/DAF+Data+Element+Based+Queries+-+HL7
- HIMSS — Resource Center https://www.himss.org/resource-center
Term source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025). All definitions in this series are paraphrased for editorial purposes. Readers are encouraged to consult the primary source for exact language.
Eric Andrew Kristof, RN, CAHIMS is a Healthcare IT professional and HIMSS Arkansas Chapter member based in Hot Springs Village, AR, with hands-on Epic Go-Live experience and a diverse healthcare and IT background. He writes at kristof.org at the intersection of clinical care and healthcare technology.

Leave a Reply