Your Health ID. Your health record. Connected across healthcare.
A patient carries one verified identity and one longitudinal record. Facilities exchange what they are authorised to exchange — through the systems they already run.
OpesCare connects health systems. It does not require every facility to use the same software.
Healthcare is fragmented.
A patient moves between hospitals, clinics, laboratories and pharmacies. Their medical information does not move with them.
Fragmented patient identity
The same person is a different patient at every facility. Nothing links those records back to one human being.
Disconnected health records
Each system holds a fragment. Nobody holds the history, so care gets decided from a partial view.
Delayed access to critical information
Allergies, current medication and recent results arrive after the decision that needed them — or never arrive at all.
Poor visibility and continuity
A patient cannot see who opened their record or why, and the next clinician starts again from nothing.
One identity, one record, exchanged under consent.
Five layers, in order. Each one is only possible because of the one before it.
-
Health ID
A portable, verified identity the patient owns and carries between facilities.
-
Patient Index
The same person resolved to one record across systems — matched deliberately, never merged on a guess.
-
Trust & Access
Who may see what, for what purpose, for how long — decided by the patient and recorded every time.
-
Interoperability
Standards-based exchange with the systems a facility already runs. No replacement, no rip-out.
-
Connected Care
The clinician in front of the patient has the history that patient's care depends on.
How information moves
From an existing hospital system, through OpesCare, to another authorised system — and back again.
-
1
Identify
The patient is resolved to their Health ID — by QR code, identifier or verified lookup.
-
2
Match
That identity is matched against the patient index. An uncertain match goes to human review, never a silent merge.
-
3
Authorize
The requesting facility asks for the scope it needs. The patient approves, denies, or revokes later.
-
4
Exchange
Only the approved scope crosses, in a standard format the receiving system can already read.
-
5
Record
The exchange is written to the patient's timeline and to an audit trail neither side can quietly edit.
What OpesCare gives the ecosystem
Five capabilities. Everything else on this platform is built out of them.
Health Identity
One verified Health ID per patient, portable across every facility on the network.
Patient Index
One person, one record — resolved across systems without probabilistic auto-merging.
Longitudinal Record
Visits, results, prescriptions and referrals in one timeline that outlives any single facility.
Trust & Access
Consent, purpose, scope and duration on every exchange, with an audit trail behind each one.
Interoperability
HL7 FHIR R4 and a Connect surface that meets a facility on whatever system it already runs.
- Interoperable referrals — the next provider receives the right clinical information, scoped. Learn more
- Laboratory orders and verified results, linked to the patient record. Learn more
- Prescriptions and dispensing, connected to the patient's medication history. Learn more
- Insurance coverage as an attribute of the Health ID — read-only, and it travels with the patient. Learn more
Network services
Two things a patient needs to find urgently, answered by the network instead of by phoning around.
Medicine Finder
See which pharmacies on the network hold a medicine, and when they last said so.
How the Medicine Finder worksBlood Finder
Find available blood by group and component across connected hospitals and blood banks.
How the Blood Finder worksAvailability is published by the facility that holds it and timestamped. It is information to act on, not a reservation.
Who connects to OpesCare
Everyone in the patient's journey, each through the surface that fits them.
For patients
Carry one Health ID, decide who sees your record, and find care faster.
For health facilities
Register patients, document care and exchange records without replacing your system.
For organizations
Insurers and health authorities, connected to verified identity and coverage data.
For developers
FHIR R4, a Connect API, SDKs, an embeddable widget, and a sandbox to build against.
Patients stay in control.
Access is a decision, not a default. Before a facility sees anything, the patient is told exactly what is being asked for — and can refuse, or change their mind later.
How consent worksBreak-glass access opens a limited emergency profile — identity, blood group, allergies, active conditions and an emergency contact. It requires a stated reason, alerts the patient, and is reviewed afterwards.
About emergency accessConnect your health system to the OpesCare network.
Give patients one Health ID, and give the clinician in front of them the history their care depends on.
Still have questions? Read the FAQ