What Software Do Hospitals Use? A guide to the hospital technology stack

By TSB HealthCare · Published August 14, 2026

What software do hospitals use? Not one system — a stack. A typical hospital runs an EHR as the clinical record, revenue-cycle software for billing, departmental systems for labs and imaging, workforce tools for staff rostering, analytics on top, and patient access software for booking, check-in and flow — all wired together by an integration layer. This guide walks the stack layer by layer: what each system does, who the major vendors are, and where the gaps sit.

Layer 1: the EHR — the clinical system of record

The electronic health record is the centre of gravity. It holds the chart: diagnoses, medications, allergies, notes, orders and results. Clinicians live in it, and most other systems ultimately read from or write to it.

• Epic dominates large U.S. health systems and academic medical centres, and its MyChart portal is many patients’ main touchpoint with their record.
• Oracle Health (formerly Cerner) is the other giant, with a large hospital footprint and major government deployments.
• MEDITECH has deep roots in community and mid-size hospitals, prized for cost-effectiveness.
• Altera Sunrise and Paragon (the former Allscripts hospital products) and regional players round out the market; outside the U.S., national and provincial procurements shape the mix.

The EHR is a system of record, and that is the point to hold onto for the rest of this tour: it is excellent at storing the truth about a patient, and often mediocre at the operational work that happens around the chart.

Layer 2: practice management and revenue cycle

Revenue-cycle management (RCM) software handles registration, insurance eligibility, coding, claims, denials and payments. In big EHRs this is a module (Epic’s Resolute, for instance); many hospitals also run dedicated RCM vendors or clearinghouses alongside. Practice management systems play the same role for clinics and physician groups, bundling front-desk registration, billing and basic staff-side scheduling.

The pattern to notice here repeats down the stack: the core record lives in the EHR, and a specialist system takes over wherever the built-in module underperforms on a metric someone is accountable for — denial rates and days in accounts receivable, in this layer’s case.

Layer 3: patient access and scheduling

This layer decides how patients get in the door: appointment types and durations, provider and resource matching, referral and waitlist handling, online self-booking, and the reminders that keep booked patients showing up. EHRs include staff-facing scheduling modules, but patient-facing access — booking at 11pm without a phone call, rescheduling from a text message — is usually where dedicated patient scheduling software and online booking platforms take over. This layer also owns the economics of attendance: reminder programs, waitlists and slot backfill live here, which is why it is the layer that moves no-show rates.

Layer 4: patient flow and queue management

Scheduling builds the day; flow software runs it. This layer tracks the visit after arrival — check-in, queue position, called-next displays, room readiness, completion — and shows leaders where the day is backing up across sites. It is a distinct category from the EHR and from scheduling, covered in depth in our patient flow management guide. Kiosks and queue management systems live here.

Layer 5: LIS and RIS/PACS — labs and imaging

Diagnostics run on their own systems. The laboratory information system (LIS) manages specimens, tests and results in the lab. Radiology runs a RIS for imaging workflow and a PACS to store and read the images themselves, with modality worklists feeding the scanners. Both feed results back to the EHR, and both generate heavy appointment volume — which is why lab draws and imaging slots are frequent targets for dedicated scheduling and flow tooling.

Layer 6: workforce management — a different kind of scheduling

Hospitals also schedule their staff: nurse rosters, physician call schedules, shift bidding, time and attendance. This is workforce management — vendors like UKG, and healthcare rostering specialists — and it is a completely separate category from patient scheduling, even though both get called “healthcare scheduling software.” One allocates employees to shifts; the other books patients into slots. When you search for scheduling software, decide which problem you are solving first, because the vendor lists do not overlap.

Layer 7: analytics and business intelligence

Every layer above produces data; analytics turns it into decisions. Hospitals use the EHR vendors’ own reporting tools, general BI platforms, and domain-specific analytics for quality, finance and operations. Operational flow metrics — wait times, throughput, no-show rates, idle capacity — typically need data the EHR does not capture well, which is why flow analytics is its own discipline.

Layer 8: integration — how the stack talks

None of this works as islands. Hospital systems exchange data mainly through HL7 v2 messages — terse, decades-old, and still the workhorse for admissions, orders, results and scheduling events — routed through interface engines such as InterSystems or Rhapsody. The modern layer is FHIR, an API standard that exposes clinical data as web resources (Patient, Appointment, Observation) and powers most new patient-facing and third-party integrations. When you evaluate any new system, its HL7 and FHIR story determines how painful the install will be.

The layers everyone forgets

A few more systems round out the picture, even if they rarely lead the conversation. Pharmacy systems manage medication dispensing and interact tightly with the EHR’s ordering module. ERP and supply-chain software runs the hospital as a business — procurement, inventory, payroll, finance. Telehealth platforms carry video visits, sometimes as an EHR feature and sometimes as a standalone product. And a growing patient-engagement layer — portals, messaging, surveys, sometimes a healthcare CRM — handles the relationship between visits. Each of these is a market of its own; the point is simply that “hospital software” is a federation of a dozen categories, not a product you can buy.

The gap in the stack — and where TSB fits

Here is the pattern that emerges from the tour: the EHR is the system of record, but it is usually weak at patient-facing access and cross-site flow. It knows the truth about the chart; it does not make self-booking easy, keep lobbies moving, fill cancelled slots, or show a health authority which of its sites is backing up right now. That is why hospitals run dedicated patient access platforms alongside the EHR rather than instead of it.

That access-and-flow layer is what TSB HealthCare builds: one platform for patient scheduling, online booking, self check-in kiosks, queue management and flow analytics, integrating with the EHR, LIS and RIS you already run. It operates across 68+ sites today, with 3.3M+ appointments booked. If you are mapping your own stack’s gaps, our guide to choosing patient scheduling software is the next read.