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.13.10 Resource DecisionSupportRule - Operations

This resource has 1 operation associated with it:

$evaluateEvaluate

For more information about operations, including how they are invoked, see Operations.

4.13.10.1 Evaluate

The evaluate operation requests clinical decision support guidance based on a specific decision support module

Formal Definition (as a OperationDefinition).

URL: [base]/DecisionSupportRule/[id]/$evaluate

In Parameters:
NameCardinalityTypeBindingProfileDocumentation
requestId0..1 (code

An optional client-provided identifier to track the request

evaluateAtDateTime0..1 (dateTime

An optional date and time specifying that the evaluation should be performed as thought it was the given date and time. The most direct implication of this is that references to "Now" within the evaluation logic of the module should result in this value. In addition, wherever possible, the data accessed by the module should appear as though it was accessed at this time. The evaluateAtDateTime value may be any time in the past or future, enabling both retrospective and prospective scenarios. If no value is provided, the date and time of the request is assumed

inputParameters0..1Parameters

The input parameters for a request, if any. These parameters are defined by the module that is the target of the evaluation, and supply the input information to the module.

inputData0..*Any

The input data for the request. These data are defined by the data requirements of the module and typically provide patient-dependent information

patient0..1Reference(Patient)

The patient in context, if any

encounter0..1Reference(Encounter)

The encounter in context, if any

initiatingOrganization0..1Reference(Organization)

The organization initiating the request

initiatingPerson0..1Reference(Patient|Practitioner|RelatedPerson)

The person initiating the request

userType0..1CodeableConcept

The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.)

userLanguage0..1CodeableConcept

Preferred language of the person using the system

userTaskContext0..1CodeableConcept

The task the system user is performing, e.g. laboratory results review, medication list review, etc. This information can be used to tailor decision support outputs, such as recommended information resources

receivingOrganization0..1Reference(Organization)

The organization that will receive the response

receivingPerson0..1Reference(Patient|Practitioner|RelatedPerson)

The person in the receiving organization that will receive the response

recipientType0..1CodeableConcept

The type of individual that will consume the response content. This may be different from the requesting user type (e.g. if a clinician is getting disease management guidance for provision to a patient). E.g. patient, healthcare provider or specific type of healthcare provider (physician, nurse, etc.)

recipientLanguage0..1CodeableConcept

Preferred language of the person that will consume the content

setting0..1CodeableConcept

The current setting of the request (inpatient, outpatient, etc)

settingContext0..1CodeableConcept

Additional detail about the setting of the request, if any

Out Parameters:
NameCardinalityTypeBindingProfileDocumentation
return1..1GuidanceResponse

The result of the request as a GuidanceResponse resource. Output parameters, if any, will be contained in the parameters element of the response

Note: as this the only out parameter, it is a resource, and it has the name 'return', the result of this operation is returned directly as a resource