Registration and transfer: safety review and evidence

Registration completed, record integrated and clinical follow-up handed over are separate outcomes. Review the evidence for each.

Read process and requirements first. The questions below are original review prompts. They are not extra DSIC requirements or findings about an assessed product.

Read unavailable automation for capability gaps, deployment dependencies and exceptions. Read record-transfer fallback for recovery, reconciliation and the continuing duties.

Separate the two safety responsibilities

DSIC's Clinical Safety standard requires supplier DCB0129 work and safety documentation that enables the deploying organisation's DCB0160 assessment. ⁰⁰⁴

Review	Evidence to examine for this activity
Manufacturer — DCB0129	Product hazards, identity controls, transfer states, completeness and interpretation controls, failure tasks, audit evidence, tests and safe-use instructions.
Deployment — DCB0160	Local workflow, named queue owners, clinical review, escalation, absence cover, continuity arrangements, training and acceptance of residual risks.
Shared boundary	Which actions the supplier expects the practice to perform, how the practice implements them, and how both parties verify the handover.

This allocation is a proposed evidence map for the activity. Use the actual intended use and local deployment when deciding applicability. See safety responsibilities.

Questions across the patient journey

Possible failure or harm	Process question	Evidence to request
A record is attached to the wrong person	Who resolves identity uncertainty before registration and transfer proceed?	Identity workflow, mismatch handling, representative tests and audit trail.
Registration is treated as proof that records arrived	Can staff distinguish administrative completion, receipt, integration and unresolved exceptions?	Status definitions, queue views, timestamps and completed examples.
Important history or an attachment is absent	How are incomplete transfers identified, chased and reconciled?	Exception list, completeness checks and recovery records.
Medication or allergy meaning changes during transfer	Who reviews medication and resolves degrades before relying on affected information?	Clinical review procedure, supplier instructions and evidence of resolved tasks.
Failure tasks disappear without recovery	What prevents a transfer being closed while required recovery remains incomplete?	Task lifecycle, permissions, escalation and closure evidence.
Care is delayed while records are unavailable	What information and clinical support can the practice use safely during the gap?	Locally approved contingency procedure and an exercised example.
A pending result or referral loses its owner	Who acts, who chases and how is responsibility accepted?	Handover record, urgency, receiving team and escalation route.
Information arrives at the former practice after the move	How is the new information reviewed and communicated to the appropriate team?	Late-information workflow, acknowledgement and action record.
A retry omits newer information or reaches an outdated destination	How are intervening changes and a second registration move handled?	Retry tests, destination checks and reconciliation evidence.
Paper records or unresolved duplicates remain	Who reconciles each outstanding component and records the outcome?	Records inventory, exception decisions and completion review.

The linked process page identifies the formal clauses and guidance behind these topics. The questions extend those sources into possible hazards; they do not establish that any failure occurred.

Evidence that distinguishes the outcomes

For a sampled transfer, request a trace from registration through record availability to resolution of relevant exceptions. Record the patient identifier securely in the assessment environment. Then identify the sending and receiving organisations, relevant dates, outcome, outstanding tasks and responsible people.

A transport acknowledgement alone does not demonstrate clinical review. A closed clinical task alone does not prove that missing attachments arrived. Use the evidence appropriate to each claim.

For pending results, do not assume that visibility transfers responsibility. BMA guidance supports explicit responsibility and action arrangements, with urgent action considered by the clinician who receives the information. ¹⁰⁰

The review team should define risk-based escalation times for urgent information. The transfer service's eight-day fallback trigger does not establish a safe waiting period for an individual patient.

Classify findings carefully

Assess the original failure and the fallback separately. A safe manual procedure does not establish that a required automatic capability is present. Equally, one recovered transaction failure does not establish that the whole product is noncompliant. Use the automation examples and finding classifications and fallback findings with the applicable baseline.

Evidence position	Appropriate treatment
No supplied procedure or test demonstrates recovery	EVIDENCE-GAP. Request the missing material.
Supplier route, contract or adopted version is unknown	APPLICABILITY-UNRESOLVED. Establish the applicable baseline.
A cited specification or attachment was not inspected	SOURCE-DETAIL-REQUIRED. Obtain the relevant controlled detail.
Verified behaviour contradicts an applicable requirement	Consider REQUIREMENT-NONCONFORMANCE, with the clause, scope and contradictory evidence.
A plausible harm pathway lacks adequate analysis	Record a safety concern for CSO review. Do not invent a risk score or residual-risk acceptance.

These dispositions follow the general review method. No actual Hazard Log, product or practice has been assessed here.

Use with the closed-network review

For a fallback sample, request the incident, route decision, package inventory, recipient checks, clinical task outcomes and post-restoration reconciliation. Identify any residual supplier defect separately from completed patient-record recovery. These are proposed evidence requests, not evidence that the documents already exist.

The workbook remains in the approved Copilot environment. Any workbook sheet, row or cell references must come from the actual workbook inspected there. Never invent locations from this wiki.

This investigation is a wiki supplement. It is not included in the existing version 1.1 combined Markdown reference. Keep its source date and evidence qualifications if it is later incorporated into a controlled export.

Return to process and requirements or specific activity investigations.