2014-05-15 Developers Forum

How to Join

 Click here to expand...


By Browser

By telephone

  • US telephone number: +1 201.479.2627




  • Quickly review previous meeting minutes (5 min)
    • Infrastructure Update, Lightning Talks, Pre-GSoC Q&A
  • After-action review & next week's agenda (5 min)

In Attendance

  • You


View at notes.openmrs.org

Developers Forum 2014-05-15
Recording:  http://goo.gl/Jy8g2Z (audio only)
  • Burke Mamlin
  • Suranga K
  • Steve Githens
  • Jeremy Keiper
  • Ryan Yates
  • Chris Power
  • Wyclif Luyima
  • Willa
  • Elliott Williams
  • Michael Downey
  • Nyoman Ribeka
  • Ganesh K
  • Eli __
  • Karl Wurst
  • Sara Fatima
  • Ujjwal Arora
  • Tobin Greensweig
  • Lara __
  • Lukas Breitwieser
  • Joseph Kaweesi
  • Daniel Kayiwa
  • Harsha Kumara
  • Shubham Rai
  • Darius Jazayeri
Agenda & Minutes
  • Review last week (5 min)
  • Topic fest -- topics have been updated on schedule, request for feedback has gone out
  • Infrastructure Update (10 min) - Michael
  • Since last update
  • Moved/upgraded remaining infrastructure to XSEDE
  • Upgraded Confluence, JIRA, Bamboo, Crowd
  • Testing Confluence Questions to replace OSQA & better unify our documentation resources
  • switched over to etherpad-lite it supports https
  • demo.o.o used to reset server every 2 hours / 3 min of downtime each - 36 min          
  • now we reset DB every 2 hours / 6 seconds of downtime each         
  • we reset tomcat twice a day 3 min of downtime - 6 min 
  • patched all server for the heartbleed vulnerability the day it was announced.   
  • Future Plans:
  • Migrate servers to ubuntu 14.04 
  • Apache 2.4
  • Implement PFS/HSTS improve security:
  • Update to confluence 5.5 - 3 weeks (cool new project managment stuff)
  • Update on Bamboo/Crowd issues :-(
  • CWDSUP-9095: Ongoing support issue
  • Summary: Atlassian apps time out when attempting a full directory sync. Bamboo won't start up with directory integration as a result.
  • Workaround: Run Bamboo disconnected from OpenMRS ID until problem resolved
  • Opened April 4, 2014
  • Escalated internally with Atlassian development team
  • Possible bug with Crowd user management
  • Atlassian has a copy of our configuration running in an internal sandbox
  • Back-and-forth tests/discussion continues nearly every day
  • Follow-up on Connect vs. UberConference discussion - update mailing list
  • What do you like/not like about each?
  • What works well on each?
  • What doesn't work well on each?
  • Lightning Talks (30 min)
  • Chart Search (Tobin)
  • A tool for viewing and searching patient data
  • Questions/Comments
  • When showing a flowsheet, make sure to search for individual components, not just battery, when collecting data for flowsheet table.  So, for example, an individual platelet count will show in the CBC flowsheet, comprehensive metabolic panel (CMP) results that are also in a basic metabolic panel (BMP) will show in a BMP flowsheet, a BMP will be included in a CMP flowsheet, etc.
  • Need to show active patient 
  • Also the Anytime feature looks more like button not like a drop down. May be we can highlight it as a filtering option
  • Operation Theater Module (Lukas)
  • Plans for GSoC project
  • Questions/Comments
  • FYI - we are introducing "Care Setting" in 1.10 (with order entry) that will define available care context (e.g., Hospital A, Foo Clinic, Emergency Room) which will have an attribute of type like: INPATIENT, OUTPATIENT, EMERGENCY.  You may be able to leverage those in 1.10+
  • Administrative Tools for OpenMRS 2.0 (Ujjwal)
  • Plans for GSoC project
  • Questions/Comments
  • Consider combining role & privilege management, since these are very related and it has historically been very difficult for implementations to get these right.
  • Look at the "Account Management" app created for Mirebalais
  • In Record Management, filter by patient and/or date range
  • Separate data management & system settings at a high level
  • Pre-GSoC Q&A (10 min)
  • Student questions/concerns?
  • I can't say it enough: make sure that you aim for a deployable target early in the summer.  Your project will have a long life if people can come in the future and add features to a working, running, deployed module.  If you make an awesome, full-featured module that gets 99.5% done but not deployed by the end of the summer, it will likely follow many before it in sitting idle, gathering dust, and eventually being abandoned.
  • Announcements/reminders
  • Remember to use mailing lists, Talk, design forums, etc., for defining project requirements
  • Students should participate in IRC Scrum reports daily if their schedule permits
  • Students should participate in weekly developer forums if their schedule permits
  • Students must have posted a communication plan and project plan on the wiki by Monday
  • Students must publish one blog post by each weekend
  • Students must submit one status report each week by weekend
  • Requirements will be checked every Monday -- 3 misses = removal
  • Next week (5 min)
  • Orders (1.10) Update/Review
  • Review API interactions within the throwaway order UI module
  • After Action Review
  • What did you expect to happen?
  • What actually happened?
  • What can we do better?




  • Backchannel IRC transcript
  • Audio recording of the call: Listen online or download - available after the meeting