Use Cases
When to use Records
Six scenarios where Records produces the evidence you need — from release gates and drift detection to multi-server comparison, regulatory submissions, CI/CD pipelines, and agentic FHIR workflows.
When to Use Records
Six concrete scenarios where Records produces the evidence you need.
Release Safety Gate
Validate before pushing an IG/Profile update, FHIR server upgrade, or mapping change to production.
Drift & Regression Detection
Detect conformance drift from terminology updates, IG changes, and upstream system changes — continuously, not just at go-live.
Multi-Server Comparison
Compare conformance across servers, suppliers, and environments. Enforce SLAs with objective, vendor-neutral evidence.
Regulatory & Audit Evidence
Produce reproducible, timestamped quality evidence for regulatory submissions (ICH E6(R3), 21 CFR Part 11) and program-acceptance gates.
CI/CD Quality Gate
Add FHIR validation to your GitHub Actions or GitLab CI pipeline. Catch conformance issues before they merge.
Agentic FHIR Workflows
Validate FHIR generated, transformed, summarized, or routed by AI agents before it becomes downstream data.
