Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

General Sprint Information:

Lead (Product Owner): 

Developer Lead: Wyclif Luyima (wyclif@openmrs.org)
 
Known Developers Assigned: Mujir, Sushmitha, (more to be added)
 
Key Contributors: Bahmni, Kenya EMR
 
Kick Off - Friday, 13th Dec, 2013. Time: TBD 
 
Sprint dashboard: https://tickets.openmrs.org/secure/RapidBoard.jspa?rapidView=44
 
Source Code: https://github.com/openmrs/openmrs-core/tree/1.10.x

Sprint Goals:

The overarching goal of OrderEntry is to provide an order entry service capable of supporting simple outpatient orders, focusing initially on medication orders and tests but allowing for other types (referrals, nursing, etc.).
 
With that in perspective, the focus of the current sprint is to:
 

  1. Place an drug order. Medication and Test
  2. Retrieve a drug rode for a patient: Active & discontinued
  3. Revise an existing drug order for a patient
  4. Discontinue an existing drug order 
  5. Search from an existing drug inventory and prescribe medicines from for a patient.

 

Design:

Pending design queries:

To be added

Effort Accounted For:

Effort Estimated: To be added after the kick-off meeting

KickOff Meeting:

Meeting details:

Day & Date: Friday 13th, 2013

Time:

Dial In:

Hangout:

Kickoff meeting recording:

 

How to Participate

 

This first sprint for the Appointment module will not be advertised to the whole community however those interested in working with us on future sprints should contact us!

 

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 [the IRC channel|IRC:] and say "???": I'd like to participate in the sprint!"
  2. Pick a ticket from the available tickets in the top-left of the sprint dashboard page. (listed below)
    • 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|docs:Using Git] 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.
    # [Join the daily scrum to share your updates|https://wiki.openmrs.org/display/RES/Daily+Scrum+Meeting]

    h2. Tasks To Be Completed Prior To Design
    composition-setup: Unsupported icon type: wikicloak.toggle.type=wiki

During Project Notes for sprint:

To be added while the project progresses

 

Sprint Retrospective:













  • No labels