Turn one regulatory change into a review-ready evidence packet.
Anchor an approved reference, compare the records that should reflect it, expose evidence and ownership gaps, then export a portable packet for human review. Type each observed value, or upload that record's PDF and let this page suggest one from the text near the field name — you review and correct every value either way. No account, no black-box score. Nothing is sent to ClinicOps.
Evidence boundary. ClinicOps does not infer which source is legally authoritative and this page does not determine compliance. You choose the approved reference and declared scope. The tool structures the comparison and review queue.
This utility is a component of the Regulatory Integrity Scanner. Start there for the combined single-change and portfolio workflow; this page stays for the deep single-change packet with SHA-256 fingerprint and JSON re-import.
What PDF upload does here. This page reads an uploaded PDF's text locally (self-hosted pdf.js, no network call) and looks for the field name or record name you typed, then suggests whatever text sits next to it. Unlike the Technical File Consistency Check, which matches against a curated bilingual pattern library for a fixed set of regulatory fields, this is a plainer proximity search against the free-text label you chose — it works well when your PDF prints that exact label, and finds nothing when it doesn't. Every suggestion is marked and must be reviewed or corrected before the packet means anything; it never overwrites a value you typed yourself.
1 · Anchor the change
2 · Declare the downstream records
Mark a record in scope only when your team expects it to reflect this change. An empty observation is NOT OBSERVED, not proof that the real record is wrong. Type each observed value, or upload that record's PDF to suggest one.
strong: the label appeared with a value right next to it weak: a looser match — check it carefully
Record 1
Record 2
Record 3
Record 4
Evidence packet
Build the packet to see reconciliation and review-routing signals.
NOT RUN
0matching
0different
0not observed
0%evidence completeness
Declared record
Observed
Evidence
Signal
Owner
No packet built yet.
Deterministic review queue
No actions generated yet.
Packet fingerprint
Generated after the packet is built.
Identifies the generated packet bytes. It is not a digital signature and does not prove who approved the content.
TraceableReference, observations and evidence references stay distinct.
Fail-closedNo reference = no interpretation. No observation = no invented conclusion.
Human-ownedDifferences become routed review items, not automated compliance conclusions.
What the completeness score means
The score is simple and inspectable. It rewards a declared reference value, reference evidence, in-scope observations, evidence references, and owners for unresolved items. It is an evidence-packet completeness measure only — not a risk, regulatory or compliance score.
Use placeholders for confidential work. Nothing is sent to ClinicOps, but still avoid patient-identifiable information, credentials or material you are not authorised to process.
See the full register pattern
This tool handles one change event. The specimen register shows many findings, each with source evidence, machine state, action routing and an explicit human decision.