Artifact lifecycle management defines profiles to manage the lifecycle, governance, provenance, versioning, and representation of artifacts, as well as the relationships between artifacts.
Artifact lifecycle management profiles define 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.
Functional Profile
- 5.2.1.1.1 - Governance Sept. 6, 2010 Governance.
- 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 Establish relationships and dependencies between models, content and forms.
- 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.
