Previous Page TOC Index Next Page

7.7.2 CSP - clinical study phase segment

The CSP segment contains information on a patient’s status for a particular phase of the study. This segment is optional and is useful when a study has different evaluation intervals within it. (See Section 7.5.1.2, "phase of a clinical trial.") The CSP segment is implemented on a study-specific basis for messaging purposes. The fact that the patient has entered a phase of the study that represents a certain treatment approach may need to be messaged to other systems, like pharmacy, nursing, or order entry. It is also important to sponsors and data management centers for tracking patient progress through the study and monitoring the data schedule defined for each phase. It may subsume OBR and OBX segments that follow it to indicate that these data describe the phase.

Figure 7-15. CSP attributes

SEQ

LEN

DT

OPT

RP/#

TBL#

ITEM#

ELEMENT NAME

1

60

CE

R



01051

Study Phase ID

2

26

TS

R



01052

Date/time Study Phase Began

3

26

TS

O



01053

Date/time Study Phase Ended

4

60

CE

C



01054

Study Phase Evaluability

7.7.2.0 CSP field definitions

7.7.2.1 Study phase ID (CE) 01051

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>

Definition: This field identifies the phase of the study that a patient has entered. The set of codes will generally be developed for each clinical trial, although there are patterns that trials in particular disease or prevention categories may follow. The phase structure will be based on data collation and reporting needs for the study. It is an operational structure and need not be discussed in the clinical trial protocol documentation or even made known to patient care or data collection personnel. The coding system will usually be developed by the sponsor for multicentered clinical trials to standardize the receipt of automated data. Local codes could be added if an additional local message is desired. Otherwise, local coding conventions will be used. Example: 2^Init Rx, Crs 1^NCI T93-0807 Phases

7.7.2.2 Date/time study phase began (TS) 01052

Definition: This field contains the date the patient began this phase interval. The time is optional.

7.7.2.3 Date/time study phase ended (TS) 01053

Definition: This field contains the date the patient ended this phase interval.

7.7.2.4 Study phase evaluability (CE) 01054

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>

Definition: This field contains the disposition of the patient’s data for this phase interval for quality control and data analysis purposes. The set of codes will vary across clinical trials. An example answer set: Complete, Adverse Events Only, Outcome Only, None, Unknown.

Previous Page TOC Index Next Page