Find where controlled regulatory information no longer agrees.
ClinicOps reconciles the client-approved sources and downstream surfaces you place in scope, preserves the evidence behind each finding, and routes ambiguity to named human review.
The review is designed for real operational questions: a regulated fact changed, several records or documents depend on it, and your team needs a clear discrepancy register before deciding what to correct.
What the review checks
Source authority
If supplied controlled sources disagree, the case becomes UNRESOLVED_AUTHORITY. ClinicOps does not silently choose the winner.
Cross-surface reconciliation
Declared fields are compared only across the evidence population the client explicitly approves.
Change propagation
Approved old/new values are checked against the downstream surfaces the client declares as affected.
Human review
External ClinicOps outputs remain behind named review, finding dispositions and exact artifact binding.
What one first review looks like
- one device family or Basic UDI-DI group;
- 1–3 client-approved controlled sources;
- 2–6 downstream surfaces;
- 3–10 declared fields;
- optional approved change event with explicit old/new values;
- one named qualified reviewer.
The output is a human-reviewed evidence and discrepancy pack with source references, findings, unresolved-authority cases, reviewer dispositions and documented next-action ownership.
Four fail-closed machine states
| State | Meaning |
|---|---|
| PASS | No discrepancy found by the declared checks. Human review is still required before the ClinicOps work product is delivered. |
| REVIEW_REQUIRED | A declared field is missing or differs from the single supplied controlled value. |
| UNRESOLVED_AUTHORITY | The supplied controlled evidence does not establish one authoritative value. |
| HOLD_FOR_HUMAN_DECISION | A declared change has not propagated, the approved source does not match the declared new value, or a downstream surface contains a third value. |
What happens after the review
Remediate
After client RA/QA approves the authoritative value, ClinicOps can coordinate agreed corrections across the records and documents placed in scope.
Maintain
For recurring change, ClinicOps can map affected surfaces, coordinate propagation, verify implementation and document closure.