Child pages
  • 2015-09-17 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 http://connect.iu.edu/omrsdf. 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/IRC

  • Chat is available in the Adobe Connect meeting room (see above).
  • A backchannel meta-discussion during the meeting also occurs on IRC.

Agenda

  • Quickly review previous meeting minutes (5 min)
  • WIP: AMPATH Update (showcase of their new POC system)
  • Review next meeting agenda

Minutes

OpenMRS Developers Forum 2015-09-17

Audio Recording: https://goo.gl/0x2XNQ
Attendees
  • Burke Mamlin
  • Nicky Kibor Kimaina
  • Erick
  • Willa
  • Michael Downey
  • Ali Habib
  • Serghei Luchianov
  • Daniel Kayiwa
  • Wyclif Luyima
  • Ada Yeung
  • Simon Savai
  • Melissa Kornspan
  • Suranga Nath Kasthurirathne
  • Alfayo Kwatuha
  • Allan Kendagor Kimaina
  • Elly Makuba
  • Saptarshi Purkayastha
  • Darius Jazayeri
  • Jonathan Dick
  • Sri Maurya Kummamuru
Agenda/Notes
  • Review last week's TODOs:
  • Topic Fest: TODO's were simply to add the schedule & notify presenters
  • Get Project Buendia slides and post
  • TODO: Begin looking at "Getting started as a developer" page each week in PM call
  • TODO: Create filter(s) for recent curation
  • TODO: Create filter(s) for recently completed priority tickets
  • TODO: Create a page summarizing these metrics (filters)
  • WIP: AMPATH Update – showcasing their new POC system
  • Using Angular, Angular Formly, REST
  • Patient search, Encounter entry for providers, and basic reporting (e.g., upcoming appts and defaulters)
  • Interact with both native OpenMRS application and a custom ETL server (based on node js) to serve data (raw and calculated)
  • Angular-based Forms using Angular Formly library (handles rendering/processing of forms)
  • Pages contain sections contain questions
  • Pages are rendered as tabs
  • Sections are panels/blocks within a page's tab
  • Questions are listed in order
  • Currently using UUIDs, but plan to allow reference term
  • ETL server
  • Nodejs + HAPI (a node library, not Java HL7 API)
  • Scripts running as cron jobs transform OpenMRS data into an ETL db (flat tables)
  • Reporting features are querying the ETL database
  • Duplicating some features in core or done by others
  • Login
  • Routing
  • Form Entry
  • Plan to use something like ionic to make a thicker app to be used offline
  • Questions?
  • How does this interact with OpenMRS?
  • Angular app deployed in Tomcat next to OpenMRS
  • Uses REST to get data
  • How does this compare to JSON forms?
  • JSON forms was created for the pharmacy system and is not still used.
  • Did AMPATH try HTML form entry? Why not use it?
  • Focusing on building an app that would run on mobile devices (especially tablets used by providers) as easily as desktops.
  • Have you found REST services adequate?
  • ~90% was working
  • Had to do some fixes to RESTWS module
  • After Action Review
  • What did we expect to happen?
  • What actually happened?
  • What can we do better?
  • Next week:
  • Overview of what OMRS support and does not support
  • RefApp 2.3 review

 

Transcripts

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

 

 

  • No labels