Page History

Page info
title title

This section describes user interactions with the Semantic Infrastructure tools and services. Specifically it addresses "a day in the life" of an developer, analyst, architect, clinician and bioinformatician as they use the tools. It provides an overview of the interactions, workflow and dependencies with external tools and platform. The following topics are included:

Rule Authoring

1. A Clinical Decision Support (CDS) Rule Author receives notification of a new clinical decision support requirement.
2. The Rule Author identifies the clinical logic required in order to implement the rule.
3. The Rule Author identifies the required data elements from the metadata registry (ECCF). The data element identification is done at a level of abstraction consistent with the clinical logic contained in the rule, and is not dependent on the specific codings or formats contained in the actual patient data messages or document instances that are received and stored.
4. The Rule Author codes the rule logic using Arden Syntax, and the data access expressions using GELLO, either through the use of an authoring tool or by hand.
5. The newly created decision support rule is added to the rule base for subsequent evaluation (execution) by the rules engine when an associated rule trigger is activated.
6. New or updated patient data is received which triggers the evaluation (execution) of the decision support rule. During the rule evaluation an attempt is made to retrieve all of the data that matches the data elements previously specified in the rule. The set of matching patient data instances for each specified rule data element is determined using the Semantic Infrastructure, based on the HL7 RIM objects and associated ontologies. This allows data that is encoded at lower levels of abstraction or more specific granularity to be linked and applied to the appropriate data elements specified in the rule, and for matching data instances to satisfy one or more of the rule criteria.

Search and Access

If sufficient rule criteria are satisfied, then one or more specified clinical decision support actions are performed or scheduled. These actions may include, but are not limited to, sending an alert to a health care provider, creating a reminder for future action to be taken, adding an interpretation to the patient record, returning a result to a calling MLM, and evoking other MLMs.

1. Develop service requirements.
2. Construct search of registry using metadata.
3. Identify potential service definition.
4. Retrieve service specification objects.
5. Analyze quality of requirements fit to service specification
6. Retrieve known end points and Directories for Service.

Author

1. Import WSDL and Schemas for service definitions
2. Link Service Definition to model artifacts
3. Identify Endpoints and Directories
4. Automate Discovery of Services on Bus

Adminster Services and Specifications

1. Submit Service Specification for governance
2. Construct conformance statements
3. Run validations on specification and supporting artifacts
4. Apply constraints, rules, and policies

...