Init1pm16.1 - 21090 Datatype Support - Import Datatypes
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 |
ISO 21090 datatypes are registered in a metadata repository |
Post condition |
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:
|
Steps to take |
|
Alternate Flow |
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 |
High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
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. |
Init1pm16.2 - 21090 Datatype Support - Localize Datatypes
Use Case Number |
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:
|
Actor(s) for this particular use case |
Information Modeler |
Pre-condition |
ISO 21090 datatypes have been imported in the model (see use Init1pm16.1 above) |
Post condition |
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 |
|
Alternate Flow |
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 |
High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
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. |
Init1pm16.3 - 21090 Datatype Support - Generate XML Mapping
Use Case Number |
Init1pm16.3 |
Brief Description |
In addition to providing a platform independent UML representation of healthcare datatypes, ISO 21090 defines an XML binding of those datatypes to be used when exchanging data between physical systems. Specifically, ISO 21090 requires the following for Indirect Conformance:
|
Actor(s) for this particular use case |
Information Modeler |
Pre-condition |
The ISO 21090 datatypes have been localized in the Information Modelers UML modeling tool using the necessary metadata repository conventions. |
Post condition |
An XML Schema and mapping guide are generated. |
Steps to take |
|
Alternate Flow |
The Information Modeler manually creates XML Schema, a mapping document, and annotates the model accordingly with the UML-to-XML Schema mapping information. |
Priority |
High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
|
Init1pm16.4 - 21090 Datatype Support - Register Datatypes
Use Case Number |
Init1pm16.4 |
Brief Description |
caBIG compability and ECCF require that semantic metadata be registered and advertised in order to facilitate interoperability. This use case describes the process by which an Information Modeler takes his localized, XML Schema mapped model to the centralized metadata repository. |
Actor(s) for this particular use case |
Information Modeler |
Pre-condition |
A localized ISO 21090 model exists in the Information Modeler's UML modeling tool with all required annotations to be registered, including XML Mappings. |
Post condition |
The information model is registered and available in the metadata repository. |
Steps to take |
|
Alternate Flow |
None. |
Priority |
High |
Associated Links |
|
Fit criterion/Acceptance Criterion |
The entire information model should be registered, including the localized ISO 21090 datatypes and XML Schema mappings. It should be obvious from which vanilla ISO 21090 datatypes the localized data are derived. |
Init1pm16.5 - 21090 Datatype Support - Interoperate on Datatypes
Use Case Number |
Init1pm16.5 |
Brief Description |
The true test of whether the semantic infrastructure is handling ISO 21090 requirements is that it is possible to:
|
Actor(s) for this particular use case |
System Architect |
Pre-condition |
Two or more systems have correctly imported, localized, generated XML Schema, and registered information models with ISO 21090 datatypes. Furthermore, these information models are implemented by real systems with ECCF compliant APIs. |
Post condition |
Touch points are discovered and data is successfully exchanged. |
Steps to take |
|
Alternate Flow |
|
Priority |
None. |
Associated Links |
|
Fit criterion/Acceptance Criterion |
The documentation and semantic metadata should be sufficient information to determine the mechanism by which data can be exchanged between systems. |