'/%3e%3cpath%20d='M92%2044a34%2034%200%201%200%204%2033H66'%20fill='none'%20stroke='%23fff'%20stroke-width='12'%20stroke-linecap='round'%20stroke-linejoin='round'/%3e%3ccircle%20cx='96'%20cy='32'%20r='9'%20fill='%23FF6A2B'/%3e%3c/svg%3e)
Platform module
Consent, Health Access Codes & the GSHS Network
How one hospital sees another hospital's record — only with the patient's explicit, scoped, time-limited permission.
What it is
The whole platform rests on one rule: validate before you reveal. Asking whether a Global Patient ID exists returns only whether it exists and whether it is active — never a name, never a date of birth, never a phone number.
Everything beyond that requires the patient's permission, expressed as a code they issue or a request they approve, with a scope and an expiry they chose.
Health Access Code
Patient-controlled network access
Access approved
Valid for Riverside Medical Centre
Health Access Code
7K3M-P9XQ
Expires in 42 minutes
This code shares
Every use is recorded in your access history.
Why teams value it
Patient-issued codes
Scope and duration chosen by the patient.
Provider requests
Staff can ask; only the patient can grant.
Scoped views
Only the categories consented to are shown.
Emergency path
Break-glass access, restricted and reviewed.
A code that says exactly what it opens
The patient chooses the data categories, an optional named hospital and a duration of fifteen minutes, one hour or a day. The code is shown once and stored only as a hash — it can be revoked but never re-displayed.
- Hashed at rest, shown once
- Optional single-organisation lock
- Revocable while unused
Ask properly, in writing
A clinician who needs history submits a request with a reason, the scope and a duration. The patient approves or declines from their portal, and approval makes the record immediately readable by that organisation alone.
- Reason recorded with the request
- Patient decision stored with any reason given
- Access expires automatically
See only what was granted, and know it
Authorised access opens a Patient 360 restricted to the consented categories, under a persistent banner naming the scope and the expiry time, so the clinician always knows the basis on which they are looking.
- Persistent authorisation banner
- Only consented categories load
- Every disclosure written to the audit trail
For the unconscious patient
Where consent is impossible, a clinician can re-enter their password, pick a reason code and write a justification to obtain a restricted emergency set — active allergies, current medicines, current conditions, nothing else. Every invocation goes to a review queue with an ageing clock.
- Step-up authentication required
- Restricted dataset only
- Reviewed by a Security & Privacy Officer against an SLA
Questions about this module
Explore related modules
Patient Records & Global Patient ID
One record per patient per hospital, and one identity for that patient across every hospital on the network.
Read moreClinical Encounters, Admissions & Discharge
Consultations, ward rounds, admissions and discharge in a record that keeps its history instead of being overwritten.
Read moreAppointments, Scheduling & Referrals
A real clinician calendar, double-booking prevented at the database, and referrals tracked to a decision.
Read moreLaboratory & Imaging
Orders, specimens, results and a separate verification step, with turnaround measured rather than estimated.
Read moreSee this module on real screens
Book a walkthrough and we will demonstrate it using workflows that match your facility.