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:

• Discover healthcare touchpoints between systems that localize ISO 21090 in different ways
• Programmatically interoperate between these systems

Actor(s) for this particular use case

System Architect
Software Engineer

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

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
The state of the system after the user interacts with it

Touch points are discovered and data is successfully exchanged.

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 System Architect uses the metadata browser to identify two or more systems with the same ISO 21090 datatypes localized in different ways.
2. The System Architect documents a data exchange scenario
3. The Software Engineer uses the metadata, ECCF artifacts, and caBIG compliant APIs to exchange data from one system to another.

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

Medium None.

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 documentation and semantic metadata should be sufficient information to determine the mechanism by which data can be exchanged between systems.

Use Case Number

Init1pm16.6

Brief Description

ISO 21090 data types have a specific encoding scheme that is significantly different than what has been used thus far in caBIG services.  Rather than reengineering existing services entirely, it may be desirable to have a common translation service interface and implementation toolkit that can be used to "wrap" existing non-compliant services.

Actor(s) for this particular use case

Software Engineer

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

One or more services exist that expose datatypes that are not ISO 21090 compliant.

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

A new service is implemented that exposes the same semantics but with ISO 21090 datatypes.

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 Software Engineer enters a service into the toolkit for remapping
2. The Software Engineer uses the toolkit provided to create mappings from the original datatypes to the ISO 21090 datatypes with minimal coding
3. The Software Engineer generates the new information model automatically and registers it
4. The Software Engineer deploys the new and (if necessary) old service

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

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.

Init1bes12 - Mapping_transformation support for ISO21090 data types

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

As little coding as possible should be required.