Monitor During Development

The Problem

Your team is building 5 FHIR APIs — four under CMS-0057-F plus CMS-9115-F's Provider Directory — to meet CMS-0057-F requirements. Development takes 6-12 months. By the time you reach Inferno testing, you've accumulated months of potential drift.

Every sprint adds features, refactors data models, and updates dependencies. Any of these changes can break conformance. But you won't know until certification testing—when fixing issues is expensive and delays are costly.

How Tessara Helps

• Continuous conformance checks during development sprints
• Catch drift when code is fresh in developers' minds
• Reduces Inferno testing iterations (saves weeks)
• Provides evidence chain for internal QA reviews
• Zero configuration required—point at your development APIs and start monitoring

Development Workflow Integration

Run Tessara in your CI/CD pipeline or as a scheduled job. Get drift reports before PRs merge. Surface conformance issues when they're easiest to fix—during active development, not months later during certification.

# Run the full 5-stage conformance check in CI
tessara check \
  --spec ./igs/carin-bb-2.1.0.tgz \
  --target https://dev.example.com/fhir \
  --key ./ci-signing.key \
  --operator "Acme Health" \
  --mandate CMS-0057-F \
  --output conformance-verdict.json

# Exit status is non-zero on NON-CONFORMANT verdict,
# failing the build before the drift reaches staging.