CI/CD Quality Gate

Run the same FHIR validation contract in your pipeline that teams use for investigation and release evidence.

Ship safely · Decision brief

Use the same validation contract in CI that Records uses for investigation, re-runs, and release evidence.

Trigger: Pull request, merge, deployment candidate, or scheduled pipeline
Evidence: Records validation run, threshold result, and linked investigation context
Decision: Merge, deploy, or fix the FHIR output first?
Validation scope: Pipeline artifact or server, profiles, terminology, rules, baseline, and threshold policy

Start from the pipeline state
See the development validation state that the merge or deployment workflow is about to evaluate.
Open the run and evaluate the gate
Open the pipeline run and read the gate decision, validation scope, score, thresholds, and linked evidence.
Use the selected run as evidence
Close the merge decision on the selected Records run with its status, score, and evidence context.

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

Supports

A deterministic pipeline signal with machine-readable output and a run that can be investigated after the build.

Does not decide

Branch protection policy, clinical correctness, or whether production data matches the fixtures checked in CI.

Continue the workflow

Developer path

Copy the command, pin the validation basis, and connect the result to Records.

Start with one command, then connect Records when you need baselines, comparisons, and evidence.