All of care on one shared record
Admissions, records, lab, pharmacy and billing on a single clinical history.


Systems that do not integrate cost more than the ones you lack
- The record on paper, with a different copy held by each area
- Manual retyping between laboratory, pharmacy and the cashier
- Services delivered that never reach the invoice, with no way to quantify the leakage
The modules and how they integrate
Itera Salud connects admissions, the clinical record, laboratory, pharmacy and billing in a single system: each area records what falls to it, and all of them read the same clinical history, instantly.
The health record, at the point of care
It is the core of the system: everything else writes here or reads from here. On the same screen where they document, the physician sees allergies, active medication and prior studies.
- ICD-10
- Encrypted data
- Access audit log






The record, in your pocket
The same clinical history on the phone, wherever the patient is seen.


Analytics and compliance
Occupancy, waiting times and activity by specialty, up to date.
- Occupancy
- Readmissions
- Time per module


Admissions and scheduling
Appointment, arrival and triage on one schedule. The system sets the duration, and overlaps are flagged before you save, not after.
- Schedule by physician
- No overlaps
- No-show rate tracked
Orders and results
What the physician orders in the consult lands in the department's queue and comes back signed into the record. No paper in between.
- LOINC
- Traceable sample
- Signed report
Pharmacy and inventory
Stock by site, batches with their expiry and a ledger of every movement. On invoicing, what was dispensed leaves inventory on its own.
- Batches and expiry
- Stock ledger
- Real-time stock
Billing and payments
Invoice numbering by site, discounts that require a reason, and payments applied to the patient's account — even partial ones.
- Numbering by site
- Discount with reason
- Partial payment
Module by module, at the hospital's pace
Going live does not require replacing the whole hospital in a single window. The area of greatest impact is enabled first and the rest follows from there, on the same database and with no migration when the next module comes in.
Start with one module
Whichever area hurts most today, in production and on real data.
Add the ones you need
Each one lands on the same database. Nothing to export or key in twice.
The whole hospital
With no final migration: by the time you get here the data has been in for months.