Falcon EHR

Falcon Electronic Health Record (EHR) is a Nephrology-specific application dedicated to serving practices in the office and the dialysis center.

Healthcare IT is known across the industry for poor usability, and for two years I worked as a UX/UI Designer and Agile Product Owner to re-create features of the EHR in a usable way.

▼

Drug Interactions Redesign

Roles: UI, UX, Product Owner

Problem:

Drug interactions are difficult to read and cause alert fatigue by popping up and interrupting the providers desired workflow. This can lead to medical care providers overlooking important drug interactions that could affect their patient's health.

Competitive Analysis:

Other health record software displays alerts in order of severity; however each interaction must be overridden one by one – a point of contention because it slows the user down.

Solution:

Show an alert on the medication field, and when clicked call up the drug interaction pop up. Display the interactions in categories (drug-drug, condition-drug, drug-allergy, and precautions respectively) filtered by severity, and allow the user to override all alerts by selecting one of the several preset reasons or enter their own reasoning.

Health History Redesign

Roles: UI, UX, Product Owner

Problem:

The patient Health History is not accessible outside of an encounter note and must be copied forward into each encounter note to avoid loss of data. The Health History also does not allow for custom problems to be added to the Past Medical History or Family Health History sections.

Solution:

Move the Health History into the patient chart, a static historical view of the patients record where it can be viewed at any time without an encounter note present. Link the Health History to a DB table to ensure that data is always present. Add the ability to add custom problems to the Past Medical History and Family Health History.

PQRS Attestation Redesign

Roles: UI, UX, Product Owner

Problem:

PQRS (Physician Quality Reporting System) is a CMS program aimed at measuring the quality of care a provider gives their patients and then adjusting their Medicare reimbursements according to how they score in comparison to their peers. Providers struggle to understand the requirements of each quality measure and how to properly report on them. This ultimately impacts their Medicare reimbursements.

Solution:

Move the location of the PQRS attestations out of the bill and into the encounter documentation, so that they can be accessed easily from a place where the provider already goes when patients are in the exam room. Work with the legal department to come up with more user-friendly, but still accurate, measure and attestation language. Link out to the CMS PQRS website, allowing the user to further examine the PQRS measures if they still have questions.

Daily Schedule Redesign

Roles: UI, UX, Product Owner

Problem:

The daily schedule did not exist in an installable desktop application that was created for use in the office. Older versions of the daily schedule from other apps were difficult to read.

Solution:

Create a graphical timeline representation of the providers day, color coded for visit completeness, no shows, and out of office time blocks. Include important information like room # where checked in patients can be found and the type of visit the patient is coming in for.

Snippet Redesign

Roles: UX

Problem:

Snippets (inserting saved comments) are difficult to understand, and many users do not know that they are present. The feature also works very differently in the companion iPad application, causing further confusion.

Solution:

Collaborate with iPad UX Designers to create a more intuitive desktop snippet workflow that complements the iPad’s snippet functionality. In usability testing, it became clear that moving the "Create New Snippet" ”button to be more prominently placed at the bottom of the snippet quick list and allowing users to add titles to their snippets via the desktop were the main attributes that would benefit our users.