RIPS in Colombia

RIPS, the Registro Individual de Prestación de Servicios de Salud (individual record of health services provided), is the data set a provider reports on every encounter: who was treated, what was done, with which diagnosis and for what amount.

For twenty years it was a statistical report. Today it is the mandatory support for the healthcare electronic invoice, and without it nothing gets collected.

In short

• What it is: the detailed record of each encounter that supports the healthcare electronic invoice.
• Who generates it: the provider, from its information system.
• How it is validated: in the MUV (Mecanismo Único de Validación, the single validation mechanism) of the Ministry of Health and Social Protection (MinSalud), which checks the RIPS JSON against the invoice XML.
• What it produces: the CUV (Código Único de Validación, the unique validation code), the seal that allows filing with the payer.
• Current regulation: Resolution 948 of 2026, which repealed Resolution 2275 of 2023 and Resolutions 558 and 1884 of 2024.

From statistical report to invoice support

The shift is worth understanding, because it explains why so many institutions still operate with a logic that no longer applies.

The reporting stage. Under Resolution 3374 of 2000, RIPS was a file generated after care and sent periodically. If it had errors, it was corrected and sent again. Cash flow did not depend on it.

The prior validation stage. With RIPS integrated into electronic invoicing, the order flipped: validate first, invoice second. A RIPS file with errors is no longer a report to correct; it is an invoice that does not exist.

The current stage. Resolution 948 of 2026 consolidated the model, moved the technical specifications out of the body of the regulation so they can be updated faster, and tightened validations that used to generate only warnings.

How the flow works

1. Care. The professional records the encounter in the clinical record: diagnoses, procedures, medications, supplies.
2. Generation. The system builds the RIPS in JSON format with the structure of the current Technical Document, and the invoice in XML according to the rules of DIAN (Colombia’s tax authority).
3. Validation. Both files are sent to the MUV, which checks rules on structure, content and the relationship between the JSON and the XML.
4. CUV. If every mandatory rule is met, MinSalud issues the Código Único de Validación: an encrypted alphanumeric string that acts as a seal of approval.
5. Filing. With the CUV, the invoice is filed with the payer, which issues a unique filing number and reports it to SIIFA.
6. Audit. The payer audits the invoice and can return it or raise claim objections (glosas), under the single manual of returns, objections and responses adopted by Resolution 2284 of 2023. Filing and objection deadlines are covered in healthcare electronic invoicing.

The rule that organizes everything else: no CUV, no filing.

What RIPS contains

RIPS is organized into data groups that follow the structure of care:

Group	What it records
Users	Identification, user type, coverage regime
Consultations	Outpatient care and its diagnoses
Procedures	What was performed, coded in CUPS (Colombia’s procedure classification)
Emergency department	Immediate care, admission route and outcome
Inpatient care	Admission, stay, discharge and cause
Newborns	Newborn data linked to the delivery
Medications	Dispensing, coded in CUM or IUM (national medicine codes)
Other services	Supplies, transfers and complementary services

Each group has mandatory fields and consistency rules between groups. The hardest validations to pass are not the ones on a single field but the ones that cross groups: a billed delivery has to have its newborn, a referral has to have services at the destination, the admission route has to be consistent with what was provided.

Why a RIPS gets rejected

Across many operations, rejections almost always come from the same four places, and none of them is a file problem:

Filler codes. Filling a mandatory field with a generic code so the file goes through. Rule RVC096 of Resolution 948 blocks this: only codes that exist in the reference tables are accepted.

Incomplete record at closing. The encounter is closed without the data RIPS needs, and someone tries to reconstruct it days later.

Inconsistency between modules. The billed service does not match what was recorded in the clinical record. It happens when billing and clinical are separate systems.

Outdated catalogs. A CUPS or CUM code that no longer exists in the current table.

The pattern: RIPS is a symptom. When it fails systematically, the problem is in how care is captured, not in how the file is generated.

What your software should do

1. Generate RIPS from the recorded encounter, without parallel data entry.
2. Validate before sending to the MUV, pointing to the exact record and field.
3. Keep catalogs current (CUPS, CUM, IUM, ICD-10 and ICD-11), updated by the vendor, not by the institution.
4. Check consistency between modules when the encounter closes, while it can still be corrected.
5. Incorporate Technical Document changes without quoting each update as custom development.
6. Trace the full cycle: care, RIPS, CUV, filing, objection and payment.
7. Manage objections with the supporting documents linked, so you can respond without rebuilding the case by hand.

Point 5 is no longer a contractual detail. Since Resolution 948, the specifications live in technical documents that can be updated without issuing a new regulation, so your vendor’s update speed is now an operational risk.

How Omneri solves it

In Omneri, RIPS is not generated: it is derived. The data comes from the clinical and administrative record that already exists, coded from the moment of capture.

• Pre-submission validation with the error located in the source record, not on a line of a file.
• Consistency checked when the encounter closes, while there is still someone to ask.
• Catalogs updated as part of the service.
• Full traceability from care to invoice, from invoice to filing, and from there to payment or objection.
• Objection management with the clinical record and the supporting documents in the same account.

You can see the billing and collections pillar, read what changed with Resolution 948 of 2026 or request a demo.