Versions Compared

Key

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

...

  • End users should have access to a user interface that allows health workers to search for duplicates, identify duplicates and merge duplicates.
    • These changes should be made system-wide
    • This search should include the ability to perform a fuzzy search for potential duplicates based on name
    • (Stretch) users can choose from a number of predefined duplicate search strategies
  • All merge events from the central system(s) should be reflected in the Android client
  • If an Android client user identifies a duplicate on their device, they should be able to archive or merge the duplicate record so it is no longer displayed on their Android client, or on other devices at the same facility
  • The merging process should include a robust audit trail that is centrally viewable
  • OpenSRP server should provide specific role based access controls to limit the number of users who have the ability to view and merge patient records from a central location

Alternative Solutions To Be

...

Researched

  • We review and test OpenMRS merge features at scale and identify processes in OpenSRP server that kick off when a merge is processed
  • We can integrate with a third party tool to more quickly identify duplicates (Jembi's HEARTH, OpenEMPI, MEDIC CR) and develop a process for integrating those changes in OpenSRP server