HIMSS Word of The Day #546: RIM (Reference Information Model)

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: RIM (Reference Information Model)

Source: HIMSS Dictionary of Health Information and Technology Terms, Acronyms, and Organizations, 6th Edition (2025)

---

🔍 Plain-Language Definition

The HIMSS Dictionary describes the RIM (Reference Information Model) as a static model of health and health care information, drawn up within HL7’s standards work. It reflects a consensus among the HL7 working group and its international affiliates, and it is the source from which HL7 Version 3.0 specifications take their information content.

HL7 International describes the RIM on its own site as the cornerstone of the Version 3 development process. It calls the RIM an object model created as part of the Version 3 methodology, a large pictorial representation of HL7 clinical data (domains) that also identifies the life cycle messages carry. It is shared by all domains, and each domain creates its messages from it. HL7 also states that the RIM is an ANSI-approved standard. Its download page lists Release 7 of the ANSI normative RIM (version 2.47), a reaffirmation dated 10 December 2021 of the 2016 standard, and a long archive of earlier versions that goes back to a 1996 pre-release.

In plain terms, the RIM is not a message, a document, or a database. It is an agreed picture of the kinds of things health care talks about (such as acts, participants, roles, and entities) and how they relate. Messages and documents are then built from slices of that model. The Clinical Document Architecture (CDA), the standard behind C-CDA documents, is one of those derived standards. A 2001 article by Dolin and colleagues says the CDA “derives its semantic content” from the RIM, as part of the emerging Version 3 family.

Item	What it is	Relation to the RIM
RIM	Shared information model for HL7 Version 3	The source model
HL7 Version 3	Family of HL7 standards, including messages	Draws its information content from the RIM
CDA	Markup standard for clinical documents	Derives its semantic content from the RIM
Local data model	An organization’s own database design	May be mapped to the RIM for exchange

⚠️ Exam Alert: The RIM is the information model behind HL7 Version 3, and it is not a message format by itself. Do not confuse it with HL7 Version 2, the earlier and separate message standard, with FHIR, a different HL7 standard family built around resources, or with SNOMED CT, which is a reference terminology rather than an information model. The RIM describes how information is structured, and a terminology describes what the codes mean.

---

🌐 Why It Matters: Real-World Healthcare IT Context

A shared model sounds like a straightforward good: if everyone starts from the same picture of health care information, exchange should be easier. The literature on the RIM shows that the idea was both influential and contested. The sources below are mostly from the 2000s, when Version 3 was being developed, plus one recent application. Each was checked against its published abstract or the HL7 page, and the type of source is noted. Several are old and some are opinion papers.

HL7’s own account. The HL7 International page is the standards body’s description. It gives the role of the RIM, the ANSI status, and the release history. It is an official statement, not an outside evaluation.

A critique. Smith and Ceusters, in Studies in Health Technology and Informatics (2006), titled their paper “HL7 RIM: an incoherent standard.” They write that the RIM is described by its authors as the foundation of healthcare interoperability, but that after some ten years of development it was still subject to logical and ontological flaws that placed severe obstacles in the way of implementers. They argue that the obstacles are insurmountable and that the time had come to abandon the paradigm. It is a position paper, and its claims are the authors’ analysis.

A response. Schadow and colleagues, in the same journal (2006), responded to the main criticisms in the published literature. They identify themselves as among the chief designers of the RIM and say much of the criticism is based on misunderstandings and differences in point of view. They hope to advance the dialogue so that effective critique can lead to improvements. The authors have a stake in the model, so this is a defense by its designers.

Linking the RIM to documents. Dolin and colleagues, in the Journal of the American Medical Informatics Association (2001), described the Clinical Document Architecture, release 1.0, which became an ANSI-approved HL7 standard in November 2000. The CDA specifies the structure and semantics of clinical documents such as discharge summaries and progress notes in XML. The authors state that, as part of the Version 3 family, the CDA derives its semantic content from the shared RIM. This is a descriptive overview of a standard from its early days.

Mapping a data warehouse. Lyman and colleagues, in the AMIA Annual Symposium Proceedings (2003), explored whether the RIM could represent data stored in a local academic clinical data warehouse, as part of designing multi-institution data sharing. They describe initial efforts to map clinical concepts from a relational warehouse to the RIM. The abstract reports the approach, not results on how well the mapping worked, and the work is two decades old.

