BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to "Telerx - Patient Case Management Responsive Web Design Concepts Challenge". This challenge goal is to create Patient Case Management system in various devices that can be accessed by both medical staff and patients. At the end of this challenge, we are looking for a modern, clean and a responsive design that captures the possible interactions a staff member or patient might have with data entry, call scripting, and Question and Answer scenarios. Join us NOW!!

 

Round 1

01. Dashboard screen
02. Patient Intake (data acquisition) Screen
03. Q/A Screens

Round 2

01. Dashboard screen
02. Patient Intake (data acquisition) Screen
03. Q/A Screens
04. FAQ Screen


Project Brief 

Our client wants to build a responsive case management system to support Patient Engagement, Access & Reimbursement and Drug Safety Services. There are many patient/consumer cases that being handled by our client, but in this challenge, we require you to create a design concept for "adverse event" scenario case (there are many types of cases, it can be adverse event like being required in this challenge, or adherence case, benefits verification, adverse event capture, etc) where a "client intake specialist" will make contact with the consumer and begin to capture information (data entry) to create AE reports. This information gathering/interaction is a 2 step QA process that might include a medical doctor (MD) assessment. In this challenge we are asking you to focus on a couple of screens but to also try and capture what the possible user interactions might be. Think of modern UX design and how cool this case management system could look and work. This application will be used by different type of users and your design needs to support navigating between client accounts/contacts with clear indication of what program they are performing case management for.

Design Concept Goals
- How should this patient case management system graphically look?
- Review the brand - make sure your design is embracing their colors and brand - so it looks correct to their customers
- Look through the listed screens and think about the user experience
- As a user of this application - what should the priority features be?
- How quickly (when opening the application) could a user find what they are looking for?

User Scenario (Adverse Event Scenario)
- AE - Adverse Event 
- Billy is a middle age man that is currently under treatment and consume some medicine from our manufacturer partners. 
- After consuming the medicine, Billy experience some hives and reports it to social media.
- Our "social media specialist" employee saw the reports from social media tracking and contacts Billy via private message/phone and routes him to our "Intake specialist" person.
- Intake specialist then gathers information from Billy regarding the problem he is currently facing, interview him and documents the report in the system as Adverse Event (AE) report. Manufacturer/Client that produced the medicine also will be advised about the AE report. 
- The AE report will be reviewed through 2 steps QA process that might include a MD assessment.
- After review for the AE report is finalized, the case is closed and reported to the proper regulatory body within prescribed timeframe and related requirements (for ex. European Medicines Agency).
- The manufacturer/Client will receive daily, weekly, and /or monthly AE reports.
- AE data also arrives by phone, fax, email, or electronic interface. All AE data needs to be entered or created as a case for processing (complete intake of AE data, follow up with reporter or HCP for clarifications, submit for  investigation, QA review, etc.)

Screen Requirements (Below is suggested screens that needs to be create, feel free to add more design if necessary to explain your concept!)

01. Dashboard screen
- By default, this is the page that every client employee (any roles) will see every time they open the application.
- Dashboards should show overall case metrics in the system to the apps user.
- Dashboard should show a list of all cases that require action and or follow up (all open cases)
- Provide information summary of the case metrics via various way, chart, table, what else? 
- Cases needs to be presented can be various, it can be adherence case, benefits verification, adverse event capture, etc. 
- Ability to see cases that related to the user.
- Ability to navigate through the entire applications (Main navigation).
- Button to start and create reporting new case?
- Provide some search section in the page and highlight it to becomes center of attention, user should search for existing or duplicate case and then versioning the case to collect the follow up Q&A.
- Explore how this page should work (and keep it simple!)

02.Patient Intake (data acquisition) Screen
- This screen will be use to gather information about consumer/patient information.  
- This screen can be reach when user start reporting new case or versioning duplicate/existing case from dashboard screen.
- Some Basic content needs to be added in this screen :
* Referral Source (Pick List)
* Caller Type (Pick List)
* Epsilon ID (Text Entry)
* First Name (Text Entry)
* Last Name    (Text Entry)
* Home Phone Text Entry)
* Home Phone Extension (Text Entry)
* Cell Phone (Text Entry)
* Other Phone (Text Entry)
* Other Phone Extension (Text Entry)
* Address (Text Entry)
* City (Text Entry)
* State (Pick List)
* Zip (numeric)
* Segment (Pick List)
* Service Level    (Pick List)
* Date of Birth    (Calendar)
* 18 years or older    Radio Button (yes, no)
* Preferred Language (Pick List)
- After user enter consumer/patient information, they will assign intake specialist to manage the consumer. create this scenario to your design.
- Explore how this page should work (and keep it simple!)

03. Question and Answer (Q/A) Screens 
- Check reference from brief.zip -> ppt document -> page 11 to 19.
- This screens will be use by intake specialist to gather information from consumer/patient.
- Needs some "call script" available in this screen that will lead/guide the intake specialist to interact with consumer.
- This screens at least needs 2 steps of Q/A list that needs to be answered by consumer/reporter during the interview.
- Needs some indicators to show the Q/A process. 
- Once the Q/A list finished, intake specialist will wrapped the AE report and  will be able to send it for review by pressing/click "send to review" button. Intake specialist also will have some ability to set any persons/company contact to get updates periodically (daily, weekly or monthly) regarding the AE report status.
- We need some easy navigation for the user to navigate from FAQ to Q/A Screens and vice versa.

04. FAQ Screen
- FAQ search section.
- FAQ search result by category, questions, and answer.
- Provide details FAQ screen.
- We need some easy navigation for the user to navigate from FAQ to Q/A Screens and vice versa.

Important Design Considerations :
- Keep things consistent. This means all graphic styles should work together.
- Pay attention to the suggested brand and colors
- All of the graphics should have a similar feel and general aesthetic appearance.
- Responsive design best practices (think and plan your grid!)
- Your design needs to stay consistent but cleverly adapted layout screen for each required size.
- Be creative, there are a lot of information needs to be presented in the system, show us the effective ways to arrange this huge amount information in easy navigation solution (via menu? tab? icons? etc)

Branding Guidelines 
- Font, Color, Style : follow http://www.telerx.com    
- Desktop Size: 1024px width, height adjusting accordingly
- Mobile size: 320px width, height adjusting accordingly

Target Audience
- Patient Engagement Specialist (RNs, PharmD, Pharmacists, Social Media Specialist Workers).
- Reimbursement Specialist
- Customer Service Representatives

Judging Criteria
- How well your storyboard design fit in responsive layout?
- Cleanliness of your graphics and design (very important!)
- User Experience!

Submission & Source Files
Preview Image
Create your preview image as one (1) 1024 x 1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission in it.

Submission File
Please upload JPG/PNG images in a ZIP file with all requested contest requirements stated above. Number your files (01, 02, 03, etc) in order. This will help when reviewing with the client.

Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop or Illustrator and saved as layered PSD/AI files.

Final Fixes
As part of the final fixes phase you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.

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.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2015 topcoder Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • Layered PSD files created in Adobe Photoshop or similar
  • AI files created in Adobe Illustrator or similar

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30047033