Make and check HL7 v2 and FHIR test messages

Realistic test data built from your own schema

Flag suspect messages on your live channels

Export EHR data to FHIR and count every record

Test FHIR endpoints against their implementation guide · In Post

Test conformance in CI before January 1, 2027

Realistic patients from your own schema

Message-stream monitoring

Catch bad messages that healthy channels hide

Export, check, and count every record

Go-live testing

Test an interface with realistic messages before go-live

AI on your terms

Local models, your own key, or your AI client

Tracer benchmark

How well rules and AI catch clinical errors

Engineering notes on benchmarks, harnesses, and standards work

CLI reference, guide packages, and setup

What runs on your machine, what leaves it, and the caveats

Named for the patient segment, and who it is built for

Sales, migration, and press inquiries

Download beta Sign in

Test CMS-0057-F conformance in CI.

Get repeatable FHIR conformance evidence before the January 1, 2027 deadline, from a check your CI runs on every release.

1

What breaks

Your vendor built the payer FHIR APIs, but the mandate makes them your responsibility. "The vendor said so" is not evidence.

2

Why the usual fix falls short

Endpoints and guide versions change every release, so a one-time check goes stale. You need a repeatable check with a dated record.

3

What Pidgeon does

Conform tests each live endpoint against its guide on every release, fails the build on a broken rule, and saves a dated report.

See Conform →Free during the public beta.