Purpose and access logged on every record.
The healthcare pack helps clinical and admin teams with referrals, letters and records. Every time anyone or any AI opens a patient's record, the purpose is checked and logged. Administrators run the system without ever seeing a patient's files.
- Patient
- J. Murphy, 64
- From
- Dr Ruth Keane, GP
- Received
- 17 Oct, 08:40
- Purpose of access
- Direct care · triage
- ECG
- Attached
- Bloods
- Attached
- Medication list
- Attached
- Echo
- Not done
Breathless on exertion for 6 weeks1. New AF on the ECG2. On a blood thinner since 3 Oct3. Local protocol suggests urgent review.
Decision support only. The consultant sets the priority.
Less paper chasing. More time with patients.
Referrals arrive incomplete, letters take hours and nobody can say who looked at what. The pack does the sorting and drafting, and keeps a full account of every access.
Every access has a reason
Each time a person or an AI agent opens a record, the purpose is checked against what they are allowed to do, and the access is logged.
Summaries that cite the notes
Referral summaries and letters link each line to the note, result or letter it came from, so clinicians can check in seconds.
Clinicians make the calls
Suggestions are marked as decision support. Priorities, diagnoses and treatment are set by a named clinician.
One pack. A lens for each role.
Clinicians, booking teams, information governance and administrators each see only what their role needs.
- Consultant
Referrals waiting on a priority, with a sourced summary and what is missing.
- Booking team
Who needs an appointment and when, without the clinical detail.
- GP and referrer
Whether the referral was accepted, what was asked for, and the outcome letter.
- Information governance
Who opened which record, for what purpose, and any access that looks wrong.
- System administrator
Health, settings and users. Never a patient's record.
From referral to a booked appointment.
The same path for every referral, with a purpose recorded at every step.
Receive
Referrals arrive from GPs and other services. The pack files each one and records the purpose of care.
Summarise and check
The letter, results and medicines are read. A sourced summary is drafted and anything missing is flagged.
Clinician decides
A consultant reviews the summary and sets the priority. Suggestions from local protocols are shown as support only.
Book and seal
The booking team books. The referrer and the patient are told. The decision and every access are sealed.
Screens for clinical and admin teams.
Sample screens with a fictional health group. Product screens show the Nexus core the pack runs on.
A summary that cites the notes
Every line of the summary links to the letter, result or medicine list it came from. Missing items are flagged before the consultant sees it.
- Patient
- J. Murphy, 64
- From
- Dr Ruth Keane, GP
- Received
- 17 Oct, 08:40
- Purpose of access
- Direct care · triage
- ECG
- Attached
- Bloods
- Attached
- Medication list
- Attached
- Echo
- Not done
Breathless on exertion for 6 weeks1. New AF on the ECG2. On a blood thinner since 3 Oct3. Local protocol suggests urgent review.
Decision support only. The consultant sets the priority.
Who opened what, and why
Every access to a patient's record is logged with the person or AI agent, their role and the purpose. Unusual access is flagged for information governance.
| When | Who | State |
|---|---|---|
| 17 Oct 08:41 | Referral assistant (AI) | Allowed |
| 17 Oct 09:15 | Dr Sarah Lynch, consultant | Allowed |
| 17 Oct 10:02 | Booking team | Limited view |
| 17 Oct 22:47 | Staff member, finance | Check |
The finance user saw only the name and was refused the record.
Run the system, not the records
Administrators manage users, settings and health. Patient records never appear in their screens or exports.
Counts, storage, where data lives, retention and erasure requests. No names, no notes, no results.
- Region
- In-country
- Patient records
- 182,410
- Erasure requests
- 3 open
- Retention
- Per national schedule
An administrator who needs a record must ask a clinician, and the request is logged.
Purposes you set
Each purpose of use, such as direct care, booking or audit, says who may use it, what they may see and for how long. AI agents get purposes too.
| Purpose | Who | May see |
|---|---|---|
| Direct care | Treating clinicians | Full record |
| Triage summary | Referral assistant (AI) | Referral, results, medicines |
| Booking | Booking team | Name, contact, priority |
| Clinical audit | Audit team | Pseudonymised |
A request outside its purpose is refused and logged.
Each decision, sealed with every access.
When a clinician decides, the decision, the summary they read, its sources and every access along the way are sealed together.
- Which clinician decided, and when
- The summary they read, with each source
- What the AI suggested and whether it was followed
- Every access to the record, with its purpose
- The time stamp, witnessed outside Adverant
Your information governance team, auditors or a regulator can check the seal without an account. Try the seal check →
Triage decision · REF-2026-11902SampleMapped to the rules health services answer to.
Each sealed record is linked to the articles it helps answer, so governance teams have evidence ready.
- GDPRRegulation (EU) 2016/679, Art. 9Health data is a special category, with strict conditions on its use.
- European Health Data SpaceRegulation (EU) 2025/327Patients' access to their records, health record systems and secondary use of health data.
- Medical devicesRegulation (EU) 2017/745 (MDR)Software meant for a medical purpose, including AI, can be a medical device.
- In vitro diagnosticsRegulation (EU) 2017/746 (IVDR)Rules for diagnostic devices and the software that runs them.
- EU AI ActRegulation (EU) 2024/1689, Annex IAI in medical devices is high-risk. Those duties apply from 2 August 2028.
- NIS2Directive (EU) 2022/2555Security and incident reporting for healthcare providers in scope.
AI Act dates as amended by Regulation (EU) 2026/1744, the Digital Omnibus, published in the Official Journal on 24 July 2026. Not legal advice. Certification and legal opinions stay between you and your advisers.
Six modules. One log of every access.
Every module runs on the same Nexus core, with the same purposes and the same access log. Open one to see what goes in, what comes out and who signs off.
Referral intake
Receives referrals from GPs and services, files them and records the purpose of care.
- Goes in
- Referral letters, e-referrals
- Comes out
- A filed referral with its purpose
- Signs off
- Nobody: it only files
Referral summary
Drafts a sourced summary and flags what is missing for the receiving team.
- Goes in
- Letter, results, medicines
- Comes out
- A summary with links and a missing-items list
- Signs off
- Consultant
Clinic letters
Drafts clinic letters from the consultation notes for the clinician to edit and sign.
- Goes in
- Notes, results, plans
- Comes out
- A letter ready to sign
- Signs off
- Treating clinician
Purposes and access
Holds the purposes of use and checks each access against them.
- Goes in
- Roles, purposes, requests
- Comes out
- Allowed or refused access, logged
- Signs off
- Information governance
Patient requests
Handles patients' requests to see, correct or move their records.
- Goes in
- Requests from patients
- Comes out
- A response with what was shared
- Signs off
- Data protection officer
Audit and research copies
Makes pseudonymised copies for audit and approved research, with the approval kept.
- Goes in
- Approved study or audit
- Comes out
- A pseudonymised data set
- Signs off
- Approval committee
Runs where health data must stay.
Run the pack in an in-country cloud or in your own data centres. Remote clinics can work offline.
In-country cloud
In its own private space, in your country or the EU.
Your data centre
On your own Kubernetes, beside your record systems.
An appliance
For a hospital or clinic that needs its own box.
Remote clinics
Mobile and remote clinics keep working offline and sync later.
Questions health services ask.
Does the AI diagnose or set priorities?
No. It summarises, checks for missing items and shows what your local protocol suggests. A named clinician decides, and the record shows who.
Is it a medical device?
That depends on each module's intended purpose under the MDR. Clinical suggestions are marked as decision support and every decision records the clinician who made it. Your clinical safety and regulatory teams decide where each module is used.
Can administrators see patient records?
No. Admin screens show counts, settings and health only. An administrator who needs a record has to ask a clinician, and that request is logged.
Where is patient data kept?
In your country or the EU, in a private space, or in your own data centre. Models can run on your own hardware so nothing leaves.
Does it replace our patient record system?
No. Your record system stays the system of record. The pack reads from it and writes back letters and decisions where you allow.
How are AI agents controlled?
Each AI agent has its own purposes, like a member of staff. It can only read what those purposes allow, and every access is logged.
Other packs
See the healthcare pack on your own referrals.
Bring an anonymised referral pathway and your access rules. We will show you how it runs, in your own region.