Electronic health record interoperability (IHCE)
Five years between the law that created it and the regulation that put it to work. Here is where it landed.
Electronic health record interoperability (IHCE) is the national mechanism that lets a patient’s clinical data be exchanged between providers, regardless of which institution treated them or which software each one uses.
It is not a product or a platform you buy: it is a regulatory and technical framework that institutions’ information systems connect to.
In short
- What it is: the mechanism for exchanging relevant clinical data between healthcare providers in Colombia.
- Created by: Law 2015 of 2020.
- What is exchanged: the digital care summary (RDA), adopted by Resolution 1888 of 2025.
- Which data: the relevant clinical data elements of Resolution 866 of 2021.
- Which standard: HL7 FHIR R4 and the official terminology catalogs.
- Status: an obligation in force since April 15, 2026, with providers joining in groups throughout 2026.
The regulations that built it
IHCE did not come from a single regulation. It was built in layers, and understanding the order helps you know what each one requires:
| Regulation | What it contributed |
|---|---|
| Law 2015 of 2020 | Created the interoperable electronic health record and ordered the Ministry of Health and Social Protection (MinSalud) to adopt an implementation plan |
| Resolution 866 of 2021 | Defined the set of relevant clinical data, the mandatory terminology catalogs and the actors in the system |
| Resolution 1888 of 2025 | Adopted the RDA as the document that is exchanged and set the implementation deadline |
| RDA implementation guide | Defines the technical detail: FHIR profiles, codes and construction rules |
The gap between 2021 and 2025 explains why many institutions had the impression that interoperability was a pending, distant issue: for four years the what existed, but not the how or the when.
How the exchange works
The model has three movements, defined as services in article 3 of Resolution 1888:
- Generation. The provider delivering care builds the RDA from its own system, with the defined structure and codes.
- Submission. The RDA is transmitted to the national interoperability platform, over an encrypted channel and with the institution’s own credentials.
- Search and lookup. Another provider, the one that sees the patient next, finds and views that patient’s available RDAs, under the principles of purpose limitation and restricted access.
What matters about the design: the full clinical record is not centralized. What travels is the structured summary of each encounter. Custody of the full record remains with the institution that provided the care, under the rules of Resolution 1995 of 1999.
The three technical pillars
Exchange standard. HL7 FHIR R4. It defines how the information package is structured so any system can read it without bilateral agreements between vendors.
Terminologies. This is the part institutions underestimate most. Interoperating is not just sending a file: it means the receiver understands the same thing as the sender. That requires shared catalogs: ICD-10 and ICD-11 for diagnoses, CUPS for procedures, IUM for medications, plus LOINC and SNOMED CT. A diagnosis written in free text does not interoperate even if the file arrives intact.
Security and identity. Credentials issued by MinSalud, encrypted transport and access traceability. Health data is sensitive data under Law 1581 of 2012, and the mechanism has to be able to answer who viewed what and when.
What your software needs to connect
A short list to evaluate your own system or compare vendors:
- A structured, coded clinical record, not free-text fields. It is the underlying requirement that all the others depend on.
- Generation of the four RDA types from existing care workflows.
- Built on HL7 FHIR R4 according to the Colombian profiles in the official guide.
- Up-to-date catalog management, including the transition from ICD-10 to ICD-11.
- Authenticated, encrypted connection to the national platform.
- Integrated lookup of external RDAs in the patient view.
- Access audit for clinical information.
- Operation with intermittent connectivity, with later sync and no double data entry.
If a vendor answers this with “we are working on interoperability,” ask to see a real RDA being sent in a test environment. It is a concrete, verifiable demonstration.
How Omneri solves it
Omneri was built on a structured clinical record, which is the precondition for everything else. Relevant clinical data is captured in coded form during care, not transcribed afterward.
On that foundation, the system generates the four RDA types from the outpatient care, emergency department and inpatient care workflows; validates them before sending them; transmits them over an authenticated channel; and shows other providers’ available RDAs within the patient’s record. Every access to clinical information is logged with the user and the time.
Because interoperability does not live on its own, it works alongside the rest of the operation: patient journey, clinical operations and billing and collections on the same database.
You can read what an HIS is to see where interoperability fits, or request a demo.
Frequently asked questions
No. What is exchanged is the digital care summary for each encounter, not the full file. The clinical record remains in the custody of the institution that provided the care, with the retention and confidentiality obligations of Resolution 1995 of 1999. The model shares summaries; it does not move files.
The HCE, historia clínica electrónica or electronic health record, is an institution’s clinical record. IHCE is the national mechanism that lets those records talk to each other across institutions. The RDA is the specific document that travels through that mechanism. In order: the HCE is the content, the RDA is the envelope, IHCE is the mail.
Yes, within the defined scope of application. MinSalud organized implementation in groups based on technological capacity and connectivity, recognizing that a practice with no software and a high-complexity clinic do not start from the same point. That changes the support and the pace, not the obligation.
The value grows with adoption, but the obligation does not depend on it. And there is an immediate benefit even if the rest of the sector moves slowly: to generate RDAs you need a structured, coded clinical record, and that improves regulatory reporting, invoicing and internal auditing from day one.
They share the same origin, the record of care, but they go to different mechanisms. RIPS, the individual record of services provided, supports billing and the audit of the invoice; IHCE supports continuity of care. When clinical capture is done well once, both feed from it. When it is not, the institution ends up entering the same data twice for two different destinations.
Official source
IHCE microsite, Ministry of Health and Social Protection (opens in a new tab)Informational content for general guidance, not legal advice. The regulation in force and its technical annexes are the ones published by the competent authority.
Tell us how your hospital or clinic runs today.
We set up a demo around your case: size, sites and critical modules.
Book a demo
