Encounter

From Endeavour Knowledge Base
Revision as of 14:21, 9 April 2020 by Admin (talk | contribs) (Created page with "An encounter is an interaction between a patient and healthcare provider for the purpose of providing care, including assessment of care needs. Encounters are the mainstay of...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

An encounter is an interaction between a patient and healthcare provider for the purpose of providing care, including assessment of care needs. Encounters are the mainstay of care provision and the concept covers encounters in any care domain. For example, a GP consultation is an encounter and an in-patient stay is an encounter. Encounters are often defined according to the publisher’s definition or even the nature of the IT system in use. In the DDS, an encounter model is a superset of the different encounter models from the different domains and systems. The different patterns are differentiated by the use of Encounter types or archetypes. For example, a hospital stay would be considered an encounter. The admission and discharge events are also considered an encounter, subsidiary to the hospital stay encounter. Similarly, an accident and emergency attendance may have a subsidiary encounter for the initial assessment. The additional properties relating to encounter types (such as method of admission, or critical care function type) are considered as non-core and are referenced via the information model concepts. Each property type has a concept and each value class is considered concept. Consequently these are not specified in this document but are available via the ontology.