Carries cumulative dosage constraints for substances administered during a clinical study. Each instance specifies a maximum dosage limit and the time interval over which it applies, enabling study protocol enforcement and safety monitoring. It appears in clinical trial master file messages and is used by pharmacy and research systems to validate dosing against protocol-defined thresholds.
from zato.hl7v2 import CDO
cdo = CDO()
cdo.set_id_cdo = '1'
cdo.action_code = 'A'How to construct and work with real-world CDO segments.
Clinical study data object with a cumulative daily dosage limit for a trial substance
from zato.hl7v2.v2_9 import CDO
from zato.hl7v2.v2_9 import CQ
cdo = CDO()
cdo.set_id_cdo = '1'
cdo.action_code = 'A'
cdo.cumulative_dosage_limit = CQ(
quantity='500',
units='mg'
)
cdo.cumulative_dosage_limit_time_interval = CQ(
quantity='1',
units='d'
)Dosage constraint specifying a weekly cumulative ceiling for a study compound
from zato.hl7v2.v2_9 import CDO
from zato.hl7v2.v2_9 import CQ
cdo = CDO()
cdo.set_id_cdo = '2'
cdo.action_code = 'A'
cdo.cumulative_dosage_limit = CQ(
quantity='3500',
units='mg'
)
cdo.cumulative_dosage_limit_time_interval = CQ(
quantity='7',
units='d'
)Dosage limit update using micrograms and a monthly time interval
from zato.hl7v2.v2_9 import CDO
from zato.hl7v2.v2_9 import CQ
cdo = CDO()
cdo.set_id_cdo = '3'
cdo.action_code = 'U'
cdo.cumulative_dosage_limit = CQ(
quantity='250',
units='mcg'
)
cdo.cumulative_dosage_limit_time_interval = CQ(
quantity='30',
units='d'
)Step-by-step guides for working with HL7 v2 in Zato.
CDO carries cumulative dosage constraints for clinical study protocols. It specifies maximum dosage limits and the time intervals over which they apply, allowing pharmacy and research systems to enforce protocol safety thresholds.
The cumulative_dosage_limit field uses the CQ (composite quantity with units) datatype:
from zato.hl7v2.v2_9 import CDO, CQ
cdo = CDO()
cdo.cumulative_dosage_limit = CQ(
quantity='500',
units='mg'
)Use cumulative_dosage_limit_time_interval with a CQ datatype referencing HL7 table 0924:
from zato.hl7v2.v2_9 import CDO, CQ
cdo = CDO()
cdo.cumulative_dosage_limit_time_interval = CQ(
quantity='7',
units='d'
)The action_code field accepts standard master file action codes: A (add), D (delete), and U (update):
from zato.hl7v2.v2_9 import CDO
cdo = CDO()
cdo.set_id_cdo = '1'
# A = Add a new record
cdo.action_code = 'A'
# U = Update existing record
cdo.action_code = 'U'
# D = Delete existing record
cdo.action_code = 'D'Set both the dosage limit and the time interval together to define a complete constraint:
from zato.hl7v2.v2_9 import CDO, CQ
cdo = CDO()
cdo.set_id_cdo = '1'
cdo.action_code = 'A'
cdo.cumulative_dosage_limit = CQ(
quantity='1000',
units='mg'
)
cdo.cumulative_dosage_limit_time_interval = CQ(
quantity='14',
units='d'
)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.
Complete list of fields in the CDO segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | set_id_cdo | SI | Optional | No | - |
| 2 | action_code | ID | Optional | No | - |
| 3 | cumulative_dosage_limit | CQ | Optional | No | - |
| 4 | cumulative_dosage_limit_time_interval | CQ | Optional | No | HL70924 |
Get started with Zato and connect your systems in minutes.