Closed mapsam closed 9 years ago
An administrator may be looking at the history to do an audit or to evaluate staff performance. They will probably want information on the referral history of a patient population for a given time period.
Right now, such information is probably best available as a CSV dump of:
A navigator would want to know past values of certain fields, particularly contact information (this was mentioned explicitly by at least 3 different navigators). They would also want to know where else a patient has been seen, for the purpose of making better referrals, or being able to get more details about the patient's history.
A screener would likely want to know where else the patient had been seen, particularly if that information would help determine eligibility or (in the case of being ineligible) deflect the patient to a more appropriate place.
An in-context link example:
Seems like separating "events" (visits/shares) from "edits" would be important. Let's focus on patient information first - and once we have user roles established we can work on views for user statistics.
:+1: for in-context edit history. Going to do some mockups for in-context edit history in #27
:+1: for patient details view of visit/share history in #28
When looking at a patient's edit history, how do we visualize each edit and important events?