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

Seed a staging database without touching PHI.

Fill staging with realistic patients built from your own schema, with no real patient data involved.

1

What breaks

Legal says no to the production snapshot, again. Staging stays a museum of test patients from 2019.

2

Why the usual fix falls short

Hand-built data never reaches the depth of a real system: the foreign keys, the overlapping encounters, the rare patients.

3

What Pidgeon does

Flock generates patients from your own schema, including the edge cases you choose. None of it was ever real, so there is no patient data for the committee to review.

See Flock →Flock is free during the beta. You sign in with a free Pidgeon account.