Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Child pages
  • 2014-09-25 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)
  • "Content Modules." Can we define a standardized pattern by which a module could include metadata
  • Review next meeting agenda

Minutes

View at notes.openmrs.org

 

Developers Forum 2014-09-25
Recording: x (audio)  x (Adobe Flash)
 
Attendees
  • Michael Downey
  • Ryan Yates
  • Nyoman Ribeka
  • Burke Mamlin
  • Ada Yeung
  • Paul Biondich
  • Sara Armson
  • Wyclif Luyima
  • Darius Jazayeri
  • Mike Seaton
  • Willa
  • Daniel Kayiwa
  • Karl Wurst
  • Mike Seaton
*** Reminder: September Support Sweep contest for contributors! Win swag! http://om.rs/s3
Agenda & Notes
  • Review last week's outstanding TODO's (OpenMRS 2.1 Planning)
  • TODO: Burke to schedule a dev forum to revisit future release process/scheduling/strategy
  • TODO: Schedule next round of Allergies tasks (don't drop the ball -Darius)
  • TODO: Sara will email TW & Bhamni team to ask for which week later in October works and we'll swap topics
  • "Content Modules": Can we define a standardized pattern by which a module could include metadata
Background
  • A lot of content with OpenMRS is used within the scope of a particular "program" – e.g., for HIV Care, for Chronic Care, for Tuberculosis, etc.
  • It's difficult for implementations to easily manage, communicate, exchange, or update the metadata related to a particular "program"
  • For example, someone looking for best practice (or any material) to treat condition X doesn't have a clear place to go to find examples of what others are doing
  • We'd like to give people a recipe for a new study or program to create X, Y, and Z and then package those into a collection of content (metadata, forms, and reports) that could be delivered to a system.  Ideally, there would be a path to update these as well.
Design
  • Example from KenyaEMR (email to dev list from Rowan)
  • OpenMRS Content-Related Application Particulars = .OCRAP files
TODO
  • Get KenyaEMR team to describe how bundles are delivered
  • How are they packaged (do they have to be baked into core applicationContext? Delivered via module?)
  • What infrastructure changes exist to incorporate the bundle
  • Schedule design call(s) on how 2.x UI should handle the bundled content and including programs
  • 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
  • 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 

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