HL7 DB1 Disability
HL7 field reference DB1 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 |
|---|---|---|---|---|---|
| DB1.1 | Set ID - DB1 | Yes | No | SI | |
| DB1.2 | Disabled Person Code | No | No | IS | 0334 |
| DB1.3 | Disabled Person Identifier | No | Yes | CX | |
| DB1.4 | Disabled Indicator | No | No | ID | 0136 |
| DB1.5 | Disability Start Date | No | No | DT | |
| DB1.6 | Disability End Date | No | No | DT | |
| DB1.7 | Disability Return to Work Date | No | No | DT | |
| DB1.8 | Disability Unable to Work Date | No | No | DT |
DB1 records disability information for patient administration, reporting, eligibility, or billing workflows.
The standard describes DB1 this way: The disability segment contains information related to the disability of a person. This segment was created instead of adding disability attributes to each segment that contains a person (to which disability may apply). This is an optional segment that can be used to send disability information about a person already defined by the Patient Administration Chapter. The disabled person code and identifier allow for the association of the disability information to the person.
Patient-administration segments add detail around the person, visit, account, diagnosis, procedure, insurance, merge, death, disability, and grouping state carried by the message.
These fields often drive matching, billing, encounter routing, reporting, and front-desk workflow. Separate patient identity, visit identity, account identity, and clinical facts carefully.
The v2.5.1 structures show DB1 in ADR_A19 - Patient query, ADT_A01 - Admit/visit notification, ADT_A02 - Transfer a patient, and ADT_A03 - Discharge/end visit, and 16 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.
DB1-1 is the sequence number for this DB1 segment within its repeating group. It keeps multiple DB1 lines in order; it is not the business identifier for the patient-administration workflow.
DB1-2 identifies the Disabled Person Code for this patient-administration 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.
The generated panel links this to HL7 table 0334; many real interfaces narrow that list further, so follow the receiver's implementation guide.
DB1-3 identifies the Disabled Person Identifier for this patient-administration 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.
DB1-4 tells the receiver the state of this patient-administration 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 0136 or the narrower table in the local profile.
DB1-5 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.
DB1-6 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.
DB1-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.
DB1-8 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.
Related links
- PID - Patient Identification
- PD1 - Patient Additional Demographic
- PV1 - Patient Visit
- PV2 - Patient Visit - Additional Information
- DG1 - Diagnosis
- DRG - Diagnosis Related Group
- PR1 - Procedures
- IN1 - Insurance
- IN2 - Insurance Additional Information
- IN3 - Insurance Additional Information, Certification