Patient
A person arrives.
A new patient or a returning one. Either way, the hospital should know who is in front of it.
Moon 01 · Digital world
HMS — Hospital Management System
HMS is an independent, hospital-agnostic information system designed to connect the fragmented layers of a patient's journey into one continuous record.
The problem
Identify the patient once.
Build the record continuously.
Where a patient's information lives today
One unified patient record
Architecture
A person arrives.
A new patient or a returning one. Either way, the hospital should know who is in front of it.
Identify once.
The patient is identified using details such as name and phone number. A returning patient is matched to the existing record instead of becoming a new one.
Used together with other details to recognise the patient.
Build the record continuously.
One continuous record per patient: illness, diagnosis, treatment, reports, prescriptions and services, ordered in time.
Every service writes to the same record.
Select a service to see how it connects.
Outpatient consultations, linked to the existing record from the first visit.
The right history, at the point of care.
Relevant information follows the patient instead of staying where it was created.
See the relevant history when the patient is in front of them.
Key capabilities
Identify patients using information such as name and phone number, and maintain continuity across subsequent visits.
Maintain a connected timeline of illness, diagnosis, treatment, reports, prescriptions and services.
Designed for standards-based integration with compatible medical devices and systems, including standards such as DICOM where applicable.
Digital prescriptions, forms and records, with the ability to print when required.
Relevant information follows the patient across departments rather than remaining isolated.
Support configurable retention policies appropriate to institutional and regulatory requirements.
A unified operational view of hospital activity.
Medical device integration
Medical devices
Independent systems
DICOM · Standards · Interfaces
How devices describe and send their output.
Integration layer
Receives, validates and matches output to the right patient and order.
HMS
System of record.
Patient record
Results join the patient's timeline.
Doctor · Department · Decision
Information reaches the people who need it.
What this does and does not mean
Patient journey
Identity is established, or matched to an existing record.
The consultation is recorded against the record.
Clinical findings and diagnosis are noted.
Orders go out; results come back to the same record.
Reports are attached and visible to the right people.
Issued digitally, printable when required.
Scheduled and recorded with the context of earlier visits.
A ward stay continues the same record.
Summary and instructions are recorded.
The patient returns. The record is already there.
Next visit, the same identity is matched, and the record picks up where it left off.
Intelligence layer
Ask where something is and be taken to the relevant part of the record.
Surface operational and workflow patterns across structured hospital data.
Find the history that matters at the point of need.
Responsible by design
Two systems
HMS · digital world
Understands the hospital's information.
Patients, records, orders, results and services.
PWIP · physical world
Understands the hospital's physical environment.
People, objects, spaces, movement and events.
Physical world
People, spaces, equipment.
PWIP
Understands the physical environment.
Events / observations
Structured, with evidence.
HMS / operational systems
Understands the hospital's information.
Context
Physical events meet clinical and operational records.
Intelligence
Better questions, better answers.
Independent by design
The universe
ALIENCORE
Optional integration
Start a mission
Tell us about your hospital, your departments and the systems you already run.