Challenge Summary
eAHR is a system to help manage data records while performing the various tasks of a study including scheduling of events, documenting actions performed and recording experiment results. Data management is considered to be a key element of a research program. There are also several regulatory requirements for laboratory to keep proper records in a research facility. The application needs to make it easy to capture entire data histories and has special requirements around how the information in the system needs to be viewed at certain points in the research workflow.
This first contest in a set of wireframe builds will define the overall navigation for the module and build out the screens for managing the scheduled events for data records and other related use cases described below and in the attached documentation.
NOTE: This contest will be run as a private competition. This means all documentation and forum discussion will be private and only available to members who have completed a CCA specific to this project. The public forum for this contest has more information about the CCA Process and how to get approved to access to the documentation.
Goal The goal of this contest is to wireframe the "main processing workflow" for the eAHR module. Based on the requirements provided in the private forum, you will need to wireframe the required use cases for the application. We are looking for you to meet the stated requirements and create a smart solution with the best overall page/click flow and user experience. A prototype for other, related modules of the application has already been created and will be provided to give you the context of the overall application and navigation. You do not have to integrate the prototype navigation skin or look and feel into your submission. You are required to show the top level navigation. You are also required to create a site map to accompany your submission: Several wireframe competitions will run to complete the eAHR module. For this first wireframe, you are required to complete a site map that outlines how the screens of the module will fit together and relate at an appropriate level of detail. It is important to think logically about eAHR navigation and how the user will easily be able to navigate and perform their various tasks. This should not simply be a representation of the screens defined in your wireframe submission. It should cover the entire module as described by the conceptualization document. It is OK to keep screens at a higher level of abstraction than individual pages or use cases. However, it should be complete enough so it is obvious where future wireframe competitions will ?integrate? and complete enough for the client to review and approve. Requirements Implement the use cases that make up the "Process Records" ? "Main Processing Loop" (See conceptualization Document 3.3.1). This process flow includes: - Step 1: Query/Search AHR - Step 2: View AHR - Step 3: Perform Actions - Step 4: Fill Events - Step 5: Perform Custom Processing The following Use Cases map to the above process flow. These requirements are highlighted in the attached concept document to help you focus on the required use cases and information for this wireframe. General use cases: - 4.4.7 View Health Records (4.4.50 Import Data from Ordering System - This use cases is needed for list of display fields.) - 4.4.8 Search Health Records - 4.4.14 View Resource Scheduling/Perform Actions - 4.4.17 View Event Schedules - 4.4. 27 Process Scheduled Events - 4.4.28 Process Unscheduled Events Manage/Fill Event Data - 4.4.32 Create Event Schedule - 4.4.33 Edit Event Schedule - 4.4.34 Remove Event Schedule Perform Custom Processing - 4.4.26 Perform Actions with AHR You are also required to create a site map as described above in the goals section. Contest Deliverables Round One For Round One please a first draft of the following wireframe pages for client feedback. The draft must include a site map to describe how the module use cases fit with the overall application. This first draft must be complete/coherent enough for the client to fully evaluate the module page flow. Incomplete wireframes will not be eligible for any Round One prizes. The following use cases are: - 4.4.7 View Health Records - 4.4.8 Search Health Records - 4.4.14 View Resource - 4.4.17 View Event Schedules - 4.4. 27 Process Scheduled Events - 4.4.28 Process Unscheduled Events - 4.4.32 Create Event Schedule - 4.4.33 Edit Event Schedule - 4.4.34 Remove Event Schedule Round Two In Round Two we will need you to take the client feedback and provide final/complete wireframes. The use cases from round 1 should be finalized. The following additional details/screens contained in the provided documents are required in this round: - 4.4.26 Perform Actions with AHR - Incorporate client feedback from use cases listed for round 1. - Incorporate client feedback for the sitemap submitted for round 1. - Any partially completed use cases from round 1 should be finalized. The client may add additional requirements based on Round 1 results and decisions made between now and the start of Round 2. You must submit all requested deliverables to be considered for prizes - you may submit more if necessary to explain your solution. Target Audience The application will be used primarily by research scientists and doctors. Their main goal is to easily perform the tasks needed to accurately schedule and complete actions and events at a specific time. Entry of data should be precise as well. Judging Criteria Your submission will be judged on the following criteria: - How well your wireframes provide a consistent user flow - How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client) Wireframe Resources - Wireframes on Wikipedia:http://en.wikipedia.org/wiki/Web_site_wireframe - Wireframe software option:www.axure.com - Example Wireframe: http://www.gdoss.com/web_info/web-site-wireframe.php Submission & Source Files Preview Image Please create your preview image as one (1) 1024x1024 px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it. You are free to resize or crop your submission to fit this size, but do not add any filters or elements for dramatic effect, such as drop shadows or reflections. Submission File All Requested Contest Submission Requirements stated above. Source Files All original source files of the submitted ideas. If you would like to submit notes please include ia notes.txt file. Final Fixes As part of the final fixes phase you may be asked to modify content or user click paths.
Round 1
At the end of Round 1 the client will choose five (5) Round 1 winners, each will win $100 and a receive a Design Review. These winners and any member who had a passing submission in round one will be eligible to compete in Round 2 for the additional $1,500 in prizes.Round 2
Round 2 will start with the announcement of the five (5) $100 Round 1 winners and their wireframe review from the client.Goal The goal of this contest is to wireframe the "main processing workflow" for the eAHR module. Based on the requirements provided in the private forum, you will need to wireframe the required use cases for the application. We are looking for you to meet the stated requirements and create a smart solution with the best overall page/click flow and user experience. A prototype for other, related modules of the application has already been created and will be provided to give you the context of the overall application and navigation. You do not have to integrate the prototype navigation skin or look and feel into your submission. You are required to show the top level navigation. You are also required to create a site map to accompany your submission: Several wireframe competitions will run to complete the eAHR module. For this first wireframe, you are required to complete a site map that outlines how the screens of the module will fit together and relate at an appropriate level of detail. It is important to think logically about eAHR navigation and how the user will easily be able to navigate and perform their various tasks. This should not simply be a representation of the screens defined in your wireframe submission. It should cover the entire module as described by the conceptualization document. It is OK to keep screens at a higher level of abstraction than individual pages or use cases. However, it should be complete enough so it is obvious where future wireframe competitions will ?integrate? and complete enough for the client to review and approve. Requirements Implement the use cases that make up the "Process Records" ? "Main Processing Loop" (See conceptualization Document 3.3.1). This process flow includes: - Step 1: Query/Search AHR - Step 2: View AHR - Step 3: Perform Actions - Step 4: Fill Events - Step 5: Perform Custom Processing The following Use Cases map to the above process flow. These requirements are highlighted in the attached concept document to help you focus on the required use cases and information for this wireframe. General use cases: - 4.4.7 View Health Records (4.4.50 Import Data from Ordering System - This use cases is needed for list of display fields.) - 4.4.8 Search Health Records - 4.4.14 View Resource Scheduling/Perform Actions - 4.4.17 View Event Schedules - 4.4. 27 Process Scheduled Events - 4.4.28 Process Unscheduled Events Manage/Fill Event Data - 4.4.32 Create Event Schedule - 4.4.33 Edit Event Schedule - 4.4.34 Remove Event Schedule Perform Custom Processing - 4.4.26 Perform Actions with AHR You are also required to create a site map as described above in the goals section. Contest Deliverables Round One For Round One please a first draft of the following wireframe pages for client feedback. The draft must include a site map to describe how the module use cases fit with the overall application. This first draft must be complete/coherent enough for the client to fully evaluate the module page flow. Incomplete wireframes will not be eligible for any Round One prizes. The following use cases are: - 4.4.7 View Health Records - 4.4.8 Search Health Records - 4.4.14 View Resource - 4.4.17 View Event Schedules - 4.4. 27 Process Scheduled Events - 4.4.28 Process Unscheduled Events - 4.4.32 Create Event Schedule - 4.4.33 Edit Event Schedule - 4.4.34 Remove Event Schedule Round Two In Round Two we will need you to take the client feedback and provide final/complete wireframes. The use cases from round 1 should be finalized. The following additional details/screens contained in the provided documents are required in this round: - 4.4.26 Perform Actions with AHR - Incorporate client feedback from use cases listed for round 1. - Incorporate client feedback for the sitemap submitted for round 1. - Any partially completed use cases from round 1 should be finalized. The client may add additional requirements based on Round 1 results and decisions made between now and the start of Round 2. You must submit all requested deliverables to be considered for prizes - you may submit more if necessary to explain your solution. Target Audience The application will be used primarily by research scientists and doctors. Their main goal is to easily perform the tasks needed to accurately schedule and complete actions and events at a specific time. Entry of data should be precise as well. Judging Criteria Your submission will be judged on the following criteria: - How well your wireframes provide a consistent user flow - How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client) Wireframe Resources - Wireframes on Wikipedia:http://en.wikipedia.org/wiki/Web_site_wireframe - Wireframe software option:www.axure.com - Example Wireframe: http://www.gdoss.com/web_info/web-site-wireframe.php Submission & Source Files Preview Image Please create your preview image as one (1) 1024x1024 px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it. You are free to resize or crop your submission to fit this size, but do not add any filters or elements for dramatic effect, such as drop shadows or reflections. Submission File All Requested Contest Submission Requirements stated above. Source Files All original source files of the submitted ideas. If you would like to submit notes please include ia notes.txt file. Final Fixes As part of the final fixes phase you may be asked to modify content or user click paths.
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.