Hospital management information system

Keep hospital work connected from first contact to completion.

CliviQue connects patient registration, clinical encounters, emergency, inpatient care, orders, referrals, theatre, billing, transport, mortuary, duty coverage, and facility operations.

Built for authorized hospital teams. Public pages do not expose patient, facility, or clinical workspace data.

Existing staff login

Facility operations

Current workflow visibility

Facility scoped

Operational signal

Active encounters

Operational signal

Beds and admissions

Operational signal

Orders and referrals

Operational signal

Billing and clearance

One connected patient context

Registration → encounter → orders and hand-offs → billing or discharge → movement trail and documents.

Operational continuity

Design around real hospital hand-offs—not disconnected menus

Each public feature page maps to an implemented MVP workflow and states its current limitations, helping hospitals evaluate the product without treating future modules as finished capability.

Clinical and facility workflows

Orders, referrals, and completion

Billing and operational clearance

Role and facility-scoped access

Core CliviQue features

Follow work across care, departments, finance, and operations

Start with the major workflows below, then review the complete feature catalogue and each page’s explicit implementation scope.

Patient registration and OPD

Move an outpatient visit from registration to a completed encounter

Register patients, create encounters, capture triage and consultation details, add diagnoses, place service orders, bill, receive payment, and close the visit.

View implementation scope

Emergency and casualty

Coordinate emergency visits, observations, procedures, and disposition

Create emergency visits, assign bays, record observations and procedures, and hand patients off to discharge, admission, theatre, transfer, referral, or mortuary workflows.

View implementation scope

Inpatient and bed management

Manage admission, ward and bed assignment, rounds, transfers, and discharge

Admit patients from encounters, assign wards and beds, record rounds and observations, administer medication, transfer beds or wards, generate bed charges, and discharge after clearance.

View implementation scope

Clinical orders and fulfilment

Keep lab, imaging, pharmacy, and procedure orders tied to the encounter

Place and fulfil clinical service orders without losing the patient, encounter, department, billing, or completion context.

View implementation scope

Internal referrals

Preserve patient context across departmental and specialist hand-offs

Request, accept, reject with a note, complete, or cancel referrals between OPD, emergency, inpatient teams, departments, and specialists.

View implementation scope

Theatre workflows

Progress a theatre request from booking through operation and recovery notes

Create theatre requests from procedure orders or emergency hand-offs, book rooms and staff, progress case status, capture notes, and complete the linked procedure order.

View implementation scope

A connected operating flow

Preserve context as responsibility moves between teams

01

Identify the patient and visit

Register or find the patient, then open the correct encounter, emergency visit, or admission context.

02

Coordinate care and hand-offs

Progress triage, consultation, orders, referrals, theatre, inpatient work, transport, and related departmental queues.

03

Resolve completion requirements

Connect service activity to billing, payments, clearance, documents, discharge, transfer, or final workflow completion.

Security boundary

Public content stays outside the clinical workspace

Public pages do not load the workspace shell or private clinical QueryClient. Production authentication is restricted to the configured HMIS host, with actual web credentials held in HttpOnly cookies behind a same-origin gateway.

Review security architecture

Configured subscription

Pricing follows the organization’s actual deployment

CliviQue currently configures subscriptions from package access, covered facilities, licensed staff capacity, add-ons, currency, and billing interval. Fixed public prices are not published.

Understand CliviQue pricing

Frequently asked questions

Evaluating CliviQue

What is CliviQue?+

CliviQue is a hospital management information system for connected clinical, operational, facility, billing, and care-team workflows.

Is CliviQue a public patient portal?+

No. The current product is an authorized staff HMIS. Public website pages explain the product but do not expose hospital or patient records.

How is CliviQue priced?+

Current subscriptions are configured for each organization based on its package, covered facilities, licensed staff capacity, add-ons, currency, and billing interval. Public fixed prices are not currently published.

Does CliviQue replace clinical judgment?+

No. CliviQue supports recordkeeping and workflow coordination. Authorized healthcare professionals and hospitals remain responsible for clinical decisions and governance.

Does the public website share a clinical session?+

No. Production authentication is restricted to the central HMIS application host, while public pages remain outside the private clinical cache and workspace shell.

Guided implementation

See how CliviQue fits your hospital workflows

Start with a guided product conversation covering facilities, staff capacity, modules, implementation scope, security, and subscription configuration.