Page History

...

Page info
title title

...

Summary

Description of the profile

Information visualization.

...

• Provide an integrated system of tools and one place to find everything out about a UML model/system (not different repositories: GME, CDE browser, UML model browser)
• Provide an integrated, web-based environment for model/service registration and browsing.
• Provide a Content Driven, clinician friendly browser that does not require extensive KR training, or for them to know meta-model structure or schema. This browser will envision an alphabetical, or category driven structure that surfaces the content for them, and allows them to view/browser content more easily.
• Provide an interface (e.g., wizard tool) so that a scientist that knows nothing of metadata, modeling, or the grid can register a new "thing" (data element or analytical service)
• Show UML model graphics
• Provide an EASY traversal from UML<>Ontology<>Metadata<>XSD<>API, depending on one's point of view and expertise.
• Provide a forms building tool that will express the structure of a form as well as the model elements to which form items are bound in order to describe the form definition (including the persistence model, behavior and structure) so that the definition could be consumed by any form rendering platform and effectively collect standard data.
• Provide means to reuse metadata content more easily, including XSD, forms, OC, DEC, VD, UML Classes, UML Models, etc. Need to have tooling to navigate and follow relationships to related metadata.
• Explore building a tool that "understands" the domain of an ontology engineer by asking Questions and seeking Answers, and in turn, assisting the ontology engineer in modeling her ontology
• Programmatic Access to LexEVS API
• Create interfaces with a low barrier of entry for end users
• Support Reusable Modules / Sections of Forms
• Create tools to facilitate authoring of information models
• Provide usable authoring, discovery, and management tools.
• Generate standards-based data collection forms
• Design Development Support
• Provide tools to support the building of data collection forms.
  

This Functional Profile includes, but is not limited to, the following capability elaborations:

• integratedDevelopmentEnvironment
• clinicianFriendlyBrowser
• scientistFriendlyRegistration
• umlDiagramModel
• modelNavigator
• ontologyEngineeringTool
• informationModeling
• developerFriendlyModelBrowser

Derived From Requirements

