Reference·UM Segment·UM03
X12 278 Reference

UM03 in X12 278: A Field Guide to Service Type Code

Jul 27, 2026 · 4 min read
← UM02 UM04 →

UM03 borrows the same service type code list that shows up on eligibility inquiries, which makes it tempting to treat it as an afterthought — but on a 278 it's the code that decides which clinical review criteria the payer applies, not just what benefit category gets described back.

Quick answer

UM03 is the Service Type Code in an X12 278 UM segment — it identifies the clinical category of the service being authorized, such as an inpatient stay, an office visit, or a surgical procedure, and the payer selects its review criteria based on this value.

What this element contains

Format
Two-character code — drawn from the standard service type code list shared with eligibility transactions
1
Medical Care — a broad general-medical review category
98
Professional (Physician) Visit - Office — office-based professional services
Repeatable
Not repeated within one UM segment — a request covering multiple service types needs a separate UM iteration or additional service line detail

Example

Synthetic example Generated by Synthibase
UM*HS*I*98*21:B*Y

98 identifies this as a professional office visit request rather than an inpatient or surgical review. Synthetic prior authorization data.

Where this trips people up

Because UM03 draws from the same code list as EQ01 on a 270 eligibility inquiry, teams sometimes assume the two are interchangeable and reuse eligibility test fixtures to build 278 test cases. The code values line up, but the review criteria a payer applies to a UM03 authorization request are not the same as the benefit lookup triggered by an EQ01 eligibility check, so borrowed fixtures can pass validation while never actually exercising the authorization logic they were meant to test.

X12 278 UM Segment Guide: Fields, Format, and Testing Gotchas
X12 278 Prior Authorization: Format, Fields, and Testing Guide
HIPAA 5010 Transaction Sets: Complete List and Reference
Test every service type your authorization workflow supports
Synthibase generates synthetic 278 requests spanning the full range of service type codes, purpose-built for prior authorization scenarios rather than repurposed eligibility fixtures.
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.