OCE.8:5.1 - Unlike Transfer Probe – Emergency-Department Medication Reconciliation
A public hospital emergency department considers third-party AI support from medication-history assembly through acceptance of the reconciled list and any medication-order action. Continuous service, patient and worker protection, privacy, licensed practice, and statutory authority remain in force. PumpWorks thresholds, roles, and options do not transfer.
Gather decision-bearing perspectives before drawing specialist conclusions. Clinicians and pharmacists describe actual reconciliation Work, exceptions, handoffs, suggestion-review burden, and fallback. Other emergency-department workers, Operations, and service staff supply queue, coordination, downtime, and continuity knowledge. Patients and caregivers supply evidence about medication-use, communication, privacy, and protection conditions; a missing voice qualifies only the dependent claim or option. Provider technical and service staff supply service-boundary, data/model handling, support, failure-return, substitution, knowledge-retention, and exit knowledge. Use these contributions to revise the comparison. Any clinical or legal conclusion, agreement, veto, authority, choice, or adoption claim needs its own applicable basis.
| Direct owner | What absence blocks | Result needed to reopen the affected option |
|---|---|---|
| clinical governance and licensure | Any discrepancy acceptance, reconciled-list acceptance, or medication-order action assigned to provider AI/staff or an unqualified holder. | For each action and holder: allowed, conditional, or forbidden, with authority/licensure basis, scope, supervision, escalation, interval, and evidence. |
| clinical safety and target-domain practice | AI-suggestion options and their probe, not a complete clinician-only way. | Conditions for displaying, using, checking, overriding, escalating, and stopping suggestions, plus comparison, failure, and clinician-only fallback evidence. |
| privacy, information governance, and cybersecurity | Any unapproved data flow or provider service. | Permitted fields, purpose, accessors, locations, interval, provider access, custody, retention/deletion, provenance, incident return, and patient-information condition. |
| provider, procurement, contract, and service | Reliance on an unproved promise, continuity, recovery, substitution, or exit. | Bounded promise and capability evidence, continuity window, failure return, substitution, exit, and data/model/artifact/knowledge return. |
| Operations, workforce/labor, human factors, and patient/worker protection | Any arrangement or probe whose service burden or fallback cannot be compared safely. | Service window, queue/workload and coordination burden, downtime/manual fallback, staffing constraints, protection conditions, and stop/revert observations. |
For each provider contribution, use only the action and holder combination permitted by the direct authority, licensure, safety, and data-governance results. Bounded processing or suggestions can be considered within those conditions; clinical acceptance or medication-order action needs its own affirmative basis. Verify provision separately from a commitment and qualify capability for the required Work envelope separately from one successful case. Keep applicable clinician-only and AI-only comparisons visible; reject AI-only enactment when a direct authority or safety result forbids it. When a required result is absent, keep the dependent action blocked and name the request and affected option. Obtain the jurisdiction-specific predicates even when a proposal includes “human in the loop”.