Defines a single phase within a clinical study identified by the preceding CM0, carrying the phase identifier and description. It is used in MFN messages to communicate the structure of multi-phase clinical trials between clinical trials management systems and participating institutional systems.
from zato.hl7v2.v2_9 import CM1
from zato.hl7v2.v2_9 import CWE
cm1 = CM1()
cm1.set_id_cm1 = '1'
cm1.study_phase_identifier = CWE(
identifier='ENROLL',
text='Enrollment',
name_of_coding_system='WELLPHASE',
)
cm1.description_of_study_phase = 'Welcome and orientation week'How to construct and work with real-world CM1 segments.
Sequence 1 with CWE phase code and onboarding description
from zato.hl7v2.v2_9 import CM1
from zato.hl7v2.v2_9 import CWE
cm1 = CM1()
cm1.set_id_cm1 = '1'
cm1.study_phase_identifier = CWE(
identifier='ENROLL',
text='Enrollment',
name_of_coding_system='WELLPHASE',
)
cm1.description_of_study_phase = 'Welcome and orientation week'Phase 2 highlighting coaching and scheduled fitness sessions
from zato.hl7v2.v2_9 import CM1
from zato.hl7v2.v2_9 import CWE
cm1 = CM1()
cm1.set_id_cm1 = '2'
cm1.study_phase_identifier = CWE(
identifier='ACTIVE',
text='Active participation',
name_of_coding_system='WELLPHASE',
)
cm1.description_of_study_phase = 'Coached workouts and nutrition workshops'Closing segment with screening review and goal check-in
from zato.hl7v2.v2_9 import CM1
from zato.hl7v2.v2_9 import CWE
cm1 = CM1()
cm1.set_id_cm1 = '3'
cm1.study_phase_identifier = CWE(
identifier='FOLLOW',
text='Follow-up assessment',
name_of_coding_system='WELLPHASE',
)
cm1.description_of_study_phase = 'Health screening review and goal review'Step-by-step guides for working with HL7 v2 in Zato.
CM0 names the overall study or program, CM1 defines each phase label, and CM2 maps scheduled milestones to events so wellness timelines stay coherent in master-file traffic.
Yes—populate identifier and text for humans, and name_of_coding_system when you rely on a private catalog such as WELLPHASE for program phases.
Build CWE with your phase code and vocabulary tag:
from zato.hl7v2.v2_9 import CM1
from zato.hl7v2.v2_9 import CWE
cm1 = CM1()
cm1.study_phase_identifier = CWE(
identifier='ENROLL',
text='Enrollment',
name_of_coding_system='WELLPHASE',
)SI ordering helps receivers sort repeating CM1 rows inside a message, for example when a program publishes three wellness phases in one batch.
ST accepts a single string; keep prose concise in the wire format and move lengthy coaching notes to NTE segments if your profile allows.
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 CM1 segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | set_id_cm1 | SI | Required | No | - |
| 2 | study_phase_identifier | CWE | Required | No | - |
| 3 | description_of_study_phase | ST | Required | No | - |
Get started with Zato and connect your systems in minutes.