- Atlas
- Medicine & Health
- Health Data Standards
Health Data Standards
A patient's care is recorded in many places: a family doctor's notes, a hospital laboratory system, a pharmacy database, a ward chart, a national registry.
9 frameworks, from 1918 to today · Health Informatics · Medicine & Health
- Hospital Standardization and Medical Record Practice 1918-Present
- International Classification of Diseases 1948-Present
- SNOMED CT 1965-Present
- HL7 Version 2 Messaging 1989-Present
- ISO/IEEE 11073 1990-Present
- LOINC 1994-Present
- Model-Driven Standards (HL7 Version 3 and RIM) 1999-2015
- Clinical Document Architecture (CDA) 2000-Present
- Fast Healthcare Interoperability Resources 2014-Present
Overview
A patient's care is recorded in many places: a family doctor's notes, a hospital laboratory system, a pharmacy database, a ward chart, a national registry. Health data standards are the agreed rules that let those records mean the same thing and move between systems without losing their sense1. They come in several kinds. Classifications sort diseases and procedures into numbered categories for counting and billing2. Terminologies capture clinical detail in coded form—not just "diabetes" but which kind, in which part of the body, with what complications3. Messaging standards define the structure of a message sent from one computer system to another4. Identifier systems give laboratory tests and observations stable codes5. Document standards specify how a whole clinical document is packaged6. Device standards let bedside machines talk to information systems7. And resource-based standards model health data as modular, web-friendly objects8.
What is at stake is interoperability: the ability of different systems to exchange data and use it9. Without standards, every hospital builds its own tower of records, and information dies at the boundary. With them, a laboratory result can follow a patient across a city, a country, or a lifetime. The history of health data standards is the story of how the field moved from paper forms and statistical lists toward a global, web-based architecture—and of the compromises and competing philosophies along the way.
Paper Records, Hospital Standardization, and the Birth of the Medical Record Profession
In the early twentieth century, hospitals in North America and Europe began to be judged on how well they documented care. The American College of Surgeons, founded in 1913, launched a hospital standardization program in 1918: hospitals seeking approval had to keep complete, organized medical records. This created a new occupation. The Association of Record Librarians of North America was founded in 1928 (it later became the American Health Information Management Association), and its members—mostly women—developed rules for what a record should contain, how it should be indexed, and how diagnoses should be coded. The problem they solved was basic: a hospital could not audit its own care, or defend itself in court, without records that were complete and retrievable. Their solution was a profession with its own standards of practice, and the medical record became an object of deliberate design rather than an afterthought.
Statistical Classification: The ICD
The other great strand came from public health and epidemiology. International statistical classification of causes of death began in the nineteenth century; the International Statistical Institute adopted a classification in 1893, and the first International Classification of Diseases (ICD) was issued by the World Health Organization's predecessor in 1948. The ICD assigns each disease a code so that deaths and hospital discharges can be counted and compared across places and years10. Its logic is statistical: categories are broad enough to aggregate, and revisions every decade or so reflect changing medical knowledge. The ICD became the backbone of morbidity and mortality reporting worldwide, and later revisions—ICD-9, ICD-10, and the current ICD-11—extended it to procedures, functioning, and traditional medicine. Its limitation is equally important: designed for counting, it cannot express the fine clinical detail a treating doctor needs.
Compositional Clinical Terminology: SNOMED
That limitation drove the development of clinical terminologies. SNOMED—Systematized Nomenclature of Medicine—grew from the Systematized Nomenclature of Pathology, published by the College of American Pathologists in 1965, which organized terms along axes such as topography and morphology. Successive versions added clinical terms, and in 2000 SNOMED RT merged with the UK's Clinical Terms Version 3 to produce SNOMED CT, now maintained by SNOMED International. SNOMED CT is compositional: concepts are defined by their relationships to other concepts, so a clinician can build a precise expression—say, a fracture of a specific bone with a specific type—from simpler parts11. The idea is that a computer can reason with the result, not merely store it. SNOMED CT is now used in dozens of countries, though full implementation remains uneven.
Messaging: HL7 Version 2
Meanwhile, hospital computers needed to talk to each other. In 1987 a group of hospital system vendors and users in the United States formed Health Level Seven (HL7), named for the seventh layer of the OSI networking model—the application layer, where health data live. HL7 Version 2, first published in 1989, defined messages for admissions, orders, results, and billing, built from segments of pipe-delimited fields. Its great virtue was pragmatism: it was relatively simple to implement, and it spread globally. Its weakness was that it was flexible to the point of ambiguity—different sites interpreted fields differently, so "HL7-compliant" did not guarantee that two systems could actually understand each other. Version 2 remains in wide use today, a testament to the value of a workable standard over a perfect one.
Naming Observations: LOINC
A laboratory result is only useful if the receiving system knows what was measured. In the 1990s, Clement McDonald and colleagues at the Regenstrief Institute in Indianapolis developed LOINC—Logical Observation Identifiers Names and Codes—first released in 1994. LOINC gives each laboratory test and clinical observation a stable code built from parts: the component measured, the property, the timing, the specimen, and so on. A glucose measurement in serum has a different LOINC code from a glucose measurement in urine, and both are distinct from a glucose measurement in a different unit. LOINC solved the problem of semantic drift—the same test called by different names at different hospitals—and is now the international standard for identifying observations.
Devices at the Bedside: ISO/IEEE 11073
Medical devices—infusion pumps, ventilators, patient monitors—generate a constant stream of data. The ISO/IEEE 11073 family of standards, developed from the 1990s onward by the IEEE and the International Organization for Standardization, defines how these devices communicate with each other and with information systems. The standards specify not only the transport of data but the nomenclature of measurements and device states, so that a monitor's reading of heart rate can be understood by a clinical information system without custom integration7. Adoption has been slower than for messaging standards, partly because device vendors had little incentive to open their systems, but the family remains the reference point for device interoperability.
The Model-Driven Turn: HL7 Version 3 and the Reference Information Model
By the late 1990s, HL7's leadership concluded that Version 2's flexibility was a trap. The answer was Version 3, built on a formal Reference Information Model (RIM): a small set of object classes—entities, roles, acts, participations—from which all messages would be derived. The RIM was intended to make messages unambiguous and machine-processable. It was an ambitious, model-driven approach, and it produced a generation of specifications, including the Clinical Document Architecture (CDA), which defines how to structure a clinical document such as a discharge summary so that it is both human-readable and machine-processable6. CDA found real use in national programs, notably in the United States and Europe, for exchanging summaries of care. But Version 3 was complex, expensive to implement, and slow to win adoption; many implementers stayed with Version 2. The episode taught the field that formal rigor alone does not guarantee uptake.
FHIR and the Resource-Based Present
The response came from a new generation. In 2011, Grahame Grieve, an Australian health informatics engineer, proposed a simpler approach: model health data as resources—discrete, reusable objects such as a Patient, an Observation, or a MedicationRequest—each with a defined structure and a web API. This became FHIR, Fast Healthcare Interoperability Resources, developed under HL7 and first published as a draft standard in 2014. FHIR borrowed the best of the web: RESTful interfaces, JSON and XML formats, and modular resources that could be combined as needed8. It also learned from the past by reusing established terminologies—SNOMED CT, LOINC, ICD—rather than inventing new ones. FHIR has been adopted with unusual speed by vendors, national programs, and app developers, and it is now the focus of global interoperability efforts, including the United States' interoperability rules and the European Union's health data space.
Where the Field Stands
Today the main approaches coexist rather than replace one another. HL7 Version 2 still carries most hospital messaging; CDA remains in use for document exchange; FHIR is the growth area, extending from clinical data to genomics, public health, and research. SNOMED CT, LOINC, and ICD remain the semantic backbone, and the ISO/IEEE 11073 family continues to define device communication12. The open questions are familiar in new form: how to map between terminologies without losing meaning; how to govern standards so that they serve patients across countries with different resources and legal systems; how to make FHIR implementations genuinely interoperable rather than merely conformant; and how to keep standards current as medicine and technology change. The history suggests that the standards which endure are those that balance rigor with usability—and that the work of making health information travel is never finished.
References
- Clinical data standards, Wikipedia
- Medical classification, Wikipedia
- SNOMED CT, Wikipedia
- HL7, Wikipedia
- LOINC, Wikipedia
- Clinical Document Architecture, Wikipedia
- ISO/IEEE 11073, Wikipedia
- Fast Healthcare Interoperability Resources, Wikipedia
- Interoperability, Wikipedia
- International Classification of Diseases, Wikipedia
- Systematized Nomenclature of Medicine, Wikipedia
- IEEE 11073 service-oriented device connectivity, Wikipedia
The frameworks of Health Data Standards
Each framework is a way of working the field has used: when it held, and the question it answers.
- 1918-Present
Hospital Standardization and Medical Record Practice
What should a complete medical record contain?
- 1948-Present
International Classification of Diseases
How can diseases be counted and compared across places?
- 1965-Present
SNOMED CT
How can clinical detail be coded so computers can reason with it?
- 1989-Present
HL7 Version 2 Messaging
How can hospital computer systems exchange messages?
- 1990-Present
- 1994-Present
- 1999-2015
Model-Driven Standards (HL7 Version 3 and RIM)
How can health messages be made formally unambiguous?
- 2000-Present
Clinical Document Architecture (CDA)
How should a whole clinical document be structured?
- 2014-Present
Fast Healthcare Interoperability Resources
How can health data be modelled as modular web resources?
How the ideas connect
Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.
Model-Driven Standards (HL7 Version 3 and RIM) reacted against HL7 Version 2 Messaging
HL7 Version 3 was created explicitly as a rejection of Version 2's flexible, ambiguous segment-based messages, which implementers had found could not guarantee semantic interoperability. The RIM was designed to make messages formally unambiguous in response to Version 2's perceived failures.
Carried by Health Level Seven; Reference Information Model.
Clinical Document Architecture (CDA) grew out of Model-Driven Standards (HL7 Version 3 and RIM)
The Clinical Document Architecture was developed within the HL7 Version 3 framework and built directly on the Reference Information Model, deriving document structures from the same RIM classes. CDA is a specification produced by the model-driven approach.
Carried by Health Level Seven; Reference Information Model.
Fast Healthcare Interoperability Resources reacted against Model-Driven Standards (HL7 Version 3 and RIM)
FHIR was proposed by Grahame Grieve as a deliberate alternative to the complexity and slow uptake of HL7 Version 3 and the RIM, replacing model-driven derivation with modular resources and web APIs. FHIR's designers defined it against Version 3's heavy formalism.
Carried by Grahame Grieve; Fast Healthcare Interoperability Resources (2014).
SNOMED CT influenced by International Classification of Diseases
The statistical classification of disease showed that coded categories enabled aggregation but could not capture clinical detail, and this limitation was the explicit motivation for building compositional clinical terminologies. SNOMED's developers set out to provide the fine-grained clinical coding that ICD could not.
Carried by College of American Pathologists; Systematized Nomenclature of Pathology (1965).
Fast Healthcare Interoperability Resources influenced by SNOMED CT
FHIR resources bind to SNOMED CT for clinical coding rather than inventing a new terminology, so SNOMED concepts are carried into FHIR's coded fields. The resource standard explicitly reuses the established clinical terminology.
Carried by Health Level Seven; SNOMED International.
Fast Healthcare Interoperability Resources influenced by HL7 Version 2 Messaging
FHIR was developed under HL7 and reused the messaging concerns and much of the domain content that Version 2 had addressed, while adopting a simpler resource-based structure. It grew out of the same standards organization and its accumulated experience with hospital messaging.
Carried by Health Level Seven; Grahame Grieve.
Fast Healthcare Interoperability Resources influenced by LOINC
FHIR's Observation resource uses LOINC codes to identify what was measured, carrying LOINC's identifier system into the resource-based architecture. FHIR adopted LOINC as the standard code system for observations.
Carried by Health Level Seven; Regenstrief Institute.
Fast Healthcare Interoperability Resources influenced by International Classification of Diseases
FHIR allows ICD codes to be used in its resources for diagnoses and statistical reporting, reusing the classification rather than replacing it. The classification's codes remain available within the resource model.
Carried by Health Level Seven.
Beyond the field
Where Health Data Standards's ideas came from in other fields, and what they led to there: the strongest 12 of 38 links.
Hospital Standardization and Medical Record Practice led to Accreditation and External Accountability in Quality Improvement
Hospital standardization and medical record practice, pioneered by the American College of Surgeons' hospital standardization programme, is the direct ancestor of modern health care accreditation. The later accreditation bodies grew out of and extended that standardization and survey tradition.
Carried by American College of Surgeons.
International Classification of Diseases influenced by Civil Registration and Vital Statistics in Global Health Metrics And Evaluation
Civil registration and vital statistics supplied the cause-of-death data and coding needs that the International List of Causes of Death, the ICD's ancestor, was created to standardize in 1893.
Carried by Jacques Bertillon.
International Classification of Diseases grew out of Vital statistics in Public Health
The ICD descends from the international cause-of-death classification (the Bertillon Classification) adopted in 1893, which itself built on earlier vital statistics compilations of mortality by cause going back to the 17th-century bills of mortality tradition.
Carried by Jacques Bertillon; International Statistical Institute.
International Classification of Diseases grew out of Vital statistics in Public Health Informatics
The ICD originated as the International List of Causes of Death, a classification designed for compiling vital statistics; the cause-of-death tabulation practices of vital statistics offices were the direct basis for it.
Carried by Jacques Bertillon.
International Classification of Diseases influenced International Classification of Functioning, Disability and Health in Rehabilitation Outcomes
The ICF was built as a companion classification to the ICD, adopting the ICD's taxonomic architecture and its aim of a common international language for health information. WHO developers explicitly framed the ICF as complementing the ICD's classification of disease with a classification of functioning.
Carried by World Health Organization.
Model-Driven Standards (HL7 Version 3 and RIM) grew out of HL7 in Nursing Informatics
HL7 Version 3 and the Reference Information Model were developed by HL7 itself as a successor to its earlier Version 2 messaging standards. The RIM and V3 methodology grew directly out of the HL7 organisation's prior work on clinical message exchange.
Carried by Health Level Seven.
Fast Healthcare Interoperability Resources grew out of HL7 in Nursing Informatics
Fast Healthcare Interoperability Resources was created within HL7 as a lighter-weight, REST-based alternative to the HL7 Version 3 and CDA specifications. FHIR reuses HL7's data element concepts while replacing the V3 modelling and messaging approach.
Carried by Health Level Seven; Grahame Grieve.
Hospital Standardization and Medical Record Practice influenced Clinical Information Systems and Electronic Health Records in Digital Health
Hospital standardization and medical record practice established the standards for complete, uniform, retrievable patient records that electronic systems then implemented. The accreditation-driven record requirements shaped the data elements and documentation rules of the EHR.
Hospital Standardization and Medical Record Practice influenced Clinical Classification and Terminology Systems in Health Informatics
Hospital standardization required standardized medical records and diagnoses, creating the demand and standards that clinical classification systems served.
Carried by American College of Surgeons.
Hospital Standardization and Medical Record Practice influenced Health Information Exchange and Interoperability Standards in Digital Health
Hospital standardization and medical record practice established uniform record content and identification conventions that later data standards encoded. The interoperability effort inherited the assumption of standardized, comparable records.
Hospital Standardization and Medical Record Practice influenced Problem-Oriented Medical Record in Digital Health
Hospital standardization and medical record practice set the requirements for complete, uniform records that the problem-oriented record reorganized around explicit problem lists. The accreditation-driven documentation standards shaped its form.
Carried by Lawrence Weed.
Hospital Standardization and Medical Record Practice influenced Interoperability Standards and Health Information Exchange in Public Health Informatics
Hospital standardisation and medical record practice, from the American College of Surgeons hospital standardisation programme onward, established uniform record content and formats across institutions. Interoperability standards built on this prior standardisation of the medical record, extending uniformity from paper records to electronic exchange.

Health Data Standards is a planet in Nousfarer
Its city has a tower for each of these 9 frameworks. Land, walk in, and climb one concept at a time.
Land on Health Data StandardsRelated fields
Fields its ideas are linked to
- Digital Health 7 links
- Nursing Informatics 6 links
- Health Information Systems 5 links
- Health Informatics 4 links
- Clinical Informatics 3 links
- Public Health Informatics 3 links
- Global Health Metrics And Evaluation 2 links
- Quality Improvement 1 link
- Global Health 1 link
- Psychiatry 1 link
- Public Health 1 link
- Assistive Technology 1 link
More in Health Informatics
- Clinical Informatics
- Consumer Health Informatics
- Digital Health
- Health Informatics
- Health Information Systems
- Public Health Informatics
See where Health Data Standards sits on the Map of Human Knowledge