Resolution 1888 of 2025

On September 15, 2025, the Ministry of Health and Social Protection (MinSalud) issued Resolution 1888, which adopts the digital care summary (Resumen Digital de Atención en Salud, RDA) within the framework of electronic health record interoperability (Interoperabilidad de la Historia Clínica Electrónica, IHCE) and defines the mechanism to implement it nationwide.

It is the regulation that turns into concrete operations something that had been on paper for five years: the interoperable clinical record created by Law 2015 of 2020.

In short

• What it adopts: the digital care summary (RDA) as the document exchanged between providers.
• Who it applies to: the actors listed in article 2 of Resolution 866 of 2021. In practice, health service providers and the other members of the system that record care.
• What it requires: generating the RDA for every care encounter, sending it to the national interoperability platform and being able to look up the RDA of other providers.
• Since when: article 6 set a maximum period of six months from October 15, 2025, that is, until April 15, 2026.
• Status today: that deadline has passed. The obligation is in force, and MinSalud continues to provide technical assistance and onboarding by groups throughout 2026.
• Note: Resolution 1799 of 2026 amended its articles 2, 3 and 5 and added the medication dispensing RDA.

What the regulation says

The resolution is short, seven articles, because the technical detail lives outside it.

Article 1. Purpose. Adopts the RDA within the IHCE framework and establishes the mechanism for its national implementation, in accordance with Law 2015 of 2020 and Resolution 866 of 2021.

Article 2. Scope. It does not define its own list: it refers to the actors in article 2 of Resolution 866 of 2021. That reference matters, because it means the set of obligated parties is the same one already defined for relevant clinical data.

Article 3. Content. The RDA is made up of the relevant clinical data elements defined in Resolution 866 of 2021. It also sets four types that must be implemented initially:

RDA type	When it is generated
Patient RDA	When a clinical care event occurs
Inpatient care RDA	In inpatient care processes, to support continuity and referral
Outpatient care RDA	In ambulatory care encounters
Emergency department RDA	In immediate care, available immediately for continuity

The same article defines three associated information services: generation of the RDA by the provider, sending it to the interoperability platform, and search and retrieval of the available RDA. A paragraph (parágrafo) leaves the door open for MinSalud to add more types.

Article 4. Refers to Technical Annex No. 1, which contains the implementation guideline and is not published within the body of the resolution.

Article 5. Orders the implementation of the IHCE according to the technical annex and the schedule published on MinSalud’s microsite.

Article 6. Transition. Grants six months from October 15, 2025 to integrate systems with the IHCE model and make them interoperate.

Article 7. Takes effect upon publication.

What changed afterwards: Resolution 1799 of 2026

Resolution 1888 did not stay frozen. Its article 3 allowed MinSalud to add more types of RDA, and that power has already been used.

Resolution 1799 of 2026 amended articles 2, 3 and 5 of Resolution 1888 and added information on the dispensing of medications and health technologies to the RDA. The goal is to cover the full chain: from prescription to routing (direccionamiento), scheduling and actual delivery to the patient.

This extends the set of obligated parties to pharmaceutical managers (gestores farmacéuticos) and to IPS (instituciones prestadoras de salud, Colombia’s healthcare provider institutions) with licensing (habilitación) for pharmacy services, which have a transition period of six months from September 1, 2026 to adapt their systems.

If you are going to assess your compliance, do it against Resolution 1888 as amended by Resolution 1799. Reading the original regulation in isolation is a common mistake.

What changes for an IPS

The underlying change is not about documents, it is architectural. Until now, the clinical record could stay locked inside each institution’s system, and sharing it with another provider meant a PDF, an email or the patient carrying a folder.

With Resolution 1888, every care encounter must produce a structured document, in a defined format, that leaves the institution for a national platform. That requires three things that used to be optional:

Data has to be coded, not written. A diagnosis narrated in free text does not travel. Interoperability requires codes from the official catalogs, captured at the time of care.

The record has to be complete at closing. If the RDA is generated when the encounter ends, missing fields cannot be filled in “later, when there is time”.

The institution needs connectivity and a technical identity. Credentials, certificates and an encrypted channel to MinSalud’s platform.

For an IPS with paper clinical records, or with a system that does not export structured data, this is not a configuration: it is a system change.

What your software must do to comply

If you are assessing whether your current system lets you comply, or comparing vendors, this is the short list of what it has to be able to demonstrate:

1. Generate the four types of RDA (patient, inpatient care, outpatient care and emergency department) from the clinical record, with no separate data entry.
2. Produce the document in the technical annex format, which relies on the HL7 FHIR R4 standard and the official RDA implementation guide.
3. Code with the mandatory catalogs: ICD-10 and ICD-11 for diagnoses, CUPS for procedures, IUM for medications, plus the value sets defined in the guide.
4. Send over an encrypted, authenticated channel, with the credentials issued by MinSalud.
5. Look up other providers’ RDA from the same interface where the professional provides care. Sending is of little use if nobody looks them up.
6. Log access traceability: which RDA was viewed, by whom and when. The clinical record is still sensitive data under Law 1581 of 2012.
7. Validate before sending, so rejections are caught in-house and not on the platform.

One point that gets overlooked: item 5 is what decides whether interoperability is of any use. A system that sends but does not show what others sent complies with the regulation and does not improve care.

How Omneri solves it

Omneri generates the RDA from the same record where the professional documents the care. There is no separate interoperability module and no extra screen that someone has to fill in at the end of the shift: the relevant clinical data is captured coded during the encounter, and the summary is built from it.

In practice, that means:

• The four types of RDA come out of the flow that already exists: outpatient care from the consultation, emergency department from triage and immediate care, inpatient care from progress notes and discharge.
• Coding at the point of capture. The professional picks the diagnosis from the catalog while documenting, instead of writing it in free text for someone to translate later.
• Validation before sending, so structural errors are fixed before they reach the national platform.
• Integrated lookup: the available RDA from other providers appear inside the patient’s record.
• Access auditing on every lookup of clinical information, recording user, time and reason.

If you want to see this on your own operation, request a demo and we will review it with your services and your catalogs.