HL7 v2 GT1 Segment Guide: Fields, Format, and Testing Gotchas
GT1 shows up in DFT and BAR messages carrying the person who is financially responsible for the visit, and it is the segment most likely to get skipped in test suites because nobody thinks of "who pays the bill" as clinical data.
GT1 is the Guarantor segment in HL7 v2. It carries the name, address, phone, relationship-to-patient, and SSN of whoever is financially responsible for the encounter, most often used in financial and billing-triggered messages like DFT and BAR. If your downstream system does patient statements, self-pay follow-up, or bad-debt routing, it is almost certainly reading GT1.
The fields that actually matter in practice
Example
A synthetic GT1 segment for a self-pay guarantor. All names, addresses, and the SSN are fabricated for this example.
Where this trips people up
Teams building test data for billing workflows tend to treat GT1 as an afterthought because it feels administrative rather than clinical, so test files ship with the segment missing entirely, or with every guarantor set to "self" so the relationship-code branches in the billing engine never actually get exercised. Another common miss: SSN fields in GT1 are frequently left populated with realistic-looking values in lower environments, which is exactly the kind of PHI exposure that synthetic data generation exists to prevent. If your test generator isn't producing a spread of guarantor relationships and consistently fake SSNs, your GT1 coverage is thinner than it looks.