MedVertical

Use cases

Drift & Regression Detection

See what changed between comparable validation runs and trace the delta to the affected resource and field.

Understand change · Decision brief

Distinguish a real regression from pre-existing debt, then trace it to the exact affected resource and field.

Trigger
Scheduled validation, upgrade, profile change, or upstream data change
Evidence
Pinned run comparison with new, resolved, changed, and remaining findings
Decision
Remediate, accept the risk, or establish a new baseline?
Validation scope
Comparable dataset, validation engine, profiles, terminology snapshot, and environment
  1. Choose the accepted baseline

    Select the accepted run in the comparison view and make it the reference every later validation delta must preserve.

  2. Compare like with like

    Run the same scope on a schedule or after a change and classify the delta without mixing engine or profile drift into data drift.

    Readable delta summary with score movement, regressions, and resolved issues.
  3. Inspect the concrete finding

    Read the affected resource, field path, applied profile, and deterministic validation message that explains the regression.

    Selected Patient validation context with profile, field, and remediation evidence.

What this evidence supports

Records makes the measurement explicit. Your team still owns the decision.

Supports

A reviewable decision basis

A defensible distinction between new, resolved, changed, and remaining findings under one pinned validation basis.

Does not decide

The governance outcome

Whether the change was intended, which upstream release caused it, or whether the underlying value is clinically correct.

Follow a real baseline comparison.

See how Records moves from a change signal to the concrete finding.