STU 3 Ballot
ConformanceThis page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
. Page versions: R5 R4B R4 R3
This is the narrative for the resource. See also the XML or JSON format.
OPERATION: Apply
The apply operation realizes a definition in a specific context
Parameters
| Use | Name | Cardinality | Type | Binding | Documentation |
| IN | patient | 1..1 | Reference | The patient that is the target of the activity to be applied | |
| IN | encounter | 0..1 | Reference | The encounter in context, if any | |
| IN | practitioner | 0..1 | Reference | The practitioner in context | |
| IN | organization | 0..1 | Reference | The organization in context | |
| IN | userType | 0..1 | CodeableConcept | The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.) | |
| IN | userLanguage | 0..1 | CodeableConcept | Preferred language of the person using the system | |
| IN | userTaskContext | 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 | |
| IN | setting | 0..1 | CodeableConcept | The current setting of the request (inpatient, outpatient, etc) | |
| IN | settingContext | 0..1 | CodeableConcept | Additional detail about the setting of the request, if any | |
| OUT | return | 1..1 | Any | The resource that is the result of applying the definition |
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
© HL7.org 2011+. FHIR STU3 Ballot (v1.6.0-9663) generated on Thu, Aug 11, 2016 17:06+1000. QA Page
Links: Search |
Version History |
Table of Contents |
Compare to DSTU2 |
|
Propose a change