UX Redesign From 3rd Sep 2013

• Technically speaking, each installation of OpenMRS has its own dictionary.
  • In the examples below, this role is filled by a lovely fictitious gentlemen named "Dave".
• The big dictionary in the sky is called MVP/Ciel.
  • This main dictionary that can be downloaded by local OpenMRS implementations
• Andy Kanter, who is a real person, is the main dictionary manager.

Dictionary Downloads (Out of Scope)

• When a local administrator (referred to Lynette below)  downloads a new version of the MVP/Ciel, there is automatic mapping that happens between the concepts in her local dictionary and the ones in the new MVP/Ciel. 
• This is existing functionality in another module, so we don't need to worry about that part. the status that concepts receive in the CPM don't interfere with this mapping

• Whenever she wants, Lynette the local admin can create a new form on her own machine/local installation, and can create several new concepts.
  • This functionality already exists. 
  • It's how Lynette usually does things for her own clinic
    • See http://ec2-54-245-1-154.us-west-2.compute.amazonaws.com:8080/openmrs/dictionary/index.htm
  • Therefore, we want the CPM to give Lynette the ability to send mulitple concepts she has already created, along with some information, within a single proposal.
    
    • This proposal will be sent to a dictionary manager. 
    • This dictionary may be the MVP who's manager is Andy or a different dictionary who would have a different dictionary.
      • Which dictionary this is, is determined by the CPM's settings (in scope).
• We asked about changing the 'create new concept' flow to include a 'submit for review button'. This is not technically possible.
• Forms can be in various formats, anything from HTML to MS Word. Lynette cannot always send her form to a dictionary manager with the proposal (and can only send a group of individual concepts), but it would be nice if she could add a screenshot or some other attachment.
• As above, Lynette needs to be able to send her concept proposals to Andy Kanter, or to a dictionary manager of another hospital (this is often true of local admins within PIH).
  • We forgot to add this settings bit out of our screen flow thinking - need to do.

• The Local Adminstrator (Lynette) and the Dictionary Manger (Dave) - either of the MVP or another hospitals' dictionary - will now both operate from dashboards that look similar to each other.
• Each persona/user type has 3 screen views:
  • A dashboard showing all proposals
  • A single proposal (which will be a link that opens it), where discussion happens about the proposal occurs.
  • A single concept within a proposal (which will be a link that opens it), which is identical to the current OpenMRS concept view, except with added 'status' (e.g. http://ec2-54-245-1-154.us-west2.compute.amazonaws.com:8080/openmrs/dictionary/concept.htm?conceptId=955)
• Some changes will be made to the columns that each person sees on their 3 views. See the photos below.
• Most of the discussion between Dave and Lynette will happen on the View page. 
  • It would be nice to have inline comments back & forth, like in facebook, but this is probably something for v2.
• Lynette can add comments to a single concept before submitting, Dave can't. Dave will add his thoughts in the discussion section of the whole proposal
• When Lynette is on her dashboard (which displays the Proposals she has created) and Dave has done something new on one of her proposals (e.g. changed status, added notes), the proposal will look different somehow to notify her of this (TBA, but e.g. bold, colour, icon, etc.). 
  • Same is true for Dave (who's Dashboard shows Proposals he has been sent) if Lynette changes something.
• The status of a proposal can be: 
  • Draft
  • Submitted
  • In review
  • Accepted
  • Rejected
• The status of a individual proposed concept (within in a Proposal) can be: 
  • Nothing
  • In review
  • Accepted
  • Rejected [may need to discuss finer points of this]
• Dave can reject one or more concepts within a proposal, while accepting the proposal itself (and all the rest of the concepts within it)