Reference·X12 837I·DTP
X12 837I Reference

X12 837I DTP Segment Guide: Fields, Format, and Testing Gotchas

Jul 28, 2026 · 6 min read

On a professional claim, DTP is mostly background noise — an onset date here, a statement period there. On an institutional claim, two specific DTP occurrences, admission and discharge, directly drive length-of-stay calculations that feed DRG pricing and per-diem logic, which makes getting this segment right a much bigger deal on the facility side.

Quick answer

DTP (Date or Time or Period) is a generic date segment reused throughout an X12 837I claim. On an institutional claim its most consequential occurrences carry the admission date and the discharge date, since the gap between the two is what downstream systems use to calculate length of stay and price the claim accordingly.

The elements that actually matter in practice

DTP01 →
Date/Time Qualifier — identifies which date this occurrence represents — admission, discharge, statement period, and more — see the dedicated page below
DTP02 →
Date Time Period Format Qualifier — tells the parser whether DTP03 is a single date or a range — see the dedicated page below
DTP03 →
Date Time Period — the actual date value, formatted according to DTP02 — see the dedicated page below

Example

Synthetic example Generated by Synthibase
DTP*435*DT*202607241430

A synthetic admission DTP: qualifier 435 marks this as the admission date and time, format DT means DTP03 carries both date and time, here July 24, 2026 at 2:30 PM. Synthetic claim data.

Where this trips people up

Length-of-stay logic that reads the admission and discharge DTP occurrences independently, without checking they actually belong to the same encounter, can silently miscalculate the stay when a claim carries multiple DTP segments for related but distinct dates — like a statement period that doesn't line up exactly with the admission-to-discharge span on a claim that was billed in installments. Test data that only ever produces a clean, matching admission/discharge pair never exercises that mismatch, so the bug doesn't surface until a real multi-page inpatient stay comes through with dates that don't perfectly nest inside each other.

How to Test 837I Institutional Claims: A Complete Guide
How to Write EDI Test Cases That Actually Catch Go-Live Failures
Generate every institutional date scenario your claims need
Synthibase generates synthetic 837I claims with realistic admission, discharge, and statement-period date combinations — including mismatched and multi-page stays — so length-of-stay logic gets tested against more than one clean happy path.
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.