Cardea
cardea.fhir.
DeviceRequest
Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker.
resourceType – This is a DeviceRequest resource
identifier – Identifiers assigned to this order by the orderer or by the receiver.
definition – Protocol or definition followed by this request. For example: The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x%.
basedOn – Plan/proposal/order fulfilled by this request.
priorRequest – The request takes the place of the referenced completed or terminated request(s).
groupIdentifier – Composite request this is part of.
status – The status of the request.
intent – Whether the request is a proposal, plan, an original order or a reflex order.
priority – Indicates how quickly the {{title}} should be addressed with respect to other requests.
codeReference – The details of the device to be used.
codeCodeableConcept – The details of the device to be used.
subject – The patient who will use the device.
context – An encounter that provides additional context in which this request is made.
occurrenceDateTime – The timing schedule for the use of the device. 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”.
occurrencePeriod – The timing schedule for the use of the device. 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”.
occurrenceTiming – The timing schedule for the use of the device. 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”.
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.
reasonCode – Reason or justification for the use of this device.
reasonReference – Reason or justification for the use of this device.
supportingInfo – Additional clinical information about the patient that may influence the request fulfilment. For example, this may includes body where on the subject’s the device will be used ( i.e. the target site).
note – Details about this request that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement.
relevantHistory – Key events in the history of the request.
__init__
Initialize self. See help(type(self)) for accurate signature.
Methods
__init__([dict_values])
Initialize self.
assert_type()
assert_type
Checks class values follow set possible enumerations.
get_dataframe()
get_dataframe
Returns dataframe from class attribute values.
get_eligible_relationships()
get_eligible_relationships
Returns class relationships for attributes that are used.
get_id()
get_id
Returns fhir class identifier.
get_relationships()
get_relationships
Returns class relationships.
set_attributes(dict_values)
set_attributes
Sets values to class attributes.