Model and Annotate defines profiles supporting models, including model maintenance, constraints, bindings, extensions, and semantic annotations.
Static models include a variety of models with different representations.
Behavioral dynamic models capture the behavior of services. Behavior of services provides an unambiguous 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.
Forms include both ODM and CDA documents. This includes all aspects of the document including the style, definitions and semantics.
Content includes all unstructured text and other forms of content that make up a service specification. Examples include storyboards, and scope. Content is an integral part of service specification, and content is leveraged across the enterprise for documentation and communications.
This set of requirements includes providing an application developer with the ability to define application-specific attributes (for example, defined using ISO 21090 healthcare datatypes) and an information model that defines the relationships between these attributes and other attributes in the broader ecosystem. In particular, the last requirement suggests linked datasets, where application developers can connect data in disparate repositories as if the repositories are part of a larger federated data ecosystem. Additional requirements include the ability to publish and discover information models. Support is needed for forms data and common clinical document standards, such as HL7 CDA. To support the use of binary data throughout the system, the binary data must be typed and semantically annotated.
All Information models, their representation and binding to data-types and terminologies will be managed by the semantic infrastructure. The ability to publish and discover information models will be supported by the semantic infrastructure, and the platform will leverage these capabilities.
Link to use case satisfied from caGRID 2.0 Roadmap: The pathology, radiology and other data have various data formats which must be described, and the information model for the patient record must link between these various datatypes. The complete information model includes semantic links between datasets to build a comprehensive electronic medical record. Annotations on data are defined and included in the information model.
Functional Profile
- 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.
