Pediatrics
DEMO-10 — Positive Newborn Screen Without Documented Confirmatory Testing
Authored demonstration. Not a live employer result.
01 · Situation
The program named the test, the owner, and the deadline. The deadline passed.
An illustrative newborn screening program — presented here as a named illustrative program record, since real newborn-screening requirements vary by jurisdiction and no single universal rule is asserted — flags a positive result requiring confirmatory testing within a program-defined window. The program record itself names the required test, the responsible party, and the deadline.
02 · Evidence
What the record holds.
- E1Positive newborn screening result
Verified · Day 0
- E2Illustrative newborn screening program record naming the required confirmatory test, the responsible pediatric provider, and a 14-day window within which the provider is responsible for both ordering the test and following up on its completion
Verified · Day 0
- E3Confirmatory-test-result repository reviewed through Day 14; no result found
Verified · Day 14
- E4Program follow-up-tracking log reviewed through Day 14; case still marked open, unconfirmed
Verified · Day 14
03 · Obligations / Owners
The chain of responsibility.
- 01
Screening program (notify and name the required test, owner, and deadline — done, per E2)
- 02
Pediatric provider (order and follow up on completion of the confirmatory test within the window, per E2)
04 · Accountability Break
Where the chain broke.
The program correctly named the requirement, owner, and deadline; the confirmatory-test repository shows no result at the deadline, and the program's own tracking log independently confirms the case remained open.
05 · Next Action
The corrective obligation.
Pediatric provider completes or documents attempted completion of the confirmatory test; program escalates any case still open at the window's close.
06 · Economic Boundary
Where the evidence stops.
Not established.
07 · Engine Answer
What the Engine can and cannot establish.
The pediatric provider was required, per the illustrative program record in E2, to order the named confirmatory test and follow up on its completion within 14 days. The confirmatory-test-result repository, reviewed through Day 14, contains no result, and the program's own tracking log independently shows the case still open and unconfirmed at that date. The Engine can demonstrate that a clearly defined, program-sourced obligation — test, owner, and deadline all specified by the governing record itself — was not demonstrably fulfilled by its deadline. It cannot establish whether the test was performed outside the reviewed repository, or why the case remained open in the program's own tracking.
The program named the test, the owner, and the deadline. The deadline passed with no result on file.