100% Offline Reference
278 (005010X217)
ASC X12 278 Prior Authorization & Utilization Management Hierarchy (005010X217)
With CMS Interoperability and Prior Authorization automation mandates accelerating 278 adoption, understanding its deep 6-level HL tree (20 → 21 → 22 → 23 → EV → SS) is critical for EHR and payer engineers.
Six-Level 278 HL Tree & UM / HCR Segments
| Loop | HL-03 Code | Role & Key Segments |
|---|---|---|
2000A / 2000B | 20 / 21 | Utilization Management Organization (UMO) & Requester (Provider). |
2000C / 2000D | 22 / 23 | Subscriber & Dependent Patient. |
2000E | EV (Patient Event) | UM (Health Care Services Review: HS/AR/SC), HCR (Action: A1 Certified in Total, A2 Partial, A3 Not Certified, A4 Pended + Prior Auth Number in REF*BB), HI Diagnoses. |
2000F | SS (Service) | SV1/SV2/SV3 requested procedure/revenue lines with service-level HCR approvals. |
Frequently Asked Engineering Questions
Where is the approved Prior Authorization Reference Number returned in a 278 response?
When HCR-01 indicates certification (such as A1 Certified in total), HCR-02 carries the Review Identification Number (Prior Auth Number), which is subsequently submitted on the outbound 837 claim in Loop 2300 REF*G1.
Inspect, Diff, Validate & Scrub This Payload Offline in Your JetBrains IDE
Never paste regulated healthcare PHI (837/835/271) or supply-chain payloads (850/ORDERS) into browser parsers. EdiPrism X12 EDIFACT runs 100% air-gapped inside IntelliJ IDEA, PyCharm, DataGrip, Rider, GoLand, and WebStorm with a free core tier and a 14-day [Pro] trial.