Policy document
Medication governance and live recording
Edition fingerprint
SHA-256: 268e89658a3f1d490aa025508109a4f81d8170587e23bc86171d3a1734fcd5e7
Document editions
- Version 2026-11-11.3 · immutable text
Overview
Live release is additionally gated by `MEDICATION_LIVE_RELEASE_APPROVED` and by completion of the medication evidence pack (M01 Owner, M02 Privacy Adviser, M03 Clinical Reviewer, M04 Release Evidence).
7.1 Purpose
This section sets out how AnuAssure records medication activity for people receiving care. It covers the scope of the module, the roles and permissions, the outcomes the module records, the governance each organisation must put in place before using the module, and the independent evidence required before live release.
7.2 What the module is (Path B scope)
AnuAssure's medication module is a governed medication-recording module. It is not a prescribing system. It does not choose doses. It does not diagnose. It does not check interactions. It does not connect to pharmacy or NHS systems. It records, for each scheduled medication task, what happened at the time of administration or expected administration. The module supports: Organisation setup for care pathways, medication policies, source instructions, and scheduled tasks. Staff permission types: self-administration, prompting, assistance, administration, and witnessing. Recording outcomes: given, refused, omitted, already taken, self-reported, support provided, not available. "Given" authorisation: the "given" outcome is allowed only when the source instruction authorises administration. Non-given reasons: any outcome other than "given" requires a reason. Actual event times, optional witness records, explicit stock entries, corrections, and private packaging or receipt evidence. A correction preserves the original record. Overdue marker: an in-app marker shown when a scheduled task has no recorded event. The marker means "missing record". It is not evidence that the person missed or took a dose, and it is not a refusal counter. The repeated-refusal escalation workflow (three refusals, management alert, drafted email to the social worker) is under development. It is not implemented at this policy edition. When implemented, a separate policy edition will cover it.
7.3 Roles
Prescriber: sets the prescription. Not inside AnuAssure. Care organisation Registered Manager: approves the organisation's medication policy, authorises source instructions, assigns staff permissions, and reviews reports. Care staff: record outcomes against their permission level. Witnessing staff: co-sign outcomes that require witnessing under the organisation's policy or the source instruction. ANUASSURE LTD: operates the module as processor.
7.4 Permissions
Staff permissions are per-worker and per-organisation. The module enforces them at the point of recording. Permission | May record Self-administration | Self-reported outcomes only Prompting | Self-reported outcomes; "support provided" Assistance | Non-administering support outcomes Administration | "Given" (where authorised), plus all support outcomes Witnessing | Co-signs on another worker's record
7.5 Organisation prerequisites before use
Before the organisation can use the module (on any plan), the organisation must: Hold an approved organisation medication policy aligned with NICE NG67 and its own CQC-registered scope. Provide source instructions for every medication recorded, authorised by the appropriate role. Set current staff competency grants for each worker, with named reviewer and date. Name a medication lead who is an active manager or superadmin account in AnuAssure. The "named lead" field is an operational handle only; it does not of itself verify clinical qualification. Record incident procedures for errors, refusals, and omissions.
7.6 Independent evidence required before live release
The live release of this module (controlled by `MEDICATION_LIVE_RELEASE_APPROVED`) is contingent on all four evidence artefacts: M01 Owner findings. The entities, their controller or processor roles, the processing purposes, the organisation's actual medication and escalation procedures, and the responsibilities for each. M02 Privacy adviser findings. The data flows and suppliers, the agreements and transfers, the lawful bases, the notices, access, retention, legal holds, backup deletion, and rights handling. If and when the refusal email workflow is added, the review extends to recipients, message content, and delivery. M03 Clinical reviewer findings. Approval of this exact policy edition by a different, qualified clinical reviewer. The code's "named lead" field does not substitute for this review. M04 Release evidence pack. Medication safety and human factors assessment, Android and iPhone build testing, verified private storage and database recovery, monitoring, and incident procedures. Each is a separate artefact with its own reviewer. All four reach Approved before the release flag is set.
7.7 Audit
For each recorded outcome: Task identifier, schedule, person, medication, instruction reference. Outcome, event time, worker identifier, witnessing worker identifier (where applicable). Reason text where the outcome is not "given". Any correction, with the original preserved.
7.8 Retention
Medication records follow Section 2 (service user care records: 8 years from last contact; age 25 or 8 years, whichever is longer, where the person is a minor).
7.9 What this edition does not cover
The repeated-refusal escalation workflow. Any email or SMS communication to third parties about medication. Any clinical decision support. Automatic pharmacy, NHS, or local authority integration. These require separate specification, privacy review, and policy edition work.
Service scope
Publication does not authorise live medication recording. Organisation-specific clinical authority, staff competence and live-release safeguards still apply.