Software Design
Clade designed and developed a web app prototype that allows non-profits to efficiently access and share consented patient health information, thus enabling them to provide better care for at-risk populations.
The Challenge
Non-profit organizations often have a lot of difficulty working with one another to share information about the individuals that they provide services for. With no centralized method of communication, non-profits are left to individually maintain patient data, thus lowering the quality of the services they’re able to provide.
The outcome
We created a frontend prototype called ShareMyHealth, a web app that would enable organizations to see and share patient data with each other after a patient consents.
Clade was hired to work with Videntity and The Alliance for Better Health in order to create an easy way for patients who may not have various forms of identification or permanent home addresses to securely share their health information with non-profit care providers.

We tested our design with representatives from four non-profit organizations in Albany, NY that included Interfaith, Bethesda House, Trinity Alliance, and Catholic Charities. We then created a final frontend prototype to be integrated into an existing backend with biometric identity-verification methods. It was well-received and proved to be a viable solution for their teams.
We spoke with four non-profit organizations that help at-risk patients to see how we could help them do a better job of providing aid, as well as learning more about the type of information they need in order to help qualify such patients for certain programs.

We discovered that these organizations’ priorities were getting patients set up with their medical data, easily verifying their identity, quickly accessing pertinent medical records, and being able to see any other organization’s notes about a given patient.
The information architecture map helped us outline to the developer team each object that would need to exist in the database as well as the medical information we would need to access.
We ended up deciding that there should be two users for this app: the organization agent as well as the patient themselves. The patient should always have the ability to decide who gets to see their personal health information. Organization agents should be able to request information from a given patient but should otherwise never be able to access such information without the patient’s express consent.
The key workflow of onboarding a new patient at an organization was then drawn out to show when and where a patient would have to log in to give access.
This workflow helped us dictate how patients would still have full control over what information of theirs is shared per moral and legal requirements. We wanted to be sure that patients were able to share and remove access to certain organizations based on their own needs. With that being said, organizations were also able to share notes (not containing any patient data) with one another in order to more easily share information.
Wireframes were then created to start blocking out content, allowing us to test the interaction on both desktops and tablets (the main surfaces used by these organizations). We also started blocking out the frontend dev prototype based on these wireframes.
After all the content and interactions were approved using the wireframes we created the final high-fidelity screens. These screens were then shown to each of the four organizations on-site in order to get their feedback so we could make any final changes before building out the web app prototype.

Some of our other work