Reference·DTP Segment·DTP03
X12 837I Reference

X12 837I DTP03 Field Guide: Date Time Period Values and Common Mistakes

Jul 28, 2026 · 4 min read
← DTP02

DTP03 is where the admission and discharge values actually sit, but on its own it's just a string of digits — its meaning only makes sense next to the qualifier in DTP01 and the format in DTP02, and length-of-stay math depends on getting both admission and discharge occurrences right at once.

Quick answer

DTP03 is the Date Time Period element on an X12 837I claim — the field holding the actual date or date-time value, whose exact shape depends on DTP02. For admission and discharge occurrences this is typically a date paired with a time; for a statement period it's a date range.

Format by DTP02 value

Date only
CCYYMMDD — used when DTP02 is D8, e.g. 20260724
Date and time
CCYYMMDDHHMM — used when DTP02 is DT, e.g. 202607241430 for an admission at 2:30 PM
Date range
CCYYMMDD-CCYYMMDD — used when DTP02 is RD8, from-date then through-date, for a statement period

Example

Synthetic example Generated by Synthibase
DTP*096*DT*202607281115

DTP03 carries 202607281115 — a discharge on July 28, 2026 at 11:15 AM, four days after the admission on July 24. Synthetic claim data.

Where this trips people up

Validation logic that checks DTP03 in isolation for correct length and digit patterns rarely cross-checks it against the matching occurrence elsewhere in the same claim — so a discharge date that falls before the admission date, or a length of stay that spans an implausible number of days, sails through untouched as long as each individual value is well-formed. Since synthetic test data tends to generate admission and discharge dates that are already sensible relative to each other, this gap only gets caught once a real, malformed pair from a trading partner reaches production and produces a negative or absurd length of stay downstream.

X12 837I DTP Segment Guide: Fields, Format, and Testing Gotchas
How to Test 837I Institutional Claims: A Complete Guide
How to Write EDI Test Cases That Actually Catch Go-Live Failures
Generate both valid and deliberately broken date pairs
Synthibase generates synthetic 837I claims with both properly ordered and deliberately reversed admission/discharge pairs, so length-of-stay validation gets tested against more than well-formed happy-path dates.
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.