Visit is selected by the visitUuid sent in the EncounterTransaction. Within the visit, the encounter is filtered based on the following logic for regular encounters, retrospective encounter, on behalf of encounters and encounter edits. , in that order
Regular Consultation & Retrospective Consultation
Visit Document
Regular Consultation Encounter & Retrospective Consultation Encounter
Encounter type to be used for finding an encounter or creating a new encounter for regular consultation or retrospective consultation is based on either of the following logic in the given order,
by location uuid - mapping present in entity_mapping table with entity_mapping_type as 'location_encountertype' (OR)
- Location encounter type mapping can be inserted using the following query:
insert into entity_mapping(uuid, entity_mapping_type_id, entity1_uuid, entity2_uuid, date_created) values (uuid(), <mapping_id_of_location_encountertype>, <uuid_of_location>, <uuid_of_encounter_type>, now()) |
Program Consultation Encounter
Encounter type to be used for finding an encounter or creating a new encounter for program consultation is based on either of the following logic in the given order,
For other encounters, following encounter types are picked irrespective of location: