STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.12 Resource DecisionSupportServiceModule - Content

Clinical Decision Support Work GroupMaturity Level: 0Compartments: Not linked to any defined compartments

The DecisionSupportServiceModule describes a unit of decision support functionality that is made available as a service, such as immunization modules or drug-drug interaction checking.

4.12.1 Scope and Usage

This resource is a draft proposal for use as part of an approach to Clinical Quality within FHIR, and is documented as part of the Clinical Quality Improvement Framework Implementation Guide.

The DecisionSupportServiceModule defines a module of clinical decision support functionality made available by a decision support service. For example, a service may provide immunization modules, drug-drug interaction checking, or appropriate use assessment.

Each module defines three main features related to its functionality:

  • Input and output parameters
  • Data requirements
  • Triggers

Input and output parameters are used to specify any named parameters used by the module. These are typically patient-independent configuration parameters such as an A1C threshold for a diabetes control module, but they may also be used to return calculations performed by the module.

Data requirements are used to specify the set of data that must be provided (or available) to the module in order to achieve a successful evaluation. For example, if the module requires A1C lab results within the last 6 months, or information on bilateral or both left and right amputation at or below the knee.

Triggers are used to advertise when the module should be invoked. On encountering a specific trigger, a clinical application can invoke the modules associated with the trigger using the $evaluate operation. Any data required by the module can be sent as part of the request, and any suggested actions and other output data are returned via the GuidanceResponse resource.

For a more detailed discussion of the evaluation process, refer to the Integrating Decision Support in a Clinical Workflow topic in the CQIF IG.

4.12.2 Boundaries and Relationships

The DecisionSupportServiceModule is similar in structure to the DecisionSupportRule, and supports an identical $evaluate operation. The difference between the two is that the DecisionSupportRule is designed to enable the sharing of the rule definition, as opposed to the DecisionSupportServiceModule, which only supports evaluation of the module; the internal functionality is opaque.

This resource is referenced by guidanceresponse

4.12.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DecisionSupportServiceModule ΣDomainResourceA description of decision support service functionality
... moduleMetadata Σ0..1ModuleMetadataMetadata for the service module
... trigger Σ0..*TriggerDefinition"when" the module should be invoked
... parameter Σ0..*ParameterDefinitionParameters to the module
... dataRequirement Σ0..*DataRequirementData requirements for the module

doco Documentation for this format

XML Template

<DecisionSupportServiceModule xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <moduleMetadata><!-- 0..1 ModuleMetadata Metadata for the service module --></moduleMetadata>
 <trigger><!-- 0..* TriggerDefinition "when" the module should be invoked --></trigger>
 <parameter><!-- 0..* ParameterDefinition Parameters to the module --></parameter>
 <dataRequirement><!-- 0..* DataRequirement Data requirements for the module --></dataRequirement>
</DecisionSupportServiceModule>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DecisionSupportServiceModule ΣDomainResourceA description of decision support service functionality
... moduleMetadata Σ0..1ModuleMetadataMetadata for the service module
... trigger Σ0..*TriggerDefinition"when" the module should be invoked
... parameter Σ0..*ParameterDefinitionParameters to the module
... dataRequirement Σ0..*DataRequirementData requirements for the module

doco Documentation for this format

XML Template

<DecisionSupportServiceModule xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <moduleMetadata><!-- 0..1 ModuleMetadata Metadata for the service module --></moduleMetadata>
 <trigger><!-- 0..* TriggerDefinition "when" the module should be invoked --></trigger>
 <parameter><!-- 0..* ParameterDefinition Parameters to the module --></parameter>
 <dataRequirement><!-- 0..* DataRequirement Data requirements for the module --></dataRequirement>
</DecisionSupportServiceModule>

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

4.12.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
descriptionstringText search against the descriptionDecisionSupportServiceModule.moduleMetadata.description
identifiertokenLogical identifier for the module (e.g. CMS-143)DecisionSupportServiceModule.moduleMetadata.identifier
statustokenStatus of the moduleDecisionSupportServiceModule.moduleMetadata.status
titlestringText search against the titleDecisionSupportServiceModule.moduleMetadata.title
topictokenTopics associated with the moduleDecisionSupportServiceModule.moduleMetadata.topic
versionstringVersion of the module (e.g. 1.0.0)DecisionSupportServiceModule.moduleMetadata.version