ISO 13606

ISO 13606
Title	ISO 13606
Status	Published
Year	2008
Organization	International Organization for Standardization
Domain	Health informatics

ISO 13606 is an international standard that defines a formal framework for the electronic exchange of health record information between computer systems. It specifies an archetype-based model intended to preserve semantic integrity and enable shared clinical meaning across disparate World Health Organization, European Commission, United States Department of Health and Human Services, National Health Service (England), and other national health infrastructures. The standard has influenced subsequent specifications and national initiatives in France, Germany, Spain, United Kingdom, Australia, and Canada.

Overview

ISO 13606 provides an archetype-driven methodology to represent, communicate, and preserve parts of the Electronic health record for purposes such as continuity of care, secondary use, and research. It separates a reference model from constrained clinical models so that implementers in environments like NHS Scotland, Kaiser Permanente, Mayo Clinic, Cleveland Clinic, and Partners HealthCare can map clinical content without losing provenance or auditability. The standard aims to support data exchange between systems including Epic Systems, Cerner Corporation, Allscripts, GE Healthcare, and regional health information exchanges such as Carequality and CommonWell Health Alliance.

History and Development

Work on the standard involved international committees and stakeholders including the International Organization for Standardization, CEN (European Committee for Standardization), and clinical informatics groups from World Health Organization member states. Early conceptual roots trace to modeling efforts at institutions like University College London, Karolinska Institutet, University of Sydney, and Institut National de la Santé et de la Recherche Médicale. Influences include archetype research from openEHR, clinical modelling from Health Level Seven International, and terminology integration practices linked to SNOMED International, LOINC, ICD-10, and ICPC. Adoption was driven by national eHealth programmes in Denmark, Norway, Netherlands, and Estonia.

Architecture and Components

The ISO 13606 architecture decomposes into a Reference Model, an Archetype Model, and a Terminology Model. The Reference Model defines building blocks analogous to those used by HL7 FHIR, openEHR, and DICOM for structuring clinical content, while the Archetype Model enables reusable clinical constraints akin to artefacts used by Clinical Document Architecture. The Terminology Model integrates bindings to SNOMED CT, LOINC, ICD-10-AM, and national code sets to ensure semantic interoperability with terminology services operated by organizations such as IHTSDO and regional terminology servers like NHS Digital's terminology service.

Key components include the EHR Extract, Compositions, Sections, Entries, and Item structures, designed to preserve provenance and audit trails important to institutions such as Johns Hopkins Hospital, Mount Sinai Health System, and Stanford Health Care. The model supports data typing, versioning, and mapping mechanisms for integration with messaging and document standards endorsed by World Wide Web Consortium and International Electrotechnical Commission bodies.

Standards and Versions

ISO 13606 evolved through multiple parts and editions endorsed by standards bodies including ISO/TC 215 and national mirror committees. Its parts cover the Reference Model, Archetype Interchange, Reference Archetypes, Security and Privacy, and Interface specifications, analogous in scope to multipart standards like ISO 9001 and ISO/IEC 27001. Later editions aligned terminology and interoperability guidance with parallel standards such as HL7 CDA, HL7 FHIR, and ISO work on health informatics, responding to regulatory and procurement frameworks in jurisdictions like European Union member states and United States federal programs.

Implementation and Use Cases

ISO 13606 has been applied in regional EHR exchanges, national health record systems, and research data repositories operated by organizations such as Agence du Numérique en Santé, eHealth Belgium, Estonian Health Insurance Fund, and large academic networks. Use cases include discharge summaries exchanged between Royal Infirmary of Edinburgh and tertiary centers, laboratory result sharing involving Quest Diagnostics and hospital laboratories, and structured clinical registry submissions to initiatives like European Medicines Agency studies. Implementations often combine ISO 13606 archetypes with terminology services, consent frameworks used by European Data Protection Board guidance, and identity management systems from providers such as Okta or national eID schemes.

Interoperability and Integration

Interoperability scenarios employ ISO 13606 alongside HL7 FHIR APIs, IHE integration profiles, and messaging gateways connecting vendors like InterSystems and MEDITECH. Mapping strategies translate archetypes to FHIR resources, CDA documents, or proprietary database schemas for vendors including Philips Healthcare and Siemens Healthineers. Integration with clinical decision support systems from vendors or hospital informatics teams leverages terminologies like SNOMED CT and value sets maintained by bodies such as NHS Digital and Centers for Medicare & Medicaid Services.

Criticisms and Limitations

Critiques of ISO 13606 highlight complexity, tooling scarcity, and steep learning curves for implementers at organizations such as smaller hospitals and startups. Comparisons with alternatives like HL7 FHIR and openEHR point to differing trade-offs in agility versus formal semantic modelling, affecting adoption in fast-moving markets influenced by companies like Google Health and Apple Inc.. Challenges include harmonizing archetype libraries across jurisdictions, governance disputes similar to debates seen in ICANN policy contexts, and practical integration burdens with legacy systems from vendors such as Siemens and Cerner. Operational limitations often cited involve performance concerns for high-throughput scenarios and the need for mature clinical modelling communities similar to those supporting SNOMED International or LOINC.

Category:Health informatics standards