Frequenty asked questions

What is Amalga? +

Amalga is a modular hospital information system (HIS) that connects clinical, administrative, and operational workflows into a single platform.

Modules for patient administration, clinical management, surgical management, revenue cycle management, inventory, and patient experience, and can be rolled out one by one or grouped together.

Who is Amalga for? +

Amalga is built for hospitals and multi-site hospital networks that need a standards-based HIS without the cost and rigidity of legacy enterprise systems. It is particularly suited to hospitals in South East Asia and New Zealand.

Current deployments include private hospital groups (Sun Group, Vinmec), public health systems (Te Whatu Ora / Health New Zealand), and specialty hospitals (Rutnin Eye Hospital, Kaweka Hospital).

How is Amalga different from legacy hospital information systems? +

Amalga is modular and standards-based, so a hospital adopts the modules it needs on its own timeframe rather than committing to a single multi-year replacement programme. Each module goes live and delivers value on its own, and connects to existing systems through HL7 and FHIR interfaces. Scope, cost and clinical disruption stay contained to one module at a time.

Who owns Amalga today? +

Amalga is owned by McCrae Tech (founded by Ian McCrae, who also founded Orion Health).

How is Amalga deployed? +

Amalga supports both on-premise and cloud-hosted deployments. Hospitals can choose based on their infrastructure, data residency requirements, or existing IT investment.

For multiple hospital rollouts, Amalga can be hosted in a multi-tenant cloud.

How does Amalga work with multi-site hospital networks? +

Amalga uses a hub-and-spoke model for fast time-to-value across multi-site hospital networks.

A central hub coordinates shared data and workflows while individual sites retain local configuration. This accelerates deployment and helps manage costs.

Do we need to roll out every Amalga module at the same time? +

No. Amalga is modular by design. Hospitals can roll out one or several modules (Patient Administration, Clinicals, Surgical, Revenue Cycle, Inventory, Patient Experience) on a timeframe that suits rather than committing to a full-suite implementation upfront.

How long does a typical Amalga implementation take? +

For multi-site hospital networks, the first site rollout typically takes six months with every additional hospital coming on board within 10 weeks.

Is Amalga interoperable? +

Amalga is built on HL7 and FHIR standards. It exposes open APIs and maps to FHIR R4, HL7 v2/v3 and SNOMED CT, so hospitals can plug into national and regional exchange platforms. This means Amalga integrates with the systems a hospital already runs, rather than requiring a rip-and-replace of existing infrastructure.

Does Amalga support local regulatory and language requirements? +

Yes. Amalga adapts to local languages, regulations, and clinical workflows. Current deployments operate in New Zealand, Vietnam, Thailand and Myanmar with local teams supporting them.

Does Amalga include AI capabilities? +

Yes. Amalga includes dedicated AI features: Scribe for ambient documentation and dictation, Pre-admission screening, and Revenue leakage detection for complete revenue capture.