Associates a specific order or observation with a clinical trial by carrying the study sponsor's identifier, study identifier, and time point. It is included alongside ORC and OBR segments in order and result messages so that downstream systems can tag orders and results as trial-related for proper blinding, billing, and regulatory tracking.
from zato.hl7v2.v2_9 import CTI
from zato.hl7v2.v2_9 import EI, CWE
cti = CTI()
sponsor_id = EI(entity_identifier='WELL2024001')
cti.sponsor_study_id = sponsor_id
cti.study_phase_identifier = CWE(
identifier='BASELINE',
text='Baseline Assessment'
)How to construct and work with real-world CTI segments.
Linking order to fitness research study
from zato.hl7v2.v2_9 import CTI
from zato.hl7v2.v2_9 import EI, CWE
cti = CTI()
cti.sponsor_study_id = EI(entity_identifier='WELL2024001')
cti.study_phase_identifier = CWE(
identifier='BASELINE',
text='Baseline Assessment'
)
cti.study_scheduled_time_point = CWE(
identifier='WEEK0',
text='Initial Visit'
)Linking result to dietary research study
from zato.hl7v2.v2_9 import CTI
from zato.hl7v2.v2_9 import EI, CWE
cti = CTI()
cti.sponsor_study_id = EI(entity_identifier='NUT2024002')
cti.study_phase_identifier = CWE(
identifier='INTERV',
text='Intervention Phase'
)
cti.study_scheduled_time_point = CWE(
identifier='WEEK4',
text='Week 4 Assessment'
)Linking follow-up to screening study
from zato.hl7v2.v2_9 import CTI
from zato.hl7v2.v2_9 import EI, CWE
cti = CTI()
cti.sponsor_study_id = EI(entity_identifier='PREV2024003')
cti.study_phase_identifier = CWE(
identifier='FOLLOWUP',
text='Follow-up Phase'
)
cti.study_scheduled_time_point = CWE(
identifier='WEEK12',
text='Week 12 Follow-up'
)Step-by-step guides for working with HL7 v2 in Zato.
CTI contains clinical trial identification information to link orders and results to specific wellness research studies, phases, and time points.
Use sponsor_study_id to identify the study:
cti.sponsor_study_id = EI(entity_identifier='WELL2024001')CTI follows OBR segments to link observation requests to specific wellness research studies. This enables tracking of study-related orders and results.
Yes, use study_phase_identifier for the study phase and study_scheduled_time_point for the specific assessment time point within that phase.
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 CTI segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | sponsor_study_id | EI | Required | No | - |
| 2 | study_phase_identifier | CWE | Optional | No | - |
| 3 | study_scheduled_time_point | CWE | Optional | No | HL70595 |
| 4 | action_code | ID | Optional | No | - |
Get started with Zato and connect your systems in minutes.