Page History

Page info
title title

Artifact lifecycle management defines profiles to manage the lifecycle, governance, provenance, versioning, and representation of artifacts, as well as the relationships between artifacts.

...

• caBIG® Clinical Information Suite: This project has adopted Enterprise Conformance and Compliance Framework (ECCF) for specifications and Clinical Document Architecture (CDA) documents for interoperability. The project requirements include the need for an infrastructure for managing all the artifacts generated during specification process, including HL7 models and documents.The 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.
• Office of the National Coordinator (ONC) and other external electronic health record (EHR) adopters: ONC has adopted Continuity of Care Document (CCD) and Continuity of Care Record (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.

Functional Profile

• 5.2.1.1.1 - Governance Sept. 6, 2010 Service Oriented Architecture is an architectural paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. Consequently, it is important that organizations that plan to engage in service interactions adopt governance policies and procedures sufficient to ensure that there is standardization across both internal and external organizational boundaries to promote the effective creation and use of SOA-based services.
• 5.2.1.1.2 - Load Sept. 6, 2010 Load any new artifact, through multiple interfaces
• 5.2.1.1.3 - Manage Sept. 6, 2010 Determine provenance, jurisdiction, authority and intellectual property.
• 5.2.1.1.4 - Register Sept. 6, 2010 Mediated awareness promotes loose coupling by keeping the consumers and services from explicitly referring to each other and the descriptions. Mediation lets interaction vary independently. Rather than all potential service consumers being informed on a continual basis about all services, there is a known or agreed upon facility or location that houses the service description. A common mechanism for mediated awareness is a registry-repository.
• 5.2.1.1.5 - Version Sept. 6, 2010 The Semantic Infrastructure keeps track of each version, any relevant provenance information (e.g., who made the change), and supports the concept of being able to revert to any prior state. This version control would include the authoring of any new metadata (making contexts more explicit) and the assertions of model alignments.