MediShare
MediShare streamlines medical image-sharing, enhancing access and exchange between various providers and patients.
Problem Statement
Patients need a way to swiftly transmit medical imaging to various healthcare providers who may work at separate hospitals/practices. Already grappling with health concerns, delays in sharing critical diagnostic data can prolong the anxiety of awaiting a diagnosis and treatment plan, potentially impacting their overall well-being and recovery journey.
Problem Background
MediShare customers will include healthcare providers and patients. Currently, healthcare providers cannot share imaging across separate networks, leaving the patient responsible for requesting disks or figuring out how to share imaging from secured platforms. This is a problem for patients who want second opinions from healthcare providers. It slows down the transfer of imaging and creates more anxiety and work for the patient.
Research Insights
User Pain Points
Using Survey Monkey, we identified a few different categories of prospective users with over 10 user interviews
Supporting Data
88% reported that difficulty accessing imaging was their greatest challenge
Feedback
Our preliminary user research to validate this problem with patients sharing medical imaging found that there is a variety of ways patients send medical imaging, each with their own pain points
Survey: https://www.surveymonkey.com/r/GBBXDRT
Future Steps
This is what we learned from speaking to customers …
- Difficulty accessing imaging was the main challenge, followed by cost and long waiting times
- Having to call healthcare offices multiple times to receive imaging
- Having a different pacs system often hinders the process.
- Not every provider gives you a copy through the portal so you have to ask them to email/fax which takes a long time.
- 60% of responders use a digital medical chart currently to keep track of imaging
Images
Learnings
Product Manager Learnings:
Oliver Soble
Designer Learnings:
Designer Learnings:
Jo Sturdivant
- Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
- Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
- Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.
Developer Learnings:
Developer Learnings:
Vanady Beard
&
As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.
Developer Learnings:
Stephen Asiedu
&
As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.
Developer Learnings:
&
Developer Learnings:
Maurquise Williams
&
- Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
- Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
- Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.
Developer Learnings:
Jeremiah Williams
&
All in all this experience was very awesome I learned that in coding with others being transparent is key
Developers Learnings:
Justin Farley
&
I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.