HL7 v2 PV2-3 (Admit Reason): Format, Values, and Testing Notes
Admit Reason is the field a human actually reads when they're trying to understand why a test encounter exists - so if your synthetic data leaves it blank or nonsensical, every downstream review takes longer.
PV2-3 records the reason a patient was admitted, expressed as a coded element that can carry a diagnosis code, a free-text description, or both together depending on how the sending system populates it. Unlike some administrative PV2 fields, Admit Reason tends to carry real clinical signal, so test data generators should populate it with values that are internally consistent with the rest of the encounter - a fractured wrist admit reason paired with a maternity accommodation code will get flagged by anyone reviewing results, and rightly so.
What this field contains
Example
PV2-3 carries R65.2^ABDOMINAL PAIN RLQ^I10 - a code, its text, and the coding system it was drawn from.
Where this trips people up
It's tempting to treat Admit Reason as a throwaway free-text field and fill it with lorem-ipsum-style placeholders. That works fine for parser-level unit tests, but it falls apart the moment the test data feeds a workflow that routes on diagnosis category, or a QA reviewer cross-checks it against the diagnosis segments elsewhere in the message. Keep Admit Reason plausible and consistent with the rest of the encounter, especially in any test suite that exercises clinical decision support or utilization review logic.