Resolution 948 of 2026

On May 14, 2026, the Ministry of Health and Social Protection (MinSalud) issued Resolution 948, which regulates the individual record of health services provided (Registro Individual de Prestación de Servicios de Salud, RIPS) as support for the electronic sales invoice (Factura Electrónica de Venta, FEV) in healthcare.

It is not just another amendment to the previous text: it repeals Resolutions 2275 of 2023, 558 of 2024 and 1884 of 2024, and replaces them with a single regulatory text.

In short

• What it does: consolidates into a single regulation the model of RIPS as support for the healthcare electronic invoice.
• What it repeals: Resolutions 2275 of 2023, 558 of 2024 and 1884 of 2024.
• What changes at its core: the technical annexes leave the body of the resolution and become technical documents published on the FEV RIPS microsite, which can be updated without issuing a new regulation.
• What it introduces: the CUCON (Código Único de Contrato, the unique contract code) and new obligated parties.
• Key dates: June 1, 2026, July 1, 2026 and September 2026.
• What does not change: RIPS is still mandatory support for the invoice, and without a CUV the invoice cannot be filed with the payer.

The structural change: annexes outside the regulation

This is the change with the most consequences in the medium term, and the one discussed least.

Until now, field specifications and validation rules lived inside the resolution. Changing a rule required issuing a new regulation, which produced the chain of successive amendments that Resolution 948 came to close.

Now there are two separate technical documents:

• Technical Document 1: specifications of the data fields and validation rules of RIPS as support for the FEV.
• Technical Document 2: health sector data fields in addition to those used to generate the FEV.

They are published on the FEV RIPS microsite with version, date and change control, and they are updated without amending the resolution. Governance runs through the Technical Committee of SIIFA, the health system’s integrated financial and care information system (Resolution 2669 of 2025), with approval from the Vice Ministry of Social Protection.

For an IPS (instituciones prestadoras de salud, Colombia’s healthcare provider institutions), the practical reading is uncomfortable but clear: validation rules can now change faster than before. Monitoring the microsite is no longer optional, and your software vendor’s ability to incorporate changes without quoting a development project becomes a top selection criterion.

CUCON: the contract stops being free text

The contract number left room for everyone to write it their own way. Resolution 948 replaces it with the unique contract code (Código Único de Contrato, CUCON): a 64-character string generated with SHA-256 by SIIFA, once the payer (entidad responsable de pago) registers the contract and the contractor accepts it.

The effect is traceability: every invoice is tied to the exact contract under which the service was provided, with no ambiguity from typing.

Alongside the CUCON, the CUV (Código Único de Validación, the unique validation code) keeps operating: the encrypted string that the single validation mechanism (Mecanismo Único de Validación, MUV) issues when the RIPS meets all mandatory rules. The underlying rule did not change: without a CUV, the invoice cannot be filed with the payer.

New obligated parties and exclusions

Joining the model (article 2, item 4) are manufacturers, importers and marketing authorization (registro sanitario) holders that make bulk sales of medicines, devices or supplies to EPS (entidades promotoras de salud, Colombia’s health insurers) and other payers. They must validate conventional invoices in the MUV module and register the CUCON.

Expressly excluded from the health scope are driver medical certification centers, research centers, cosmetic surgery and alternative medicine without public funding. For them, RIPS is not mandatory and only the electronic invoice validated by the DIAN (Colombia’s tax authority) applies.

It also clarifies that RIPS cannot be required for public health or for the Collective Interventions Plan (Plan de Intervenciones Colectivas, PIC), with a specific MUV module for those conventional invoices.

Billing without a contract

A mandatory data group, facturasincontrato, is added for cases where the service is provided without a contract with the payer. It applies only in these scenarios:

• Emergency department care
• Care covered by ADRES (the health system’s funds administrator), SOAT insurers (mandatory traffic accident insurance) and voluntary health plans
• Care ordered by tutela rulings (constitutional protection actions) or court orders
• Portability and mass assignment of members
• Exceptional cases based on quotes or authorizations without a contract
• Organ recovery management for transplant

The dates that matter

Date	What happens
June 1, 2026	Validation rules that move from notification to rejection. The requirement for field M03 (medication authorization) is removed
July 1, 2026	Structural adjustments: ICD-11 and the VIDA code as mandatory fields, dispensing value fields (M28 and S18), new consistency rules
September 1, 2026	Full implementation. The SIRAS field (U12) becomes enforceable for type 10 users, with three months in notification before moving to rejection

The shift from “notification” to “rejection” is the one you feel in your cash flow. A validation in notification lets the invoice through with a warning; in rejection, there is no invoice. Errors that were noise in a report for months turn into stalled billing.

What changes in RIPS

Structural additions

• ICD-11 and the VIDA code: new mandatory fields in consultations, procedures, emergency department, inpatient care, newborns and medications.
• SIRAS (field U12): mandatory for type 10 users, traffic accident victims.
• Fields M28 and S18: dispensing value, only when the pharmaceutical manager (gestor farmacéutico) bills the payer, and only for the value of the logistics.

Permanent removal

• Field M03 (medication authorization number): removed, and requiring it for outpatient and inpatient medications is prohibited.

New validation rules with rejection

• RVC062, destination traceability: if the patient was referred to another service, there must be service data at that destination.
• RVC054, admission consistency: the admission route must be consistent with the services provided.
• RVC096, code integrity: blocks fake or filler codes; only codes that exist in the CUPS (procedures), CUM and IUM (medications) reference tables are accepted.
• RVC023, birth traceability: if a delivery or C-section is billed, the newborn’s data must be reported.

RVG015 is relaxed: a patient can go directly to observation without a prior emergency department consultation, typical of referred patients, and the rule moves from rejection to notification.

Adjustment notes. They are used only to update clinical data and do not affect the amount. Data with a financial impact still requires a credit or debit note.

A point in providers’ favor: payers cannot require structures or supporting documents beyond those defined in the regulations.

What your software must do to comply

1. Generate RIPS in the current version of Technical Document 1, and update when that document changes, without charging each change as custom development.
2. Validate before sending to the MUV, showing which record and which field fail.
3. Capture ICD-11 and the VIDA code at the point of care, not in a later correction.
4. Work with CUCON, taking the code of the contract registered in SIIFA instead of a text field.
5. Handle the no-contract scenarios with the corresponding data group.
6. Meet RVC062, RVC054, RVC096 and RVC023 at the source, because they are consistency rules across modules: they are met if the care was recorded correctly, not if someone fixes the file at the end.
7. Adjustment notes that distinguish clinical corrections from financial corrections.

Rule RVC096 deserves special attention: it prohibits filler codes. Many institutions have the practice of filling a mandatory field with a generic code so the file passes. That no longer works.

How Omneri solves it

Omneri generates RIPS from the recorded care, not from a separate upload. Codes come from the official catalogs at the moment of capture, and the invoice is built with the clinical support already linked.

• Validation before the MUV, with the error detail located in the record where it originates.
• Regulatory updates included in the service: when the Technical Document changes, the system changes.
• CUCON and no-contract scenarios built into the billing flow.
• Consistency rules checked when the care encounter is closed, so the rejection does not show up weeks later in the filing process.
• Management of claim objections (glosas) and returns with the clinical record and supporting documents in the same account. See healthcare electronic invoicing.

You can see the billing and collections pillar or request a demo.