VitaCore

The problem

A patient visit moves through reception, consultation, diagnostics, pharmacy and billing. When departments keep separate records, staff can lose sight of what has happened and what needs to happen next. VitaCore is being built to connect those handovers and preserve a traceable history of the visit.

The approach

The system organises care around a shared patient visit, with dedicated workflows for each department. Facility boundaries, server-enforced permissions and a protected audit history are central to the architecture. Clinical amendments create new versions, preserving the original record and the reason for each change.

The build

• —The visit workflow connects registration and triage with consultation, laboratory testing, prescriptions, dispensing and billing.
• —Multiple facilities share a deployment while maintaining separate services, prices, inventory and staff.
• —A tamper-evident audit history records each action, its author and time, the patient involved, and the values before and after a change.
• —Clinical amendments retain the original record alongside a new version documenting who changed it, when and why.
• —Administrators configure roles and permissions, with access enforced on the server.
• —Department worklists cover patient queues, laboratory results, pharmacy stock and billing, including cash-till operations.
• —Facilities, hospital-number formats and payment methods can be configured without a new deployment. Background tasks use a database-backed queue without a separate message broker.

The outcome

VitaCore is published as an open-source project with workflows for outpatient and inpatient care, radiology, pharmacy, insurance, billing, inventory, theatre, maternity, reporting and a patient portal. The demo uses synthetic data. Clinical content still requires clinician sign-off, and installation and restore drills must be completed on the hospital's own hardware before real deployment.

Open source

VitaCore's backend and frontend are available on GitHub to explore, run and adapt under the GNU AGPL v3 licence. A commercial licence is also available. The repository includes local setup instructions, synthetic demo data and deployment documentation. Issues and pull requests are welcome; the contribution guide covers development checks, commit sign-off and the contributor licence agreement.