PROJECT: HOSPICE END TO END UX
competitive analysis > user research > information architecture > prototype > user testing > revised prototype > design collaboration > implementation > continuous iterations
Project context
-
I helped the local hospice recognize a major pain point in their systems by using paper patient records, identify an online database tool, guided their team through requirements gathering and building a proof of concept, and then into design iterations and launch.
-
3 team members: executive director (budget, HIPAA & organizational requirements), subject matter expert and implementation manager, my role = Strategy, Information architecture, UX
-
HIPAA certified, main use will be on client wifi or cellular data on tablets, use in demanding environments
-
Paper forms, Excel, Knack
-
April 2020 - current
Defining the problem and platform research: April 2020 - August 2020
Proof of concept: August 2020
Phase 1 build: September 2020 - January 2021
Launch: January 18, 2021
Iterations and Phase 2 build: January 18, 2021 - current
The story
Background
In a pandemic filled world my friend and I were out for a socially distanced walk - to check in on each other and share information on to navigate these new waters. She told me about long hours on the phone transcribing notes the hospice nurses had from video “home” patient visits into the physical patient files back in the office where only she was allowed for COVID-19 safety precautions.
It was A LOT. Not only were they trying to navigate COVID-19 with terminally ill patients, their previous system wasn’t easily supporting the nurses in this online care environment.
Platform research
Based on my experience with Knack, I identified it as a viable solution for their electronic health record needs. I advised the organization to conduct due diligence, ensuring the platform met their specific business, privacy, and security requirements.
In August 2020, the project received approval for a pilot phase. I volunteered my expertise to lead the information architecture and develop a proof of concept for board review.
Guided by the Design Justice principles, my approach prioritized:
User-centricity: Centering the needs of nurses and the organization to ensure seamless and exceptional care to terminally ill patients and their families.
Empowerment: Teaching the organization the tools and processes necessary to maintain full ownership of the system.
Information architecture and building a proof concept: August 2020
Faced with a tight timeline and the need to re-familiarize myself with the software, I led collaborative working sessions with the executive director and the implementation manager. My goal was to shift the focus from merely digitizing paper forms to building a robust, long-term digital strategy.
I guided them through critical operational hurdles with targeted discovery on topics I identified during discovery:
Technical requirements: Establishing offline protocols for remote patient visits.
Functional requirements: Identifying essential information for data exports.
Compliance requirements: Defining HIPAA-aligned data retention and archiving protocols for the nurses.
Within weeks, I translated these insights into a comprehensive set of application requirements and a functional proof of concept.
Phase 1 build: September 2020 - January 2021
After securing approvals from the nurse team and board of directors, we launched the Phase 1 build using Knack. I began by aligning expectations on the working relationship and the project requirements, and establishing a regular feedback loop with the implementation manager to meet our January 2021 deadline.
Key highlights of this phase included:
Human-centered design: Rather than a literal paper-to-digital translation, I optimized layouts for iPad use and field-nursing workflows, utilizing custom code to enhance Knack’s native capabilities.
Process optimization: I facilitated a review of data collection practices, helping the staff eliminate non-critical data points to streamline the digital experience.
Architecture integrity: By prioritizing a patient-centric database structure and clean information architecture, I prevented future technical debt and ensured scalability.
As we rounded the corner into the end of the year, the implementation manager used weekly team meetings to train the nurses on the application. We successfully transitioned the team to full digital use by January 18, 2021.
Iterations and Phase 2 build
Post-launch, I transitioned into a mentorship role, training the implementation manager in system troubleshooting and database management. In April 2021, we expanded functionality for office administration while refining the core user experience through several key design principles:
Information hierarchy: Simplifying layouts to ensure essential data remained visible and actionable.
System integrity: Designing "guardrails" to prevent accidental data loss or user error.
Standardization: Developing a mini content and design system to ensure consistent language and UI patterns.
The Result: The platform now scales with the organization. It has successfully integrated new bereavement services and social work workflows, allowing nurses to shift their focus from paperwork to patient care. I continue to oversee high-level database architecture and UX strategy for all major expansions.
Project Retrospective
The project is on-going so it is helpful to think about what we can keep doing well, and what could be improved upon.
What went well?
Building trust: Securing early and continuous input from the nursing team ensured high adoption rates during a significant operational shift..
Phasing functionality: Prioritizing core patient-care workflows allowed for an accelerated launch, leaving secondary features for later iterations.
Clear expectations: Maintaining transparent communication regarding project deliverables, timelines, and my capacity as a volunteer kept the project on track.
What can be improved?
Layout standards: Outlining more standards for display and layout (a very rudimentary design system) would help consistency throughout the application
Documentation: On this time-constrained project, documentation could have been prioritized earlier to use as a training tool and to have a reference for decision making.
What did I learn?
Planning for success: Worst-case scenarios are often planned for, but in this work, we were a bit of a victim of our own success. The transition went so well and the application has so significantly helped improve patient care that other roles in the organization are requesting functionality.
Prioritize empowerment: Be deliberate in taking time to teach along the way. It feels easier to do things yourself in the short-term, but teaching someone to fish is always the right choice in the long-term.