PUBLIC HOSPITALS
One patient journey. Across a whole health system.
Patients move between hospitals, services and teams. Their administration shouldn't start again every time they do.
One health system can still operate like many different ones.
Different patient administration systems, local processes and years of integration create variation across hospitals. That makes it harder to manage services consistently, harder for information to follow patients between facilities, and harder to make a system-wide change without working through another set of local dependencies.
Some variation is necessary. Fragmentation doesn't have to be.
Run the patient journey and the hospital around the same information
Give teams one view of the patient journey
Give authorised teams access to the information they need as patients move between hospitals and services.
Keep patient administration connected when care moves from one facility or service to another.
Reduce the administrative handovers created by separate patient administration environments.
Manage patient administration across the system
Referrals, admissions, discharges, waitlists, surgical bookings and bed allocation through a shared PAS.
See patient administration activity across hospitals and services rather than facility by facility.
Support regional services from the same patient administration environment.d from the final account.
Standardise what’s common
Establish common patient administration processes across hospitals and services.
Accommodate genuine operational differences where local teams need to work differently.
Make system-wide changes once rather than repeating them across separate PAS environments.
Move to a shared PAS without recreating everything around it
National services, clinical systems, reporting platforms and specialist applications still need to connect to patient administration.
Amalga supports HL7, FHIR and APIs, so those systems can continue to do their job while patient administration moves to a shared platform. Standardise what should be common across the system while accommodating the workflows, integrations and local differences that still need to remain.
One platform across the South Island
SI PICS provides a single Patient Administration System across 15 hospitals, replacing nine legacy PAS environments with one regional platform.
“SI PICS is more than an upgrade, it’s infrastructure for connected care.”
Got questions 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. In New Zealand, 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.
-
Yes. Amalga can standardise common patient administration processes while accommodating genuine operational differences between hospitals and services. This creates consistency where it benefits the health system without assuming every facility works identically.
-
Yes. Amalga can provide shared patient administration infrastructure across multiple hospitals and services. In New Zealand, SI PICS provides a single regional platform across 15 South Island hospitals, supporting 8,000 users and a population of 1.2 million.
-
A shared PAS keeps patient administration information available across participating hospitals and services. This reduces duplication and supports smoother transitions when patients move between facilities.
Bring patient administration together across the health system.
Move from separate PAS environments towards a shared foundation for patients, teams and services