2013-3-7 Patient Data Definitions

General Info

Topic: Patient Data Definitions

Type of Project (Spike, Sprint, Epic): 

Lead (Product Owner): 

Developer Lead: 

Known Developers Assigned (amount of effort in hrs dedicated to this work if possible): 

Sprint Dashboard:

Source code at:

Date: Estimate 3/7/13

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]

  Tasks To Be Completed Prior To Design

Goals

Goals: Must Have, Should Have, Could Have and Won’t Have

Must Have means we must have this as part of the solution. It is a requirement or we should rethink doing this work.  This is what we will deliver before the end of the work period this also doubles as our DOD “Definition Of Done”

Should have means we would be embarrassed not to have it. We could technically produce the solution without it but people would be surprised.

Could have means anything else we could do.  But this does not always mean low priority.  But our selection of which could haves to include or exclude (or deliver later).  Also is considered low hanging fruit (if we are in this code already for x reason wecan deliver  y with little or no extra effort) or can be items or ideas for this module that can be packaged for a later spike or sprint.

Won’t Have means this will not happen.  It might be technically impossible, a taboo for our organization or out of scope. It does not mean “might happen or would be nice”. 

Must Have: 

Should Have:

Could Have:

(This can be moved around, just wanted to get it in one location)- CP

. Patient Data definitions

    Sprint focused on producing lots of patient data definitions (for patient summaries or data exports):

• • Obs values based on other data (CD4 count closest to ARV start date)
  • Obs values in a group that have constraints
  • Obs values in an encounter that have constraints
  • Obs values during the duration of a program enrollment
  • Order-data (drug order, regimen, order extension)
  • Current program enrollment data
  • State history for current program enrollment (or any program enrollment), by workflow
  • Address based on address template (format / converter)
  • Name based on name template (format / converter)
  • Obs values only when recorded in a particular encounter type
  • Relationships (all, or of one or more particular types)
  • etc.

Won't have:

Design

There should be multiple design meetings.  The first starts off with a small group working with the leader to determine the high level scope of the project and then to break down into smaller pieces to eventually place as tickets.  Once those meetings havehappened use of the community design meeting time should be used to refine the tickets and if possible assign them to who will be doing the work.
Risks (these should be resolved prior to or during the design meetings):

Enter anything that is still questionable or worrisome that has not been answered: (open issues, potential concerns) Once a decision is made make sure that a summarized answer is included.

Example: Q. How will we handle issues with conflicting userID’s?  A. All ID’s will have an added identifier that is unique.

Effort Accounted For: (At the end of the design call all tickets should have an estimated effort and that total should be balanced against the known available effort of the developers assigned) (Yes/No)

 If not in balance in favor of success why and the action plan for remaining items
via IRC on the [#openmrs|IRC:Home] channel on freenode.

Use this channel for ALL debugging and random questions having to do with the sprint. Please avoid direct messaging to personal contacts. If you have a question, someone else most likely does too, and our geographically distributed community benefitsfrom public group discussion.

Sprint Break down: If tickets have not already been laid out or explained this is a good place for this.

 Risks: ?

Enter anything that is still questionable or worrisome that has not been answered: ?

Effort Accounted For: ?

Sprint Break down: ?

Kickoff Meeting

Kickoff meeting Date: TBD

Kickoff meeting recording:

(Meeting setup with known developers after the final design meeting, but prior to the start date):

During Project Notes

Post Project (Retrospective)

Resources

Additional Information: