5.2.1.2.2 - Reasoning Sept. 6, 2010

Identify data elements that should be harmonized with existing data elements that are semantically close

Gap Analysis::Transform::030 - Harmonization of semantically similar data elements

Provide mappings between similar data elements

Gap Analysis::Transform::058 - Provide mappings between similar data elements

Identify and "translate" data that is really identical, but has been assigned different datatypes.

Gap Analysis::Transform::101 - Cross-datatype equality check

Make it easy to expose XML-OWL transformations on the grid.

Gap Analysis::Transform::117.2 - OWL Transformations

Provide a mechanism to deal with overlap of terms from multiple vocabularies, the same term in different sources may or may not be identical in meaning and the system will need to "merge" views of identical terms and keep unique terms separate from one another.

Gap Analysis::Transform::138 - Term disambiguation

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