Workflow reference
Use this section to answer the operational form of the exam question: which legislation, regulations, standards, confidentiality rules, guidance and other controls govern this information-sharing workflow?
Start with the Executive summary, choose whether information is moving Out of primary healthcare or Into primary healthcare, and select the workflow from that directional matrix. The matrix compares candidate instruments across workflows; the linked detail page applies those candidates to the operational boundary, message legs, failure states and open checks.
These pages do not create authority or replace the maintained Law, Standards register, Evidence matrix or primary sources.
Clinical and operational workflows
| Workflow family | Out of PHC | Into PHC | What the detail page separates |
|---|---|---|---|
| Shared records, summary records and care plans | Record views and contributions made available to another care team | External records or care plans viewed or received by PHC | On-demand view, contributed content, care relationship and role-filtered access |
| Diagnostic ordering, results and imaging | Requests, orders, context and status queries | Reports, results and approved imaging discovery or retrieval | Order, acknowledgement, result and imaging legs; DAPB4101 and NIR boundaries |
| Referrals, triage and bookings | Referral or booking request | Acknowledgement, triage, booking, rejection, return and outcome | Referral content, BaRS use case and closed-loop ownership |
| Transfers of care and clinical correspondence | Care summary, handover, care plan or clinical correspondence | Acute discharge, handover or correspondence entering PHC | Broad transfer workflow versus the scoped DAPB4042 discharge leg |
| Medicines, prescribing and pharmacy | Prescription, medication and allergy information sent by PHC | Pharmacy event, vaccination or medicine information received by PHC | Authoritative medicine state, dm+d and the scoped DAPB4008 return leg |
| Patient and carer access, requests, communications and contributions | Record access, proxy access, transactions and messages | Requests, measurements, questionnaires and other patient-generated information | Access, delegated authority, communications, transactions and clinical responsibility |
| Patient registration, demographics and GP-record transfer | Registration or transfer information leaving the current practice | Registration, demographic or longitudinal record information entering a practice | Identity, demographic update and record-transfer hand-offs |
Purpose-specific and residual workflows
| Workflow family | Direction | Use this page when |
|---|---|---|
| Planning, commissioning, population health, research and audit | Out of PHC | The purpose is beyond the individual’s care and must be separated from a direct-care pathway |
| Safeguarding, public-health notifications and other required disclosures | Out of PHC | A specific legal duty, power, direction, request, court order or professional/public-interest gateway may apply |
| Community, mental-health, ambulance, social-care and other-provider updates | Into PHC | An event-driven document or message does not fit diagnostics, referral, transfer, pharmacy or shared-record viewing |
How to use a workflow page
Follow the route in order:
- Direction: select the outward- or incoming-PHC matrix.
- Workflow: open one row and preserve the named service, direction and message leg.
- Applicability: read the scope boundary and test every candidate legal, regulatory, confidentiality, standards, safety and contractual layer against the linked evidence.
- Decision guide: carry the direction, workflow, sender, recipient, message leg and purpose into Decide a data flow.
- Decision record: follow the guide to the auditable record only after every applicable layer has passed.