2012-06-30 Pharmacy Meeting

Owned by Nathan Leiby (Unlicensed)
Last updated: Jun 29, 2012Version comment
2 min read

====================================================
Pharmacy meeting -- June 29, 2012 at 10-11am IST
====================================================

Participants: Jeff Hung (Unlicensed), Yan Jin (Unlicensed), John V Stoecker (Unlicensed), Surajit Nundy, Nathan Leiby

iDart port status

  • followed guide on how to make a module in OpenMRS
  • used module as a template
  • added tables
  • built hibernate classes for the iDart tables (surface, pojo, dao)
  • todo: xml file

REST calls for pharmacy

  • can be built directly on current implementation? or need a service layer in between? (ex. creating a stock center)
  • we're using OpenMRS 1.9 in Raxa

Development Approach

  • prioritize just Raxa needed functionality
  • probably easier to bring tables over with full fields, instead of removing them ... get it working faster
  • try to select parts that are non-overlapping with existing OpenMRS (just the drug-related parts)
    • in OpenMRS, already has ~5 tables for drugs (drug, drug ingredient, orders, ...)
    • visual datamodel ... helps show which tables are "drug related" in iDart
  • want to use the Raxacore repo: https://github.com/Raxa/raxacore

Joining Raxa community

  • how to simplify things to learn... lots to sort through!

Followup

  • Share Raxacore knowledge ( TODO-42 - Getting issue details... STATUS )
    • Share simple REST client ... REST Client FireFox addon
    • Share some examples of REST in Raxacore
    • Explain how to use / commit to Raxacore https://github.com/Raxa/raxacore
    • pull requests for Raxacore -- give at least one pharmacy team member (whoever wants to be gatekeeper) permission to accept pull requests on raxacore repo
  • Design Review of Raxa pharmacy screens ( TODO-43 - Getting issue details... STATUS )
    • Connect Jeff and others to Pharmacy UI designer for Raxa to walk through our designs
    • Share a google doc to manage design questions / feedback
  • Pharmacy REST services ( RAXAJSS-234 - Getting issue details... STATUS )
    • Get "1 screen working" (or even part of a screen) with REST calls, etc (useful, simple screen - "stock management" or "inventory" (p18 onward)))
    • Umbrella ticket for Pharmacy REST calls
    • a few Subtasks based on this call
    • can add additional sub-tasks as we progress
    • Alerts: determine alert datamodel ( RAXAJSS-237 - Getting issue details... STATUS )
  • meet again within 1 week
    • 1-week goal is to "complete 1 page end-to-end" (likely p19 from v4 pharmacy designs)
    • want to get at least some of that page's functionality exposed via REST