Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Encounter Type Matching

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,

  1. by

    programUuid

    location uuid -

    mapping

     mapping present in entity_mapping table with entity_mapping_type as '

    program

    location_encountertype'

    by location uuid - mapping

     (OR)
        - Location encounter type mapping can be inserted using the following query:
          

    Code Block
    languagesql
    titlelocation_encountertype
    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())
  2. by default encounter type provided in global property ( bahmni.encounterType.default).

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,

  1. by programUuid - mapping present in entity_mapping table with entity_mapping_type as 'locationprogram_encountertype' (OR)
  2. by default encounter type provided in global property ( bahmni.encounterType.default)

 

...

  1. .

For other encounters, following encounter types are picked irrespective of location:

  1. Registration Encounter - 'REG'
  2. Radiology Upload Encounter - 'RADIOLOGY'
  3. Patient Document Encounter - 'Patient Document'
  4. Admission Encounter - 'ADMISSION'
  5. Discharge Encounter - 'DISCHARGE'
  6. Transfer Encounter - 'TRANSFER'