Design responsibilities
  • UI 
  • Prototype

MEDISCAN APP-

PROJECT OVERVIEW

Mediscan is an app for finding doctors, as well as ordering medicines, scheduling diagnostic tests or having an online evaluation, quick and easy.

The app should be intuitive and organic as possible, as well as clear and clean in order to be used by users who are not always in good medical condition.

It contains a questionnaire to be filled in by the user, which must be designed in a way that would not exhaust them despite a large number of questions.

Design brief, based on prior research

These features were designed as a first iteration based on prior research: 

Flexible search bar: The user can either use the search bar to search for information about an illness or browse the categories suggested below it.

Accessible answers: The F.A.Q section is immediately visible, as it was given in the brief that it is known that users ask many questions in healthcare-related products.

The user can scroll down for more detailed information, including information about the doctors who work with this service.

Include reviews for a tighter trust connection:

Reviews can be swiped by, horizontally. The user can enter either read them briefly or click to enter a more detailed review section.

Purchase flow

Scan a prescription flow

Answering the medical questionnaire is exhausting and time-consuming. Therefore, the user has the option of relying on heir latest questionnaire answered.

Once this feature is enabled, only the relevant folds of the accordion menu will open. Questions that demand no necessary attention will remain hidden, and inside the collapse panel, the user will find them prepopulated.

Finishing the process

When the third step is accomplished, the last yellow dot is filled.

The user receives a success message regarding the next steps and is invited to complete the task of updating their profile. 

A scroll down read is available again like in screen one, only this time in a different order: The user can scroll to read about the doctors, and then reach the F.A.Q section. 

This is decided while taking the next step under consideration: The user is waiting to hear approval from the doctor, a person they might meet. Thus I worked with the assumption in mind that this would be the next relevant information they will be looking for in the app.