Approach/tool for keeping track of many OpenMRS Implementations

Implementing
17

openmrs-module-systemmonitor module originally supported the following indicators;

  • Server Id (HostName-MacAddressWithoutcolons)
  • Processor (e.g. Intel(R) Core™ i5-5257U CPU @ 2.70GHz)
  • Server Uptime (minutes)
  • Operating System
  • Operating System Arch
  • Operating System Version
  • Java Version
  • Java Vendor
  • JVM Version
  • JVM Vendor
  • System Language
  • System Timezone
  • Java Runtime Name
  • Java Runtime Version
  • System DateTime
  • File System Encoding
  • User Directory
  • Temporary Directory
  • User Name
  • OpenMRS App Name
  • OpenMRS Version
  • OpenMRS Uptime (minutes)
  • Installed Modules
  • Date for last backup
  • Server’s Real Location
  • Total Memory (MB)
  • Used Memory (MB)
  • Free Memory (MB)

in the last development timeline we added more indicators listed below for a Rwandan SPH study for which the module is currently implemented in production;

  • active patient - 8m
  • active patient - 8m - CD4 (EMR)
  • active patient - 8m - VL (EMR)
  • active patient - 20m - CD4 (Last Year)
  • active patient - 20m - VL (Last Year)
  • Initial viral load
  • Initial CD4 Count
  • Followup CD4 Count
  • Followup viral load
  • OpenMRS Uptime (%)
  • Number Of OpenMRS DownTimes
  • OpenMRS Downtime (%)
  • OpenMRS Downtime (minutes)
  • OpenMRS UpTime Intervals
  • OpenMRS DownTime Intervals

For more details about each of the indicators such as a description of what is monitored consider looking into the documentation at JEMBIDEV-OpenMRSSystemMonitorModuleDocumentation-200417-1025.pdf (757.3 KB)

I recommend setting up the module using the documentation, point it to a different DHIS2 instance and see if it meets part or all of your requirements, we can help direct you in-case you need to make any logical changes in the metrics etc.

We chose to move away from an initial script we had started supporting cloning it from PIH tools since it was Ubuntu requiring and we needed to do more with the tool, the script had direct openmrs database access which was a security threat and so we chose to re-write an OpenMRS module that does exactly and more than the script was doing.