Hospital information system (HIS)
An HIS is not the clinical record with more screens. It is the institution's nervous system.
HIS stands for Hospital Information System: the system that integrates the clinical, administrative and financial information of a healthcare institution on a single database.
The key word is “integrates.” What sets an HIS apart is not the number of modules, but that data captured at one point is available everywhere else without anyone carrying it over.
What sets it apart from other systems
The most common confusion is between HIS, EMR and ERP. They are not the same, and they do not compete with each other:
| System | What it covers | The question it answers |
|---|---|---|
| EMR / EHR | The patient’s clinical record | What was done to this patient? |
| ERP | The organization’s resources: finance, purchasing, payroll | How does the institution sustain itself? |
| HIS | Both, on a common base | What happened, and what does it mean clinically and financially? |
| LIS / RIS | Laboratory / diagnostic imaging | What did this test show? |
An institution can have an excellent EMR and an excellent ERP and still have the underlying problem: two versions of the truth about the same patient that someone has to reconcile by hand.
The modules of an HIS
Patient journey. Scheduling, admissions, triage, inpatient care, census, beds, discharge and referral. It is the patient’s path and the point where information originates.
Clinical record. Electronic health record, notes, progress notes, orders, consent forms and sick leave certificates.
Diagnostic support. Laboratory, imaging, pathology: orders that originate in care and results that flow back into it.
Pharmacy and supplies. Dispensing, crash cart, inventory and consumption tied to the clinical act that generated it.
Billing and collections. Electronic invoicing, contracts, accounts receivable, claim objections (glosas), cash desk and account settlement.
Administration. Warehouse, purchasing, accounting, staff shifts, fee schedule and cost centers.
Regulatory reporting. Generated from data already captured, validated before it is submitted.
How it works in practice
The best way to understand an HIS is to follow one piece of data through an episode of care:
- Admission. The patient’s details, their contract and the admission route are recorded. Once.
- Care. The physician documents in the record and generates orders. They do not type the patient’s name again.
- Diagnostic support. The order reaches the laboratory; the result returns to the record with no manual step.
- Pharmacy. Dispensing deducts from inventory and is linked to the patient’s account.
- Closing. The encounter is closed with the required consents; if any are missing, it cannot be billed.
- Billing. What actually happened is billed, with the clinical support already attached.
- Reporting. Regulatory reports are derived from that same record.
In a fragmented system, every arrow in that chain is a person copying information. In an HIS, they are queries to the same database.
What a modern HIS should have
Beyond the list of modules, five criteria separate a current HIS from one that only digitized paper forms:
Data is captured where it happens. If, to meet a reporting requirement, someone has to go into a separate module and retype what is already in the record, the system moved the problem instead of solving it.
Validation before submission. Errors in a report should be caught in-house, not when the receiving entity rejects it weeks later.
Offline operation. In Colombia, connectivity fails. Critical modules must keep running and sync when the connection comes back, with no double data entry.
Full traceability. From care to invoice, from invoice to filing, from filing to payment or objection. And an audit trail of who viewed which record.
Regulatory updates included. The sector changes its reporting obligations frequently. If every change is quoted as custom development, the real cost of the system is not the one in the proposal.
The HIS in the Colombian context
An HIS designed for another health system can cover the clinical side well and fall short exactly where the cash flow of a Colombian IPS (instituciones prestadoras de salud, Colombia’s healthcare provider institutions) is at stake.
Here the system has to understand contracts with EPS (entidades promotoras de salud, Colombia’s health insurers), objections and how to respond to them, MIPRES (the prescription platform for services outside the basic benefits plan), RIPS (the individual record of services provided), electronic invoicing with DIAN (Colombia’s tax authority), SOAT (mandatory traffic accident insurance) and FURIPS (the claims form for accident and catastrophic event care). Not as extensions added later, but as part of the core, because they cut across daily operations.
And it has to move at the pace of regulation. Resolution 948 of 2026 rebuilt RIPS as the supporting document for the healthcare electronic sales invoice (FEV); Resolutions 866 of 2021, 1888 of 2025 and 1799 of 2026 took clinical record interoperability all the way to the digital care summary (RDA) and medication dispensing; and SIIFA (Resolution 1962 of 2025) connected contracting, invoicing and payments on a single platform of the Ministry of Health and Social Protection (MinSalud). An HIS that does not keep up with that chain forces the IPS to plug the gaps by hand.
Omneri is an HIS platform built for that context: it covers the patient journey, clinical operations, billing and collections, and administrative operations, with Colombian regulations included in the service.
You can see what each pillar covers, check what it looks like inside or request a demo.
Frequently asked questions
The electronic health record (EHR), or EMR, is the patient’s clinical record. The HIS includes it, but also covers scheduling, admissions, billing, inventory, accounting and regulatory reporting on the same database. The EHR answers what was done to the patient; the HIS, what that means for the whole institution.
In many cases, yes, because a complete HIS already covers purchasing, inventory, accounting and cost centers. Institutions with complex corporate structures sometimes keep a corporate ERP and integrate the HIS through an API. The decision depends on how much of the accounting lives outside care delivery.
Four to twelve weeks for a mid-sized institution with several sites, depending on how many modules are turned on and how clean the source data is. It is done in phases so care does not stop. We cover it in detail in the guide to migrating without downtime.
The clinical record has legal retention and availability requirements, so it must be exportable in full and in a readable format. It is a question to ask before signing, not after: ask to see a real export during the evaluation.
Yes. The inpatient modules are simply not turned on. The value of integration (data that is not repeated across care, billing and inventory) does not depend on whether there are beds.
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
