Page History

Page info
title title

This section includes the following:

...

• Syntactical and semantic models: XML, OWL, RDF representations
• Information Models: HL7 MIF, UML, 11179 representations
• Meta Models
  • HL7 RIM (Reference Information Model)
  • BRIDG (Biomedical Research Integrated Domain Group)
  • LS-DAM (Life Sciences Domain Access Model)
• Transforms
  • Object Management Group (OMG) Ontology Definition Metamodel Tranforms
• Model Constraints
  • Object Constraint Language (OCL), Schematron
• Data Types
  • ISO 21090 and HL7 R2
  • HL7 R1
  • Primitives

Behavioral Models

In The behavioral models that will be managed by Semantic Infrastructure 2.0 are identified in the context of the Semantic Infrastructure 2.0 Roadmap, and in compliance with the CBIIT implementation of the Service-Aware Interoperability Framework (SAIF) Behavior Framework (BF).

The SAIF BF defines behavior as "a collection of interactions with a set of constraints on when they can occur in a given Working Interoperability/business process context." The "behavioral models" that will be managed by Semantic Infrastructure 2.0 collectively specify the behavioral semantics of services at the interface and NOT at the implementation level this paper, 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.

Dynamic models include but are not limited to:

• HL7 SAIF (Service-Aware Interoperability Framework) behavioral model (which provides a formal model and grammar for service contracts)
• Orchestrations and Workflows
• Business Rules

model semantics, as defined in a CBIIT-defined and SAIF-compliant behavioral metamodel, will collectively define the behavioral metadata. A number of technologies still being explored will be used, including UML (Unified Modeling Language) profiles, OWL (Web Ontology Language), Resource Description Framework (RDF), and rules engines (such as Jess), to produce the metadata necessary to support automated (or at least semi-automated) workflow composition. As-yet-unspecified user-friendly tools will be used to provide various contextual inputs for a given workflow including but not limited to known pre- or post-conditions, input data sources, and desired data operations.

Content

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. Content includes:

...

Clinical Trials: Clinical trials 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.