Reference·DTP Segment·DTP01
X12 834 Reference

X12 834 DTP01 (Date/Time Qualifier): Format, Values, and Testing Notes

Jul 28, 2026 · 4 min read
DTP02 →

One three-digit code decides whether the date that follows means a member's coverage is starting or stopping.

Quick answer

DTP01 is the qualifier that tells a downstream system what a given DTP occurrence's date actually represents. On an 834 enrollment file, the two qualifiers that matter most for coverage status are the coverage-begins date and the coverage-ends date, though the same segment shape can carry other date types depending on the loop.

Valid code values

348
Coverage Begins — the date the member's coverage under this plan takes effect
349
Coverage Ends — the date the member's coverage under this plan terminates
336
Employment Begin — the date the member's employment started, used for group eligibility waiting periods

Example

Synthetic example Generated by Synthibase
DTP*349*D8*20261231

In this synthetic segment, DTP01=349 marks the date that follows as a coverage-ends date, with the member's coverage terminating on 2026-12-31.

Where this trips people up

It's easy to build test data that only ever includes a 348 coverage-begins qualifier, since that's the minimum needed to enroll a synthetic member. But a termination file needs a 349, and some carriers send both qualifiers on the same member loop at once — an addition with a future termination already scheduled. If your ingestion logic assumes there's exactly one DTP per member and grabs whichever one it finds first, it will misread a termination as an effective date or drop the termination entirely. Test with 348 alone, 349 alone, and both together in the same loop.

X12 834 DTP Segment Guide: Fields, Format, and Testing Gotchas
EDI 834 Enrollment File: Format and Testing Guide
How to Write EDI Test Cases That Actually Catch Go-Live Failures
Test every coverage-date qualifier before go-live
Synthibase generates synthetic 834 files with realistic combinations of coverage-begin and coverage-end qualifiers, including members with both scheduled at once, so date-handling logic gets exercised before a real file gets it wrong.
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.