Exposure Registry - Submission Form Wireframe Contest

Welcome to Exposure Registry - Submission Form Wireframe Contest.
Soteria promotes safety in the workplace and one aspect of safety is exposure to hazardous materials or chemicals. The ability for workers to register their exposures with Soteria allows for better tracking and documentation if and when problems occur. 

The Exposure Registry program will provide the workers, employers and others (ex. worker representatives, health care professionals, etc.) the ability to register exposure incidents that occurred in the workplace, including historical ones.  Users who are registering an exposure might be 1) anonymous, 2) a worker, 3) an employer or 4) another non-anonymous user.

At the end of this contest, the client is looking appropriate system workflow that easy to understand for all users and clean, intuitive wireframes that will become a great input for storyboard design contest.

Please read the contest details below, and feel free to post your questions in forums.

Round 1

Submission design for client review:

• Workflow for Anonymous User (including resuming an incomplete submission)
• Workflow for Identified Worker User (including resuming an incomplete submission)
• Any notes for the client about your submission

Round 2

Submission design for client review:

• Workflow for Anonymous User (including resuming an incomplete submission)
• Workflow for Identified Worker User (including resuming an incomplete submission)
• Workflow for Identified Employer User (including resuming an incomplete submission)
• Workflow for Identified User who is not the Worker or Employer User, but has registered an exposure (including resuming an incomplete submission)
• Any notes for the client about your submission

The client wants a web application which will provide users the ability to register exposure incidents in a user-friendly manner.  The audience will be broad.  It will span from users who are not computer-literate, or English is not their first language to users who have dealt with Soteria in the past and are already familiar with the terminology used.  
Therefore the client is looking for an application that is interactive, adaptable to the audience using it and simple to use.  It is also important that the look and feel is not the typical ‘government-bland’.  For example, you should not design a large form with many fields to populate, but rather the data collection process should be interactive and user-friendly, dynamically determining what types of data to request from the user based on previous responses or based on the type of user (anonymous, worker, etc.).

Attached documentation covers other functionality, but for this contest you will focus only on "submit an exposure" section. 

Required Wireframes:
The wireframes should show the following functionalities: 
- Context-related Help functionality
- Exposure Registration (including how to stop the registration and resume it at a later date, provide user ability to submit multiple registrations without having to re-enter all the information each time)
- Ability to match the registration to an existing worker or employer
- Attach supporting documentation
- User is directed to helpful safety information after registration is complete
- Ideas on how system will handle situation where a potential duplicate registration is detected
- Print 

User Experience Concepts:
To better illustrate the user experience concepts for the anonymous user wireframes, here are some more ideas:
1. Utilize an online tutor or wizard that helps the user fill out the submission (eg. Having “Don’t Know” or “Don’t understand” option that user can click at each point to get context sensitive and plan language help.  This Help could also provide some definitions or Soteria terminology (eg. What is a worker, what is an incident, what is an exposure, etc.)
2. Utilize structured question trees than a form to gather the information.  The questions/input fields would vary by the questions previously asked
3. Use an interactive approach that varies by the audience.  In this way, we could provide more help for workers who need help through questions; but not make the application too time consuming for employers and union reps who are familiar with Soteria language and have filled out many registrations in the past
4. Utilize an interactive approach within the registration process to identify whether the worker submitting is already known to us (ie. matching).  Eg. Ask “Have you registered an exposure with us before?”, and if the answer is “Yes”, then ask for the name, birth date and phone number to see if the application can match to a worker already in the database.  If there is a match, the application could pull in the worker information and confirm that it is still current.  If the worker doesn’t exist, give them fields to fill out to register their worker profile information.  The employer or submitter matching could be done in a similar manner.

Important: Please review the attachment "Additional Client Notes.txt"  There is not enough room in this contest spec to provide it here.

Note:
- You are provided with conceptualization and questionaire document, please read these documents carefully to fully understand the scenario and the functionality for each users. Please don't hesitate to ask any questions in the forum. 
- Please use the "Exposure Registry Data.xlsx" as information for all the data the application might collect from the user. 

Target Audience:  Workers, Employers or Anyone

Judging Criteria: 
Your submission also will be judged using following criteria : 
1. Completeness & accuracy as defined in the attached supplemental documents
2. How well it demonstrates the interactive nature of the system that the client is striving for.  The client wishes to take advantage of the fact that this is a web application, not a web form.  So the submission must demonstrate that the system will adapt to user responses to questions during the Exposure Registration process.  For example, if the Country is US or Canada, then the system would request the State or Province as applicable.  Another idea is that the way the application elicits information could be closer to a conversation than a web form.  Ex. Instead of asking if the user is the worker or employer, the question could be: “Were you exposed to hazardous material in the workplace?”.  A useful tip to keep in mind is that although the Exposure Registry Data.xlsx lists all the data needed it may not always be necessary to ask the submitter for the information if the system can default information based on how the submitter answered a question.  Ex.  If the submitter identifies themselves as the worker, then obviously the registration is submitted on behalf of the worker, so there is no need to ask that question.
3. Usability.  We suggest you look at the application from the point of view of each of the target audiences.  Ex. is it intuitive?  Does it guide the user so they can very easily register an exposure?  Is information captured in a flow that makes sense?  Can someone who is not computer literate easily use it?  How about someone who isn’t comfortable with English, does the application provide enough guidance?  Is the language used by the application simple enough?  Can the user access the Help function without having to leave the registration process?  For Employers who are familiar with Soteria, does the application streamline the process for them?  For internal users & administrators, are there shortcuts to common tasks?
4. When the client looks at the wireframes for the Exposure Registration function, the initial impression is not that this is a typical government application

Submission and Source Files:  

Preview Image:
Create a 1024x1024 JPG or PNG file and place a screenshot from your submission within it. 

Submission File:
All requested contest requirements/screens as clickable HTML files unless otherwise stated in the contest details. 

Source Files:
Wireframes should be built in HTML, Axure (.rp).