Page History

...

This section presents the dervied requirements, as a result of the requirements analysis of the use cases presented in previous section. The analysis includes tracing of requirements up to the use case and stakeholders and down to service capabilities specified later in this document.

...

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 Static Models: 

Static models include a variety of models with different represenations. These models

Static models include (but not limited to):

• XML Schemas
• UML/HL7 Models, including domain models like BRIDG and LS-DAM.
• OWL
• Meta Models
• Transforms
• Model Constraints, like OCL
• Data Types

Behavioral Models: 

...

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

Content:

Content includes all instructured text and other forms of content that make up a service specification, storyboards, etc. Content is an integral part of service specification that is leveraged across multiple initiatives.

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

Forms:

Forms include both ODM and CDA documents. This includes all aspects of the document including the style, defintions and semantics.

• Form Templates
• Form Defintions

...