[Durgical](https://durgical.com/en/) › [DurgiPedia](https://durgical.com/en/durgipedia/) › [Epidemiology](https://durgical.com/en/epidemiology/) › [Medical informatics](https://durgical.com/en/epidemiology/areas/informatics/) › Health data interoperability: standards and Colombia's RDA

# Health data interoperability: standards and Colombia's RDA

- System and programme

Your patient's allergy was recorded in another city. Interoperability decides whether your screen shows it as data you can use or not at all.

Updated Nov 19, 2026

## Key points

- Syntactic interoperability: systems agree on the structure of the message, for example HL7 FHIR resources in JSON.
- Semantic interoperability: both ends mean the same thing by each field, through shared code sets (SNOMED CT for clinical concepts, LOINC for tests and observations, ICD for classification).
- Organisational interoperability: governance, consent, roles, workflows and law, so that the data may be used.
- Colombia: Resolution 866 of 2021 set the relevant clinical data elements and their mandatory catalogues; Resolution 1888 of 2025 adopted the RDA built from them.
- RDA types: patient, hospitalisation, outpatient and emergency; services: generation, sending and search and consultation on a central Ministry platform.

On this page

- The basics Key points
- What it is
- How to think about it
- How it is organised
- Worked example
- The layers of interoperability
- In practice
- Reference norms
- Common traps
- Elsewhere in DurgiPedia

- Study Test yourself

- Connections Connections

## What it is

Interoperability is the ability of different systems to exchange information, understand it and use it. Law 2015 of 2020 defines it in these terms for Colombia's interoperable electronic health record (IHCE). It works in layers: a shared format (syntactic), a shared meaning (semantic) and shared rules between organisations (organisational). Resolution 866 of 2021 fixed the relevant clinical data elements, and Resolution 1888 of 2025 adopted the Resumen Digital de Atención en Salud (RDA), the standard summary that providers send to the national platform.

## How to think about it

Interoperability is a conversation between strangers. They need a channel (a network), a grammar (the message format), a dictionary (shared codes for each concept) and manners (rules on who may speak and listen). Remove any one and the message arrives but is not understood, or is understood but may not be used.

## How it is organised

- Technical layer: the network and secure transport between systems.
- Syntactic layer: message formats; HL7 FHIR describes care as small «resources» (Patient, Encounter, Condition, Observation, AllergyIntolerance, MedicationRequest) exchanged through web interfaces.
- Semantic layer: terminologies and classifications; a terminology such as SNOMED CT names clinical meaning in detail, a classification such as ICD groups it for statistics, LOINC identifies the test.
- Organisational layer: who may send, view and use which data, with consent and traceability.
- Colombia's model is centralised: each provider generates the RDA from its own record system and sends it to the Ministry's platform, where authorised professionals search and view it.

## Worked example

- Ten providers want to share records. Point to point, each pair needs its own link: 10 × 9 / 2 = 45 interfaces to build and maintain.
- With one national platform and one standard, each provider builds one connection: 10 links instead of 45.
- Syntax works: hospital A sends an allergy as free text «PNC»; hospital B receives the field but its software cannot recognise it.
- Semantics fixed: A sends the allergy as a coded concept from the agreed catalogue; B's system recognises it and can trigger an alert.
- An audit of 100 shared allergies finds 30 as free text: only 70 / 100 = 70 % can drive decision support at the receiving end.
- Reading: the message arriving is not enough; coded, agreed meaning is what lets the next doctor's system act on it.

## The layers of interoperability

| Layer | Question it answers | Example | Failure looks like |
| --- | --- | --- | --- |
| Technical | Can the bits travel? | Secure network between provider and platform | Nothing arrives |
| Syntactic | Can the message be read? | HL7 FHIR resource in JSON | The file arrives but cannot be parsed |
| Semantic | Do both ends mean the same thing? | Allergy and test coded from shared catalogues | Data arrives but software cannot act on it |
| Organisational | May it be used, by whom and for what? | Consent, roles, traceability, law | Data is available but its use is unlawful or unclear |

## In practice

- What you record well is what the next doctor sees: use structured fields and the catalogue entries for allergies, diagnoses and medicines instead of free text.
- In an emergency, check the platform for the patient's RDA before relying only on memory or a paper [referral](https://durgical.com/en/family-medicine/referral-and-counter-referral-from-the-doctor-s-side/).
- A summary is a summary: when the RDA conflicts with what the patient says, ask, examine and record the discrepancy.
- The legal rules on access, consent and custody of the record are on the electronic health record page; this page is about how the data travels.

## Reference norms

- Law 2015 of 2020, art. 2: interoperability is the capacity of several systems to exchange information, understand the data and use them.
- Resolution 866 of 2021 (Ministries of Health and of ICT): the set of relevant clinical data elements and their mandatory catalogues.
- Resolution 1888 of 2025 (15 September 2025): adopts the RDA, defines its first four types and the generation, sending and search services, and gave the actors six months from 15 October 2025 to interoperate; its technical annex names HL7 FHIR.

## Common traps

- **If the file arrives, the systems are interoperable**: that is only syntax; without shared codes the receiving system cannot understand or act on the data
- **SNOMED CT and ICD do the same job**: SNOMED CT is a detailed clinical terminology for recording care, ICD a classification that groups conditions for statistics and payment
- **Free text is just as good once it is shared**: a human can read it, but software cannot alert on it, count it or map it
- **Interoperability is a software problem only**: consent, roles, governance and law decide whether shared data may be used at all
- **The RDA replaces the provider's own record**: it is a standard summary of relevant data; each provider keeps its full record

## Test yourself

Think of the answer, then tap the question to see it.

## Hospital B receives an allergy from hospital A as the free text «PNC» and its software raises no alert. Which layer failed?

The semantic layer: the message was read, but the allergy was not sent as an agreed coded concept the receiving system could recognise.

## Why does a national platform scale better than links between each pair of providers?

Pairwise links grow as n(n−1)/2 (45 for 10 providers); a hub needs one connection per provider (10), each using the same standard.

## A colleague says SNOMED CT will replace CIE codes in the RIPS. What is the confusion?

A terminology records clinical meaning in detail; a classification such as ICD groups it for statistics and payment. They work together, often linked by maps.

## What does the RDA carry, and what does it not replace?

It carries the relevant clinical data of an attention in a standard form; it does not replace each provider's full record, which stays in its own system.

[Add to my cards (4)](https://durgical.app/estudiar/?add=/en/epidemiology/health-data-interoperability-standards-and-colombia-s-rda/)

## Elsewhere in DurgiPedia

- [The electronic health record: Ley 2015 de 2020](https://durgical.com/en/medical-ethics/the-electronic-health-record-ley-2015-de-2020/)
- [Ley 1581 de 2012: personal data in health](https://durgical.com/en/medical-ethics/ley-1581-de-2012-personal-data-in-health/)
- [Telehealth and telemedicine in Colombia: Law 1419 of 2010 and Resolution 1644 of 2026](https://durgical.com/en/medical-ethics/telehealth-and-telemedicine-in-colombia-law-1419-of-2010-and-resolution-1644-of/)
- [Telephone and video consultations: consulting safely at a distance](https://durgical.com/en/clinical-skills/telephone-and-video-consultations-consulting-safely-at-a-distance/)

## Connections

## Related 5

- [Health information systems in Colombia: SISPRO, RIPS, RUAF](https://durgical.com/en/epidemiology/health-information-systems-in-colombia-sispro-rips-ruaf/)
- [Clinical coding in Colombia: ICD-10, ICD-11 and CUPS](https://durgical.com/en/epidemiology/clinical-coding-in-colombia-icd-10-icd-11-and-cups/)
- [Using the electronic record safely](https://durgical.com/en/epidemiology/using-the-electronic-record-safely/)
- [Study management and data quality](https://durgical.com/en/epidemiology/study-management-and-data-quality/)
- [Patient safety and adverse events](https://durgical.com/en/epidemiology/patient-safety-and-adverse-events/)

[← All of epidemiology](https://durgical.com/en/epidemiology/)

Educational content on epidemiological and statistical methods; the examples use made-up numbers to teach the calculation. Not a clinical or legal guide: current Colombian rules are in the official sources.

Sources: [Ley 2015 de 2020, por medio de la cual se crea la historia clínica electrónica interoperable](https://www.funcionpublica.gov.co/eva/gestornormativo/norma.php?i=105472) (Función Pública, Gestor Normativo, 2020); [Resolución 866 de 2021, set of relevant clinical data elements for medical record interoperability](https://www.minsalud.gov.co/sites/rid/Lists/BibliotecaDigital/RIDE/DE/DIJ/resolucion-866-de-2021.pdf) (Ministerio de Salud y Protección Social, 2021); [Resolución 1888 de 2025, adopting the Resumen Digital de Atención en Salud (RDA) within the interoperable electronic health record](https://www.minsalud.gov.co/sites/rid/Lists/BibliotecaDigital/RIDE/DE/DIJ/resolucion-1888-de-2025.pdf) (Ministerio de Salud y Protección Social, 2025); [The Fast Health Interoperability Resources (FHIR) Standard: Systematic Literature Review of Implementations, Applications, Challenges and Opportunities](https://pmc.ncbi.nlm.nih.gov/articles/PMC8367140/) (JMIR Medical Informatics (PubMed Central), 2021).

## **Spotted a mistake?** We are always improving for the community. Tell us what is wrong and our team will review it. Report a mistake

Representative model, for educational purposes only.

---
Source: https://durgical.com/en/epidemiology/health-data-interoperability-standards-and-colombia-s-rda/
License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Cite as: DurgiPedia (durgical.com), https://durgical.com/en/epidemiology/health-data-interoperability-standards-and-colombia-s-rda/
