Child pages
  • 2017-03-30 Developers Forum
Skip to end of metadata
Go to start of metadata

How to Join

 Click here to expand...

In person

Courtesy, please

If you are joining remotely via telephone, Adobe Connect, or Skype, please use a headset-microphone, or at least earphones. Please use the mute feature when you are not speaking.

Interactive meeting - Adobe Connect

  • We routinely share a screen during the call. You can view the screen via our Adobe Connect meeting room at For large meetings, the room has the ability to broadcast audio and connect to a telephone-based system as well, as controlled by the meeting hosts.

By telephone

  • US telephone number: +1-888-510-4073
  • Access code: 24222#

By Browser


  • Chat is available in the Adobe Connect meeting room (see above).
  • A backchannel meta-discussion during the meeting also occurs on IRC.




  • Matt
  • Maimoona
  • Burke
  • Wyclif
  • Daniel
OpenSRP Update
  • Connecting front-line health workers to national health systems.
  • Focused on client-facing applications
  • Bridging the gap between clinical (OpenMRS) and outreach
  • Demo of child immunization application
  • Trying to optimize every interaction
  • Removing forms where possible
  • Have created chat interfaces (e.g., Telegram, SMS, Facebook Messenger)
  • Using a CouchDB database
  • Storing data in a FHIR-like model
  • Do a 2-way sync between OpenSRP and OpenMRS (use Atomfeed module)
  • Using OWA for UI (can call OpenSRP REST endpoints)
  • Server
  • CouchDB
  • Motech + quartz for scheduling
  • CouchDB-Lucene for faster searches
  • OpenMRS and DHIS2 for reporting
  • Mobile client
  • Have integrated with both OpenMRS and Bahmni
  • Created a team management module
  • Allows for hierarchy of teams
  • Keeps track of changes in teams over time
  • Has been really helpful for allowing easier permission management by granting access based on team assignment
  • Created a DHIS location module
  • Enhanced cohort module
  • Created schedule tracking module
  • Described road map
  • Hope to get to a point someone can create a register without having to program in Android
Are there plans to include "dateChanged" as a filter (search parameter) into REST calls?
  • Burke: this is certainly feasible. Not sure if it's on anyone's radar to do.
  • Would need to add at the API level. Wouldn't necessarily need to be all or none (could target a few high priority API methods as an exemplar of how we'd do it for other API methods in the future)
Does OpenMRS have an unattended install (e.g., using Docker)?
  • Burke: I thought we had this
  • Wyclif: I don't think we have this.
  • Daniel: I think we alrady have this.
  • TODO: Need to find (or create) documentation for how to do unattended install
  • Daniel will look into this
Is there an audit module?
  • Wyclif: We created one years ago, but it never reached production level.
  • Burke: I think this was created as a path toward centralizing the audit (changed/updated) attributes.
  • Why not use relationships for recording patient-provider relationships?
  • OpenMRS REST service wasn't efficient enough for pulling across teams.
  • Did you consider appointment module for scheduling needs?
  • Needed treatment schedules (e.g., vaccination)
  • Are you using or considering Docker (with Ansible)?
  • Yes. Have a Docker installation. Learning from Bahmni.
  • Does the household register using cohorts?
  • Not yet.



  • Audio recording of the call: Listen online or download (available after the meeting)



  • No labels