PUBLIC HOSPITALS
One patient journey across a whole health system
Patients move between hospitals, services and teams. The hospital system behind their care shouldn’t.
Proven in public health
One hospital system can still operate like many different ones.
Different systems, local processes and years of integrations create variation across hospitals. That makes services harder to manage consistently and information harder to move between facilities. Every system-wide change has to work through another set of local dependencies.
Two ways public hospitals run on Amalga.
One patient record across the region
- Register a patient once and carry that record to every hospital and service they use.
- Manage referrals, transfers, admissions and discharges on the same platform at every site.
- Keep the clinical systems each hospital already relies on. Amalga becomes the administrative layer they share.
Run regional services from one place
- Manage waitlists, surgical bookings and bed allocation from one view.
- See demand and capacity across hospitals, so patients can be booked where there is space.
- Control access by role, so authorised teams see what they need at each site.
One set of processes for the system
- Set common patient administration processes for every hospital.
- Make a change once and it applies across the system.
- Retire separate PAS environments as each hospital moves across.
Run the whole hospital on one connected system
- Carry each patient's record through outpatients, admission, theatre, wards, billing and discharge.
- Clinical, surgical, revenue and inventory teams work from the same information.
- Care recorded on the ward and in theatre carries through to the patient's bill.
Start with most of the hospital already configured
- Around 80% of hospital-wide processes work out of the box, leaving 20% for local fine-tuning.
- Support national social health insurance claims and local billing rules as part of the revenue workflow.
- Roll out across the whole hospital at once, or one area at a time, in the languages your teams use.
One platform as the hospital grows
- Add modules and AI tools, such as Pre-admission Risk Screening, as the hospital needs them, on the same platform and patient record.
- Report on the whole hospital from one source.
- Open new departments and services on the configuration already in place.
Public hospitals don’t run in isolation.
Patient administration sits at the centre of a much larger technology environment. National services, clinical systems, reporting platforms and specialist applications all depend on the information moving through it. Amalga supports HL7, FHIR and APIs, providing a common patient administration foundation while integrating with the systems that still need to do their job.
One system shouldn’t inherit every local workaround.
Moving from multiple legacy systems to a single PAS is an opportunity to decide what should become consistent across the system and where local variation still serves a purpose. Amalga gives public hospitals a common foundation for patient administration while allowing implementation to account for the integrations already operating around it.
See how one platform works across a region
South Island Patient Information Systems (SI PICS) in New Zealand provides a single Patient Administration System
across 33 hospitals and clinics, replacing nine legacy environments with one regional platform.
“SI PICS is more than an upgrade, it’s infrastructure for connected care.”
FAQs about how Amalga works in public hospitals
-
Yes. Amalga can provide a common PAS across multiple hospitals and services, replacing separate legacy environments with a shared patient administration foundation. SI PICS consolidated nine legacy PAS into one regional platform across the South Island.cription text goes here
-
No. Amalga is designed to integrate with the national, regional, clinical and specialist systems that need to remain. It supports HL7, FHIR and APIs, allowing the PAS to change without requiring the wider health technology environment to be replaced with it.
-
No. Some public health systems need a shared PAS and nothing else. Others take Amalga end to end, from patient administration through clinical, surgical, revenue and inventory workflows. Both run on the same platform, so a health system can start with one and extend later.
-
A shared system keeps patient administration information available across participating hospitals and services. This reduces duplication and supports smoother transitions when patients move between facilities.
Connect the teams across your public hospitals
Move from separate environments towards a single foundation.
We'll show you how Amalga fits the way your teams work today. Run the patient administration module on its own, or as the operational foundation for other Amalga modules.