Skip to main content

​
pidgeon config analyze

Analyze sample messages to detect vendor-specific patterns and save as a named profile. 
pidgeon config analyze --samples <dir> --save <name>
FlagTypeDescription
--samples <dir>stringDirectory of sample messages to analyze
--save <name>stringName to save the profile as
pidgeon config analyze --samples ./epic-er-messages --save epic_er

​
pidgeon config list

List all saved vendor profiles. 
pidgeon config list

Profile          Standard    Message Types         Samples
──────────────────────────────────────────────────────────
epic_er          HL7 v2.3    ADT^A01, ADT^A08      47
cerner_lab       HL7 v2.3    ORU^R01               23
meditech_pharm   HL7 v2.3    RDE^O11               15

​
pidgeon config show

Display details of a saved profile. 
pidgeon config show <name>

pidgeon config show epic_er

​
pidgeon config use

Set a profile as the default for all commands. 
pidgeon config use <name>

pidgeon config use epic_er

​
pidgeon config export

Export a profile as JSON for sharing with your team. 
pidgeon config export <name>

pidgeon config export epic_er > epic_er_profile.json

​
pidgeon config diff

Compare two vendor profiles side by side. 
pidgeon config diff <a> <b>

pidgeon config diff epic_er cerner_lab

​
Workflow Example

1

Analyze sample messages

pidgeon config analyze --samples ./epic-messages --save epic_er
2

Generate with the profile

pidgeon generate ADT^A01 --vendor epic_er --count 20
3

Validate against the profile

pidgeon validate --folder ./test-data --profile epic_er