Reference·PV2 Segment·PV2-8
HL7 v2 Reference

What Is HL7 v2 PV2-8? Expected Discharge Date/Time, Explained for Testers

Jul 27, 2026 · 4 min read
← PV2-7 PV2-12 →

Length-of-stay dashboards, discharge planning tools, and bed-turnover forecasts all lean on one small timestamp buried in PV2 - and it's rarely tested with realistic values.

Quick answer

PV2-8 is the standard HL7 timestamp field capturing when a patient is projected to be discharged, set at or near admission and often revised as the stay progresses. It follows the same YYYYMMDDHHMMSS convention as other HL7 v2 timestamps. Test suites that exercise discharge planning, bed forecasting, or utilization review workflows depend on this field being populated with a plausible date relative to the expected admit date in PV2-7 - a discharge date before the admit date is an easy but common test-data mistake.

What this field contains

Format
YYYYMMDD[HHMMSS] — standard HL7 v2 timestamp precision
Typical use
Discharge planning — feeds bed forecasting, utilization review, and length-of-stay calculations
Relationship check
vs. PV2-7 — should fall after the Expected Admit Date/Time on the same segment

Example

Synthetic example Generated by Synthibase
PV2||A^SEMI-PRIVATE^HL70129|R65.2^ABDOMINAL PAIN RLQ^I10||||20260726073000|20260729120000||||20260724150000||||||||||||1^HOME^HL70112

PV2-8 holds 20260729120000, a three-day expected stay following the 20260726073000 admit time in PV2-7.

Where this trips people up

It's common to see test generators populate Expected Discharge Date/Time with a fixed offset (say, always "next Tuesday") regardless of the admit reason or accommodation type, which produces a data set where a same-day observation visit and a multi-week rehabilitation stay end up with identical projected lengths of stay. If your test suite validates length-of-stay logic at all, vary the offset by scenario rather than defaulting to one interval everywhere.

Testing HL7 v2 PV2: The Fields Your System Actually Needs to Handle
Regression Testing for EHR Upgrades: A Complete Guide
Synthetic Patient Data: Complete Guide for Software Testing
Model realistic lengths of stay in your test data
Synthibase varies PV2-8 and related visit timestamps by encounter type, so your synthetic patients produce believable length-of-stay patterns instead of one flat interval repeated across every test case.
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.