Live synthetic specimen · version 2

A discrepancy register should show the evidence chain—not just the red flags.

Explore a fictional ClinicOps review output. Each row keeps the approved reference, observation, evidence basis, machine signal, owner and human decision separate so a reviewer can see what is known, what is inferred and what still needs authority.

Build a free evidence packet Scope one real review

Synthetic by design. Every device name, identifier, source and finding below is invented. This page demonstrates method and work-product structure only. It is not a compliance determination, legal opinion, safety assessment, release authorization or evidence of a client engagement.

6illustrative findings

4distinct evidence states

100%rows with explicit evidence basis

0automated compliance conclusions

Explore the register

Filter the synthetic findings, then select any row to inspect its evidence chain and decision boundary.

ID	Field	Reference	Observed surface	Observed	Signal	Owner / decision
F-01	IFU revision	IFU-12	EUDAMED export	IFU-11	DIFFERENT	Regulatory Affairs · review open
F-02	Manufacturer name	Example MedTech GmbH	SS(C)P	Example MedTech GmbH	MATCH	Evidence preserved · no discrepancy action
F-03	Storage upper limit	25 °C / 30 °C conflict	Label artwork	25 °C	UNRESOLVED	RA/QA owner · authority decision required
F-04	Basic UDI-DI	BUDI-ALPHA-001	Distributor master	BUDI-ALPHA-01	DIFFERENT	Master Data · correction candidate
F-05	Sterile status	Sterile EO	ERP product text	Sterile	CLOSED	QA decision · wording accepted in context
F-06	Contraindication phrase	Reference phrase v4	Local IFU	Reference phrase v3	DIFFERENT	Medical / RA review · propagation check

What makes the register evidence-first

Source ≠ observationThe approved reference and the downstream observed value remain separate records.

Signal ≠ conclusionDIFFERENT means text or declared data differs. It does not mean noncompliance.

Automation ≠ authorityWhen sources conflict, the workflow stops at unresolved authority and routes the decision to a named human owner.

Example evidence chain

1 · Reference evidenceApproved change record / controlled source

2 · ObservationDeclared downstream record and captured value

3 · Deterministic signalMatch / different / unresolved / not observed

4 · Human decisionAccept, correct, investigate, defer or close with rationale

ClinicOps can automate the structure and comparison. The accountable client role retains source-authority and release decisions.

From free check to controlled review

The browser-local integrity check produces one portable evidence packet. A real review extends that pattern across an agreed population of fields, sources and downstream surfaces with preserved source references, exception routing and a named reviewer.

Try the free integrity check Build a scope brief Email info@clinicops.dk

Need the earlier static artifact? Open archived PDF specimen v1.5. The interactive page above is the current specimen experience.