Subject: Exported From Confluence
Content-Type: text/html; charset=UTF-8
General Feedback Mechanism (Design Page)
General Feedback Mechanism (Design Page)
The intention of this project is to provide a mechanism for users to co=
mmunicate with system supporters/admins with system-related (not patient-s=
pecific) messages. For example:
- "The system is running much slower than usual today."
- "We need a diagnosis term for Sarcoidosis."
- "This system would be better if I could more easily find my pat=
ient's lab results."
- "I tried to select BOB SMITH and got this error" (with scr=
eenshot and a snapshot of recent log exceptions attached)
Ideally, this is ubiquitously available in the interface in a simple &a=
mp; intuitive format =E2=80=93 e.g., a "Feedback" link (or button=
) or an option under "Help" like "Send Feedback" that =
pops up a simple form.=C2=A0 When feedback is submitted, the user receives =
confirmation and the feedback is forwarded to the system administrator.
- Experience with java programming
- Familiarity with JSP and servlet programming
- Build an OpenMRS module
- Add a "Feedback" link to the OpenMRS header
- Collect feedback through a modal form
- Create an administration screen for viewing and managing feedback
- This is best served by a =
module instead of being built into core OpenMRS.=C2=A0=C2=A0 The module=
should link to an extens=
ion point in the header of the page to provide the same access througho=
ut the app.
- The feedback form could have options like "Report a problem&quo=
t; (default), "Request a new feature", etc. followed by a texta=
rea and a submit button.
- When the form is submitted the user should receive some form of conf=
irmation ("Thank you for your feedback")
- The text entered by the user should be saved along with context (e.g=
., page they were on) in a row in a feedback table created by the module.
- The feedback table contents should be displayed in a jsp page so tha=
t an admin can see all feedback, delete feedback, act on it, etc.
- Since feedback could contain sensitive patient information, we want =
to avoid sending feedback content directly over e-mail.
Ordered by priority
- You have a bordered b=
ox in a popup dialog, which gives unnecessary nested borders. Get rid of th=
e box. Done : http://twitpic.com/5xf02w/full .
- Allow multiple commen=
ts for a feedback item : Done.
- Allow admin to set an=
e-mail address to receive notifications of new feedback entries =E2=
=80=93 e.g., the admin may w=
ish to receive an e-mail with convenient links to act on the feedback (e.g.=
, single-click options to "delete", "-mark as duplicate", "forward to OpenMRS as bug", etc.)- : Done , screenshot=
s : http://twitpic.com/5xrtr9/full
- Allowing for the simp=
lest use case of clicking a feedback button, writing a comment in a textar=
ea, and submitting =E2=80=93 i.e., provide a default for other fields or m=
ake them optional. ( Source : Link ) : Done
- No need for Index col=
umn in predefined subject edit form ... Done , screenshots : http://twitpic.com/5xj1oo/full , http://twitpic.com/5xj1sh/f=
ull , http://twitpic.com/5xj1vo/full
- Why are times not bei=
ng stored? I only see dates for what should be a datetime column Don=
e: Now changed to the timestamp in liquibase.xml file : http://twitpic.=
- Rather than "Add=
Severity" and "Add Status" perhaps use "Severities&quo=
t; and "Statuses" ... "Stati"? Done , screenshot=
s : http://twitpic.com/5xjho2/full and http://twitpi=
- In case you add a se=
verity after the module has been running for a while, you should be able t=
o put it in the middle of the list, where it belongs. (Same for status.) (=
adding a "sort_weight" column to each of the two tables?) =
Done will be seen as of very next commit after commit 22100 .
- "Creator" s=
hould probably display the default PersonName rather than userid ... unless=
that is a requirement. : Done : http://twitpic.com/5xgc02/=
- It would be nice for =
the admin to be able to define what text is shown to the user after they s=
ubmit. It could just be stored as a global property. - Ben Wolfe (=
- In Manage Feedback, c=
hange Date Submitted to age (e.g. "yesterday"). Added Supp=
ort to : http://ocpsoft.com/prettytime/ , screenshot : http://twitpic.com/5xit6d/full=C2=A0 is this okey ?
- Perhaps show example =
of "default" selections for subject and severity level. : =
- Can the simple edit f=
orms be done in a popup dialogs?=C2=A0 (same for other one-liner phrases)<=
- Provide a simple mech=
anism for the admin(s) to forward feedback to OpenMRS when appropriate (e.g=
., bugs reports) =E2=80=93 i.e., after removing or ensuring there is no ide=
ntifiable patient information in the content. Done.
- Allow the admin to ed=
it templates for e-mail notifications (both confirmation to user and notifi=
cation to admin)
- Optionally e-mail the=
user confirming that the feedback was received with a "ticket num=
ber" to uniquely identify the feedback : Done.
- Put some example subj=
ects, severities, etc into the module.This will let people test it immediat=
ely and help guide them towards what kind of subjects/severties, etc they s=
hould use. Done.
- Add a "cancel" to form when editing a subject.
- Why do I see "fe=
edback.notification.number.error" as the message after adding a subjec=
t with an invalid priority?
- Add a description aft=
er the priority input box so users know what/why/how/who/when it is.=
- Make the priority inp=
ut box a lot smaller.Only needs to be big enough for a few numbers=
- Edit subject page has=
- Remove the help text =
on the edit page, its confusing because it doesn't look like the page chang=
ed at first
- Rename the help secti=
ons to all just have the title of "help"
- Reword the help to be=
something like "This is used for ...." or "this is meant to=
- The second like shoul=
d be "Example statuses are: "", "_"
- When using the "submit feedback" in the upper right, don't=
redirect the user to the "Add feedback" page after they have com=
pleted.Just let them stay where they are.After clicking "submit" =
it should be like they just clicked the "X" on the modal popup.=
- After submitting feed=
back either from the Add Feedback page or using the Submit Feedback form, t=
he success message is squished in half and unreadable : This will be=
solved once defaults are put in the settings.
- Why do you have both =
"Manage Feedback" and "Submitted Feedback" in the list =
of links?=C2=A0 You should only need one : Holding this for now as M=
anage Feedback is for listing of all feedback whereas Submitted feedback is=
to list the feedback submitted by currently logged in user.
- Match the order of li=
nks in the local header to those in the admin extension point.Use a LinkedH=
ashMap in the admin extension point java class if you aren't already so tha=
t its sorted on order of entry instead of randomly : Already using t=
his, now fixing order now.
- Rename "setting&=
quot; to "Settings"
- Put defaults in the s=
- Add descriptions next to the settings boxes so users know what they =
- Change EMail > Ema=
- Email Id > Email Address
- The email boxes don't=
need to be so huge
- The message boxes pro=
bably don't have to be so big either. : Assumed this is Feedback Mes=
- Add "label"=
html tags on the user preferences pages.=C2=A0 Its a nice little addition =
to radio buttons to make them more usable by users.=C2=A0 You have to set a=
certain attribute on the label to the id of the radio button it controls.=
=C2=A0 Look up that syntax, I don't remember it.
- --User Preference --> User Preferences-