Segment

Disability

Contains disability information for a person, including the disability type, start and end dates, and return-to-work date. It can apply to patients, guarantors, or next of kin and appears in ADT messages. It is used by case management, workers' compensation, and occupational health systems.

8fields

1required

v2.9HL7 version

from zato.hl7v2 import DB1

db1 = DB1()
db1.set_id_db1 = '1'
db1.disabled_person_code = 'PT'
db1.disabled_indicator = 'Y'
db1.disability_start_date = '20260101'

Python examples

Build DB1 segments in Python

How to construct and work with real-world DB1 segments.

Accommodation support record

Records a patient accommodation entry with the person code, active indicator, and the effective start date for benefits coordination

from zato.hl7v2.v2_9 import DB1
from zato.hl7v2.v2_9 import CWE

db1 = DB1()
db1.set_id_db1 = '1'
db1.disabled_person_code = CWE(
    identifier='PT',
    text='Patient',
    name_of_coding_system='HL70334'
)
db1.disability_indicator = 'Y'
db1.disability_start_date = '20240115'

Completed accommodation period

Shows a closed accommodation record with start date, end date, and the return-to-activity date after a successful recovery

from zato.hl7v2.v2_9 import DB1
from zato.hl7v2.v2_9 import CWE

db1 = DB1()
db1.set_id_db1 = '1'
db1.disabled_person_code = CWE(
    identifier='PT',
    text='Patient',
    name_of_coding_system='HL70334'
)
db1.disability_indicator = 'Y'
db1.disability_start_date = '20240201'
db1.disability_end_date = '20240501'
db1.disability_return_to_work_date = '20240515'

Associated party accommodation

Accommodation record for an associated party, identified by a facility-issued CX identifier, with the effective dates for benefits processing

from zato.hl7v2.v2_9 import DB1
from zato.hl7v2.v2_9 import CWE, CX

db1 = DB1()
db1.set_id_db1 = '1'
db1.disabled_person_code = CWE(
    identifier='AP',
    text='Associated Party',
    name_of_coding_system='HL70334'
)
db1.disabled_person_identifier = CX(
    id_number='12345',
    assigning_authority='HOSP',
    identifier_type_code='PI'
)
db1.disability_indicator = 'Y'
db1.disability_start_date = '20240301'
db1.disability_unable_to_work_date = '20240301'

Tutorials

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

MLLP

Receive and parse HL7 v2 messages

Set up an MLLP channel, parse incoming messages, and respond with acknowledgments.

Start tutorial Build

Build and send HL7 v2 messages

Construct HL7 v2 messages from scratch using typed segment classes and send them over MLLP.

Start tutorial

FAQ

Frequently asked questions

DB1 carries accommodation and support details - the type of person involved, an indicator flag, and dates for start, end, and return to work. It appears in ADT and benefits-enrollment messages to coordinate workplace support and benefits processing.

Create a DB1 segment and read its fields directly:

from zato.hl7v2.v2_9 import DB1

db1 = DB1()
db1.set_id_db1 = '1'
db1.disabled_person_code = 'PT'
db1.disabled_indicator = 'Y'
db1.disability_start_date = '20240101'
db1.disability_return_to_work_date = '20240402'

indicator = db1.disabled_indicator
start = db1.disability_start_date
return_date = db1.disability_return_to_work_date

The disabled_person_code field uses the CWE datatype with HL7 table 0334:

from zato.hl7v2.v2_9 import DB1, CWE

db1 = DB1()

# PT = Patient
db1.disabled_person_code = CWE(identifier='PT')

# AP = Associated Party
db1.disabled_person_code = CWE(identifier='AP')

Set the disability_return_to_work_date field with an HL7 DT value:

from zato.hl7v2.v2_9 import DB1

db1 = DB1()
db1.set_id_db1 = '1'
db1.disabled_person_code = 'PT'
db1.disabled_indicator = 'Y'
db1.disability_start_date = '20240115'
db1.disability_end_date = '20240401'
db1.disability_return_to_work_date = '20240402'

