This project is a prototype of a potential solution for the following problem posed by J&J at HackZürich:

How can we digitalize medication information leaflets?

We analyzed the problem from a UX standpoint and built a prototype that improves that in various ways. The underlying problem is that leaflets are required to be printed out in physical form and put into the same packaging as the medication itself.

This creates a severe shortage of printing space, resulting in dense, small, hard to read, and have to target at a huge demographic.

For many, most information on medical information leaflets are not relevant or are too dry to properly study. Further, once the leaflets are printed, it's hard to update them with new information.

Our Contribution

Our contribution is a prototype of a future method of medical information communication, and with that motivate a swifter transition to digitized leaflets.

At the core lies the design principle of WYSIWYN, or "what you see is what you need" - only show information that is actually relevant to the user.

We reimagine future medical leaflets to be machine-parsable, and semantically tagged documents so that it will be easy to filter and curate personalised relevant information for the reader.

After providing his/her medical background to the app - meaning: age, gender, allergies, etc. - the app will automatically filter out relevant parts from all manuals.

img

For instance, if a person has an iodine hypersensitivity, the app will mark a section relevant for people with this predisposition:

img

The app further supports rich text and content using markdown:

img

Finally, when important information is updated, a push notification on all users' app can inform the users that they should review the manual.

img img

We imagine these websites to be accessible via QR Codes (or any phone readable codes)

which could be made specific not just to the type of medicine, but to each package itself, and hence display and warn about package-specific properties such as the expiry date.

How we built it

  • Frontend: React; Ant Design
  • Backend: Firebase as database; page itself is hosted statically
  • Images: Unsplash, Wikihow

Built With

Share this project:

Updates