Page History

...

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.

Satic Models: 

Static models include (but not limited to):

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

Behavioral Models: 

In the context of this paper, behavior/dynamic models capture the behavior of services. Behavior of services provides an uambigous definition of the service constraints, capabilities, dependencies and interactions. The metadata and grammar required to realize service behavior is called behavioral semantics, behavioral semantics provide a mechanism for better service discovery and enforcing the constraints at design and runtime.

Dynamic models include (but not limited to):

...

 Artifact lifecycle management and metadata provides the metadata requirements include 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 and views of the information, realized through the appropriate transforms
• Access control and other security constraints
• Annotations for better discovery and searching of artifacts
• Usage
• Represenations
• Scenarios and Context for the information
• Terminology and Value Set binding

The artifacts are bound to the services via the service metadata, the service metadata combined with the artifacts and its 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
•  

The requirements listed above are derived from the following use cases in the previous section:

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 to the community and vendors. The infrastructure needs to support better discovery, making all the relevant information avaialble in the right context

ONC and Other external EHR adopters: ONC has adopted CCD and CCR for meaninfuly 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 Trails: Clinical trails 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.

Service Lifecycle Management and Governance

...

Link to use case: The origin of data is tied to the data creator, allowing the oncologist performing the match against TCGA data and other datasets to include and exclude data sets based on their origin.

-         Semantic Infrastructure Users and Roles
-         Functional Requirements
   Artifact Management
§  Static Models
§  Behavioral Models
§  Forms

Data Semantics

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 Semantics Infrastructure, although there will be a touchpoint between the caGrid 2.0 and the semantics infrastructure to annotate data with semantics. Integration with the semantics infrastructure will enable reasoning, semantic query, data mediation (for example, ad hoc data transformation) and other powerful capabilities.

...