Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Child pages
  • 2014-08-21 Developers Forum
Skip to end of metadata
Go to start of metadata

How to Join

 Click here to expand...

 

By Browser

By telephone

  • US telephone number: +1 201.479.2627

 

Agenda

  • Quickly review previous meeting minutes (5 min)
  • Review next meeting agenda

Minutes

View at notes.openmrs.org

 

Developers Forum 2014-08-21
Attendees
  • Wyclif Luyima
  • Paul Biondich
  • Michael Downey
  • Ryan Yates
  • Win Ribeka
  • Suranga K...
  • Ada Yeung
  • Daniel Kayiwa
  • Sara Armson
  • Mike Seaton
  • Dave DeSimone
  • Joseph Kaweesi
  • Cosmin Ioan
  • Alexis Duque
  • Geoff
  • Steve Githens
Topics
  • Topic Fest (20-30 min)
  • Getting Chart Search into OpenMRS 2.x
Notes
Chart Search:
  • What it will take to get the module into the reference application
  • Review the code in the module
  • Where to hook the UI of the reference application
  • What requirements the module has e.g metadata etc 
  • Does it have a clear owner  and some one to lead the development efforts?
  • Feedback, suggestions and questions
  • What are the allowed tokens to enter when searching?
  • Add ability to search other domain objects e.g Orders, Allergies and Problems
Topics Brainstorm:
  • How can we make documentation better *for developers*? (Content, organization, AND tools)
  • Status on CI/CD, Sonar, What we can do better in the future (Ryan Yates)
  • 2014 Year In Review: What did we accomplish? What did we expect to happen? What can we do better in 2015? (Do this in late December)
  • Providing better technical documentation for implementers? (Ada)
  • OpenMRS 2.1 planning (in September)
  • OpenMRS 2.1 retrospective (in October, after release)
  • OpenMRS 2.2 planning
  • QA (how can we get better, next steps for testing releases)
  • Problem List for Reference Application (to kick off a series of design calls on the topic)
  • "Content Modules." Can we define a standardized pattern by which a module could include metadata (Program, some Concepts, an Intake form, a Followup form a Program Completion form, a Patient Summary view, Reports, etc) and the 2.x UI would handle this intelligently without you having to do true programming? PIH thinks about this a lot. If others want to help us build this, it could be worth a dev call discussion.
  • Order Entry, round 2: Order Sets, Templates, and Order Groups (to kick off a series of design calls on this topic)
  • Best Practices for modeling medical constructs (?) and sharing these (Seaton)
  • Sharing/synchronize patient records between multiple OpenMRS server instances. Sync Module status update. Is anyone else besides PIH using this module? Discuss Master Patient Index.
  • Incorporate Atlas Module to OpenMRS distribution
  • Maven and Continuous Delivery
  • What's what in the OpenMRS ecosystem? 
  • What is the status of established, known modules (formentry modules, reporting modules)?
  • What new modules have emerged that others are excited about?
  • How can we do better at aligning the roadmaps of existing modules and development of new modules into our overall "product" roadmap/vision
  • Suggestions for modules that need development attention based on their usage
  • WIPs/Updates:
  • Bahmni
  • PIH(Mirebalais)
  • Staples
  • Infrastructure update
  • Scrum/sprint Updates
September 4
  • Best Practices for modeling medical constructs (?) and sharing these
September 11
  • OpenMRS 2.1 planning
September 18
  • Scrum/sprint Updates (Allergy Sprint)
  • Incorporate Atlas Module to OpenMRS distribution
September 25
  • "Content Modules." Can we define a standardized pattern by which a module could include metadata 
October 2
  • 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 (tentative date, pending ThoughtWorks schedule)
October 9
  • Order Entry, round 2: Order Sets, Templates, and Order Groups (to kick off a series of design calls on this topic)
October 16
  • FHIR update (Suranga)
October 23 (FYI: Google Summer of Code Reunion)
  • Providing better technical documentation for implementers? (Ada)
  • Have a brainstorm session to collect ideas how we can improve technical documentation for implementers
  • Develop simple user guide for each topic
October 30
  • OpenMRS 2.1 retrospective
November 6
  • OpenMRS 2.2 planning
November 13
  • QA (how can we get better, next steps for testing releases)
  • Suggestions for modules that need development attention based on their usage (Suranga)
November 20
  • TBD web application secuirty expert talk  (Paul to find the guest speaker)
November 27
  • Cancelled (US Thanksgiving Holiday)
December 4
  • Infrastructure update
  • Topic Fest
December 11
  • 2014 Year In Review: 
  • What did we accomplish?
  • What did we expect to happen?
  • What can we do better in 2015?
December 18
  • mUzima Demo
December 25
  • Cancelled (Christmas Holiday)
January 8
  • Problem List for Reference Application (to kick off a series of design calls on the topic)
  • Sharing/synchronize  patient records between multiple OpenMRS server instances. Sync Module  status update. Is anyone else besides PIH using this module? Discuss  Master Patient Index.
January 15
  • Status on Maven CI/CD, Sonar, What we can do better in the future (Ryan Yates, Mike Seaton)
January 22
  • What's what in the OpenMRS ecosystem? 
  • What is the status of established, known modules (formentry modules, reporting modules)?
  • What new modules have emerged that others are excited about?
  • How can we do better at aligning the roadmaps of existing modules and development of new modules into our overall "product" roadmap/vision
January 29
  • How can we make documentation better *for developers*? (Content, organization, AND tools)

TODOs

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

Summary Assignee Created Due
Loading...
Refresh

Create a TODO: http://go.openmrs.org/todo

Transcripts

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

 

 

  • No labels