Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: JIRA Issue macro params updated with additional server info

...

  • Share Raxacore knowledge (
    Jira Legacy
    serverJIRA (raxaemr.atlassian.net)
    serverId8276eef1-ac20-3511-8661-137e963e10ff
    keyTODO-42
    )
    • 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 (
    Jira Legacy
    serverJIRA (raxaemr.atlassian.net)
    serverId8276eef1-ac20-3511-8661-137e963e10ff
    keyTODO-43
    )
    • 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 (
    Jira Legacy
    serverJIRA (raxaemr.atlassian.net)
    serverId8276eef1-ac20-3511-8661-137e963e10ff
    keyRAXAJSS-234
    )
    • 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 (
      Jira Legacy
      serverJIRA (raxaemr.atlassian.net)
      serverId8276eef1-ac20-3511-8661-137e963e10ff
      keyRAXAJSS-237
      )
  • 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