Register or find the patient
Create the patient record or reopen an existing one before starting the visit.
Patient registration and OPD
Register patients, create encounters, capture triage and consultation details, add diagnoses, place service orders, bill, receive payment, and close the visit.
The operational problem
Registration, triage, consultation, orders, billing, and fulfilment need a shared patient and encounter context. CliviQue keeps the operational hand-offs attached to the same visit instead of rebuilding the story from paper and verbal updates.
What CliviQue currently supports
Keep demographic details, the active encounter, clinical notes, diagnoses, orders, and billing references connected.
Support role-specific work for triage staff and clinicians without exposing every action to every user.
Create lab, imaging, pharmacy, and procedure orders from the encounter workflow.
Track the visit through charges and payment before the encounter is completed.
How the workflow progresses
Create the patient record or reopen an existing one before starting the visit.
Capture triage, consultation, diagnoses, and the required clinical service orders.
Fulfil orders, resolve billing, and close the encounter with its history intact.
Current scope and limitations
Frequently asked questions
Yes. The workflow is designed to find an existing patient or create a new record before opening an encounter.
Yes. The implemented flow includes lab, imaging, pharmacy, and procedure orders together with billing and payment hand-offs.
No. CliviQue organizes authorized workflows and records; clinicians remain responsible for care decisions.
Clinical orders and fulfilment
Keep lab, imaging, pharmacy, and procedure orders tied to the encounter
View featureHospital billing and payments
Keep charges, invoices, payments, and clearance connected to care workflows
View featurePatient timeline and movement trail
Read the operational story across care settings and hand-offs
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.