OpesCare: Every Module and the Problem It Solves

OpesCare is easiest to understand from the problems it was built to solve. A patient is a different person at every facility. A clinician decides from half a history. A family phones five hospitals looking for blood. A pharmacy has the medicine but nobody knows.

This guide lists every OpesCare module that is live today, who it is for, and the problem each one solves. Where something is limited, being rolled out, or deliberately left out, we say so.

What OpesCare is — and is not

OpesCare is a discovery, identity and coordination network for Cameroon, in English and French. Patients find care and carry one identity; facilities stay findable and serve Health ID holders at the counter.

It is not a hospital information system or a complete electronic medical record. Full clinical documentation, admissions and discharges, procurement, HR and insurance claims are out of scope on purpose. OpesCare connects to the software a facility already runs rather than replacing it. It is a private network operated by OPES Health Systems, not a government service.

For patients

Health ID and QR card

Problem: a new card and a new file number at every facility. Module: one free Health ID, issued when you sign up, with a QR card, a Presentation Mode for showing at a counter, and a public verification page so staff can check the card is genuine. Staff find you by exact ID or QR — never by name search.

Consent and access log

Problem: patients cannot see who opened their record or why. Module: consent requests tell you who is asking, why, for which data and for how long; you approve, deny or revoke. Every access is written to a log you can read. Emergency break-glass access opens only a limited profile, requires a reason and alerts you. Two privacy switches let you tighten what is shown. See who can see your record.

Longitudinal record

Problem: history scattered across facilities. Module: visits, results, prescriptions, vitals, immunisations and referrals in one timeline that outlives any single facility. You can also import past records and export your record in FHIR.

Appointments and the queue

Problem: long, uncertain waits. Module: book a slot with a provider at a facility, reschedule from the app, and follow your place in the facility's queue. Triage can reorder the queue by urgency; it does not make waits shorter by itself, and care is never conditioned on your place in the queue.

Documents with a verification QR

Problem: paper results and certificates are easy to forge and hard to check. Module: official PDFs — record exports, prescriptions and other documents — carry a QR code that leads to a verification page at opescare.com, sealed with a fingerprint of the document. Patient PDFs are generated when you download them, not stored.

Health Passport

Problem: no single summary to carry when travelling or changing doctor. Module: a multi-page Health Passport built from your real records. Pages with no data stay empty; nothing is invented to fill them.

Family and guardians

Problem: parents and carers manage health for people who cannot manage it themselves. Module: guardian accounts and family links let a parent or carer act on behalf of a child or dependent, with a guardian dashboard and inbox. Guardians can register at a dedicated sign-up page.

Finders

Problem: phoning around to find a medicine, blood, a test or a facility. Module: the Medicine Finder, Blood Finder, lab-test finder, imaging-exam finder and the Care Map facility directory, with in-app maps and directions. Results come only from what facilities publish; an empty result is shown as empty.

Payments and plans

Problem: paying a bill means queuing at a cashier. Module: pay a facility invoice with MTN Mobile Money or Orange Money where the facility has enabled it. Payments switch on once the mobile-money merchant accounts are connected; until then OpesCare shows them as unavailable rather than pretending. Optional patient plans can be paid daily, monthly or yearly in whole francs. Nothing in care is ever blocked on payment — this is enforced by automated tests.

Mobile app, offline and languages

The mobile app covers the patient journey, shows when you are offline, and syncs certain queued entries when the connection returns. The whole product is available in English and French.

For hospitals, clinics and health centres

Clinician portal

Problem: clinicians cannot see the history they need, safely. Module: a clinician portal on the web and in the app — facility switching, patient rosters, schedule, results, referrals, messaging — with every chart read checked against a care relationship or consent grant. Clinicians can scan a patient's QR from the app.

Prescriptions

Problem: handwritten prescriptions are lost, misread or forged. Module: a prescriber desk issues prescriptions against the Health ID, with drug-interaction warnings. Each prescription carries its own verification link, and pharmacies dispense against it.

Referrals

Problem: a referred patient arrives with no information. Module: a referral desk for sending and receiving referrals, scoped to what the next provider needs.

Queue, triage, immunisation and vitals

Front-desk queue management, triage ordering, an immunisation desk and vitals entry with consistent adult reference bands.

Facility administration

Staff invitations and roles, departments, a ward and bed register for occupancy counts, invoices, reports with CSV export of aggregates, broadcasts, tasks and a go-live readiness checklist. Facilities can also prepare aggregate counts for national DHIS2 reporting, reviewed by an administrator before sending — never patient-level data.

For pharmacies

Dispensing by Health ID

Problem: no link between a prescription and what was actually dispensed. Module: the counter looks up the patient by Health ID, sees the prescription, and records full or partial dispensing. Stock is decremented when the patient collects.

Stock, prices and orders

Problem: patients cannot know a pharmacy has a medicine. Module: stock screens feed the Medicine Finder, showing when each line was last confirmed. A price list in whole XAF keeps its history. A patient orders desk receives reservations.

Stock import (rolling out)

A stock import tool reads CSV, Excel (.xlsx) and OpenDocument (.ods) files, lets the pharmacy map its own columns, shows a preview, and only then commits the lines as ordinary stock movements. Find it in your pharmacy stock menu under "Import stock".

For laboratories

Problem: results are delayed, lost, or reach the patient before the doctor can explain them. Module: a lab desk for patient requests, sample tracking and rejection, result validation and release to patient and prescriber, a printable report, critical-value read-back, and turnaround figures. The lab's published test menu feeds the public lab-test finder.

For imaging centres

An imaging desk for requests and release of results, with radiology results linked to the patient record, and a published exam list that feeds the imaging-exam finder. Radiology reporting software and PACS stay in the centre's own systems.

For blood banks

Problem: nobody knows where compatible blood is. Module: a blood desk to keep inventory by group and component current, and to receive and respond to blood requests. Published inventory appears on the Blood Finder. See how blood availability search works.

For developers and partners

Problem: every integration is a custom project. Module:

• FHIR R4 inbound ingest for DiagnosticReport, Observation, Immunization and transaction bundles, with scoped bearer tokens;
• a REST API and documentation at opescare.com/docs;
• signed, replayable webhooks (internal network addresses are refused);
• a developer dashboard with activity log, quickstart and analytics;
• an embeddable widget and a sandbox.

Developers can register at the developer sign-up page. Outbound FHIR server and HL7 v2 are not available.

Behind the scenes: identity and safety

Master Patient Index

Duplicate records are detected at registration and in scheduled scans, then reviewed by a person. Nothing merges automatically, and merges are reversible. See why duplicate records are dangerous.

Security and privacy

• Facility identity always comes from the signed-in session, never from what a request claims.
• Cross-facility access is refused.
• Clinical entries are never deleted; they are amended or voided with a trail.
• Platform administrators must use multi-factor authentication.
• A strict content security policy and hardened webhooks protect the web application.

Read our privacy notice and data protection guide.

What is deliberately absent

To avoid any confusion: OpesCare does not do insurance claims or pre-authorisation, procurement or supplier management, HR and payroll, admissions/discharge workflows, laboratory instrument interfaces, or full clinical notes. Telemedicine is limited to booking a consultation; there is no in-app video.

Conclusion

Each OpesCare module answers a concrete question: who is this patient, who may see their record, where is the medicine, where is the blood, and how does information get from one facility to the next. Together they form Cameroon's first Health ID: a first-of-its-kind, patient-owned Health ID network.

Patients: get your free Health ID. Facilities: apply to join. Developers: read the docs. Questions? Visit opescare.com/help.