Order Entry UI Sprint 2

Owned by Betty Kebenei
Last updated: Jun 10, 2018 by Lanre Lawal
2 min read



General Information

Team Lead: Daniel Kayiwa

Sprint Lead: Betty Kebenei

Timeline

Start Date: 5th April 2018

End Date: 19th April 2018

Participants

  • Flavia Nshemerirwe

  • Fredrick Mgbeoma

  • Lanre Lawal

  • Geoffrey Asiimwe

  • Osaze Edo-Osagie

  • Betty Kebenei

Sprint Goals

The main goal of this sprint is to finish implementing the Order Entry UI that was began in the previous Order Entry UI sprint.

The sub-goals that have been moved into this new sprint are:

  1. Search for an existing drug.

  2. Adding a new drug order

  3. Editing an active drug order

  4. Discontinuing/deleting an active drug order

  5. Showing all active drug orders.

  6. Showing all past drug orders.

  7. Add a tab functionality for inpatient and outpatient.

  8. Link the Order Entry UI OWA to the patient module.

  9. Paginate past drug orders.

  10. Implement tab functionality for format of giving instructions.

  11. Implement accordion for active and past drug orders.

Sprint Dashboard

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

How To Participate

Add your name to the list on this wiki page (with any comments about your availability). If you want to join after the sprint has started just join the IRC channel mentioned above and say hello.

The general process:

  1. New to OpenMRS sprints? Want help getting started? Join IRC and say "???": I'd like to participate in the sprint!". If you get no response, just ping any of the above sprint participants as per the IRC tips at http://en.flossmanuals.net/openmrs-developers-guide/support/

  2. Pick a ticket from the available tickets in the top-left of the sprint dashboard page at:

    • Make sure it does not depend on a ticket that is incomplete.

  3. If you have any questions about the ticket, ask on the group chat.

  4. Do the ticket. See our HOWTO for git. Sprint specific git HOWTO for devs with push rights: whatever works for you :-) If you don't like pull requests, don't send them. Commit and push directly to the main repo. If you do like pull requests, fork the main repo and send pull requests, but merge them right after. My favorite way is to work on the main repo, but create local branches (without pushing them to the main repo). Merge branches locally to the master and push to the main repo.

  5. Join the daily scrum to share your updates

During Project Notes For The Sprint

To be added while the project progresses

Sprint Retrospective

To be added after the end of the sprint

Resources