Healthcare Fraud Prevention - Visual Concepts for Data Analysis

Register
Submit a solution
The challenge is finished.

Challenge Summary

The Healthcare Fraud Prevention Project (HFPP) is building a system that will help to identify fraud, waste, and abuse in healthcare claims. The front end of the system is a web application that will be used to conduct studies. The overall user flow of the web app has already been designed. Now we are looking for visual concepts to define the functionality of a GUI for analyzing claims that are collected by the system.


Overview

The attached storyboards demonstrate the overall functionality of the study management application.

We are using the following terminology:

  • a partner is an insurance company that has joined the HFPP network
  • a claim is a request for payment from an insurance company
  • a study is a plan to look for fraudulent, wasteful, and abusive claims
  • data requests are sent out during a study to ask for claims from partners
  • data responses are the claims sent to the study management application by partners

In this contest, we want to fill in the part of the interface where data responses are visually analyzed.

The relevant storyboard screen is 10-3visual-tab.png, showing two areas:

  • chart selection (at left)
  • chart display (at right)

We're looking for visual concepts depicting the user flow and graphical themes of both areas. The whole tab can be expanded vertically but not horizontally.

 

Chart selection

Many different chart types are described in a Wikipedia article. We want to offer a selection of chart types that make sense for analyzing claim data.

For example, it makes sense to generate histograms in which the vertical axis shows the number of claims and the horizontal axis shows the year in which the claim occurred.

Another versatile chart type is the pie chart. For a set of claims, the pie chart can be subdivided into slices showing the proportion of claims originating from each insurer, from each partner, or for each procedure code. Note that the user controls in the left portion of the tab must be appropriate for the chart type.

Your task is to choose a representative sampling of reasonable chart types and visually demonstrate the appropriate controls.

 

Chart display

In the right portion of the tab, we'd like to see your visual concepts for the appearance of each chart type and for any associated interaction. Many different UI effects are possible.

For example, hovering over a bar in a histogram or over a slice in a pie chart can cause an info bubble to appear.

Another possibility is the direct manipulation of charts by clicking and dragging in the right pane in order to adjust the axis length, for example.

Again, we're asking you to supply creative ideas and graphical themes.

 

Submission requirements

Please submit your visual concept as a set of annotated storyboards. You can include the annotations inside or around each storyboard. The emphasis in this contest is on user flow, interface concepts, and graphical themes.

You do not have to deliver production-ready storyboards. The winning visual concept will be used as input to software contests, which will finalize the desired functionality before we come back to Studio for production graphics.

 

Target audience

The visual concepts will be provided to software architects to help them define the software logic behind these parts of the user interface.

 

Judging criteria

  • completeness: Does your visual concept cover the required functionality?
  • clarity: Do we get a good sense of the work flow in these parts of the interface?
  • graphics: Are your visuals aesthetically attractive?

 

What to submit

Submission: PNG images of your design concept.

Source: Graphical source files.

Preview image: 1024 x 1024 screenshot in JPEG or PNG format.

 

Final fixes

You may be asked for minor changes to meet the stated requirements of this contest.

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.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

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:

2014 TopCoder(R) 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

5 submissions

ID: 30035060