• Gap Analysis::Interface::001 - Unified Tool Set Provide an integrated system of tools and one place to find everything out about a UML model/system (not different repositories: GME, data element browser, UML model browser)
• Gap Analysis::Interface::021 - Clinician Friendely Browser Provide a Content Driven, clinician friendly browser that does not require extensive KR training, or for them to know meta-model structure or schema. This browser envisioned uses alphabetical, or category driven structure that surfaces the content for them, and allows them to view/browser content more easily.
• Gap Analysis::Interface::023 - Scientist Friendly Registration Provide an interface (e.g., wizard tool) so that a scientist that knows nothing of metadata, modeling, or the grid can register a new "thing" (data element or analytical service)
• Gap Analysis::Interface::027 - Show UML model graphics Show UML model graphics
• Gap Analysis::Interface::032 - Metadata Navigation and Reuse Provide means to reuse metadata content more easily, including XSD, forms, OC, DEC, VD, UML Classes, UML Models, etc. Need to have tooling to navigate and follow relationships to related metadata.
• Gap Analysis::Interface::106 - Ontology Modeling Explore building a tool that "understands" the domain of an ontology engineer by asking Questions and seeking Answers, and in turn, assisting the ontology engineer in modeling her ontology
• *Gap Analysis::Interface::135.1 - Create interfaces with a low barrier of entry for end users * Create interfaces with a low barrier of entry for end users
• Gap Analysis::Interface::156 - Information Model Authoring Create tools to facilitate authoring of information models
• Gap Analysis::Discover::160.2 - Model Search Provide a browser that will allow Information Specialist (developer) searching (discovering) and retrieval of corresponding model representations from single or multiple repositories.
• Semantic Infrastructure Requirements::Artifact Management::Artifact Lifecycle Management Artifact lifecycle management and metadata requirements include the ability to: * Manage lifecycle, governance and versioning of the models, content and forms * Establish relationships and dependencies between models, content and forms * Determine provenance, jurisdiction, authority and intellectual property * Create represention and views of the information, realized through the appropriate transforms * Provide access control and other security constraints * Create annotations for better discovery and searching of artifacts * Develop usage scenarios and context for the information * Provide terminology and value set binding The artifacts are bound to the services via the service metadata. The service metadata combined with the artifacts and supporting metadata provide a comprehensive service specification. The artifact management requirements listed above are derived from the following use cases: * caEHR: The caEHR project has adopted ECCF for specifications and CDA documents for interoperability. The caEHR project requirements include the need for an infrastructure for managing all the artifacts generated during specification process, including HL7 models and documents. The caEHR project also intends to publish these artifacts for the community and vendors. The infrastructure needs to support better discovery, making all the relevant information available in the right context. * ONC and other external EHR adopters: ONC has adopted CCD and CCR for meaningful use. All national EHR implementations are expected to support forms and the semantics of these forms play a critical role in interoperability. The semantic infrastructure must provide a mechanism to create, store and manage these forms. * Clinical Trials: Clinical trials use forms to capture clinical information, and the semantics captured by these forms are critical for interoperability and reporting. The semantic infrastructure must provide a mechanism to manage the lifecycle of these forms.
• Gap Analysis::caDSR::caDSR-4 - Provide usable authoring, discovery, and management tools The caDSR suite of tools are very difficult to use, this inhibits publishing and utilization of metadata by the community (caDSR-2). Tooling must allow novice users to effectively define, share, and find metadata definitions. These tools must also provide advanced functionality to experienced (power) users.   The caDSR/Clinical Trial tools should be directly usable by the end user (e.g., cancer researcher) and not limited to metadata specialists.  caDSR users generally do not start with a formal information model or use specific subject matter models.  They want to see tailored views of their local data elements and the caDSR data elements they are mapping to.  Functions such as grouping, matching, section grouping, and high-lighting are desired.  The tailorable views should indicate where the caDSR users are in this mapping process.  Currently, caDSR does not capture much, if any, associated metadata. The ability to document associations and make them caDSR model elements is a requirement.  In addition, those portions of caDSR 11179 Ed 2 or 11179 Ed 3 that are not to be supported by the proposed HL7 RIM-based technical approach should be identified *Source * * Interview 5/24/2010 Dianne Reeves
• Gap Analysis::caEHR::caEHR 4 - Design,Development Support The vision of caEHR and its reference implementation is one of these services based platform where the reference implementation consists of a flexible user interface development environment that obtains its UI objects from a service based on the presence of those artifacts in some model repository. This gives the flexibility for the reference implementation to change its behavior based on a service in the available models from a repository and divorces the knowledge that is rapidly changing and healthcare from the infrastructure which utilizes that knowledge. As such, the KR would be expected to provide references to those objects that make up specific UI interface elements such as a demographic object or laboratory object and to be able to bind the terminology references to these objects in order to supply the palette of objects to build a specific UI. The KR should collate these objects into specific packages that reflect disease specific or screen specific elements. There will also be a need to house the registry information that identifies specific instances of caEHR and its particular profile of objects used from the metadata repository. Since some elements for the caEHR implementations will be drawn from sources outside of NCI, it will not be possible to completely version an instance of a reference implementation. It will however be possible to version a set of objects pulled from the KR. The purpose of the KR in this particular instance is to provide consistent representations across the range of caEHR that get implemented and to promote reusability across these instances. Source * Cecil Lynch

...

Provide an integrated system of tools and one place to find everything out about a UML model/system (not different repositories: GME, data element browser, UML model browser)

Design Development Support

Provide usable authoring, discovery, and management tools.

...

Provide a Content Driven, clinician friendly browser that does not require extensive KR training, or for them to know meta-model structure or schema. This browser envisioned uses alphabetical, or category driven structure that surfaces the content for them, and allows them to view/browser content more easily.

Create interfaces with a low barrier of entry for end users

...

• An artifact is a managed resource within the Semantic Infrastructure.

An artifact is associated with the following capabilities:

• descriptions to enable the artifact to be visible, where the description includes a unique identifier for the artifact and a sufficient, and preferably a machine processible, representation of the meaning of terms used to describe the artifact, its functions, and its effects;
• one or more discovery mechanisms that enable searching for artifacts that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual artifact descriptions, possibly through some repository mechanism;
• accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.
  A well-defined service Behavior Model.

