This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Orders and Observations Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Not linked to any defined compartments |
Raw XML (canonical form + also see XML Format Specification)
Operation Definition
<?xml version="1.0" encoding="UTF-8"?> <OperationDefinition xmlns="http://hl7.org/fhir"> <id value="SpecimenDefinition-apply"/> <text> <status value="extensions"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2> apply</h2> <p> OPERATION: apply</p> <p> The official URL for this operation definition is: </p> <pre> http://hl7.org/fhir/OperationDefinition/SpecimenDefinition-apply</pre> <div> <p> The apply operation applies a SpecimenDefinition in a given context to create a Specimen resource instance</p> </div> <p> URL: [base]/SpecimenDefinition/$apply</p> <p> URL: [base]/SpecimenDefinition/[id]/$apply</p> <p> Parameters</p> <table class="grid"> <tr> <td> <b> Use</b> </td> <td> <b> Name</b> </td> <td> <b> Cardinality</b> </td> <td> <b> Type</b> </td> <td> <b> Binding</b> </td> <td> <b> Documentation</b> </td> </tr> <tr> <td> IN</td> <td> specimenDefinition</td> <td> 0..1</td> <td> <a href="specimendefinition.html">SpecimenDefinition</a> </td> <td/> <td> <div> <p> The specimen definition to be applied. If the operation is invoked at the instance level, this parameter is not allowed; if the operation is invoked at the type level, this parameter is required</p> </div> </td> </tr> <tr> <td> IN</td> <td> subject</td> <td> 1..*</td> <td> <a href="datatypes.html#string">string</a> <br/> ( <a href="search.html#reference">reference</a> ) </td> <td/> <td> <div> <p> The subject(s) that is/are the target of the Specimen instance to be created. The subject may be a Patient, Group, Device, Substance or Location. Subjects provided in this parameter will be resolved as the subject of the Specimen based on the type of the subject. If multiple subjects of the same type are provided, the behavior is implementation-defined</p> </div> </td> </tr> <tr> <td> IN</td> <td> collector</td> <td> 0..1</td> <td> <a href="datatypes.html#string">string</a> <br/> ( <a href="search.html#reference">reference</a> ) </td> <td/> <td> <div> <p> The practitioner (or practitioner role) that is collecting the specimen</p> </div> </td> </tr> <tr> <td> IN</td> <td> userType</td> <td> 0..1</td> <td> <a href="datatypes.html#CodeableConcept">CodeableConcept</a> </td> <td/> <td> <div> <p> The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.)</p> </div> </td> </tr> <tr> <td> IN</td> <td> userLanguage</td> <td> 0..1</td> <td> <a href="datatypes.html#CodeableConcept">CodeableConcept</a> </td> <td/> <td> <div> <p> Preferred language of the person using the system</p> </div> </td> </tr> <tr> <td> IN</td> <td> userTaskContext</td> <td> 0..1</td> <td> <a href="datatypes.html#CodeableConcept">CodeableConcept</a> </td> <td/> <td> <div> <p> 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</p> </div> </td> </tr> <tr> <td> IN</td> <td> setting</td> <td> 0..1</td> <td> <a href="datatypes.html#CodeableConcept">CodeableConcept</a> </td> <td/> <td> <div> <p> The current setting of the request (inpatient, outpatient, etc.)</p> </div> </td> </tr> <tr> <td> IN</td> <td> settingContext</td> <td> 0..1</td> <td> <a href="datatypes.html#CodeableConcept">CodeableConcept</a> </td> <td/> <td> <div> <p> Additional detail about the setting of the request, if any</p> </div> </td> </tr> <tr> <td> OUT</td> <td> return</td> <td> 1..1</td> <td> <a href="specimen.html">Specimen</a> </td> <td/> <td> <div> <p> The Specimen resource that is the result of applying the specimen definition</p> </div> </td> </tr> </table> <div> <p> The result of this operation is a Specimen resource based on the definition of the specimen as described in the SpecimenDefinition resource and the supplied parameters.</p> </div> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="1"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="trial-use"/> </extension> <url value="http://hl7.org/fhir/OperationDefinition/SpecimenDefinition-apply"/> <version value="4.6.0"/> <name value="apply"/> <title value="Apply"/> <status value="draft"/> <kind value="operation"/> <date value="2021-04-15T12:25:09+10:00"/> <publisher value="HL7 (FHIR Project)"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> </contact> <description value="The apply operation applies a SpecimenDefinition in a given context to create a Specimen resource instance"/> <affectsState value="false"/> <code value="apply"/> <comment value="The result of this operation is a Specimen resource based on the definition of the specimen as described in the SpecimenDefinition resource and the supplied parameters."/> <resource value="SpecimenDefinition"/> <system value="false"/> <type value="true"/> <instance value="true"/> <parameter> <name value="specimenDefinition"/> <use value="in"/> <min value="0"/> <max value="1"/> <documentation value="The specimen definition to be applied. If the operation is invoked at the instance level, this parameter is not allowed; if the operation is invoked at the type level, this parameter is required"/> <type value="SpecimenDefinition"/> </parameter> <parameter> <name value="subject"/> <use value="in"/> <min value="1"/> <max value="*"/> <documentation value="The subject(s) that is/are the target of the Specimen instance to be created. The subject may be a Patient, Group, Device, Substance or Location. Subjects provided in this parameter will be resolved as the subject of the Specimen based on the type of the subject. If multiple subjects of the same type are provided, the behavior is implementation-defined"/> <type value="string"/> <searchType value="reference"/> </parameter> <parameter> <name value="collector"/> <use value="in"/> <min value="0"/> <max value="1"/> <documentation value="The practitioner (or practitioner role) that is collecting the specimen"/> <type value="string"/> <searchType value="reference"/> </parameter> <parameter> <name value="userType"/> <use value="in"/> <min value="0"/> <max value="1"/> <documentation value="The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.)"/> <type value="CodeableConcept"/> </parameter> <parameter> <name value="userLanguage"/> <use value="in"/> <min value="0"/> <max value="1"/> <documentation value="Preferred language of the person using the system"/> <type value="CodeableConcept"/> </parameter> <parameter> <name value="userTaskContext"/> <use value="in"/> <min value="0"/> <max value="1"/> <documentation value="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"/> <type value="CodeableConcept"/> </parameter> <parameter> <name value="setting"/> <use value="in"/> <min value="0"/> <max value="1"/> <documentation value="The current setting of the request (inpatient, outpatient, etc.)"/> <type value="CodeableConcept"/> </parameter> <parameter> <name value="settingContext"/> <use value="in"/> <min value="0"/> <max value="1"/> <documentation value="Additional detail about the setting of the request, if any"/> <type value="CodeableConcept"/> </parameter> <parameter> <name value="return"/> <use value="out"/> <min value="1"/> <max value="1"/> <documentation value="The Specimen resource that is the result of applying the specimen definition"/> <type value="Specimen"/> </parameter> </OperationDefinition>
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.