Reference·PD1 Segment·PD1-16
HL7 v2 Reference

PD1-16 in HL7 v2: A Field Guide to Immunization Registry Status

Jul 28, 2026 · 4 min read
← PD1-12

PD1-16 quietly feeds public health reporting pipelines — it tells a receiving system where a patient stands with a state or regional immunization registry, and it's a field most clinical test suites never touch because it feels like someone else's problem.

Quick answer

PD1-16 is the Immunization Registry Status field, a coded value reporting the patient's current standing with an immunization information system — for example, actively tracked, inactive, or lost to follow-up. It's paired with an effective date in PD1-17 and is most relevant to public health and registry-reporting integrations.

What this field contains

A
Active — the patient is actively tracked in the immunization registry
I
Inactive — the patient's registry record exists but is not currently active
L
Lost to follow-up — the registry has lost contact or tracking for this patient
Related field
PD1-17 — the effective date the current status took hold, needed to reconcile status changes over time

Example

Synthetic example Generated by Synthibase
PD1|||SYNTHIB COMMUNITY CLINIC^^12345|4521^WELLS^SARAH^^^DR|||||||01^ONE PER PATIENT^SYNTHIBLOCAL|Y|20260101|||A|20260115

PD1-16 (A) marks this synthetic patient as actively tracked in an immunization registry, effective on the date in PD1-17.

Where this trips people up

Because PD1-16 rarely affects core clinical workflows, it's easy for test data to leave it blank across the board — which means registry-reporting integrations only ever see the absent-value case and never get exercised against an actual status transition, like a patient moving from active to lost-to-follow-up. Since public health reporting pipelines often treat a missing status differently from an explicit one, that gap can produce silent reporting failures that only surface during an audit.

Testing HL7 v2 PD1: The Fields Your System Actually Needs to Handle
How to Build a Synthetic Patient Registry for Healthcare Testing
HL7 ADT Messages: A01 through A08 Explained
Test registry-status transitions before they hit production
Synthibase can generate patients across all immunization registry status values, including status changes over time, so your public health reporting integration gets tested against real-world transitions, not just blanks.
Start free trial →
This page is written independently by Synthibase for testing and informational purposes. It is not an official publication of HL7 International or X12/Washington Publishing Company, and is not a substitute for reviewing the official standard or your trading partner's companion guide. See our Terms of Service for full legal terms.