Inferno is the conformance suite that CMS-0057-F uses to verify Da Vinci IG compliance. Implementations that pass Inferno meet a documented bar; implementations that fail need to fix the issues before production deployment. The Inferno test suites cover the Da Vinci IGs at varying depths, and the patterns for hitting conformance cleanly are well-established by 2026. Five patterns appear consistently in production-grade implementations. For the FHIR conformance and validation hub on this site, these are the practical conformance patterns.
1. Run Inferno Continuously, Not Once
The most common conformance failure pattern is one-time conformance: the implementation passes Inferno at certification time and stops being tested afterward. Code changes, dependency updates, and configuration drift slowly break conformance. By the time CMS or a customer notices, the gap has grown.
Production-grade implementations run Inferno on a continuous basis (nightly or per-deployment in CI). Conformance regressions surface immediately. The cost of running Inferno repeatedly is modest; the cost of letting conformance drift is substantial.
2. Build Inferno Into the Pre-Production Test Suite
A pattern where Inferno test scenarios are integrated into the implementation's normal test infrastructure. Engineers writing new code see Inferno results alongside their unit and integration tests. Conformance becomes a continuous concern rather than a periodic certification activity.
The integration requires Inferno tooling to work in CI environments, which has matured substantially. The HL7 Inferno project ships container images suitable for CI integration.
3. Test Against Production-Realistic Data
Inferno's default test profiles work but are intentionally narrow (small test patient populations, predictable demographics, clean data). Implementations that pass Inferno on default data sometimes fail on production data because the production data is more varied: edge cases in names, addresses, identifiers, and clinical resources.
Production-grade conformance work includes testing against larger and more varied data sets that approximate production conditions. The Inferno framework supports custom data sets; using this capability strengthens the production-readiness signal.
4. Test the Full Workflow, Not Just Individual IGs
Inferno's test suites cover individual IGs. The CRD test suite tests CRD; the DTR test suite tests DTR; the PAS test suite tests PAS. Production workflows cross IG boundaries: a CRD card launches a DTR SMART app that produces a Bundle for PAS submission. The cross-IG workflow has integration points that individual-IG testing does not exercise.
Production-grade conformance includes scenario-based testing across the full workflow. Implementations that pass each IG in isolation but fail at the workflow boundaries reveal integration gaps that Inferno alone does not catch.
5. Document Conformance Coverage With Custom Reports
Inferno produces test reports, but production-grade implementations layer their own documentation on top: which IGs are conformant, which versions, which test scenarios passed, what gaps exist. This documentation becomes the artifact shown to CMS auditors, customer compliance teams, and internal stakeholders.
The pattern is to treat the conformance report as a product artifact, not just an internal test result. Implementations that ship clean conformance documentation are easier for customers to evaluate and for regulators to assess.
How These Patterns Compound
The patterns combine to produce continuous, comprehensive, documented conformance. A production-grade implementation runs Inferno continuously (Pattern 1), with results integrated into CI (Pattern 2), tested against realistic data (Pattern 3), covering full workflows (Pattern 4), with documentation that makes the coverage visible (Pattern 5).
Implementations that adopt one or two patterns and skip the others have conformance gaps. Implementations that adopt all five have substantially stronger evidence of CMS-0057-F readiness than vendors who certify once and stop.
What Inferno Does Not Test (And What You Need In Addition)
Inferno tests conformance. It does not test production behavior under load, integration with specific EHR implementations, edge cases in operational scenarios, or long-term reliability. Inferno conformance is necessary but not sufficient for production readiness.
Production-grade Da Vinci implementations layer additional testing on top of Inferno. For PAS validation specifically, the Best tools for validating Da Vinci PAS submissions pre-production covers the testing tools. For the implementation mistakes that conformance testing alone does not catch, the 5 Da Vinci IG implementation mistakes to avoid in 2026 covers the failure modes.