The Elo Cloud family
Schedule a demo
Reference document · IT Vision (Pvt.) Ltd. · October 2026

General hospital process flows

Thirteen flows that describe how a patient moves through a hospital, from the first door to the medical records room. Every node is coloured by the department that owns it, so one department can be traced across every flow.

See how EloHIMS runs this journey arrow_outward Now at: {{ playStepName }}
Department colour key
11 families
{{ l.name }} {{ l.hex }}
{{ flow.num }} {{ flow.deptName }}

{{ flow.title }}

{{ flow.intro }}

widgets{{ flow.linkLabel }}
{{ lane.title }}
{{ step.icon }}
{{ step.title }} {{ step.tag }}
{{ step.detail }}
{{ step.title }} {{ step.detail }}
{{ kid.icon }} {{ kid.title }} {{ kid.detail }}
lightbulb Design notes for EloHIMS
{{ note }}
07 Settings, not fixed logic

Configuration matrix - where hospitals differ

Each item below is something real hospitals do differently. A generic HIMS should treat every one as a setting, not fixed logic.

AreaCommon variations (make each one a setting)
{{ r.area }} {{ r.text }}
08 Receiving screen is pre-filled

Cross-department handoffs

When a patient is passed to the next department, the receiving screen must already contain everything the next user needs.

sync_alt
{{ h.area }}
{{ h.text }}
09 Outside the main journey

Other modules

Each of these has its own smaller flow outside the main patient journey.

{{ m.icon }}
{{ m.title }}
{{ m.text }}
{{ flow.num }} {{ flow.deptName }}

{{ flow.title }}

{{ flow.intro }}

widgets{{ flow.linkLabel }}
{{ lane.title }}
{{ step.icon }}
{{ step.title }} {{ step.tag }}
{{ step.detail }}
lightbulb Design notes for EloHIMS
{{ note }}
Section {{ counter }}
Generic hospital process flows · Reference document for EloHIMS · IT Vision (Pvt.) Ltd. Schedule a demo arrow_outward
Schedule a demo