50 likes | 205 Views
Encounters / CareProvisions. Models that bridge domains PatientCare / PatientAdministration. Four-tier Encounter model. Encounters (physical or virtual) modeled for administrative / logistical reasons
E N D
Encounters / CareProvisions Models that bridge domains PatientCare /PatientAdministration
Four-tier Encounter model • Encounters (physical or virtual) modeled for administrative / logistical reasons • See http://wiki.hl7.org/index.php?title=Requirements_for_an_Universal_Encounter_model, four-tier model whereby the topmost layer could be an Encounter, but more often than not is a CareProvision: • Grouper (for clinical or organizational reasons) of ‘organizational encounters’ • Organizational encounter – encounter between organization (e.g. hospital) and patient • Unit-level encounter – encounter between a department/unit and the patient • ServiceDelivery location – changes recorded/managed by means of a managed participation associated with the Unit-level encounter
CareProvisions • The CareProvision domain has a 0..1 ‘references’ relationship from the care provision to the encounter act. • CareProvisions (in EVN mood) are the results of referrals (careProvisions in INT mood).
Encounters and CareProvisions Concern EncounterGrouper (Encounter) EncounterGrouper (CareProvision) COMP 0..* COMP 0..* Organizational Encounter REF 0..1 Organizational CareProvision FULFIL 0..1 Referral (CareProvision) COMP 0..* COMP 0..* Unit/department Encounter REF 0..1 Unit-level CareProvision Location 0..* serviceDeliveryLocation
Care Composition (PC) v. Encounter (PA) • Encounter R-MIM should be derivable from Care Compostion R-MIM – Not true today. • E.g. author v. performer • See also: http://wiki.hl7.org/index.php?title=OUH_Encounter_Model • http://wiki.hl7.org/index.php?title=Requirements_for_an_Universal_Encounter_model