The capabilities of the Behavior Model include:

• characterizes the knowledge of the actions invokes against the service and events that report real world effects as a result of those actions;
• characterizes the temporal relationships and temporal properties of actions and events associated in a service interaction;
• describe activities involved in a workflow activity that represents a unit of work;
• describes the role(s) that a role player performs in a service-oriented business process or service-oriented business collaboration;
• is both human readable and machine processable;
• is referenceable from the Service Description artifact.
  Artifact descriptions change over time and their contents will reflect changing needs and context.

Architectural implications of change on the Semantic Infrastructure are reflected in the following capabilities:

• mechanisms to support the storage, referencing, and access to normative definitions of one or more versioning schemes that may be applied to identify different aggregations of descriptive information, where the different schemes may be versions of a versioning scheme itself;
• configuration management mechanisms to capture the contents of the each aggregation and apply a unique identifier in a manner consistent with an identified versioning scheme;
• one or more mechanisms to support the storage, referencing, and access to conversion relationships between versioning schemes, and the mechanisms to carry out such conversions.
  A well-defined service Information Model.

The capabilities of the Information Model include:

• describes the syntax and semantics of the messages used to denote actions and events;
• describes the syntax and semantics of the data payload(s) contained within messages;
• documents exception conditions in the event of faults due to network outages, improper message/data formats, etc.;
• is both human readable and machine processable
• is referenceable from the Service Description artifact.
  Artifact Descriptions make use of defined semantics, where the semantics may be used for categorization or providing other property and value information for description classes.

Architectural implications of semantics on the Semantic Infrastructure are reflected in the following capabilities:

• semantic models that provide normative descriptions of the utilized terms, where the models may range from a simple dictionary of terms to an ontology showing complex relationships and capable of supporting enhanced reasoning. This is a refinement of the Artifact metadata capability.
• mechanisms to support the storage, referencing, and access to these semantic models. This is a refinement of the Artifact store capability.
• configuration management mechanisms to capture the normative description of each semantic model and to apply a unique identifier in a manner consistent with an identified versioning scheme. This is a refinement of the Change configurationManagement capability.
• one or more mechanisms to support the storage, referencing, and access to conversion relationships between semantic models, and the mechanisms to carry out such conversions.

Capabilities

• action
• clinicianFriendlyBrowser
• configurationManagement
• developerFriendlyModelBrowser
• diagramModelBinding
• discovery
• exception
• identity
• informationModeling
• integratedDevelopmentEnvironment
• message
• metadata
• modelNavigator
• ontologyEngineeringTool
• participant
• payload
• provenance
• scientistFriendlyRegistration
• semanticConversion
• serviceBinding
• store
• temporal
• transition
• umlDiagramModel
• versioning
• workflow

Requirements traceability

Anchor
_16_5_1_24a0131_1283772588169_636221_5268 _16_5_1_24a0131_1283772588169_636221_5268

action

Description

characterizes the knowledge of the actions invokes against the service and events that report real world effects as a result of those actions;

Requirements addressed

• Interacting with Services Model

Overview of possible operations

Anchor
EAID_EAB9DEA1_BBD2_4df6_B349_3F961AFD2BBC EAID_EAB9DEA1_BBD2_4df6_B349_3F961AFD2BBC

clinicianFriendlyBrowser

Description

Provide a Content Driven, clinician friendly browser that does not require extensive KR training, or for them to know meta-model structure or schema. This browser envisioned uses alphabetical, or category driven structure that surfaces the content for them, and allows them to view/browser content more easily.

Create interfaces with a low barrier of entry for end users

Requirements addressed

• Artifact Lifecycle Management
• 021 - Clinician Friendely Browser
• 135.1 - Create interfaces with a low barrier of entry for end users

Overview of possible operations

Anchor
_16_5_1_24a0131_1283700133655_905377_3117 _16_5_1_24a0131_1283700133655_905377_3117

configurationManagement

Description

Mechanisms to support the storage, referencing, and access to normative definitions of one or more versioning schemes that may be applied to identify different aggregations of descriptive information, where the different schemes may be versions of a versioning scheme itself.

Requirements addressed

