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

Init1pm16.2

Brief Description

A key aspect of ISO 21090 datatypes is that they can be localized for use within a specific information model.  The datatypes themselves define a number of optional attributes and associations, and the actual behavior of the datatypes in some cases can be modified.  Specifically, ISO 21090 has two types of conformance: Direct Conformance and Indirect Conformance.  Indirect conformance is defined as:

• Provide mappings between internal datatypes and the healthcare datatypes
• Specify for which of the datatypes an inward mapping is provided, for which an outward mapping is provided, and for which no mapping is providedThis use case describes the steps that an Information Modeler takes to localize the datatypes in alignment of Indirect Conformance.
  

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 have been imported in the model (see use Init1pm16.1 above)

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

The ISO 21090 datatypes have been localized within the Information Modeler's information model (in UML).  By value of having imported the datatypes from the metadata repository and following ONLY the below steps, the resulting localized ISO 21090 datatypes are in Indirect Conformance with the specification.

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

1. The Information Modeler localizes enumerations
   1. The Information Modeler specifies which enumerations are omitted
   2. The Information Modeler specifies which enumerated values are omitted
2. The Information Modeler localizes classes (types)
   1. The Information Modeler specifies which attributes are omitted
   2. The Information Modeler specifies which classes (types) are omitted
3. The Information Modeler annotates any special considerations, rules, mappings, etc.

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

The steps above do not preclude the creation of ECCF documents or other mappings/specification documents.  However, this use case does ease the creation of such documents because the ISO 21090 datatypes are derived directly from the metadata repository (meaning they have the appropriate level of specification/documentation already) and the localizations are made in conformance with the metadata repository conventions.

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? 

1.
2.. The datatatypes should be localized using the conventions of the UML modeling tool.  That is, it is highly desirable that user actions be constrained by what will be conformant when the localized datatypes are registered and shared.
It is absolutely critical that the resulting localized datatypes be in conformance with the conformance metrics defined in the ISO 21090 specification.