A request for a procedure to be performed. May be a proposal or an order.

Identifiers assigned to this order by the order or by the receiver.

The person, animal or group that should receive the procedure.

The specific procedure that is ordered. Use text if the exact nature of the procedure cannot be coded.

Indicates the sites on the subject's body where the procedure should be performed (I.e. the target sites).

Knowing where the procedure is made is important for tracking if multiple sites are possible.

Only used if not implicit in the code found in ProcedureRequest.type.

The reason why the procedure is being proposed or ordered. This procedure request may be motivated by a Condition for instance.

The timing schedule for the proposed or ordered procedure. The Schedule data type allows many different expressions. E.g. "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".

The encounter within which the procedure proposal or request was created.

For example, the surgeon, anaethetist, endoscopist, etc.

The status of the order.

Information that may be needed by/relevant to the performer in their execution of this request.

Any other notes associated with this proposal or order - e.g. provider instructions.

If a CodeableConcept is present, it indicates the pre-condition for performing the procedure.

The time when the request was made.

The healthcare professional responsible for proposing or ordering the procedure.

The clinical priority associated with this order.