Page History

...

Artifact management also includes the ability to manage content and clinical forms. A service specification is made up of service metadata, artifacts and the metadata supporting these artifacts. Artifact management primarily deals with managing artifact lifecycle and authoring of artifact metadata.

Functional Profile Group

• 5.2.1.1 - Administer Artifacts Sept. 6, 2010 Artifact lifecycle management defines profiles to manage the lifecycle, governance, provenance, versioning, and representation of artifacts, as well as the relationships between artifacts.
  • 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.
• 5.2.1.2 - Analyze Artifacts Sept. 6, 2010 Analyze Artifacts defines profiles supporting the analysis of artifacts utilizing semantic queries, reasoning, and rules.
  • 5.2.1.2.1 - Analysis Sept. 6, 2010 Data semantics are captured in the Semantic Infrastructure and the platform will leverage the Semantic Infrastructure interfaces for analysis.
  • 5.2.1.2.2 - Reasoning Sept. 6, 2010 Integration with the Semantic Infrastructure will enable reasoning.
  • 5.2.1.2.3 - Rules Sept. 6, 2010 Two families of rules have been identified by stakeholders. Rules related to workflow and business processes that would be executed by a general purpose rules engine (such as Drools, JESS) and rules specific to semantic reasoning (such as SWRL, SPARQL) that would be used within semantic technologies.
• 5.2.1.3 - Model and Annotate Sept. 6, 2010 Model and Annotate defines profiles supporting models, including model maintenance, constraints, bindings, extensions, and semantic annotations.
  • 5.2.1.3.1 - Bind Models Sept. 6, 2010 Bind models to data types and value sets.
  • 5.2.1.3.2 - Constrain Sept. 6, 2010 Constrain models and data types.
  • 5.2.1.3.3 - Extend Sept. 6, 2010 There were more requests for various types of extensibility than any other category of request other than improvements to tool interfaces. caBIG users and other stakeholders articulated a compelling business need to readily extend models, terminologies, and data elements in a variety of ways.
  • 5.2.1.3.4 - Model Sept. 6, 2010 Create, destroy, edit, and maintain models.
  • 5.2.1.3.5 - Semantic Annotation Sept. 6, 2010 In a diverse information environment, semantics must be used to clearly indicate the meaning of data. This requirement is expected to be addressed by the Semantic Infrastructure, although there will be a touchpoint between the caGrid 2.0 and the Semantic Infrastructure to annotate data with semantics.
• 5.2.1.4 - Publish Sept. 6, 2010 The ability to publish and discover information models will be supported by the semantic infrastructure, and the platform will leverage these capabilities.
  • 5.2.1.4.1 - Publish and Discover Information Models Sept. 6, 2010 The ability to publish and discover information models will be supported by the semantic infrastructure, and the platform will leverage these capabilities.
• 5.2.1.5 - Search and Access Sept. 6, 2010 The Semantic Infrastructure enables integrated access, search, and visualization of artifacts using a variety of search criteria, model serialization formats, and user interaction empowerment tools.
  • 5.2.1.5.1 - Access Sept. 6, 2010 Donwload models/forms definitions in different formats.
  • 5.2.1.5.2 - Search Sept. 6, 2010 Search, using different criteria.
  • 5.2.1.5.3 - View Sept. 6, 2010 Information visualization.
• 5.2.1.6 - Transform Sept. 6, 2010 Transform defines profiles for management and application of transformations to support multiple views, serialization formats, inter-operability, semantic convergence, model migration, model merge and compare, and provisioning of target artifacts.
  • 5.2.1.6.1 - Associate Transforms Sept. 6, 2010 Integration with the Semantic Infrastructure will enable reasoning, semantic query, data mediation (for example, ad hoc data transformation).
  • 5.2.1.6.2 - Transform Sept. 6, 2010 Create represention and views of the information, realized through the appropriate transforms.