Generate, validate, and deliver HL7 v2 and FHIR test messages

Schema-aware, FK-safe synthetic test data. Native HL7 v2, FHIR, and SQL

Reads the channels you already run; flags suspect messages for review

Healthcare data moved between systems as validated, reconciled exports · Beta

FHIR implementation-guide conformance evidence · In Post

Prove conformance in CI before January 1, 2027

Relationally consistent patients from your schema, no committee

Message-stream monitoring

Read the messages, not just the pipes: any engine or none

Validated, reconciled exports between systems

Go-live testing

Vendor-realistic messages, validation, delivery

AI on your terms

Local models, your own key, or your AI client through MCP.

Tracer benchmark

What rule sets, models, and toolchains actually catch, measured and published

Engineering notes on benchmarks, harnesses, and standards work

CLI reference, IG packages, deployment modes

Local execution, egress posture, and the honest caveats

Named for the patient segment, and who it is built for

Sales, migration, and press inquiries

Download beta Sign in

HL7 Table 0001 - Administrative Sex

HL7 Table 0001 (Administrative Sex) lists the coded values HL7 v2 messages use for the administrative sex of a patient, carried in PID-8.

Table	0001
Name	Administrative Sex
Carried in	PID-8
Codes shown	3 sample codes

Code	Meaning
F	Female
M	Male
U	Unknown

Example

A live, engine-generated example lands here with the phase-1 data export.

Validation context

strict A PID-8 value outside this table raises a coded-value finding in strict mode.

This answer, in your terminal

pidgeon lookup table 0001

Wire it into your AI agent:

claude mcp add pidgeon -- npx -y @pidgeonhealth/mcp

Download Post free to browse this reference with generation attached.