ALIENCORE

Welcome back

Sign in to your client portal

Moon 01 · Digital world

HMS — Hospital Management System

One patient. One continuous record.

HMS is an independent, hospital-agnostic information system designed to connect the fragmented layers of a patient's journey into one continuous record.

OPDIPDERRXDXRADLABDOCRECORDUNIFIED TIMELINEV1V2V3V4NEXT

The problem

Information is fragmented.

Healthcare information is often scattered across many places. A patient may effectively become a new record every time they return.

Identify the patient once.
Build the record continuously.

Where a patient's information lives today

  • Departments
  • Visits
  • Admissions
  • Diagnostic machines
  • Prescriptions
  • Reports
  • Paper forms
  • Disconnected systems

One unified patient record

Architecture

From patient to every service.

A patient is identified once. Every department and service then reads from, and writes to, the same continuous record. Select the parts to explore them.
  1. 01

    Patient

    A person arrives.

    A new patient or a returning one. Either way, the hospital should know who is in front of it.

  2. 02

    Identity

    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.

  3. 03

    Unified patient record

    Build the record continuously.

    One continuous record per patient: illness, diagnosis, treatment, reports, prescriptions and services, ordered in time.

  4. 04

    Connected services

    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.

  5. 05

    Doctors · Departments · Staff

    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

Built around continuity.

01

Unified patient identity

Identify patients using information such as name and phone number, and maintain continuity across subsequent visits.

02

Continuous medical record

Maintain a connected timeline of illness, diagnosis, treatment, reports, prescriptions and services.

03

Diagnostics integration

Designed for standards-based integration with compatible medical devices and systems, including standards such as DICOM where applicable.

04

Paperless clinical workflow

Digital prescriptions, forms and records, with the ability to print when required.

05

Department connectivity

Relevant information follows the patient across departments rather than remaining isolated.

06

Retention and records

Support configurable retention policies appropriate to institutional and regulatory requirements.

07

Hospital-wide monitoring

A unified operational view of hospital activity.

Medical device integration

From machine output to patient intelligence.

Diagnostic machines produce output in their own formats. HMS is designed to receive it through standards and interfaces, and place it on the right patient's record.
  1. Medical devices

    • X-Ray
    • CT
    • MRI
    • Laboratory
    • Other compatible devices

    Independent systems

  2. DICOM · Standards · Interfaces

    How devices describe and send their output.

  3. Integration layer

    Receives, validates and matches output to the right patient and order.

  4. HMS

    System of record.

  5. Patient record

    Results join the patient's timeline.

  6. Doctor · Department · Decision

    Information reaches the people who need it.

What this does and does not mean

Designed for standards-based integration with compatible medical devices and systems. Compatibility is assessed per device and per site. HMS is the system of record and the integration layer; individual devices remain independent systems, and HMS does not control medical equipment.

Patient journey

The record continues even when the visit ends.

  1. 1

    Registration

    Identity is established, or matched to an existing record.

  2. 2

    OPD

    The consultation is recorded against the record.

  3. 3

    Diagnosis

    Clinical findings and diagnosis are noted.

  4. 4

    Lab / Imaging

    Orders go out; results come back to the same record.

  5. 5

    Report

    Reports are attached and visible to the right people.

  6. 6

    Prescription

    Issued digitally, printable when required.

  7. 7

    Follow-up

    Scheduled and recorded with the context of earlier visits.

  8. 8

    Admission

    A ward stay continues the same record.

  9. 9

    Discharge

    Summary and instructions are recorded.

  10. 10

    Future visit

    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

A hospital that can understand its own information.

A future intelligence layer can operate over the structured hospital knowledge base to help users navigate information, discover patterns and retrieve relevant records.

Navigate information

Ask where something is and be taken to the relevant part of the record.

Discover patterns

Surface operational and workflow patterns across structured hospital data.

Retrieve relevant records

Find the history that matters at the point of need.

Responsible by design

Designed to assist information retrieval, operational intelligence and clinical workflows — not replace clinical judgment. It does not diagnose, and it does not replace doctors.

Two systems

Two systems. One physical world.

HMS understands the hospital's information. PWIP understands the hospital's physical environment. Together, a physical event can arrive with its clinical and operational context.

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.

  1. Physical world

    People, spaces, equipment.

  2. PWIP

    Understands the physical environment.

  3. Events / observations

    Structured, with evidence.

  4. HMS / operational systems

    Understands the hospital's information.

  5. Context

    Physical events meet clinical and operational records.

  6. Intelligence

    Better questions, better answers.

Independent by design

HMS and PWIP are separate products. PWIP can operate without HMS, and HMS can operate without PWIP. Integration is optional, and neither is a feature of the other.

Start a mission

Build a hospital that remembers.

Tell us about your hospital, your departments and the systems you already run.