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: hData
Source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025)
🔍 Plain-Language Definition
The HIMSS Dictionary describes hData as a specification for lightweight, scalable exchange of health information. Its approach is to put web-style interfaces, built on REST and Atom, in front of health data systems that already exist so those systems can interact.
Sources show that “hData” names more than one document. According to the HL7 wiki‘s product page, the hData specifications have two parts: the hData Record Format and the hData RESTful API. An OMG release dated February 15, 2012 describes them as the hData Record Format and the hData RESTful Transport, and says they offer a scalable way to exchange health information such as electronic health records and mobile health data. OMG’s page for the transport specification lists version 1.0 as a formal document published in October 2013. The Atom named in the dictionary is the Atom Syndication Format, which RFC 4287 describes as an XML-based web content and metadata syndication format.
| Item | Detail |
|---|---|
| Parts | Record Format and RESTful transport or API, per HL7 and OMG |
| Origin | MITRE initiated and led development in 2008, per OMG |
| Publishers | HL7 (Record Format) and OMG (RESTful transport) |
| Techniques named | REST and Atom |
| Relationship to FHIR | An ITU page says FHIR came later and adopted many hData ideas |
| Current status | Not confirmed in the sources checked |
⚠️ Exam Alert: hData is not the same as FHIR, HL7 Version 2, or CDA. It is an older specification for organizing and accessing records that FHIR later followed in using REST. Do not describe it as a replacement for any of them, and do not treat the dictionary’s single-specification wording as the whole story.
🌐 Why It Matters: Real-World Healthcare IT Context
hData matters mostly as a design idea in the history of health data exchange, and because exam candidates and implementers still meet the name in standards documents.
Origin and purpose. The OMG release says MITRE initiated and led hData’s development in 2008, with the goal of promoting scalable electronic health record systems. It describes hData as meant to connect clinical systems across providers so information can be shared despite differences between them, and says its tiered structure lets clinicians retrieve only the specific data they need rather than an entire record. These are the sponsoring organizations’ own descriptions, and the release gives no evaluation data.
Design goals. The HL7 wiki product page presents hData as a response to interoperability problems and to the complexity of CDA, C32, and related standards. It lists goals such as ease of implementation, a smaller data set, one consistent way to represent data, standard XML practices, and support for many kinds of content, including CDA documents, messages, fragments, and clinical data snippets. It also describes a REST-based web services alternative to WS-I (SOAP) services. The page has no status field and says the wiki has moved to Confluence, so it is not a statement of current standing.
Standardization. According to an ITU-T justification page, HL7 approved the hData Record Format as a Draft Standard for Trial Use in December 2011 and approved the final specification in June 2014. The page states that FHIR came after the initial version of hData and adopted many of its ideas. That is a statement from one document in a telecommunications standards context, not an HL7 history, and it should be read that way.
Relationship to FHIR. HL7’s current FHIR documentation describes FHIR as a RESTful specification and says its HTTP interactions are performed directly on server resources. The introduction on that page does not mention Atom or hData. For a reader choosing an approach today, that means FHIR’s API pages are where current RESTful guidance appears, and hData is background.
What is not confirmed. None of the sources reviewed for this post says whether hData is retired, maintained, or in current use, and none gives adoption figures. OMG’s page lists version 1.0 without saying whether a later version exists. This post therefore makes no claim about how widely hData is used.
Common hData problems:
- Treating hData as one specification when sources describe a record format and a RESTful transport
- Confusing hData with FHIR or assuming they are interchangeable
- Assuming a 2012 announcement describes current practice
- Using the dictionary’s short description as a complete definition
- Repeating a design goal as if it were a measured result
What supports understanding hData:
- The OMG release and specification page for dates and the transport specification
- The HL7 product page for the two-part structure and stated design goals
- FHIR’s RESTful API documentation for current practice
- A clear sense of what REST and Atom mean in this context
🏥 The Nurse’s Perspective: Clinical, Bedside, & Workflow
Nurses are unlikely to see hData by name, since it is a technical specification, but the problem it addresses is familiar at the bedside.
At the Bedside
Nurses rely on being able to find the right information about a patient quickly, whether it comes from an outside record, a device, or a prior visit. The OMG release describes hData’s tiered structure as a way to retrieve only the data a clinician needs, which echoes that everyday need. It does not say that any particular product or health system does this.
In Clinical Workflow
Nurse informaticists who work with interfaces and data exchange may see hData mentioned in standards background, in the same discussion as CDA, SOAP web services, and FHIR. Understanding that REST-based exchange developed over time helps them follow why newer APIs look the way they do. Whether any local system uses hData is a question for the integration team.
In EHR Implementation (Go-Live Perspective)
During an Epic Go-Live, analysts at the elbow rarely hear the word hData. They hear questions such as why an outside document is missing or why a result appears late, which can trace to how systems exchange data. This post does not claim that any specific go-live involved hData.
🎓 CAHIMS / CPHIMS & HIMSS Perspective
CAHIMS Exam Domain Mapping
hData supports standards and architecture knowledge:
| CAHIMS Domain | How hData Appears |
|---|---|
| Healthcare & Technology Environments | Standards history and web-based exchange |
| Clinical Informatics | Records, documents, and access to specific data |
| Healthcare Information & Systems Management | Interfaces and APIs between existing systems |
| Management & Leadership | Weighing older specifications against current standards |
Key Terms to Know Alongside hData
- REST — an architectural style for web services in which resources are identified by URLs and accessed with HTTP operations
- FHIR — the HL7 standard for exchanging health data through a RESTful API
- XML — a markup language used to structure documents and data
- Clinical Document Architecture — the HL7 standard for clinical documents
- SOAP — an XML-based messaging protocol used for web services
- Web services — software services that systems call over a network
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
- OMG — OMG and HL7 Announce Adoption of the hData Specification (February 15, 2012) https://www.omg.org/news/releases/pr2012/02-15-12.htm
- OMG — hData RESTful Transport (Hdata) specification page https://www.omg.org/spec/Hdata
- HL7 Wiki — Product hData (hData Specifications) https://wiki.hl7.org/Product_hData
- ITU-T — A.5 justification for HL7 hData Record Format (HL7 V3 HRF) https://www.itu.int/itu-t/workprog/wp_a5_out.aspx?isn=5994+
- IETF — RFC 4287, The Atom Syndication Format https://www.rfc-editor.org/info/rfc4287/
- HL7 — FHIR RESTful API (HTTP) https://www.hl7.org/fhir/http.html
- 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