SIIFA
The health system's contracts, invoices, filings and payments, recorded in one place.
SIIFA, the Sistema de Información Integral Financiero y Asistencial (integrated financial and care information system), is the platform of the Ministry of Health and Social Protection (MinSalud) where the contracts, invoices, filings and payments of Colombia’s General Social Security Health System are recorded.
Its purpose is to make the flow of funds visible: knowing what was contracted, what was invoiced, what was filed and what was paid, without depending on each party to report it in its own way.
In short
- What it is: the health system’s national platform for financial and care traceability.
- Where it comes from: Law 1966 of 2019 mandated it; Decree 228 of 2025 regulated it; Resolution 1962 of 2025 defined its structure and modules.
- How many modules it has: four. Contracting, FEV and RIPS (the electronic sales invoice and its service record), invoice tracking and payment tracking.
- Who reports: payers and health service providers, including health technology suppliers and pharmaceutical managers (gestores farmacéuticos).
- What identifier it introduces: the CUCON, the unique contract code.
- How it is rolled out: gradually and progressively, by groups and by modules, over 2025 and 2026.
The regulations behind it
| Regulation | What it contributed |
|---|---|
| Law 1966 of 2019 | Mandated the integrated financial and care information system (art. 3) and the registry of contracts for health services and technologies (art. 4) |
| Decree 228 of 2025 | Regulated SIIFA and defined who it applies to |
| Resolution 1962 of 2025 | Set the structure, responsibilities, manuals, technical committee, reporting frequency and gradual rollout |
Who it applies to
The scope is broad and goes beyond IPS (instituciones prestadoras de salud, Colombia’s healthcare provider institutions):
Payers: EPS (entidades promotoras de salud, Colombia’s health insurers), adapted entities, ARL (occupational risk insurers), territorial entities, entities that administer special and exception regimes, the health fund for the incarcerated population, SOAT (mandatory traffic accident insurance) insurers, voluntary health plans and ADRES (the health system’s funds administrator).
Providers and suppliers: IPS, independent professionals, special patient transport, entities with a different corporate purpose, and health technology suppliers, including logistics operators, pharmaceutical managers, non-governmental organizations and universities that carry out these activities.
The four modules
1. Registry of contracts for health services and technologies. The agreements, with their detail of services, amendments and closeout. This is the module that generates the CUCON.
2. Healthcare FEV and RIPS. It operates through the Mecanismo Único de Validación (MUV, the single validation mechanism). This is where RIPS and the electronic invoice are cross-checked and the CUV (unique validation code) is issued.
3. Invoice tracking. Filing, returns, claim objections (glosas), other objections and responses. This is where the unique filing number that the payer generates and reports is recorded.
4. Payment tracking. Treasury payments from paying entities and direct disbursement (giro directo) made by ADRES.
Taken together, the four modules rebuild the full money cycle: from contract to invoice, from invoice to filing, from filing to payment.
CUCON: the code that ties the invoice to the contract
The Código Único de Contrato (unique contract code) is a 64-character string generated by SIIFA with SHA-256, once the payer registers the contract and the contractor accepts it.
Its job is to remove ambiguity. Before, the contract number traveled on the invoice as free text, with all the typing variations that implies. With the CUCON, each invoice is tied to the exact contract under which the service was provided.
Since Resolution 948 of 2026, the CUCON is part of the contract identification in the XML of the healthcare electronic invoice. In other words: SIIFA is no longer a parallel system and has become part of the billing flow.
How it is rolled out
Resolution 1962 of 2025 provided for a gradual and progressive rollout, with a transition period between July 2025 and June 2026, organized by groups of stakeholders and by modules. Each combination goes through an awareness and testing stage before it goes live.
The contract registry module was the first to go live, and the rollout of the others was staggered over 2026. The current schedule by group is published on MinSalud’s official channels, and it is worth checking it there before you plan an internal date.
What it means for an IPS
The contract no longer lives only in a PDF. If the contract is not registered and accepted in SIIFA, there is no CUCON. And without a CUCON, the invoice’s contract identification is incomplete.
Filing becomes verifiable. The payer generates a unique filing number and reports it. It is no longer possible to argue about whether an invoice was filed or not.
The objection cycle is on record. Returns, objections and responses live in the invoice tracking module, with dates.
Timelines are exposed. When contract, filing and payment are on the same platform, delay has a name and a date. For a provider with overdue accounts receivable, that is a tool.
What your software must do to integrate
- Take the CUCON from the contract registered in SIIFA and include it in the invoice, instead of a free-text field.
- Generate the invoice and RIPS in the current versions, to pass the MUV and get the CUV.
- Record the unique filing number issued by the payer and keep it linked to the invoice.
- Manage returns, objections and responses with dates and supporting documents, consistent with what is reported in SIIFA.
- Reconcile payments against what was filed, including direct disbursement from ADRES.
- Keep contract setup (rate schedule, contracted services, effective periods) in sync with what is registered on the platform.
Point 6 is where operations break most often in practice. When the system’s rate schedule does not match the registered contract, the difference shows up as an objection months later.
How Omneri solves it
Omneri handles the contract as an entity in the system, not as a loose piece of data on the invoice: the rate schedule, contracted services and effective periods live in the same place that billing draws from.
- CUCON included in the contract identification within the billing flow.
- RIPS and invoice generated from the encounter, validated before they reach the MUV.
- Filing and its unique number recorded and linked to each invoice.
- Objections and returns with linked clinical support and traceability of timelines.
- Accounts receivable reconciled against what was filed and what was actually paid.
You can see the billing and collections pillar or request a demo.
Frequently asked questions
No. The single validation mechanism (MUV) is the component that validates RIPS against the invoice and issues the CUV, and it operates as part of SIIFA’s healthcare FEV and RIPS module. SIIFA is the whole system; the MUV is one of its parts.
The payer registers the contract, and the contractor accepts it. The CUCON is created from that acceptance. So the IPS is not left out: without its acceptance there is no code, and without the code the invoice’s contract identification is incomplete.
The invoice loses the standardized identification of the contract under which the service was provided. Since the CUCON has been part of the healthcare electronic invoicing model since Resolution 948 of 2026, it is worth checking that your active contracts are registered and accepted before you invoice against them.
Resolution 1962 of 2025 set a gradual and progressive rollout by groups and by modules, with a transition period between July 2025 and June 2026. The date that applies to a specific institution depends on its group and module, and the current schedule is published on MinSalud’s official channels.
It does not change the objection procedure, which follows its own rules and deadlines. What changes is visibility: filing, returns, objections and responses are recorded on a shared platform, with dates both parties can verify.
Official source
Resolution 1962 of 2025, 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
