Page History

...

The following sections provide detail on these categories of requirements, defining the requirement as well as describing the relevance to our primary and secondary use-cases. 

Artifact Management

Artifacts includes support for different formats of models, both static and dynamic. Artifact management also includes the ability to manage content and clinical documents. A service specification is made up of service metadata, artifacts and the metadata supporting these artifacts. Artifact management primarily deals with managing artifacts lifecycle and authoring of artifact metadata.

Static models include (but not limited to):

• XML Schemas
• UML/HL7 Models
• OWL
• Meta Models
• Transforms
• Model Constraints
• Data Types

Dynamic models include (but not limited to):

• HL7 SAIF behavioral model
• Orchestrations & Workflows
• Rules - Drools, etc.

Content

• Service specification content, primarily unstructured text
• Images and other representations of static content 

Forms

• Form Templates
• Form Defintions

 Artifact lifecycle management and metadata provides the ability to:

• Manage lifecycle/governance/versioning of the models, content and forms.
• Establishing relationships and dependecies between models, content and forms
• Provenance, Jurisdiction, authority and intelluctual property
• Representation or links to the appropriate transforms
• Access control
• Annotations
• Usage
• Represenations
• 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.

This service specification is used to describe all aspects a foundational requirements group that allows a service developer to build higher-level services (for example, a service in the NCI Enterprise Service Inventory) that are utilized in the use case. This group of requirements allows a primary user (service or application developer) to provide business logic as a service to the broader enterprise. This group of requirements focuses on specification-driven configuration of policies, security requirements, and metadata of the service, and a development process that allows service developers to focus on business logic.

Link to use case: service based capabilities for image databasing, image annotation creation capabilities, search and query, patient electronic medical record markup, glioblastoma recommended treatment analysis, and other capabilities in the use case.

Use Cases Addressed

• caEHR
•  

Service Lifecycle Management and Governance

...