HL7 UB1 UB82
HL7 field reference UB1 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 |
|---|---|---|---|---|---|
| UB1.1 | Set ID - UB1 | No | No | SI | |
| UB1.2 | Blood Deductible (43) | No | No | NM | 0136 |
| UB1.3 | Blood Furnished-Pints Of (40) | No | No | NM | |
| UB1.4 | Blood Replaced-Pints (41) | No | No | NM | |
| UB1.5 | Blood Not Replaced-Pints(42) | No | No | NM | |
| UB1.6 | Co-Insurance Days (25) | No | No | NM | |
| UB1.7 | Condition Code (35-39) | No | Yes | IS | 0043 |
| UB1.8 | Covered Days - (23) | No | No | NM | |
| UB1.9 | Non Covered Days - (24) | No | No | NM | |
| UB1.10 | Value Amount & Code (46-49) | No | Yes | UVC | 0153 |
| UB1.11 | Number Of Grace Days (90) | No | No | NM | |
| UB1.12 | Special Program Indicator (44) | No | No | CE | 0348 |
| UB1.13 | PSRO/UR Approval Indicator (87) | No | No | CE | 0349 |
| UB1.14 | PSRO/UR Approved Stay-Fm (88) | No | No | DT | |
| UB1.15 | PSRO/UR Approved Stay-To (89) | No | No | DT | |
| UB1.16 | Occurrence (28-32) | No | Yes | OCD | 0350 |
| UB1.17 | Occurrence Span (33) | No | No | CE | 0351 |
| UB1.18 | Occur Span Start Date(33) | No | No | DT | |
| UB1.19 | Occur Span End Date (33) | No | No | DT | |
| UB1.20 | UB-82 Locator 2 | No | No | ST | |
| UB1.21 | UB-82 Locator 9 | No | No | ST | |
| UB1.22 | UB-82 Locator 27 | No | No | ST | |
| UB1.23 | UB-82 Locator 45 | No | No | ST |
UB1 carries older UB82 institutional billing data.
The standard describes UB1 this way: The UB1 segment contains data specific to the United States. Only billing/claims fields that do not exist in other HL7 defined segments appear in this segment. The codes listed as examples are not an exhaustive or current list.
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 UB1 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.
UB1-1 is the sequence number for this UB1 segment within its repeating group. It keeps multiple UB1 lines in order; it is not the business identifier for the billing workflow.
UB1-2 carries Blood Deductible (43) 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 0136; many real interfaces narrow that list further, so follow the receiver's implementation guide.
UB1-3 carries Blood Furnished-Pints Of (40) 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.
UB1-4 carries Blood Replaced-Pints (41) 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.
UB1-5 carries Blood Not Replaced-Pints(42) 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.
UB1-6 carries Co-Insurance Days (25) 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.
UB1-7 carries Condition Code (35-39) 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.
UB1-8 carries Covered Days - (23) 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.
UB1-9 carries Non Covered Days - (24) 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.
UB1-10 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
The generated panel links this to HL7 table 0153; many real interfaces narrow that list further, so follow the receiver's implementation guide.
UB1-11 is a count or total for this billing workflow. Make the counting rule explicit before using it for reconciliation, billing, or workflow limits.
UB1-12 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.
The coded value should follow HL7 table 0348 or the narrower table in the local profile.
UB1-13 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.
The coded value should follow HL7 table 0349 or the narrower table in the local profile.
UB1-14 carries PSRO/UR Approved Stay-Fm (88) 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.
UB1-15 carries PSRO/UR Approved Stay-To (89) 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.
UB1-16 carries Occurrence (28-32) 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 0350; many real interfaces narrow that list further, so follow the receiver's implementation guide.
UB1-17 carries Occurrence Span (33) 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.
UB1-18 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.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
UB1-19 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.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
UB1-20 carries UB-82 Locator 2 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.
UB1-21 carries UB-82 Locator 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.
UB1-22 carries UB-82 Locator 27 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.
UB1-23 carries UB-82 Locator 45 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.