In clinical abstraction. data accuracy impacts efficiency, client relationships, and user satisfaction.

As case forms are completed, they are sent to a governing body which reviews it for accuracy prior to accepting the case information into the research database. Cases found with errors are returned to the abstractor for correction.

Prior to this feature, form issues were visually indicated line by line within the form. By creating a visual summary of form issues, the user could quickly address fields issues that would block submission.

User interviews, competitive analysis, and stakeholder input helped to identify key feature goals as:
A) Eliminating external workflow tools
B) Improving initial case pass rates by catching errors prior to submission.

Constraints for this project were limited development resources, and quick turn around time. In order to meet the project goals, I worked closely with product and development team members to create a detailed workflow definition. This allowed for team alignment and early identification of edge cases that would impact user flows.

The workflows demonstrated additional needs for the feature, including required field designations, and case status markers that could be adjusted by permissioned users. Workflows also demonstrated additional asserts needed by the front-end development team, such as various state changes and user messaging.

After several design iterations, the final hand-off included high-fidelity wireframes as shown above.

Challenges in this project included space limitations, and creating the summary as a parallel workflow to the data collection form. This required simplifying complex error types both visually and in the copy. The final design includes five key validation types and three descriptors to help the user prioritize issues. Text links scroll the form to the relevant field, and buttons change case status throughout the system.

Leveraging previously developed components and warning color palettes limited the burden on the development team and limited learning time for users.

A feature is rarely isolated within a product, and though the main component of this feature was the validation modal, additional workflow updates were required to create seamless functionality.

Supporting UI/UX assets were created for new form functionalities, status notifications, and user messages. Updates to the case management table allowed quick assessment of validation status, which is utilized by the abstractor, management, and in client case review.

Actionable documentation is a key part of the final deliverable. This includes a design file with specifications, development assets, content copy, workflows, and access to the design library and UI guide.

A file tracking system links handoff documents to additional design resources, such as research and design rationale notes, and maintains version control.

Detailed ground work on this project helped support quick development, and collaboration with QA and development team members allowed feature integration with few issues.

As anticipated, the MVP version of validation reduced the need for external tools and improved the pass rate of case review. Building on this success, v2 will include additional capabilities and integrate user feedback.