Use Case Number

Otherhm2.pm13.1

Brief Description

In data collections forms, it is often important to enforce specific rules that determine which data elements are captured.  These rules are termed as "conditional" CDEs or "skip patterns".  For example, if male is selected for the gender CDE question, then the question about whether the patient is pregnant would be skipped.  More complex conditionals can be defined that require mathematical evaluation (less than, greater than), etc.

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 conditional steps.

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 skip patterns with specific CDEs, which defines the action to be taken (CDEs to be skipped) depending on the answer.
3. The Metadata Specialist deploys the form for data collection.
4. The Clinical Researcher captures data using the form
5. When conditional CDEs are reached within the form, the skip patterns are conditionally executed.

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?

The skip pattern must be associated with the CDE and optionally reusable.

Use Case Number

Otherhm2.pm13.2

Brief Description

In data collections forms, it is often important to enforce that some values are not editable. These data elements could have a default value, be derived from other data elements (such as age from date of birth), or be derived from other systems.

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 non-editable CDEs not captured from user input directly

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 non-editable details for specific CDEs.
3. The Metadata Specialist deploys the form for data collection.
4. The Clinical Researcher captures data using the form
5. When non-editable CDEs are reached within the form, the Clinical Researcher is unable to enter data for that field.

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.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

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.