cardea.fhir.ProcedureRequest

class cardea.fhir.ProcedureRequest(dict_values=None)

A record of a request for diagnostic investigations, treatments, or operations to be performed.

Parameters

• resourceType – This is a ProcedureRequest resource

• identifier – Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller.

• definition – Protocol or definition followed by this request.

• basedOn – Plan/proposal/order fulfilled by this request.

• replaces – The request takes the place of the referenced completed or terminated request(s).

• requisition – A shared identifier common to all procedure or diagnostic requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier.

• status – The status of the order.

• intent – Whether the request is a proposal, plan, an original order or a reflex order.

• priority – Indicates how quickly the ProcedureRequest should be addressed with respect to other requests.

• doNotPerform – Set this to true if the record is saying that the procedure should NOT be performed.

• category – A code that classifies the procedure for searching, sorting and display purposes (e.g. “Surgical Procedure”).

• code – A code that identifies a particular procedure, diagnostic investigation, or panel of investigations, that have been requested.

• subject – On whom or what the procedure or diagnostic is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans).

• context – An encounter or episode of care that provides additional information about the healthcare context in which this request is made.

• occurrenceDateTime – The date/time at which the diagnostic testing should occur.

• occurrencePeriod – The date/time at which the diagnostic testing should occur.

• occurrenceTiming – The date/time at which the diagnostic testing should occur.

• asNeededBoolean – If a CodeableConcept is present, it indicates the pre-condition for performing the procedure. For example “pain”, “on flare-up”, etc.

• asNeededCodeableConcept – If a CodeableConcept is present, it indicates the pre-condition for performing the procedure. For example “pain”, “on flare-up”, etc.

• authoredOn – When the request transitioned to being actionable.

• requester – The individual who initiated the request and has responsibility for its activation.

• performerType – Desired type of performer for doing the diagnostic testing.

• performer – The desired perfomer for doing the diagnostic testing. For example, the surgeon, dermatopathologist, endoscopist, etc.

• reasonCode – An explanation or justification for why this diagnostic investigation is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in supportingInformation.

• reasonReference – Indicates another resource that provides a justification for why this diagnostic investigation is being requested. May relate to the resources referred to in supportingInformation.

• supportingInfo – Additional clinical information about the patient or specimen that may influence the procedure or diagnostics or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as “ask at order entry questions (AOEs)”. This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.

• specimen – One or more specimens that the laboratory procedure will use.

• bodySite – Anatomic location where the procedure should be performed. This is the target site.

• note – Any other notes and comments made about the service request. For example, letting provider know that “patient hates needles” or other provider instructions.

• relevantHistory – Key events in the history of the request.

__init__(dict_values=None)

Initialize self. See help(type(self)) for accurate signature.

Methods

__init__([dict_values])	Initialize self.
assert_type()	Checks class values follow set possible enumerations.
get_dataframe()	Returns dataframe from class attribute values.
get_eligible_relationships()	Returns class relationships for attributes that are used.
get_id()	Returns fhir class identifier.
get_relationships()	Returns class relationships.
set_attributes(dict_values)	Sets values to class attributes.

cardea.fhir.Procedure cardea.fhir.ProcessRequest