HL7 UB2 UB92 Data
HL7 field reference UB2 fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| UB2.1 | Set ID - UB2 | No | No | SI | |
| UB2.2 | Co-Insurance Days (9) | No | No | ST | |
| UB2.3 | Condition Code (24-30) | No | Yes | IS | 0043 |
| UB2.4 | Covered Days (7) | No | No | ST | |
| UB2.5 | Non-Covered Days (8) | No | No | ST | |
| UB2.6 | Value Amount & Code | No | Yes | UVC | 0153 |
| UB2.7 | Occurrence Code & Date (32-35) | No | Yes | OCD | 0350 |
| UB2.8 | Occurrence Span Code/Dates (36) | No | Yes | OSP | 0351 |
| UB2.9 | UB92 Locator 2 (State) | No | Yes | ST | |
| UB2.10 | UB92 Locator 11 (State) | No | Yes | ST | |
| UB2.11 | UB92 Locator 31 (National) | No | No | ST | |
| UB2.12 | Document Control Number | No | Yes | ST | |
| UB2.13 | UB92 Locator 49 (National) | No | Yes | ST | |
| UB2.14 | UB92 Locator 56 (State) | No | Yes | ST | |
| UB2.15 | UB92 Locator 57 (National) | No | No | ST | |
| UB2.16 | UB92 Locator 78 (State) | No | Yes | ST | |
| UB2.17 | Special Visit Count | No | No | NM |
UB2 carries UB92 institutional billing data.
The standard describes UB2 this way: The UB2 segment contains data necessary to complete UB92 bills specific to the United States. Only Uniform Billing fields that do not exist in other HL7 defined segments appear in this segment. For example, Patient Name and Date of Birth are required; they are included in the PID segment and therefore do not appear here. Uniform Billing field locators are provided in parentheses ( ). The UB codes listed as examples are not an exhaustive or current list; refer to a UB specification for additional information.
Billing segments are where clinical activity starts turning into charge, reimbursement, and account data. They can look administrative, but a bad code or account reference can cause real downstream cleanup.
Treat charge codes, revenue codes, grouping values, effective dates, and account identifiers as controlled data. Free-text labels are useful for humans, but receivers usually post, price, or group from the coded values.
The v2.5.1 structures show UB2 in ADR_A19 - Patient query, ADT_A01 - Admit/visit notification, ADT_A05 - Pre-admit a patient, and ADT_A06 - Change an outpatient to an inpatient, and 2 other message structures. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
UB2-1 is the sequence number for this UB2 segment within its repeating group. It keeps multiple UB2 lines in order; it is not the business identifier for the billing workflow.
UB2-2 carries Co-Insurance Days (9) for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
UB2-3 carries Condition Code (24-30) for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0043; many real interfaces narrow that list further, so follow the receiver's implementation guide.
UB2-4 carries Covered Days (7) for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
UB2-5 carries Non-Covered Days (8) for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
UB2-6 identifies the Value Amount & Code for this billing workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
UB2-7 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
The generated panel links this to HL7 table 0350; many real interfaces narrow that list further, so follow the receiver's implementation guide.
UB2-8 carries Occurrence Span Code/Dates (36) for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0351; many real interfaces narrow that list further, so follow the receiver's implementation guide.
UB2-9 tells the receiver the state of this billing workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
UB2-10 tells the receiver the state of this billing workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
UB2-11 carries UB92 Locator 31 (National) for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
UB2-12 identifies the Document Control Number for this billing workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
UB2-13 carries UB92 Locator 49 (National) for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
UB2-14 tells the receiver the state of this billing workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
UB2-15 carries UB92 Locator 57 (National) for this billing workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
UB2-16 tells the receiver the state of this billing workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
UB2-17 is used for reconciliation. The receiver may compare it with the segments, batches, messages, rows, or items actually received, so do not populate it from a stale estimate.