Versions Compared

Key

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

...

  1. facility_instance.properties (sample file)
    facility.catchments:- This accepts the list of catchments for the current facility. E.g :- for a gazipur district hospital it will be 3033, for Kaliganj UHC it will be 303334, It signifies the area which falls under it. But for a hospital in Dhaka it can’t be 30, Because it accepts minimum 4 chars, so it will be a comma separated list of all possible catchments in Dhaka division. E.g. :- 3033,3026…
    facility.facilityId :- This is the facility id in HRM of the current hospital.
    facility.apiToken:- This is the token from HRM for user.
    facility.clientId :- This is the user id from HRM.

  2. identity.properties (sample file)

  3. lr.properties (sample file)

  4. fr.properties (sample file)

  5. pr.properties (sample file)

  6. tr_atomfeed_properties.properties (sample file)

  7. shr.properties (sample file)

  8. mci.properties (sample file)

  9. fhir_mapping.properties (sample  file)
    visitTypeToEncounterClassMap :- This is a JSON representing a map from openmrs visit type to fhir encounter class (A fhir value-set) names , this will be used while uploading an encounter to shrencounterClassToVisitTypeMap shr.
    encounterClassToVisitTypeMap :- This is a JSON representing a map from fhir encounter class name to openmrs visit type name ,this will be used while downloading an encounter from shr.
    mrsEncounterTypeToFhirEncounterTypeMap :- This is a JSON representing a map from openmrs encounter type to Fhir encounter type (A value-set in TR) , this will be used for uploading an encounter to shr.
    fhirEncounterTypeToMrsEncounterTypeMap :- This is a JSON representing a map from fhir encounter type to openmrs encounter type, this will be used for downloading an encounter from shr.


...