Defines the timing of clinical study data collection events, such as a scheduled lab draw or assessment at a specific study milestone. It communicates the scheduled time point and the actual date the data was collected, linking clinical observations to the study protocol timeline. Used to coordinate data collection between clinical trial management systems and clinical or laboratory systems.
from zato.hl7v2.v2_9 import CSS
from zato.hl7v2.v2_9 import CWE, DTM
css = CSS()
css.study_scheduled_time_point = CWE(
identifier='WEEK4',
text='Week 4 Assessment'
)
css.study_scheduled_patient_time_point = DTM('20260215')How to construct and work with real-world CSS segments.
Scheduled wellness assessment at week 4
from zato.hl7v2.v2_9 import CSS
from zato.hl7v2.v2_9 import CWE, DTM
css = CSS()
css.study_scheduled_time_point = CWE(
identifier='WEEK4',
text='Week 4 Assessment'
)
css.study_scheduled_patient_time_point = DTM('20240215')
css.study_quality_control_codes = CWE(
identifier='COMPLETE',
text='Data collection complete'
)Scheduled follow-up assessment at week 8
from zato.hl7v2.v2_9 import CSS
from zato.hl7v2.v2_9 import CWE, DTM
css = CSS()
css.study_scheduled_time_point = CWE(
identifier='WEEK8',
text='Week 8 Follow-up'
)
css.study_scheduled_patient_time_point = DTM('20240315')
css.study_quality_control_codes = CWE(
identifier='PENDING',
text='Data collection pending'
)Scheduled final wellness assessment
from zato.hl7v2.v2_9 import CSS
from zato.hl7v2.v2_9 import CWE, DTM
css = CSS()
css.study_scheduled_time_point = CWE(
identifier='FINAL',
text='Final Assessment'
)
css.study_scheduled_patient_time_point = DTM('20240515')
css.study_quality_control_codes = CWE(
identifier='SCHEDULED',
text='Assessment scheduled'
)Step-by-step guides for working with HL7 v2 in Zato.
CSS contains clinical study data schedule information including scheduled time points and data collection schedules for wellness research studies.
Use study_scheduled_time_point field with CWE datatype:
css.study_scheduled_time_point = CWE(
identifier='WEEK4',
text='Week 4 Assessment'
)CSP contains study phase information while CSS contains data collection schedules. Multiple CSS segments can exist within a study phase to track different assessment time points.
Use study_quality_control_codes to indicate data collection status such as COMPLETE, PENDING, or SCHEDULED for wellness assessments.
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 CSS segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | study_scheduled_time_point | CWE | Required | No | HL70595 |
| 2 | study_scheduled_patient_time_point | DTM | Optional | No | - |
| 3 | study_quality_control_codes | CWE | Optional | No | HL70596 |
Get started with Zato and connect your systems in minutes.