Challenge Summary
Welcome to the TTGP Web App UI Concept Design Challenge.
The purpose of this project is to build a web-based solution that lets healthy volunteers wishing to take part in a clinical trial enter their basic medical information along with the contact details of their GP. Their GP then subsequently confirms the medical information provided by the volunteer. Upon receiving the health status, the company can assess whether the volunteer is suitable to take part in the clinical study.
Challenge Objectives
- User interface concept design
- 10 screens
- Web application – desktop only (no scroll please)
- 02_01 CU staff dashboard
- 02_02 Confirmed details
- 03_01 GP initial email template
- 03_03 GP confirmation form
- Feel free to submit more screens for early feedback.
- Important: As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Please ask for a MarvelApp prototype link in an e-mail to pere.viktoria@gmail.com.
- Make sure to include a URL/Link to your design in your "declarations.txt"!
- Make sure all pages have correct flow! Use correct file numbering (00, 01, 02, 03).
01 Login Screens
- 01_01 User Login
02 CU Staff Screens
- 02_01 CU staff dashboard
- 02_02 Confirmed details
- 02_03 Reporting
03 GP Screens
- 03_01 GP initial email template
- 03_02 GP reminder email template
- 03_03 GP confirmation form
04 System Admin Screens
- 04_01 System Admin Dashboard
- 04_02 Managing users
- 04_03 Managing GP email templates
- Important: As part of your final submission, you must update your Marvel prototype.
- Make sure to include a URL/Link to your design in your "declarations.txt"!
- Make sure all pages have correct flow! Use correct file numbering (00, 01, 02, 03).
Project Background
Workflow
Please make sure your design incorporate this workflow.
Please make sure your design supports the following roles.
Please make sure your design includes the following screens.
Form Factors
Please make sure your design supports these form factors.
- Desktop: 1366px x 768px. Do not let users scroll, but use pagination where necessary.
Branding Guidelines
You have to follow the client’s brand guidelines.
Design Assets
- Branding guidelines.
- List of information for volunteer registration.
- List of information needed to be confirmed by the GPs.
- Please use a placeholder logo for the app.
Final Deliverables
For submission you have to upload a zip file that contains the following 4 files:
Marvel Prototype - We need you to upload your screens to Marvel App.
- Please send your marvel app request to pere.viktoria@gmail.com
- You MUST include your Marvel app URL as a text file in your final submission labeled “MarvelApp URL” (in your marvel app prototype, click on share and then copy the link).
The purpose of this project is to build a web-based solution that lets healthy volunteers wishing to take part in a clinical trial enter their basic medical information along with the contact details of their GP. Their GP then subsequently confirms the medical information provided by the volunteer. Upon receiving the health status, the company can assess whether the volunteer is suitable to take part in the clinical study.
Challenge Objectives
- User interface concept design
- 10 screens
- Web application – desktop only (no scroll please)
Round 1
Submit your initial designs on these key screens for a checkpoint feedback:- 02_01 CU staff dashboard
- 02_02 Confirmed details
- 03_01 GP initial email template
- 03_03 GP confirmation form
- Feel free to submit more screens for early feedback.
- Important: As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Please ask for a MarvelApp prototype link in an e-mail to pere.viktoria@gmail.com.
- Make sure to include a URL/Link to your design in your "declarations.txt"!
- Make sure all pages have correct flow! Use correct file numbering (00, 01, 02, 03).
Round 2
Submit your final designs improved according to the feedback:01 Login Screens
- 01_01 User Login
02 CU Staff Screens
- 02_01 CU staff dashboard
- 02_02 Confirmed details
- 02_03 Reporting
03 GP Screens
- 03_01 GP initial email template
- 03_02 GP reminder email template
- 03_03 GP confirmation form
04 System Admin Screens
- 04_01 System Admin Dashboard
- 04_02 Managing users
- 04_03 Managing GP email templates
- Important: As part of your final submission, you must update your Marvel prototype.
- Make sure to include a URL/Link to your design in your "declarations.txt"!
- Make sure all pages have correct flow! Use correct file numbering (00, 01, 02, 03).
Project Background
- A clinical study is an important phase in the development of a new medicine. In order to be able to assess new medicines, pharmaceutical companies need to recruit healthy volunteers with no pre-existing medical conditions. The medical status of the volunteers for these projects need to be confirmed by their general practitioners for accuracy and this currently consumes a significant amount of time and leads to delays in assessing the suitability of volunteers. This web app will help our client to automate this process.
- If the GP has confirmed the information about the volunteer, the company can decide if the volunteer is suitable for the given clinical trial, so the objective of the app is also to let the client’s Clinical Unit staff monitor the return of information by the GPs to ensure this happens in a timely manner.
- The web app will be used by the volunteers’ GPs, the client’s Clinical Unit staff, and the client’s system admins.
- If the GP has confirmed the information about the volunteer, the company can decide if the volunteer is suitable for the given clinical trial, so the objective of the app is also to let the client’s Clinical Unit staff monitor the return of information by the GPs to ensure this happens in a timely manner.
- The web app will be used by the volunteers’ GPs, the client’s Clinical Unit staff, and the client’s system admins.
Workflow
Please make sure your design incorporate this workflow.
Initial state (you don’t need to design this) The volunteer enters his/her basic information (name, date of birth) and his/her GP’s contact details (one or more of Email/Fax/Address) and submits his data to the system along with a valid legal authorization for the company to request the information from the volunteer’s GP.
Step 1
System sends automatic request to GP via all contact channels provided (email, fax, snail mail), with patient name, date of birth, and authorisation and shortened web-link to provide response.
Step 2
System issues reminders to the GP via all contact channels provided at the 2nd, 5th and 10th days ONLY if data has not been provided.
Step 3
GP accesses web link and provides required information via secure webform designed for SPII. The GP might send the form via fax or post as well. Clinical Unit staff can also manually enter these data to the same location if the GP provides them by post.
Step 4
Client’s staff can see which GPs have not responded and can intervene where automated requests have not resulted in requested information.
User RolesStep 1
System sends automatic request to GP via all contact channels provided (email, fax, snail mail), with patient name, date of birth, and authorisation and shortened web-link to provide response.
Step 2
System issues reminders to the GP via all contact channels provided at the 2nd, 5th and 10th days ONLY if data has not been provided.
Step 3
GP accesses web link and provides required information via secure webform designed for SPII. The GP might send the form via fax or post as well. Clinical Unit staff can also manually enter these data to the same location if the GP provides them by post.
Step 4
Client’s staff can see which GPs have not responded and can intervene where automated requests have not resulted in requested information.
Please make sure your design supports the following roles.
GP user
Volunteer’s doctor who must complete the requested health information.
Clinical Unit Staff User
Client’s employees who are responsible for ensuring validation data from GP is received in a timely manner.
System Admin User
Client’s tech staff who administer the system.
Screens/FeaturesVolunteer’s doctor who must complete the requested health information.
Clinical Unit Staff User
Client’s employees who are responsible for ensuring validation data from GP is received in a timely manner.
System Admin User
Client’s tech staff who administer the system.
Please make sure your design includes the following screens.
01 Login Screens
02 CU Staff Screens
04 System Admin Screens
01_01 User Login: Provide login page for the users of the system (CU Staff and system admin). They will use their official email address to login. Please support credential validation, wrong credentials message and forgot password flow.
02 CU Staff Screens
02_01 CU staff dashboard: Provide a dashboard for the client’s CU staff. CU staff must be able to see a table of incoming registrations of volunteers and their details in a glance and confirmation statuses. We would like to see your suggestions about the data and the visualizations shown on the dashboard. Do not let users scroll, but use pagination instead.
- Each row should show details like ID, Patient Name, Respective patient's GP name, Status of the Response (like Response Received, Not received, if received, link to show the details), and details about reminders (like initiated 1st reminder, 2nd reminder). It can be a checkbox or any other better UI control with proper color coding to distinguish the status.
- CU staff should have the ability to view when transmission of the request has failed (e.g. email bounce-back or other error messages received)
- CU stuff should be given an export option to download the data on the dashboard.
- CU staff can change the default reminders, and can disable them as well, if the filled in form has been sent via post by the GP.
- CU staff can scan and upload or input the data from the printed form received via post or fax from the GP. Provide an opportunity for the user to initiate this task.
02_02 Confirmed details: If the GP has confirmed the volunteer’s health status, the details will become available in the system through the CU staff dashboard.
02_03 Reporting: App must have the ability to report/export data of volunteers, registrations, confirmations and GPs. Each record, once received from the GP must be manually checked by a clinical unit member against the volunteer provided health information using this export functionality.
03 GP Screens- Each row should show details like ID, Patient Name, Respective patient's GP name, Status of the Response (like Response Received, Not received, if received, link to show the details), and details about reminders (like initiated 1st reminder, 2nd reminder). It can be a checkbox or any other better UI control with proper color coding to distinguish the status.
- CU staff should have the ability to view when transmission of the request has failed (e.g. email bounce-back or other error messages received)
- CU stuff should be given an export option to download the data on the dashboard.
- CU staff can change the default reminders, and can disable them as well, if the filled in form has been sent via post by the GP.
- CU staff can scan and upload or input the data from the printed form received via post or fax from the GP. Provide an opportunity for the user to initiate this task.
02_02 Confirmed details: If the GP has confirmed the volunteer’s health status, the details will become available in the system through the CU staff dashboard.
02_03 Reporting: App must have the ability to report/export data of volunteers, registrations, confirmations and GPs. Each record, once received from the GP must be manually checked by a clinical unit member against the volunteer provided health information using this export functionality.
03_01 GP initial email template: After the volunteer submits his data, the system will send an email to the appointed GP. Please provide a template for this email, which includes the reason why they got the message, details of the volunteer and their digital authorisation, steps to fill in the form, and a UNIQUE short URL to the form that has to be filled in.
03_02 GP reminder email template: If the GP has not responded within a preset amount of time, he will be sent reminder emails. Please provide a template for this email as well.
03_03 GP confirmation form: The GP will arrive to this landing page unique to the individual volunteer where he will find the basic information of the volunteer, so he can find patient data in his own system. The form will include 2 parts – the current paper form is included. We are looking forward to your suggestion about the layout of the form. Firstly, the GP is presented with a list of diseases and he has to indicate if the volunteer had experienced any conditions. Provide text areas where the GP can elaborate on any given current or past disease of the volunteer. Secondly, another set of questions (attached) will have to be answered that will investigate other aspects of the medical status of the volunteer. Before submitting the form, the GP has to accept the Terms & Conditions of the client’s system. FYI: in the future we will employ a digital signature function. The GP can either submit the form online, or he can print out the empty form and fill it in by hand, than send it to the client via post. Please make printing, pdf downloading and online submitting available.
03_02 GP reminder email template: If the GP has not responded within a preset amount of time, he will be sent reminder emails. Please provide a template for this email as well.
03_03 GP confirmation form: The GP will arrive to this landing page unique to the individual volunteer where he will find the basic information of the volunteer, so he can find patient data in his own system. The form will include 2 parts – the current paper form is included. We are looking forward to your suggestion about the layout of the form. Firstly, the GP is presented with a list of diseases and he has to indicate if the volunteer had experienced any conditions. Provide text areas where the GP can elaborate on any given current or past disease of the volunteer. Secondly, another set of questions (attached) will have to be answered that will investigate other aspects of the medical status of the volunteer. Before submitting the form, the GP has to accept the Terms & Conditions of the client’s system. FYI: in the future we will employ a digital signature function. The GP can either submit the form online, or he can print out the empty form and fill it in by hand, than send it to the client via post. Please make printing, pdf downloading and online submitting available.
04 System Admin Screens
04_01 System Admin Dashboard: Provide a landing page for the client’s system admin. His tasks will include management of staff, Change of email templates and the notification/reminder settings. On the landing page you can show a list of users for instance. We are opened to suggestions about visualizations and summaries on the dashboard.
04_02 Managing users: The system admin has to be able to add and remove users from the system, so as deactivating and activating them, and setting their user roles (CU staff or system admin). There should be printing and exporting functions as well.
04_03 Managing GP email templates: The admin is going to be responsible for the content of the GP e-mails. Please provide the screens necessary to support this flow.
04_02 Managing users: The system admin has to be able to add and remove users from the system, so as deactivating and activating them, and setting their user roles (CU staff or system admin). There should be printing and exporting functions as well.
04_03 Managing GP email templates: The admin is going to be responsible for the content of the GP e-mails. Please provide the screens necessary to support this flow.
Form Factors
Please make sure your design supports these form factors.
- Desktop: 1366px x 768px. Do not let users scroll, but use pagination where necessary.
Branding Guidelines
You have to follow the client’s brand guidelines.
Design Assets
- Branding guidelines.
- List of information for volunteer registration.
- List of information needed to be confirmed by the GPs.
- Please use a placeholder logo for the app.
Final Deliverables
For submission you have to upload a zip file that contains the following 4 files:
Source.zip – All original source files.
Files should be created in Adobe Photoshop and saved as a layered PSD file, Adobe Illustrator or as a layered AI file, Sketch or Adobe XD.
Submission.zip – PNG/JPG files
Submit JPG/PNG image files based on Challenge submission requirements stated above.
preview.png – Your preview image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72 dpi and place a screenshot of your submission within it.
declarations.txt – All your declarations and notes
This file must contain your notes if any, your Marvel link, fonts, stock art and icons used.
Files should be created in Adobe Photoshop and saved as a layered PSD file, Adobe Illustrator or as a layered AI file, Sketch or Adobe XD.
Submission.zip – PNG/JPG files
Submit JPG/PNG image files based on Challenge submission requirements stated above.
preview.png – Your preview image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72 dpi and place a screenshot of your submission within it.
declarations.txt – All your declarations and notes
This file must contain your notes if any, your Marvel link, fonts, stock art and icons used.
Marvel Prototype - We need you to upload your screens to Marvel App.
- Please send your marvel app request to pere.viktoria@gmail.com
- You MUST include your Marvel app URL as a text file in your final submission labeled “MarvelApp URL” (in your marvel app prototype, click on share and then copy the link).
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.