Prerequisites
- Pidgeon CLI installed (
dotnet tool install -g pidgeon) - Optionally: a vendor profile from real sample messages
Generate your first messages
Start with a basic HL7 ADT admission message:Multi-standard generation
Pidgeon auto-detects the standard from the message type. You can also specify it explicitly:Use vendor profiles for realistic patterns
Real-world messages vary by EHR vendor. Use vendor profiles to match specific patterns:Analyze sample messages
If you have real messages (de-identified), analyze them to create a profile:
Generate with the profile
Batch generation with output files
Save generated messages to files for use in integration testing:Common message type combinations
Here are typical combinations for integration testing scenarios:| Scenario | Message Types | Description |
|---|---|---|
| ED Visit | ADT^A01, ORU^R01, ADT^A03 | Admit, lab results, discharge |
| Pharmacy | ORM^O01, RDE^O11 | Order, dispense |
| Lab Order | ORM^O01, ORU^R01 | Order, result |
| Immunization | VXU^V04 | Vaccination record |
| Billing | DFT^P03 | Charge posting |
Next steps
- Validate your generated messages to catch structural issues
- Build multi-step scenarios with the Workflow Wizard
- Set up vendor profiles for environment-specific testing

