The Elo Cloud family
Registers & Governance

Statutory Registers, Kept from Live Activity

Regulatory registers are non-negotiable — and in most hospitals a monthly clerical ordeal of copying from files into ledgers, hoping nothing was missed. EloHIMS keeps the core statutory registers automatically, from live activity, so the regulatory return becomes a click instead of a fortnight of transcription.

Book a demo Start free trial
Statutory registers
Auto-maintained
Births registerlive
Deaths registerlive
ADT registerlive
Operation Theatre registerlive
Emergency register1-click return

Registers that keep themselves current.

The system maintains ready-made statutory registers — births, deaths, admission/discharge/transfer (ADT), Operation Theatre and Emergency — and populates them continuously as those events actually happen. A birth recorded in maternity, a discharge processed on the ward, a case done in theatre: each flows into the appropriate register the moment it occurs, so the register is always current, always complete, and never dependent on someone remembering to write it down. EloHIMS keeps the registers; registering the facility and answering an inspection remain the hospital's own work, done from records that are already in order.

What you get

Registers kept from live activity, not clerical effort

Births registerKept automatically from maternity and delivery activity as each birth is recorded — with a column for the baby's own MRN.
Deaths registerAn inpatient death recorded at discharge writes the death record and its mortality-register entry, with the timing band; Emergency deaths are recorded too.
ADT registerCaptures admissions, discharges and transfers as they are processed on the ward.
Operation Theatre registerBuilt from actual theatre cases and activity, with no duplicate data entry.
Emergency registerPopulated from Emergency department attendances as patients present.
Continuously auto-maintainedRegisters are populated from live activity, eliminating manual transcription into ledgers.
Always current & completeEntries are created when the event happens, not reconstructed later from memory.
Consistent with the recordEach register draws from the same source data as the clinical event itself.
One-click regulatory returnsData is already assembled rather than compiled by hand each month.
A4 & 80mm printingRegisters and returns are ready for submission and filing on any printer.
Full audit trailEvery entry is logged, giving regulators and auditors a defensible record.
Death certificate cause chainCauses recorded as (a), (b), (c) and part II, printed on the certificate and written to the register.
Police intimation for MLC deathsA death is medico-legal when its ER visit was an MLC or the patient carries an MLC alert; the body is not released until the police are intimated.
Body release to a named personReleased to a named person with their relation and CNIC — a non-MLC body only after certification.
Baby's MRN on the birth registerEach live birth gets its own patient file and MRN, linked to the mother, and the birth register shows it.
Deaths & Mortuary

Certified, intimated, released — in that order

When a patient dies on the ward, recording the discharge as expired writes the death record and the mortality-register entry together; a death in Emergency is recorded the same way. The Deaths & Mortuary page, in the IPD sidebar, then takes each body through three steps.

The doctor certifies the cause of death as a chain — (a), (b), (c) and part II — which prints on the death certificate and is written to the register; an unnatural manner of death on a case that is not medico-legal is stopped. A medico-legal death needs police intimation, never dated before the death, with its own print. Release goes to a named person with relation and CNIC: a non-MLC body only after certification, an MLC body only after police intimation.

1. Certify
cause chain (a)/(b)/(c) + II, certifying doctor and time; death-certificate print.
2. Intimate the police (MLC)
for medico-legal deaths; police-intimation print.
3. Release the body
to a named person, with relation and CNIC — only once the earlier steps are done.
"Baby of" file at delivery
date and time of birth, sex and birth weight, on the next MRN.
Mother and baby linked
both ways, shown on the patient profile.
Baby's MRN column
on the birth register and the labour-room list.
NICU under the baby's own MRN
"Admit baby to NICU" straight from the delivery.
Births register

Every live birth gets its own record

Recording a delivery gives a live-born baby its own patient file and MRN on the hospital's usual numbering, linked to the mother. A stillbirth does not get a file. Older births can be given a file with a "Create baby's file" button.

The birth register carries the baby's MRN beside the mother's entry, so the register, the NICU admission and the baby's later visits all point to the same record. More on the maternity side in obstetrics and gynaecology.

Quality, Incidents & Feedback

You cannot improve what you never hear about

Near-misses go unlogged, complaints get lost at the front desk, and by the time a pattern is obvious it has already cost the hospital. EloHIMS closes the loop: staff record incidents when something goes wrong or nearly does, and capture patient feedback about their experience — both in structured records rather than a drawer.

Those entries feed quality review, giving your governance process a live, growing body of evidence. Critically, incident and feedback signals also flow up to the Executive Command Centre, so leadership sees emerging quality and safety issues alongside the revenue and occupancy figures — problems become actionable signal instead of folklore.

Incident capture
a structured way to log events and near-misses the moment they happen.
Patient feedback capture
the patient's experience recorded directly in the system.
Feeds quality review
governance works from live, accumulating evidence rather than anecdote.
Surfaces to the Command Centre
quality and safety signals in front of leadership alongside operational metrics.
Audited & isolated
a full audit trail on every entry, with sensitive quality data kept strictly per facility.
The outcome

Core regulatory registers are kept automatically from live activity — and incidents and feedback feed quality review and reach leadership — so statutory returns become a single click and problems become actionable signal. Deaths are certified, intimated and released in order, and every newborn is on the register with an MRN of their own.

Where the register entries come from

Make the regulatory return a click.

Statutory registers kept from live activity, quality signals surfaced to leadership — registers without the clerical burden.

Book a demo Start free trial
Schedule a demo