• Service Description Model

Overview of possible operations

Anchor
EAID_52650F86_8D78_4c3b_B56B_A0BBDF943594 EAID_52650F86_8D78_4c3b_B56B_A0BBDF943594

developerFriendlyModelBrowser

Description

Provide a browser that will allow Information Specialist (developer) searching (discovering) and retrieval of corresponding model representations from single or multiple repositories.

Requirements addressed

• 160.2 - Model Search

Overview of possible operations

Anchor
_16_5_1_24a0131_1283771708338_164073_5189 _16_5_1_24a0131_1283771708338_164073_5189

diagramModelBinding

Description

Is both human readable and machine processable.

Requirements addressed

• Interacting with Services Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283714222600_103266_4106 _16_5_1_24a0131_1283714222600_103266_4106

discovery

Description

One or more discovery mechanisms that enable searching for artifacts that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual artifact descriptions, possibly through some repository mechanism.

Requirements addressed

• Governance Model
• Service Description Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283771707561_426141_5167 _16_5_1_24a0131_1283771707561_426141_5167

exception

Description

Documents exception conditions in the event of faults due to network outages, improper message/data formats, etc.

Requirements addressed

• Interacting with Services Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283714222601_506267_4107 _16_5_1_24a0131_1283714222601_506267_4107

identity

Description

Descriptions which include a unique identifier for the artifact.

Requirements addressed

• Service Description Model
• Governance Model

Overview of possible operations

Anchor
EAID_A7667655_BAC3_4b31_A0C4_E9C9DF459B54 EAID_A7667655_BAC3_4b31_A0C4_E9C9DF459B54

informationModeling

Description

Create tools to facilitate authoring of information models

Requirements addressed

• Artifact Lifecycle Management
• 156 - Information Model Authoring

Overview of possible operations

Anchor
EAID_C8942C0B_A57F_4d95_8075_084D79B0158A EAID_C8942C0B_A57F_4d95_8075_084D79B0158A

integratedDevelopmentEnvironment

Description

Provide an integrated system of tools and one place to find everything out about a UML model/system (not different repositories: GME, data element browser, UML model browser)

Design Development Support

Provide usable authoring, discovery, and management tools.

Requirements addressed

• caDSR-4 - Provide usable authoring, discovery, and management tools
• Artifact Lifecycle Management
• 001 - Unified Tool Set
• caEHR 4 - Design,Development Support

Overview of possible operations

Anchor
_16_5_1_24a0131_1283771690875_660929_5145 _16_5_1_24a0131_1283771690875_660929_5145

message

Description

Describes the syntax and semantics of the messages used to denote actions and events

Requirements addressed

• Interacting with Services Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283714222603_853936_4108 _16_5_1_24a0131_1283714222603_853936_4108

metadata

Description

A representation of the meaning of terms used to describe the artifact, its functions, and its effects.

Requirements addressed

• Service Description Model
• Governance Model

Overview of possible operations

Anchor
EAID_2F7035D7_3545_465d_8F35_075009C7ED3F EAID_2F7035D7_3545_465d_8F35_075009C7ED3F

modelNavigator

Description

Provide means to reuse metadata content more easily, including XSD, forms, OC, DEC, VD, UML Classes, UML Models, etc. Need to have tooling to navigate and follow relationships to related metadata.

Requirements addressed

• 032 - Metadata Navigation and Reuse
• Artifact Lifecycle Management

Overview of possible operations

Anchor
EAID_928F6243_BF54_4069_9EDF_A672CBDF0F69 EAID_928F6243_BF54_4069_9EDF_A672CBDF0F69

ontologyEngineeringTool

Description

Explore building a tool that "understands" the domain of an ontology engineer by asking Questions and seeking Answers, and in turn, assisting the ontology engineer in modeling her ontology

Requirements addressed

• 106 - Ontology Modeling
• Artifact Lifecycle Management

Overview of possible operations

Anchor
_16_5_1_24a0131_1283772593723_513110_5301 _16_5_1_24a0131_1283772593723_513110_5301

participant

Description

describes the role(s) that a role player performs in a service-oriented business process or service-oriented business collaboration;

Requirements addressed

