Hi,

Thank you to everyone who helped in testing the 1.9 nightly, most of the
issues reported are related to making changes in the UI and it's workflows.

Below  is the summary of the feedback. (Can we go through these on today's
design forum and decide what to work on?)

   - Created TRUNK-2693 <https://tickets.openmrs.org/browse/TRUNK-2693> -
   Allow future dates for PersonAddress.stopDatetime *(committed fix)*
   - Encounter field tag still displays 'null' for null location, (this is
   related to TRUNK-2670
<https://tickets.openmrs.org/browse/TRUNK-2670> - Encounter
   field tag should not display 'null' string for encounters with null
   location)
   - The Encounter search textbox on 'manage encounters' page needs to be
   widened to make all the text visible
   - When a visit is saved succesfully, should we redirect back to the
   patient dashboard rather than sending the user back back to form?
   - Would be nice if the user could view visit/encounter in a popup on the
   patient dashboard
   - Cancel button on edit visit page should take the user to the patient
   dashboard* (fixed this in rev:23690)*
   - there is a comment suggesting fixing
TRUNK-422<https://tickets.openmrs.org/browse/TRUNK-422> - Edit
   / View of previous forms should merge into a single interface paradigm
   - When a user creates a visit, most likley they don't want to edit it.
    Probably they want to start an encounter, or view patient dashboard. It
   would be nice if they didn't have to make another click to see the page with
   the next step.
   - Someone reported something that would depend on the fix for
TRUNK-2647<https://tickets.openmrs.org/browse/TRUNK-2647> - In
   the Edit Visit page, startDatetime and stopDatetime need time pickers
   - Manage encounters:  configure visits - they like that there's a default
   behavior. The language is confusing: "*Choose Encounter Visit Handler
   which will be used to automatically assign Encounters to Visits".  Can it
   say something like "What should happen when a new encounter is created?"
   and then the two options?*
   - *On the short patient from, the first identifier should be marked as
   preferred by default.*
   - On patient forms, address start date should default to today
   - On the patientdashboard, can we support creating  a person on the fly
   when adding a relationship?
   - For pediatric visits, there's always a caretaker listed for the
   patient.  how is this represented in the Visit API?
   - Viewing of the visit tab should be role based and not on a global
   property.
   - Should the list of visits on the create/edit encounter page be a select
   vs autocomplete?  This related to
TRUNK-2285<https://tickets.openmrs.org/browse/TRUNK-2285> -
   Add a reusable visit widget
   - Would be nice to be able to  add/remove encounters from the patient
   visits portlet without having to go to the edit visit page


Wyclif

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to 
[email protected] with "SIGNOFF openmrs-devel-l" in the  body (not 
the subject) of your e-mail.

[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]

Reply via email to