Record source workflows
Authorized teams complete work in the relevant clinical or operational module.
Patient timeline and movement trail
Present chronological milestones across encounters, emergency, inpatient, referrals, theatre, mortuary, ambulance, and completed orders.
The operational problem
Teams need a readable chronology of where the patient moved and which operational milestones were completed. CliviQue synthesizes that trail from the underlying workflow records.
What CliviQue currently supports
Combine milestones from the implemented clinical and operational modules.
Include requested, accepted, rejected, completed, and cancelled events.
Show the timeline without allowing users to rewrite source workflow history from the timeline itself.
Keep events understandable in relation to the relevant patient, visit, admission, or case.
How the workflow progresses
Authorized teams complete work in the relevant clinical or operational module.
CliviQue assembles the key events into chronological patient context.
Staff use the trail to understand prior hand-offs and current operational state.
Current scope and limitations
Frequently asked questions
No. The documented trail is read-only and derives from source workflow records.
The current documentation lists encounters, emergency, inpatient, internal referrals, theatre, mortuary, ambulance, and key completed orders.
No. It is a readable patient movement and milestone trail, not an editable or comprehensive audit ledger.
Patient registration and OPD
Move an outpatient visit from registration to a completed encounter
View featureInternal referrals
Preserve patient context across departmental and specialist hand-offs
View featureRole-based access and facility scoping
Limit actions and data to the authorized user, role, organization, and facility
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.