EPCS Non-Repudiation and the Clinical-Agent Boundary
DEA EPCS requires two factors of independent categories for controlled-substance prescribing, and it assumes something the hospital floor cannot deliver: that the authenticated session and the prescribing human are the same thing.
The prescriber-of-record problem
Workstations on wheels pass between clinicians with cached sessions. Infection control keeps hands off shared keyboards, so credentials live where they can be reached. A terminal unlocked by one colleague issues orders under another's identity for half a shift.
When a diversion investigation asks who the prescriber of record actually was at the moment a Schedule II order left the EHR, the session log answers with an account name. An account name is an assertion. Non-repudiation requires the assertion to be undeniable, and a session that outlives the human who opened it can never make it so.
The per-script audit object
The alternative binds the signature to the script. The order surfaces on the prescriber's own enrolled device. The parameters are visible. A fresh biometric press produces a signature from a hardware-bound key that only that clinician's biometric can exercise, with the order parameters hashed into the payload.
Each script chains to the prescriber's prior signed action, so the audit object is a sequence, and altering one record breaks every record after it. A DEA auditor or a state board verifies the signatures against a published key. The two factors are structural: the device is possession, the biometric is inherence, and the workstation stops mattering.
The clinical-agent boundary
Clinical AI is moving from documentation into ordering, and the boundary question arrives with it. The workable boundary is the one on our healthcare page: routine lab orders and template-compliant documentation run on the agent's own session, and the narrow set that carries legal weight requires the named human. Controlled substances. High-risk interventions. Record release outside the standing scope.
The agent can prepare the order and request approval. Only the enrolled prescriber can authorize, on their own device, with a fresh biometric, producing the same per-script artifact. An agent attempt to authorize without that signature produces no valid proof, does not execute, and lands in the audit stream as a signal.
Part 11, in one paragraph
21 CFR Part 11 asks for electronic signatures with unique identification, non-repudiation, and trustworthy audit trails. A hardware-bound, biometric-gated, per-action signature is unique identification by construction. The hash chain with daily anchors is the trustworthy trail. The same object answers both frameworks.
Common questions
Why can't a shared workstation session carry non-repudiation?
Because the session outlives the human. It proves an account was active, and an account is not a person. Non-repudiation requires evidence bound to the individual at the moment of the act.
Can a clinical agent ever order a controlled substance?
No. It can prepare and request. The order executes only on the named prescriber's fresh, hardware-bound proof.
Does this replace our e-prescribing workflow?
No. Your EHR keeps the record and the workflow. This is a thin layer on the action path that adds the per-script evidence object, exportable for DEA audit or state board review.