Public Hospitals
Patients move between hospitals, services and teams. The hospital system behind their care shouldn’t.
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.
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.
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.
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.
Kirsty Martin - Regional Group Manager Integration & Delivery, Health NZ Te Whatu Ora
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.
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.
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.