A recent use as a reference. Yang and colleagues, in the Journal of Biomedical Semantics (2022), built a national health concept data model in China from 55 data sets (4,640 data items) across seven business domains. They referenced the HL7 RIM when building the structure of the model, then applied ISO/IEC 11179 to define and standardize data elements. The result was six classes and 15 sub-classes, 100 initial data elements, and 144 general data elements, along with a model-based system to manage them. The authors describe the approach as a feasible solution for healthcare data standardization in China. This is a development report, not a comparison with other approaches.

Taken together, the sources show a model that was central to Version 3, influential on documents like the CDA, used as a reference for data models, and openly disputed. They do not settle the debate, and the oldest ones reflect the state of the standard at the time.

Common RIM problems:

• Treating the RIM as a message or file format rather than a model
• Confusing HL7 Version 2, Version 3, CDA, and FHIR
• Expecting local database designs to map to the RIM without effort
• Underestimating the abstraction involved, which can make the model hard to learn
• Relying on older articles without checking what has changed since
• Assuming a shared model guarantees shared meaning without matching terminologies

What supports using a shared information model:

• Clear separation of the information model, the terminology, and the exchange format
• Mapping tools and documented rules between local schemas and the model
• Metadata management that follows a standard such as ISO/IEC 11179
• Education for analysts on how the model relates to messages and documents
• Reviewing current HL7 materials for the version in use
• Open discussion of limits and critiques of the model

---

🏥 The Nurse’s Perspective: Clinical, Bedside, & Workflow

Nurses rarely see the RIM itself, but they work with documents and messages that rest on it.

At the Bedside

Discharge summaries, referral letters, and transfer documents that nurses read and help assemble may be built on CDA, which rests on the RIM. When the structure behind a document is sound, the allergy list, medications, and problems land in the right place for the next clinician. When it is not, nurses see the symptoms as missing or misfiled data.

In Clinical Workflow

Nurse informaticists help decide what data elements a shared document or interface should carry, and which nursing concepts need a place in the model. A model’s classes of acts, participants, and roles line up well with nursing work: who did what, to whom, and when. Bringing nursing concepts to standards conversations early helps avoid gaps that are costly to fix later.

In EHR Implementation (Go-Live Perspective)

During an Epic Go-Live, analysts at the elbow hear about documents that arrive incomplete or data that does not show up after an interface sends it. Tracing these problems often means walking through what was sent, how it was structured, and how the receiving system placed it. A basic grasp of how information models, documents, and terminologies fit together makes those conversations with interface teams faster.

---

🎓 CAHIMS / CPHIMS & HIMSS Perspective

CAHIMS Exam Domain Mapping

The RIM connects standards, data structure, and exchange:

CAHIMS Domain	How the RIM Appears
Healthcare & Technology Environments	HL7 standards, ANSI approval, and the standards development process
Clinical Informatics	Clinical concepts such as acts and roles, and how documents are structured
Healthcare Information & Systems Management	Data models, mapping, metadata management, and interface design
Management & Leadership	Standards selection, governance, and long-term planning for exchange

Key Terms to Know Alongside the RIM

• HL7 (Health Level Seven) — standards organization that develops health information exchange standards
• CDA (Clinical Document Architecture) — HL7 markup standard for clinical documents
• Semantic Interoperability — exchange in which the receiver understands the meaning of the data
• Data Model — formal description of data elements and their relationships
• Reference Terminology — terminology with formal definitions that support meaning-based retrieval
• Metadata — data that describes other data

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

1. HL7 International — Reference Information Model (RIM) https://www.hl7.org/implement/standards/rim.cfm
2. Smith and Ceusters (2006), Studies in health technology and informatics — HL7 RIM: an incoherent standard https://pubmed.ncbi.nlm.nih.gov/17108516/
3. Schadow et al. (2006), Studies in health technology and informatics — The HL7 reference information model under scrutiny https://pubmed.ncbi.nlm.nih.gov/17108519/
4. Dolin et al. (2001), Journal of the American Medical Informatics Association : JAMIA — The HL7 Clinical Document Architecture https://pubmed.ncbi.nlm.nih.gov/11687563/
5. Lyman et al. (2003), AMIA … Annual Symposium proceedings. AMIA Symposium — Mapping from a clinical data warehouse to the HL7 Reference Information Model https://pubmed.ncbi.nlm.nih.gov/14728426/
6. Yang et al. (2022), Journal of biomedical semantics — Defining health data elements under the HL7 development framework for metadata management https://pubmed.ncbi.nlm.nih.gov/35303946/
7. 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.