activitydefinition $apply

Apply

Description: The apply operation applies a definition in a specific context

Comments: The result of invoking this operation is a resource of the type specified by the activity definition, with all the definitions resolved as appropriate for the type of resource. Any dynamicValue elements will be evaluated (in the order in which they appear in the resource) and the results applied to the returned resource. If the ActivityDefinition includes library references, those libraries will be available to the evaluated expressions. If those libraries have parameters, those parameters will be bound by name to the parameters given to the operation. In addition, parameters to the $apply operation are available within dynamicValue expressions as context variables, accessible by the name of the parameter, prefixed with a percent (%) symbol. For a more detailed description, refer to the ActivityDefinition resource. Note that result of this operation is transient (i.e. none of the resources created by the operation are persisted in the server, they are all returned as contained resources in the result). The result effectively represents a proposed set of activities, and it is up to the caller to determine whether and how those activities are actually carried out.

Affects State: false

System: false

Type: true

Instance: true

URL: http://hl7.org/fhir/build/OperationDefinition/ActivityDefinition-apply

Parameters

• activityDefinition [in] 0..1 ActivityDefinition — The activity definition to apply. If the operation is invoked on an instance, this parameter is not allowed. If the operation is invoked at the type level, this parameter is required
• subject [in] 1..* string — The subject(s) that is/are the target of the activity definition to be applied. The subject may be a Patient, Practitioner, Organization, Location, Device, or Group. Subjects provided in this parameter will be resolved as the subject of the PlanDefinition based on the type of the subject. If multiple subjects of the same type are provided, the behavior is implementation-defined
• encounter [in] 0..1 string — The encounter in context, if any
• practitioner [in] 0..1 string — The practitioner in context
• organization [in] 0..1 string — The organization in context
• userType [in] 0..1 CodeableConcept — The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.)
• userLanguage [in] 0..1 CodeableConcept — Preferred language of the person using the system
• userTaskContext [in] 0..1 CodeableConcept — 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
• setting [in] 0..1 CodeableConcept — The current setting of the request (inpatient, outpatient, etc.)
• settingContext [in] 0..1 CodeableConcept — Additional detail about the setting of the request, if any
• return [out] 1..1 Resource — The resource that is the result of applying the definition