MedVertical
Open menu

Use cases

Release Safety

After a mapping or profile change, check the delivery again and compare the findings before accepting the release.

Keep the release decision tied to the change

Compare the candidate with the accepted result under the same validation basis before deciding whether to release.

Accepted baseline

The result your team accepted.

Release candidate

The delivery after the change.

Comparable checks

Aligned scope, profiles, terminology and rules.

Release decision basis

New and resolved findings, with the checked scope.

Verify a correction before accepting the delivery.

  1. Explain the finding in context

    Two terminology findings point to the same invalid identifier-use code in one of twelve synthetic Patients. Read the affected field and its required value set together.

    Two terminology findings identify the same invalid identifier-use code and its required FHIR value set.
  2. Verify the change under the same basis

    Correct the source mapping, then validate the same delivery again. The comparison shows two resolved findings and no new findings.

    A computed comparison under the same immutable validation basis reports two resolved findings and no new findings.
  3. Keep the result with its scope

    Keep the checked scope, remaining findings and validation basis with the report for the receiving team.

    The resulting report retains the corrected run, recorded scope and validation basis.

The same twelve Patients were checked before and after the source correction. Two findings resolved, no new findings appeared and 24 information occurrences remain. Your team reviews the remaining findings before accepting the delivery.

Check your next delivery before release.

Bring a test delivery, its profiles and the change your team needs to verify.