Open the emergency visit
Create the visit and place the patient in the appropriate casualty context or bay.
Emergency and casualty
Create emergency visits, assign bays, record observations and procedures, and hand patients off to discharge, admission, theatre, transfer, referral, or mortuary workflows.
The operational problem
When a casualty visit moves between bays, clinicians, procedures, and downstream departments, the receiving team needs the same operational context. CliviQue preserves the visit and disposition trail across those hand-offs.
What CliviQue currently supports
Track the active visit, bay assignment, observations, procedures, and current disposition.
Continue into inpatient admission, theatre, internal referral, ambulance transfer, discharge, or mortuary workflows.
Present emergency actions to authorized staff while the backend enforces permissions and facility scope.
Preserve emergency milestones in the patient movement trail and timeline.
How the workflow progresses
Create the visit and place the patient in the appropriate casualty context or bay.
Capture observations, procedures, and the operational status of the visit.
Hand the patient to the appropriate next workflow while retaining the emergency context.
Current scope and limitations
Frequently asked questions
Yes. Admission is one of the implemented emergency dispositions.
Yes. The implemented workflow supports a theatre hand-off where clinically and operationally required.
A transfer or referral disposition can create an ambulance transport request, but GPS and route optimization are not included in the current MVP.
Inpatient and bed management
Manage admission, ward and bed assignment, rounds, transfers, and discharge
View featureTheatre workflows
Progress a theatre request from booking through operation and recovery notes
View featureAmbulance and transfers
Track transport requests, vehicle assignment, and trip progression
View featureGuided implementation
A product walkthrough can cover the implemented workflow, roles, facility setup, subscription entitlements, deployment boundaries, and any requirements that remain outside the current MVP.