HL7 CM2 Clinical Study Schedule Master
HL7 field reference CM2 fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
CM2 describes study schedule timing, including when events are planned within a clinical-study protocol.
The standard describes CM2 this way: The Clinical Study Schedule Master (CM2) contains the information about the scheduled time points for study or phase-related treatment or evaluation events. The fact that a patient has data satisfying a scheduled time point is sent in the CSS segment, sequence 2. The CM2 segment describes the scheduled time points in general.
Clinical-study segments tie a message back to a trial, phase, schedule, subject registration, and protocol-specific events. They are not general observation notes; they support trial governance and reporting.
The useful data is usually the combination of study identifiers, phase identifiers, schedule timing, and subject status. Keep protocol codes and local study IDs aligned with the system that is managing the trial.
The v2.5.1 structures show CM2 in MFN_M06 - Clinical study with phases and schedules master file, MFN_M07 - Clinical study without phases but with schedules master file, MFR_M06 - Clinical study with phases and schedules master file, and MFR_M07 - Clinical study without phases but with schedules master file. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
CM2-1 is the sequence number for this CM2 segment within its repeating group. It keeps multiple CM2 lines in order; it is not the business identifier for the study workflow.
CM2-2 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
The generated panel links this to HL7 table 9999; many real interfaces narrow that list further, so follow the receiver's implementation guide.
CM2-3 is human-readable context. Keep it useful for display and troubleshooting, but do not hide required workflow logic here unless the implementation guide explicitly says the receiver parses it.
CM2-4 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
The generated panel links this to HL7 table 9999; many real interfaces narrow that list further, so follow the receiver's implementation guide.
Related links
- CM0 - Clinical Study Master
- CM1 - Clinical Study Phase Master
- CSR - Clinical Study Registration
- CSP - Clinical Study Phase
- CSS - Clinical Study Data Schedule Segment
- CTI - Clinical Trial Identification
- OBX - Observation/Result
- MFN_M06 - Clinical study with phases and schedules master file
- MFN_M07 - Clinical study without phases but with schedules master file
- MFR_M06 - Clinical study with phases and schedules master file