• Interacting with Services Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283771707107_214170_5156 _16_5_1_24a0131_1283771707107_214170_5156

payload

Description

Describes the syntax and semantics of the data payload(s) contained within messages

Requirements addressed

• Interacting with Services Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283793030699_512571_7056 _16_5_1_24a0131_1283793030699_512571_7056

provenance

Description

While the Resource identity provides the means to know which subject and subject description are being considered, Provenance as related to the Description class provides information that reflects on the quality or usability of the subject. Provenance specifically identifies the entity (human, defined role, organization, ...) that assumes responsibility for the resource being described and tracks historic information that establishes a context for understanding what the resource provides and how it has changed over time. Responsibilities may be directly assumed by the Stakeholder who owns a Resource or the Owner may designate Responsible Parties for the various aspects of maintaining the resource and provisioning it for use by others. There may be more than one entity identified under Responsible Parties; for example, one entity may be responsible for code maintenance while another is responsible for provisioning of the executable code. The historical aspects may also have multiple entries, such as when and how data was collected and when and how it was subsequently processed, and as with other elements of description, may provide links to other assets maintained by the Resource owner.

Requirements addressed

Overview of possible operations

Anchor
EAID_3E9745CA_B4AB_4f5b_9BC1_9AE62817BA96 EAID_3E9745CA_B4AB_4f5b_9BC1_9AE62817BA96

scientistFriendlyRegistration

Description

Provide an interface (e.g., wizard tool) so that a scientist that knows nothing of metadata, modeling, or the grid can register a new "thing" (data element or analytical service)

Requirements addressed

• Artifact Lifecycle Management
• 023 - Scientist Friendly Registration

Overview of possible operations

Anchor
_16_5_1_24a0131_1283765671415_826766_4835 _16_5_1_24a0131_1283765671415_826766_4835

semanticConversion

Description

One or more mechanisms to support the storage, referencing, and access to conversion relationships between semantic models, and the mechanisms to carry out such conversions.

Requirements addressed

• Service Description Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283771707949_635201_5178 _16_5_1_24a0131_1283771707949_635201_5178

serviceBinding

Description

Is referenceable from the Service Description artifact.

Requirements addressed

• Interacting with Services Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283714222609_981432_4109 _16_5_1_24a0131_1283714222609_981432_4109

store

Description

Accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.

Requirements addressed

• Governance Model
• Service Description Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283772592490_475793_5279 _16_5_1_24a0131_1283772592490_475793_5279

temporal

Description

characterizes the temporal relationships and temporal properties of actions and events associated in a service interaction;

Requirements addressed

• Interacting with Services Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283700246486_44421_3128 _16_5_1_24a0131_1283700246486_44421_3128

transition

Description

One or more mechanisms to support the storage, referencing, and access to conversion relationships between versioning schemes, and the mechanisms to carry out such conversions.

Requirements addressed

• Service Description Model

Overview of possible operations

Anchor
EAID_151F0AB1_2C78_4086_9882_BF2161AA4071 EAID_151F0AB1_2C78_4086_9882_BF2161AA4071

umlDiagramModel

Show UML model graphics

...

Provide means to reuse metadata content more easily, including XSD, forms, OC, DEC, VD, UML Classes, UML Models, etc. Need to have tooling to navigate and follow relationships to related metadata.

...

Explore building a tool that "understands" the domain of an ontology engineer by asking Questions and seeking Answers, and in turn, assisting the ontology engineer in modeling her ontology

...

Create tools to facilitate authoring of information models

...

Description

Show UML model graphics

Requirements addressed

• 027 - Show UML model graphics
• Artifact Lifecycle Management

Overview of possible operations

Anchor
_16_5_1_24a0131_1283699095521_961509_3106 _16_5_1_24a0131_1283699095521_961509_3106

versioning

Description

Configuration management mechanisms to capture the contents of the each aggregation and apply a unique identifier in a manner consistent with an identified versioning scheme.

Requirements addressed

• Service Description Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283772593164_377532_5290 _16_5_1_24a0131_1283772593164_377532_5290

workflow

Description

describe activities involved in a workflow activity that represents a unit of work;

Requirements addressed

• Interacting with Services Model

Overview of possible operations