Skip to main content
Post generates, validates, and delivers test messages: HL7 v2.3 through v2.8, FHIR R4, and NCPDP SCRIPT. Validation is derived from the published standard’s machine-readable definitions, so the generator and validator can’t drift from the spec or from each other. Free generation and validation work without an account. Pro features require a Pidgeon account sign-in.

​
Before you start

  • Install Post (or on macOS).
  • Post runs its engine in a local Bridge sidecar on localhost:5101. It starts with the app; you don’t manage it separately.

​
One loop: generate, validate, prove

1

Generate a message

Open the Generate panel (under Compose in the sidebar). Pick a message type, for example ADT^A01, set a count, and generate. The message appears in the output pane with syntax highlighting.The same operation from the CLI:
2

Validate it

Open the Validate panel (under Inspect). Paste your generated message or load the file, then choose a mode: strict (the published spec) or compatibility (real-world tolerance). Results show field-level issues with rule IDs, expected/actual values, and a fix suggestion per issue.CLI equivalent:
Exit code 0 means validation passed; 1 means issues were found. That makes it a CI gate with no extra wiring.
3

Inspect a field you don't recognize

Every validation issue links into the built-in standards reference. You can also look up any segment or field directly:
4

Run a conformance check

Open the Conformance panel (under Inspect) to probe a FHIR endpoint against a published Implementation Guide and read the pass/fail result per rule. Current IG scope includes US Core and Da Vinci PAS 2.1.CLI equivalent:
5

Export the proof

Open Reports (under Library) to export validation and conformance results as self-contained HTML you can attach to a ticket or hand to a stakeholder.

​
When something fails

​
Next steps