Create separate DB1 instances, each with its own set_id_db1:

from zato.hl7v2.v2_9 import DB1

db1_first = DB1()
db1_first.set_id_db1 = '1'
db1_first.disabled_person_code = 'PT'
db1_first.disabled_indicator = 'Y'
db1_first.disability_start_date = '20240101'

db1_second = DB1()
db1_second.set_id_db1 = '2'
db1_second.disabled_person_code = 'AP'
db1_second.disabled_indicator = 'Y'
db1_second.disability_start_date = '20240701'

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.

Reference

DB1 field reference

Complete list of fields in the DB1 segment, HL7 v2.9.

#	Python name	Datatype	Usage	Repeatable	Table
1	`set_id_db1`	`SI`	Required	No	-
2	▶`disabled_person_code`	`CWE`	Optional	No	`HL70334`
2.1	├`.identifier`	`ST`	Optional	No	-
2.2	├`.text`	`ST`	Optional	No	-
2.3	├`.name_of_coding_system`	`ID`	Optional	No	-
2.4	├`.alternate_identifier`	`ST`	Optional	No	-
2.5	├`.alternate_text`	`ST`	Optional	No	-
2.6	├`.name_of_alternate_coding_system`	`ID`	Optional	No	-
2.7	├`.coding_system_version_id`	`ST`	Optional	No	-
2.8	├`.alternate_coding_system_version_id`	`ST`	Optional	No	-
2.9	├`.original_text`	`ST`	Optional	No	-
2.10	├`.second_alternate_identifier`	`ST`	Optional	No	-
2.11	├`.second_alternate_text`	`ST`	Optional	No	-
2.12	├`.name_of_second_alternate_coding_system`	`ID`	Optional	No	-
2.13	├`.second_alternate_coding_system_version_id`	`ST`	Optional	No	-
2.14	├`.coding_system_oid`	`ST`	Optional	No	-
2.15	├`.value_set_oid`	`ST`	Optional	No	-
2.16	├`.value_set_version_id`	`DTM`	Optional	No	-
2.17	├`.alternate_coding_system_oid`	`ST`	Optional	No	-
2.18	├`.alternate_value_set_oid`	`ST`	Optional	No	-
2.19	├`.alternate_value_set_version_id`	`DTM`	Optional	No	-
2.20	├`.second_alternate_coding_system_oid`	`ST`	Optional	No	-
2.21	├`.second_alternate_value_set_oid`	`ST`	Optional	No	-
2.22	└`.second_alternate_value_set_version_id`	`DTM`	Optional	No	-
3	▶`disabled_person_identifier`	`CX`	Optional	Yes	-
3.1	├`.id_number`	`ST`	Optional	No	-
3.2	├`.identifier_check_digit`	`ST`	Optional	No	-
3.3	├`.check_digit_scheme`	`ID`	Optional	No	-
3.4	├`.assigning_authority`	`HD`	Optional	No	-
3.5	├`.identifier_type_code`	`ID`	Optional	No	-
3.6	├`.assigning_facility`	`HD`	Optional	No	-
3.7	├`.effective_date`	`DT`	Optional	No	-
3.8	├`.expiration_date`	`DT`	Optional	No	-
3.9	├`.assigning_jurisdiction`	`CWE`	Optional	No	-
3.10	├`.assigning_agency_or_department`	`CWE`	Optional	No	-
3.11	├`.security_check`	`ST`	Optional	No	-
3.12	└`.security_check_scheme`	`ID`	Optional	No	-
4	`disability_indicator`	`ID`	Optional	No	`HL70136`
5	`disability_start_date`	`DT`	Optional	No	-
6	`disability_end_date`	`DT`	Optional	No	-
7	`disability_return_to_work_date`	`DT`	Optional	No	-
8	`disability_unable_to_work_date`	`DT`	Optional	No	-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python