cardea.fhir.Encounter

class cardea.fhir.Encounter(dict_values=None)

An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.

Parameters
  • resourceType – This is a Encounter resource

  • identifier – Identifier(s) by which this encounter is known.

  • status – planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

  • statusHistory – The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.

  • class – inpatient | outpatient | ambulatory | emergency +.

  • classHistory – The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transisions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kindof discharge from emergency to inpatient.

  • type – Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).

  • priority – Indicates the urgency of the encounter.

  • subject – The patient ro group present at the encounter.

  • episodeOfCare – Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care, and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).

  • incomingReferral – The referral request this encounter satisfies (incoming referral).

  • participant – The list of people responsible for providing the service.

  • appointment – The appointment that scheduled this encounter.

  • period – The start and end time of the encounter.

  • length – Quantity of time the encounter lasted. This excludes the time during leaves of absence.

  • reason – Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.

  • diagnosis – The list of diagnosis relevant to this encounter.

  • account – The set of accounts that may be used for billing for this Encounter.

  • hospitalization – Details about the admission to a healthcare service.

  • location – List of locations where the patient has been during this encounter.

  • serviceProvider – An organization that is in charge of maintaining the information of this Encounter (e.g. who maintains the report or the master service catalog item, etc.). This MAY be the same as the organization on the Patient record, however it could be different. This MAY not be not the Service Delivery Location’s Organization.

  • partOf – Another Encounter of which this encounter is a part of (administratively or in time).

__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.