Understanding X12 278 UM04: Health Care Service Location Information in Practice
UM04 packs two separate pieces of information into one composite, and it's common to see integrations populate the first half — the facility type — while quietly leaving the second half blank, which is exactly the half a reviewer needs to tell an emergency admission apart from an elective one.
UM04 is the Health Care Service Location Information composite in an X12 278 UM segment — it combines a facility type code, describing where the service happens, with an admission type code, describing the nature of an inpatient admission when one applies.
What this element contains
Example
The composite 21:B — facility type 21 (inpatient hospital) paired with admission type B (elective) — even though this particular example's UM03 is an office visit, illustrating how the composite carries facility and admission context independently of the service type. Synthetic prior authorization data.
Where this trips people up
UM04-2, the admission type sub-element, is only meaningful when the request actually involves an admission, so plenty of integrations leave it blank by default and only populate UM04-1. That works fine for office-visit requests, but the same code path often ships unchanged into inpatient authorization workflows, where a missing admission type forces a reviewer to treat every request as ambiguous and kicks off a manual follow-up that a fully populated composite would have avoided.