5.2.1.6.2 - Transform Sept. 6, 2010

Provide an EASY traversal from UML<>Ontology<>Metadata<>XSD<>API, depending on one's point of view and expertise.

Gap Analysis::Interface::028 - Easy Model View Traversal

multiMetamodelProjection,

Support importing data coded to one data element format and have the data transformed to another data element format.

Gap Analysis::Transform::090 - Data element format transformation

mapDataElementFormat,

Provide mapping / transformation support for ISO21090 data types

Gap Analysis::Transform::091 - ISO21090 data types

mapISO21090DataTypes,

Extend terminology development to new populations and missions, and do so in a collaborative fashion. For example, NICHD has launched an effort to begin standardizing terminology for the examination of the newborn using NCI’s tools and resources.

Gap Analysis::Transform::143 - Collaborative Terminology Development

collaborativeTerminologyDevelopment,

Support pre-coordinated and post-coordinated terminology.

Gap Analysis::Transform::162 - Support pre-coordinated and post-coordinated terminology

coordinatedTerminology,

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.

Semantic Infrastructure Requirements::Artifact Management::Artifact Lifecycle Management

mapDataElementFormat, mapISO21090DataTypes, collaborativeTerminologyDevelopment, coordinatedTerminology, controlTerminologies, multiMetamodelProjection,

Groups with existing data sets often want to know how they can map their existing data models (e.g. clinical trial schema) to data element definitions that have been published in caDSR.  They do not wish to transform their existing (potentially large) datasets into caDSR data element definitions. Their existing data models usually represent a significant investment, their data element definitions are sponsor driven, and researchers cannot easily change data elements that evolved from the (very expensive) research process.  Thus, end users (e.g., Cancer Researchers) want a way to describe the mappings between their trial specific information model(s) and caDSR data elements - both semantically and syntactically.  This relates to caDSR-6 in that harmonization involves mapping or aligning of information models.

Gap Analysis::caDSR::caDSR-1 - Map caDSR data elements to existing metadata models

multiMetamodelProjection,

Provide service interface for all query and retrieval functions for clinical systems such as: * Laboratory Information Systems (LIS) * Radiology/Imaging Systems (PACS) * Admit Discharge Transfer (ADT) * Radiation Oncology dosing systems * Pharmacy * Order Entry * Clinical Care * Patient History * Clinical Notes   These services provide the core information for basic functionality of caEHR.  caEHR does not provide these functional behaviors directly, but expects these systems to maintain standard interfaces based on HL7 V3 functional descriptions.  Metadata concerning the interface, and the interface objects should be accessible via the KM system.  In addition, the business service interfaces for the following: * Referrals * Document Exchange * Outcomes * Order Tracking

Gap Analysis::caEHR::caEHR 1 - Provide service interfaces for clinical systems

controlTerminologies,

Static models include a variety of models with different representations.

Semantic Infrastructure Requirements::Artifact Management::Static Models

qvtModel,