How CCMS Is Organized
CCMS runs on SystmOne. It is a set of specialized modules that handle different stages of a patient's journey, from registration to reporting. This page explains what each module does and how the platform connects to external systems.
The Building Blocks
CCMS is built from six clinical modules that cover the full patient journey, plus three external integrations that connect to systems outside SystmOne.
Core Clinical Modules
These six modules cover the full patient journey. Data flows between them automatically — when you document a diagnosis in Clinical Documentation, it becomes available in Reporting. When you order a test in Investigations, the result returns to the same patient record.
1. Patient Management
Every patient interaction starts here. Registration staff, healthcare assistant (PPK), nurses and medical assistant may use this module to check patients in, verify identity, update demographics and maintain accurate contact details.
2. Clinical Documentation / Tab Journal
This is where the clinical encounter is recorded — using structured MOH templates or free-text journal entries. Doctors, nurses & MAs document assessments, diagnoses, and care plans here. The module enforces SNOMED CT coding, which makes the data searchable, reportable & compatible with the national health database.
3. Prescribing & Pharmacy
Doctors prescribe electronically within this module; orders flow directly to the PhIS (Pharmacy Information System) for dispensing. Safety checks — drug interactions, allergy cross-checks & duplicate therapy alerts — run automatically at the point of prescribing.
4. Appointments & Scheduling
Manages clinic rotas, queue coordination, and patient booking. The module syncs with MyVAS & MySejahtera, pushing appointments from CCMS so bookings are reflected in both platforms in real time without manual entry.
5. Investigations & Results
Handles lab orders, imaging requests, and result retrieval. Orders transmit to external lab systems electronically; results return directly into the patient's record. This creates a complete investigation history without manual transcription.
6. Reporting & Analytics
Transforms structured clinical data into workload statistics, disease surveillance & quality dashboards. Administrators and unit coordinators use this for clinic planning, KPI tracking & regulatory reporting.
External Integrations
CCMS connects to external systems to reduce duplicate data entry and create a continuous care record.
| Integration | What it does | Status |
|---|---|---|
| PhIS | Prescriptions flow electronically from CCMS to pharmacy for dispensing | Live |
| Laboratory | Lab results transmit automatically into patient records; vendor-specific | In Progress |
| MyVAS & MySejahtera | Patients book appointments through MySejahtera; syncs to SystmOne | Live |
Cloud Architecture
SystmOne operates on centralized cloud infrastructure. This means patient records are not stored on a single clinic computer.
| Feature | Benefit |
|---|---|
| Location independence | Access records from any workstation in the clinic or MOH network |
| National patient database | Patients registered at any CCMS facility are in one unified database |
| Automatic updates | TPP deploys updates centrally — no local installation needed |
| Disaster recovery | Automated backups protect against hardware failure |
| Scalability | New users and features are added without clinic-level upgrades |
- 6 core modules cover the patient journey from registration to reporting
- Data flows automatically between modules — documentation feeds reporting, orders feed results
- 3 external integrations (PhIS, iLAB, MyVAS) create a connected health ecosystem
- Cloud-based means national access, auto-updates, and no local server dependency
Contributor
Dr Fuad Jaafar
Facilitator, CCMS • KK Bandar Maharani