Ancestor: HL7Connect.Cda.CDABase

This optional class represents the setting of the clinical encounter during which the documented act(s) or ServiceEvent occurred. Documents are not necessarily generated during an encounter, such as when a clinician, in response to an abnormal lab result, attempts to contact the patient but can't, and writes a Progress Note.

In some cases, the setting of the encounter is inherent in the ClinicalDocument.code, such as where ClinicalDocument.code is "Diabetes Clinic Progress Note". The setting of an encounter can also be transmitted in the HealthCareFacility.code attribute. If HealthCareFacility.code is sent, it should be equivalent to or further specialize the value inherent in the ClinicalDocument.code (such as where the ClinicalDocument.code is simply "Clinic Progress Note" and the value of HealthCareFacility.code is "cardiology clinic"), and shall not conflict with the value inherent in the ClinicalDocument.code, as such a conflict would constitute an ambiguous situation.

EncompassingEncounter.dischargeDispositionCode can be used to depict the disposition of the patient at the time of hospital discharge (e.g., discharged to home, expired, against medical advice, etc.).


IList<HL7Connect.Cda.II> id;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.CD code;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.IVL effectiveTime;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.CD dischargeDispositionCode;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.ResponsibleParty responsibleParty;
   The responsibleParty participant represents the participant having primary legal responsibility for the encounter. This differs from the legalAuthenticator participant in that the legalAuthenticator may or may not be the responsible party, and is serving a medical records function by signing off on the document, moving it into a completed state.

IList<HL7Connect.Cda.EncounterParticipant> encounterParticipant;
   The encounterParticipant participant represents clinicians directly associated with the encounter (e.g. by initiating, terminating, or overseeing it).

HL7Connect.Cda.Location location;
   relates a healthcare facility (HealthCareFacility class) to the encounter to indicate where the encounter took place. The entity playing the role of HealthCareFacility is a place (Place class). The entity scoping the HealthCareFacility role is an organization (Organization class).

The setting of an encounter (e.g. cardiology clinic, primary care clinic, rehabilitation hospital, skilled nursing facility) can be expressed in HealthCareFacility.code. Note that setting and physical location are not the same. There is a many-to-many relationship between setting and the physical location where care is delivered. Thus, a particular room can provide the location for cardiology clinic one day, and for primary care clinic another day; and cardiology clinic today might be held in one physical location, but in another physical location tomorrow.

When the location is an organization, this is indicated by the presence of a scoping Organization, without a playing Place.

string classCode;
   l version="1.0" encoding="UTF-8"?>

string moodCode;
   l version="1.0" encoding="UTF-8"?>


© Kestral Computing P/L 2000 - 2003. HL7Connect v2.00-063 generated on 30-Nov 2015.
Keywords: Code, ID, classCode, effectiveTime, moodCode, encompassingEncounter, dischargeDispositionCode, encounterParticipant, location, responsibleParty, HL7Connect.Cda.EncompassingEncounter