ITKIT
Health · 06 / 20
OneHealth
National digital health and record exchange
From the problem to how we solve it
October 2026
Interactive prototype · synthetic data only
The problem
Your history should not live in a folder.
1
Results and histories stay inside each facility.
2
Patients carry paper files between doctors.
3
Facilities use different systems and codes.
Hospitals · Labs · Pharmacies · Paper folders · One record
ITKIT · OneHealth · Prototype screens, synthetic data
The problem
Our answer
One record · Consent and purpose · Never sold
A patient’s longitudinal record across hospitals, clinics, labs, radiology and pharmacies, with a citizen app and clinical access governed by consent, purpose and audit.
How it works · 1 of 6
One timeline
One record. Six facilities.
With OneHealth, results, prescriptions and vaccinations from every connected facility arrive in one timeline.
ITKIT · OneHealth · Prototype screens, synthetic data
How it works
How it works · 2 of 6
Lab results
Clear results. Source always shown.
Each result shows where it came from, and corrections never erase what was there before.
ITKIT · OneHealth · Prototype screens, synthetic data
How it works
How it works · 3 of 6
Clinician view
Access by consent and purpose.
Clinicians see what they need for care, only while they are treating the patient.
ITKIT · OneHealth · Prototype screens, synthetic data
How it works
How it works · 4 of 6
Emergency access
Emergency access: reasoned, time-limited, reviewed.
In an emergency, care comes first, and every emergency access is reviewed afterwards.
ITKIT · OneHealth · Prototype screens, synthetic data
How it works
How it works · 5 of 6
Transparency
You see every access.
Patients see who opened their record, why, and can raise a concern in one tap.
ITKIT · OneHealth · Prototype screens, synthetic data
How it works
How it works · 6 of 6
Interoperability
Hospitals keep their systems. The record travels.
Built on FHIR, HL7 v2 and DICOMweb, OneHealth connects the systems facilities already run.
ITKIT · OneHealth · Prototype screens, synthetic data
How it works
What it includes
21 screens and workflows in the prototype
Medical timeline
Patients and parents
Lab result detail
Patients and parents
Who accessed my record
Patients
Sharing and consent
Patients
Clinician patient summary
Clinicians and care teams
Break-glass emergency access
Emergency clinicians
HIE operations dashboard
Exchange operations team
Master patient index
Data-quality and MPI reviewers
ITKIT · OneHealth · Prototype screens, synthetic data
What it includes
Built to standards
International standards it is built to
| Standard | What it covers in OneHealth |
|---|---|
| HL7 FHIR R4 (4.0.1); R5 (5.0.0) is the current release | Canonical exchange model and national implementation guide |
| HL7 FHIR R4 Provenance resource | Source facility, author and time for every record |
| HL7 FHIR R4 Consent and IHE Privacy Consent on FHIR (PCF) 1.1.0 | Patient privacy consent, enforced separately from sign-in |
| IHE Basic Audit Log Patterns (BALP) 1.1.4 · FHIR AuditEvent | Privacy-centric audit of every disclosure |
| IHE PIXm 3.1.0 (patient identifier cross-reference) | Master patient index and matching |
| HL7 Version 2 messaging (2.9.1 latest; 2.5 in use at facilities) | Adapters for existing hospital and lab systems |
| DICOM PS3.18 Web Services (DICOMweb: QIDO-RS, WADO-RS, STOW-RS) | Imaging links without copying images centrally |
| ISO 27799:2016 with ISO/IEC 27001:2022 | Review of emergency and privileged access in health |
We align with these standards; certification is issued by accredited bodies, not by ITKIT.
ITKIT · OneHealth · Prototype screens, synthetic data
What it includes
Connects to
What OneHealth works with
Existing national health record initiative (assess first)
Hospital HIS/EHR
Lab and radiology systems
Pharmacies
OneID
ITKIT · OneHealth · Prototype screens, synthetic data
What it includes
Safeguards
What OneHealth will never do
No unrestricted government access to records, no autonomous diagnosis, no sale of patient data.
HIS/EHR replacement is a separately priced option.
ITKIT · OneHealth · Prototype screens, synthetic data
Delivery
How delivery works
Start small, prove it, then scale and hand over
6–10 weeks
Assess
Map what already exists and decide, system by system: reuse, integrate, modernise or build.
4–6 months
Pilot
OneHealth at one authority, with real users and a measured outcome, on national infrastructure.
12–24 months
Scale
Roll out by region and service, sharing identity, integration and audit.
Agreed per contract
Operate and transfer
We run it with your team, train them, then hand over operations, code escrow and keys.
Durations are typical ranges, fixed per contract
ITKIT · OneHealth · Prototype screens, synthetic data
Delivery
Next step
Book a walkthrough of the OneHealth prototype with your team.
OneHealth. One record, many facilities, and the patient in control.
1 · Demo
A guided session on the OneHealth prototype
2 · Assess
6–10 weeks to map what exists and fix the pilot scope
3 · Pilot
4–6 months with real users and a measured result
ITKIT · [contact name, email and phone]
Thank you