Testing HL7 v2 PID-19: What SSN Number - Patient Actually Needs to Handle
PID-19 is one of the highest-risk fields in the entire PID segment to get wrong in a test environment, because unlike most demographic fields, a real social security number dropped into a lower environment is a direct compliance and identity-theft exposure, not just a data-quality issue.
PID-19 is the nineteenth field of the HL7 v2 PID segment — it carries the patient’s social security number, sent either with or without dashes depending on the source system’s formatting convention.
What this field contains
Example
PID-19 carries a synthetic, dashed-format SSN. Synthetic patient — not a real person; this number is not a valid or assigned SSN.
Where this trips people up
Some source systems send SSNs with dashes and others send nine bare digits, so a field-length or format validator tuned to one convention will reject valid values from the other. More critically, teams sometimes copy real production SSNs into test environments to "make testing realistic" — which is exactly the kind of PHI exposure that synthetic test data exists to eliminate.