Clinical documentation authority
DEMO-30 — Evidence Outside the Authoritative Channel
Authored demonstration. Not a live employer result.
01 · Situation
Completion of an obligation is documented informally, outside the repository the governing protocol designates as authoritative for that obligation type. The authoritative repository itself is silent.
Illustrative documentation-authority policy, naming a specific clinical system as the sole authoritative repository for recording completion of this obligation type, and stating that informal channels (messages, personal notes) may not substitute for an entry in that system.
02 · Evidence
What the record holds.
- E1Documentation-authority policy, naming the authoritative repository and stating informal channels cannot substitute
Verified · on file
- E2Internal message from the responsible clinician stating the task was completed, sent outside the authoritative system — message exists and is located, but its account is not independently confirmed
Verified · Day 0
- E3Authoritative clinical system reviewed through Day 5; no completion entry found for this obligation
Verified · Day 5
03 · Obligations / Owners
The chain of responsibility.
- 01
Responsible clinician (complete the obligation and record it in the authoritative system named in E1).
04 · Event Type
The classification of the event.
ExecutionClaimed — E2 claims completion. EvidenceAttached — E2 and E3 are attached to the obligation. VerificationCompleted — the available evidence is evaluated against E1's completion-and-recording requirements.
05 · Verification Result
What verification established.
Evidence Status: E2 is LOCATED as an artifact. Its claim of real-world completion remains UNCONFIRMED. Repository-Review Result: INSUFFICIENT — the reviewed record does not demonstrate completion in the authoritative repository.
06 · Projection
What the evidence implies ahead.
The combined obligation is not demonstrably fulfilled. Execution is claimed but unconfirmed; required recording in the authoritative system is not demonstrated.
07 · Next Action
The corrective obligation.
Verify whether execution occurred through an accepted evidentiary path; if supported, require the completion to be recorded in the authoritative system with its actual execution and entry timestamps preserved.
08 · Economic Boundary
Where the evidence stops.
Not established.
09 · Engine Answer
What the Engine can and cannot establish.
E1 designates one specific system as authoritative for this obligation type and states informal channels cannot substitute. The authoritative system, reviewed through Day 5, contains no completion entry. A message exists outside that system claiming completion — the Engine locates and preserves that message, but its claim remains unconfirmed because no accepted verifying evidence appears in the reviewed record. The Engine can demonstrate that formal completion is not shown in the authoritative repository. It does not treat the informal message as proof the task didn't happen, and it does not treat the message as proof that it did.
Claimed outside the channel that counts. Not shown inside the one that does.
10 · What Remains Unknown
Outside the Engine's reach.
Whether the task was actually completed; whether the clinician simply failed to log it in the correct system or the work itself was not done.