2014-11-13 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)
  • WIP from Bahmni update on work their doing on top of the new order entry API in 1.10
  • WIP from Sara and ThoughtWorks on Concept Management Module
  • Showcase for Allergies
  • Review next meeting agenda


View at notes.openmrs.org


OpenMRS Developers Forum 2014-11-13
Recording: http://goo.gl/kaP0yw (MP3 audio) https://connect.iu.edu/p1lfamoh95c/ (Adobe® Flash®)
  • Burke Mamlin
  • Michael Downey
  • Ryan Yates
  • Nyoman Ribeka
  • Sara Armson
  • Mike Seaton
  • Ms Beens 2 (?)
  • Ravinder Kumar
  • Vivian So
  • Shruthi Dipali
  • Bharti Nagpal
  • Wyclif Luyima
  • Ada Yeung
  • Karl Wurst
  • Darius Jazayeri
  • Serghei Luchianov
  • Shasha _
  • Daniel Kayiwa
  • Stephen Winter
  • Jonathan Teich
  • Rafal Korytkowski
  • Joseph Kaweesi
  • Alberto _
  • Paul Biondich
  • David DeSimone
  • Ellen Ball
  • Review last week TODOs (OpenMRS 2.1 Retrospective)
  • Burke will summarize OpenMRS 2.2 planning & share with community
  • Someone will Invite Bahmni team to present their OpenERP integration as a form of billing support OOB for OpenMRS RA
  • Someone will Invite PIH to present "2.0-ified" appointment module for potential RA integration
  • Someone will Be explicit with an upfront process that will allow participants in this call know how their input will help determine what actually makes a release
  • Someone to Identify which module(s) are demonstrating best practice
  • Burke to Get updates to Modulus on OpenMRS Technical Road Map – specifically, ability for implementer to enter comment on module and ability to rate module.
  • WIP from Sara and ThoughtWorks on Concept Management Module
  • Ability to retire a concept and merge its references into another
  • Works on 1.8 and working now for 1.9.7, aiming for OpenMRS 2.x support
  • Questions
  • What references are udpated? Obs, forms, others?
  • obs, drug, drug ingredient, orders, field, program, program workflow, program workflow state, person attribute type, concept, concept answer, conceptn name, conept set, concept numeric, concept complex
  • For 1.9+
  • drug ingredient
  • What if concepts have different datatypes?
  • User is prevented from merging incompatible pages
  • What about concept references in HFE and X/Forms?
  • Consider search & replace within HFE
  • WIP from Bahmni update on work their doing on top of the new order entry API in 1.10
  • Basic order entry functionality for medications
  • Users can order in simple form or in a variable dose (i.e., 1 tab morning, 2 tabs midday, 1 tab evening)
  • Users can renew orders, discontinue orders, refill orders
  • Questions
  • In the demo, it looked like Warfarin 1 mg (Tablet) was ordered twice.  Are those consecutive orders (e.g., renewal when the first one expires)?  Or are those both considered active?  The OpenMRS API should not be allowing two or more orders for the same formulation active at the same time.
  • There are circumstances where it should (a regular dose of morphine and a conditional dose, or a set of sequential/tapering dose) but the UI should carefully validate that with the user
  • What does the color coding mean to the left of the prescriptions?
  • Yellow/orange = "active"?
  • Green = "scheduled to become active"?
  • It would be good to have a table of "all new pending changes" or "all changes that you are about to sign for" -- including adds, changes, refills, and stoppages that you have just entered
  • Drugs that are finished (past their stop date or their duration) should come off the active list.  
  • (A separate function can allow you to view all drugs ever given.)
  • I would separate out the active current drug list from any other display (e.g., of drug changes entered on one given date). The active drug list is the most important clinical display
  • Happy to talk about this more -- 
  • Serghei L: I second the active drug list for two reasons: Pharmacist requirements & Physician requirements. Both of those need to see active drug list. For the billing purposes only the dispensed (not necessarily the same as prescribed) drugs need to be seen.
  • One other function we've started to talk about is using the UI to print prescriptions (for outpatients).  
  • Nicely done!
  • +1
  • Showcase for Allergies
  • Added ability to record allergies within OpenMRS 2.x
  • Allergies listed on patient dashboard
  • Questions
  • Did this work influence the style guide at all?  For example, unselectable radio buttons?
  • Action items in row made it.
  • Unselectable radio buttons have not been added to the style guide.
  • Nuances of drug lookup, especially when matching a synonym for a concept, are being refined
  • Is there REST support for allergies?
  • DJ: I think the ticket probably should go in the Allergy project, not RESTWS.
  • Darius:  allergy project?
  • After action review
  • Cancelled due to lack of interest in reviewing ourselves
  • What did you expect to happen?
  • What actually happened?
  • What can we do better?
  • Preview next week
  • Web Application Security w/ Sherif Koussa CEO of SecurifyLabs 



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