Use Case Number

Otherhm2.pm13.3

Brief Description

In data collections forms, sometimes it is important to define a default value for a CDE.  This improves accuracy and can make some forms quicker to fill out.  When combined with non-editable CDEs, this provides a forms author a way to enter a constant into a form.

Actor(s) for this particular use case

Metadata Specialist, Clinical Researcher

Pre-condition
The state of the system before the user interacts with it

None.

Post condition
The state of the system after the user interacts with it

Data is collected with default values in CDEs

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1. The Metadata Specialist selects and defines a set of CDEs for use within a data collection form
2. The Metadata Specialist associates default values for specific CDEs.
3. The Metadata Specialist deploys the form for data collection.
4. The Clinical Researcher captures data using the form
5. When default value CDEs are reached within the form, the value is pre-entered for the Clinical Researcher
6. The Clinical Researcher can change the value if he desires

Alternate Flow
Things which would prevent the normal flow of the use case

When the value for a CDE is defined as a set of possible values, the default value must be selected from the value set and is automatically selected for the Clinical Researcher when editing the form.

Priority
The priority of implementing the use case: High, Medium or Low

High.

Associated Links
The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.

• Otherhm2 - Conditional CDEs
• Init1pm9 - Automate
• Conditional CDEs

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

None.

Use Case Number

Otherhm2.pm13.4

Brief Description

In data collections forms, it is possible that the value of a CDE is derived from the values of other CDEs.  For example, an Address CDE may be derived from a set of CDEs for Street, ZipCode, City, and State.  A derived CDE is often combined with the non-editable flag so that, when presented in a form, the user does not directly edit the value because it is composed from other values.

Actor(s) for this particular use case

Metadata Specialist, Clinical Researcher

Pre-condition
The state of the system before the user interacts with it

None.

Post condition
The state of the system after the user interacts with it

Data is collected for a derived CDEs

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1. The Metadata Specialist selects and defines a set of CDEs for use within a data collection form
2. The Metadata Specialist selects and marks a CDE as derived
3. The Metadata Specialist selects the CDEs from which the CDE is derived
4. The Metadata Specialist deploys the form for data collection.
5. The Clinical Researcher captures data using the form
6. Once the CDEs that are being used to derive a value are filled in, the derived CDE value can be evaluated

Alternate Flow
Things which would prevent the normal flow of the use case

None.

Priority
The priority of implementing the use case: High, Medium or Low

High.

Associated Links
The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.

• Otherhm2 - Conditional CDEs
• Init1pm9 - Automate
• Conditional CDEs

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

None.

Use Case Number

Otherhm2.pm13.5

Brief Description

In data collections forms, sometimes it is important to define a set of CDEs that must be asked completely in a certain order.  The question and answer pattern within the module itself has semantic meaning, and, if broken, is invalidated.  A module it sometimes combined with the non-editable flag to indicate that it cannot be altered.

Actor(s) for this particular use case

Metadata Specialist, Clinical Researcher

Pre-condition
The state of the system before the user interacts with it

None.

Post condition
The state of the system after the user interacts with it

Data is collected for the modules of a form

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1. The Metadata Specialist selects and defines a set of CDEs for use within a data collection form
2. The Metadata Specialist selects a subset of CDEs to be contained within a module
3. The Metadata Specialist deploys the form for data collection.
4. The Clinical Researcher captures data using the form
5. When a module is reached, all questions must be answered in the pattern described by the module
6. If the module is not completed as specified, no values are captured for it

Alternate Flow
Things which would prevent the normal flow of the use case

None.

Priority
The priority of implementing the use case: High, Medium or Low

High.

Associated Links
The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.

• Otherhm2 - Conditional CDEs
• Init1pm9 - Automate
• Conditional CDEs

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

None.