Child pages
  • 2015-05-14 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.



  • Quickly review previous meeting minutes (5 min)
  • ThoughtWorks-SCI Ebola Module tech deep dive w/ Darius Jazayeri
  • Review next meeting agenda


View at


OpenMRS Developers Forum 2015-05-14
Recording:   (Audio)  (Adobe® Flash®)
  • Burke Mamlin
  • Sara Armson
  • Wyclif Luyima
  • Maurya
  • Willa Mhawila
  • Ryan Yates
  • Suranga Kasthurirathne
  • Ada Yeung
  • Archana Eadara
  • Cosmin
  • Daniel Kayiwa
  • Ellen Ball
  • Hamish Fraser
  • Jonathan Dick
  • Jonathan Teich
  • Manika Maheshwari
  • Tharunya
  • Mike Seaton
  • Paul Biondich
  • Rafal Korytkowski
  • Shefali Oza
  • Tomasz Mueller
  • wintech
  • aniketha
Agenda & Notes
  • Review last week TODOs
  • TODO: Burke to notify presenters about their dev forum topics
  • TODO: Someone to Set up CI builds for MariaDB, PostgreSQL, and SQLServer, Oracle (We assume these will not be green lights)
  • TODO: Someone to Create tickets to address problems that occur for alternate DBs
  • TODO: Someone to Schedule sprint(s) to address DB tickets
  • TODO: Someone to push for mocks over integration tests
  • TODO: Someone to document how to test within IDE in dev pages in wiki
  • ThoughtWorks-SCI Ebola Module tech deep dive w/ Darius Jazayeri
  • Doctors were using tablets within the red zone (in full suits, gloves, etc.)
  • "Wouldl be neat if we had a tool to rename a module." -Darius
  • TODO: Created a ticket to add this feature as a maven task that can be invoked by SDK command "omrs-rename newname"
  • Use AngularJS code with UI Framework, so UI Framework could dynamically reload changes during devleopment
  • Avoided taking a day to set up dev environment
  • Didn't have time to embed/include localization
  • Grunt can assemble & minify javascript
  • TODO: consider using grunt maven plugin to allow automated builds to easily issue grunt commands
  • Used angular ui router
  • define "states", which specify path in browser, path to template, and can include additional data or control back button behavior
  • User login was simplified
  • User picks team and enters an ID to log in
  • This was done using a hack/workaround to bypass passwords
  • There's a ticket to formally support alternate authentication schemes: TRUNK-381
  • Created basic drug prescription writing
  • REST experience
  • does crud pretty easily, dealing with non-CRUD resources is harder (e.g., getting session information)
  • Would like to add ward and/or bed assignments as REST resources
  • Need better helper classes
  • Creating another order type worked pretty well
  • Couldn't use hibernate annotations, since Order uses hibernate mapping file
  • Used the metadatadeploy module, so all metadata was defined via code
  • CIEL dictionary was great assett and Andy was turning around updates quickly
  • Form entry
  • Created a "form flow" that hid the header and provided back/forward buttons to guide through form with save button at end
  • Questions
  • Did you consider using grunt/yeoman to manage your builds?
  • Nope
  • Did you consider using the application cache to manage version updates? 
  • Nope. We had reliable network in the facility, offline/caching wasn't necessary.
  • Next week
  • 21 May: GSoC Q&A/intro


Outstanding TODOs  (${entries.size()} issues)

Summary Assignee Created Due

Create a TODO:


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



  • No labels