iOS: Patient Matching
A Medly Project“Patient Matching” was the process of associating a new iOS patient with any existing patient records in Medly’s database by creating a unique ID that all of Medly’s products would pull to ensure that the patient’s records were up-to-date and accurate across all platforms. There was a lot of back-end work involved with this project, so I’ll be highlighting what the patient experience would be.
The problem
At a high level, in order to successfully launch the iOS App, patient matching was essential to bridge the data gap between the internal database and the iOS App. Without patient matching, Medly would have not been able to display any current or historical prescription data to the iOS patients. This would result in patients not being able to use the app to schedule a delivery for existing prescriptions.
The audience
Existing Medly patients, existing iOS App users, and new patients to Medly (previously not iOS App users)
Team roles
I was the design lead on the iOS side, working alongside another internal design lead. We worked closely with our respective Senior Product Managers and development teams throughout the process, as well as with each other to make sure we were always aligned. We also worked closely with a third development team that was overseas that handled the backend matching logic.
The process
With three teams working towards a single goal, you can imagine the number of meetings and iterations we had to make. But it’s all a part of the process, right!?
Before diving into design, we created a patient matching flow that all teams agreed upon. From there, wireframes were next to get the experience mapped out. And then eventually the visual side of things. Throughout the process, all teams remained in sync…this also included our QA specialists.
The outcome
This provided a more seamless experience and we were able to better serve our patients, as well as internally by having a single record per patient. This, in turn, built trust.
