Reference·PD1 Segment·PD1-12
HL7 v2 Reference

HL7 v2 PD1-12 (Protection Indicator): Format, Values, and Testing Notes

Jul 28, 2026 · 4 min read
← PD1-11 PD1-16 →

PD1-12 is one character wide and one of the highest-stakes fields in the whole segment — it's the flag that tells downstream systems a record needs restricted handling, and a generator that never sets it to Y means that code path ships untested.

Quick answer

PD1-12 is the Protection Indicator field, a single Y/N value marking whether the patient's record requires restricted access or special confidentiality handling. It's commonly used for VIP patients, staff members receiving care at their own facility, or anyone who has requested additional privacy protections.

What this field contains

Y
Protected — the record requires restricted access or confidentiality handling beyond standard controls
N
Not protected — standard access rules apply; this is also the default when the field is left blank in many systems
Format
Single character — no components — just a bare Y or N value
Related field
PD1-13 — carries the effective date when the protection status took effect, useful for auditing when a flag was set

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-12 (Y) flags this synthetic record as protected, paired with an effective date in PD1-13.

Where this trips people up

Because a Y in PD1-12 is supposed to trigger real access restrictions, testing it properly means generating protected records and then verifying they're actually blocked from the queries and directory listings that check the flag — not just confirming the field parses. Teams that only test the N (unprotected) case get a test suite that passes cleanly while the restricted-access logic itself has never once been triggered.

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 restricted-record handling with synthetic VIP patients
Synthibase generates a realistic mix of protected and unprotected records, so your access-restriction and directory-suppression logic gets tested against both states, not just the default.
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.