Use Case Number

Init1pm16.1

Brief Description

ISO 21090 defines a set of datatypes for reuse within healthcare applications.  When developing a new information model for sharing healthcare data, the first step is to choose a set of datatypes to "import" or "derive from".  Being able to select which datatypes you will reuse forms the basis of interoperating at the basic (datatype) level.

Actor(s) for this particular use case

Information Modeler

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

ISO 21090 datatypes are registered in a metadata repository

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

ISO 21090 datatypes are available within the Information Modeler's UML modeling tool.  This means that that the ISO 21090 datatypes have the following properties in the modeling tool:

• Available as the type for an attribute
• Represented fully as complex types (classes) with generalizations, attributes, and associations

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. Information Modeler opens modeling tool
2. Information Modeler searches metadata repository for ISO 21090 datatypes
3. Information Modeler imports ISO 21090 datatypes into his modeling tool

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

An alternate flow to this use case is that the Information Modeler imports datatypes from another information model (which may be localized rather than the vanilla ISO 21090 datatypes).  This is a highly desirable flow because it will greatly speed the adoption of ISO 21090 datatypes and interoperability.

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.

Init1pm16 - 21090 Datatype Support

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

The Information Modeler must be able to import datatypes into his UML modeling tool, these must be represented fully (so that they can be localized), and they must be able to be made the types of attributes within the information model itself.

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Brief Description

Actor(s) for this particular use case

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

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

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

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

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

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.

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

1.
2...

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Brief Description

Actor(s) for this particular use case

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

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

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

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

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

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.

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

1.
2...

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

n.n

Brief Description

Actor(s) for this particular use case

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

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

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

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

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

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.

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

1.
2...