Overlord - UX/UI Design

Spring 2012 //

Long time ago, I worked a contract for this EHR company. Not a huge EHR like Epic for hospitals, but a smaller EHR for private practices and things like that. After the contract was complete I had some time to work with Client Services.

They conveyed to me that they had no way to tell how people were interacting with the system. They wanted a custom solution, and since I was still under contract this is what we designed.

Working with the CS people (our stakeholders in this case) I was able to create a list of all the "actions" that a user can take on the system: create a patient, schedule an appointment, for example. Collaborating with the front end developers I defined the set of parameters that would constitute a successful event, like when a person successfully added a medication to a list. The little number in parentheses is the amount of times the user has taken an action on the system. Our Client Services people are primarily looking for the "0's" that way they can call up the client and ask, "How come you've never added an allergy?" and guide the customer through the tasks they are struggling with. Honestly it seemed a little overlordy to me, but if it's for the sake of usability (which they promised me it was) I'm all for it.