People Who Rely on You Need You to Get the Message.
The Story
Healthcare is the space where nothing is easy for anybody. When your body starts breaking down, you need care — and you need it quick and you need it reliably.
A direct interface built with care. Plug-and-play integrations with SureScripts. Interface engines like Mirth keeping messages flowing between pharmacy, labs, EHR, demographic systems. Custom interfaces wired together over years of experience.
And then it breaks.
It shows up as a Jira ticket. Or a distressed phone call late at night. The system is down. We are no longer receiving messages. The pharmacy called — the script never came through.
An engineer combs through a massive, complex Gordian knot of interfaces and software and HL7 messages, reading individual pipe delimiters to discover that one segment changed by this much, and that is why this patient did not get their care.
The entire resiliency of the healthcare system comes down to a lot of parts moving exactly as they need to be. And to quote the CTO of Amazon Web Services: everything breaks all of the time.
If that is the case, then you better have a plan for it.
Why We Built Pidgeon
We have dealt with just about every major provider. Epic, Cerner, SureScripts, eClinical Works, MEDITECH, Fusion, Core EMR, Frameworks. If it exists out there and we have a pattern for it, we have vendor templates so that you have the specs you need and you can prepare and test for them.
We built Pidgeon because the tools available to healthcare integration teams do not match the stakes. You are responsible for the systems that deliver lab results, medication orders, and admission data to clinicians making real-time decisions about patient care. And your testing toolkit is a text editor and 14 hand-built ADTs.
That gap is why interfaces fail silently. That gap is why engineers get paged at 2am. That gap is why patients wait.
Pidgeon closes it.
What We Believe
Open source core.
The CLI is free, open source, and MPL 2.0 licensed. The core engine that parses, validates, and generates healthcare messages belongs to the community. We build premium products on top of it — not paywalls around it.
Local-first privacy.
Your data stays on your machine. De-identification runs locally. AI features use bring-your-own-key. We never see your messages, your patients, or your interfaces.
Healthcare-native.
We are not a general-purpose data tool adapted for healthcare. We are built from the ground up by integration engineers who have debugged HL7 messages at 2am. Every feature exists because we needed it ourselves.
Three products, one engine.
Post generates and validates test messages. Flock creates entire synthetic patient populations. Loft monitors live interfaces. They share the same clinical intelligence engine — build it once, serve three high-value markets.
The Name
PID identifies every patient in healthcare. Every ADT, every ORM, every ORU starts with the PID segment — Patient Identifier. Integration engineers have typed PID ten thousand times.
PID → Pidgeon.
If you get it, you are the audience.
The Team
Team information coming soon.
Trust Pidgeon.
PID identifies every patient in healthcare. Pidgeon protects the systems that serve them.
So the troponin result arrives. So the medication order processes. So the patient in bed 4 gets their care.
Every message that arrives correctly is a patient who gets their care.
We build for the people who stay.
$ dotnet tool install pidgeon