This page is part of the FHIR Specification (v0.0.82: DSTU 1). 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: R3 R2 Content Examples Detailed Descriptions Mappings Profiles 4.10.6 Resource ProcedureRequest - Detailed Descriptions Detailed Descriptions for the elements in the ProcedureRequest resource. ProcedureRequest Definition A request for a procedure to be performed. May be a proposal or an order. Control 1..1 ProcedureRequest.identifier Definition Identifiers assigned to this order by the order or by the receiver. Note This is a business identifer, not a resource identifier (see discussion ) Control 0..* Type Identifier ProcedureRequest.subject Definition The patient who will receive the procedure. Control 1..1 Type Reference ( Patient ) ProcedureRequest.type Definition The specific procedure that is ordered. Use text if the exact nature of the procedure can't be coded. Control 1..1 Type CodeableConcept ProcedureRequest.bodySite Definition Indicates the sites on the subject's body where the procedure should be performed ( i.e. the target sites). Control 0..* Requirements Knowing where the procedure is made is important for tracking if multiple sites are possible. Comments Only used if not implicit in code found in ProcedureRequest.type. ProcedureRequest.bodySite.site[x] Definition Indicates the site on the subject's body where the procedure should be performed ( i.e. the target sites). Control 1..1 Type CodeableConcept | Reference ( BodySite ) Requirements Knowing where the procedure is made is important for tracking if multiple site are possible. Comments Only used if not implicit in code found in ProcedureRequest.type. ProcedureRequest.indication Definition The reason why the procedure is proposed or ordered. This procedure request may be motivated by a Condition for instance. Control 0..* Type CodeableConcept ProcedureRequest.timing[x] Definition The timing schedule for the proposed or ordered procedure. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Control 0..1 Type dateTime | Period | Timing ProcedureRequest.encounter Definition The encounter within which the procedure proposal or request was created. Control 0..1 Type Reference ( Encounter ) ProcedureRequest.performer Definition E.g. surgeon, anaethetist, endoscopist. Control 0..1 Type Reference ( Practitioner | Organization | Patient | RelatedPerson ) ProcedureRequest.status Definition The status of the order. Control 0..1 Binding ProcedureRequestStatus: Required : http://hl7.org/fhir/procedure-request-status (The status of the request) Type code Is Modifier true ProcedureRequest.notes Definition Any other notes associated with this proposal or order - e.g., provider instructions. Control 0..* Type string ProcedureRequest.asNeeded[x] Definition If a CodeableConcept is present, it indicates the pre-condition for performing the procedure. Control 0..1 Type boolean | CodeableConcept ProcedureRequest.orderedOn Definition The time when the request was made. Control 0..1 Type dateTime ProcedureRequest.orderer Definition The healthcare professional responsible for proposing or ordering the procedure. Control 0..1 Type Reference ( Practitioner | Patient | RelatedPerson | Device ) ProcedureRequest.priority Definition The clinical priority associated with this order. Control 0..1 Binding ProcedureRequestPriority: Required : http://hl7.org/fhir/procedure-request-priority (The priority of the request) Type code © HL7.org 2011+. FHIR DSTU (v0.4.0-4902) generated on Fri, Mar 27, 2015 00:22+1100. Links: What's a DSTU? | Version History | Specification Map | Compare to DSTU1 | | Propose a change