NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

View Functional Profile

Information visualization.

A common complaint across the stakeholders was that there are too many User Interfaces (UIs), they are hard to use, and the associated workflow / governance processes take too long and are too complex.

Just about all the stakeholders want user and domain specific user interfaces that are easy to use. This was mentioned by caDSR, CDISC, HL7 CIC, EVS, and caEHR stakeholders.

Requirements include;

  • 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:

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

integratedDevelopmentEnvironment

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.

clinicianFriendlyBrowser

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

scientistFriendlyRegistration

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)

umlDiagramModel

Show UML model graphics

modelNavigator

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.

ontologyEngineeringTool

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

informationModeling

Create tools to facilitate authoring of information models

developerFriendlyModelBrowser

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

  • No labels