Challenge Summary
Welcome to “VA PseudoVet - Wireframe Componentes Challenge”. In this challenge, we are looking for a fresh new user experience for a brand new system that creates and updates realistic and dynamic synthetic patient data. This data will provide to software developers the opportunity to develop programs and products utilizing the data types present in healthcare production system(s). You will be focused on creating how this application should look and represent the data.
We need to see intuitive and easy to use "wireframe concepts" that will let us design and build the final web user interfaces on the next stage of this project. Think on what are the best UI/UX practices when creating this wireframe.
This Studio competition will be run as a two-round tournament with a total prize purse of $2,500.00
Round One (1)
Submit your initial wireframes for checkpoint review.
1) Synthetic Patient Data Set Configuration
2) Any additional screen that support your idea
Feel free to add any screens which are necessary to explain your concept.
Submit your initial wireframes for checkpoint review.
1) Synthetic Patient Data Set Configuration
2) Any additional screen that support your idea
Feel free to add any screens which are necessary to explain your concept
Background Information
PseudoVet is an automated patient data fabrication engine which provides a set of active synthetic patients and clinical data that can be used for healthcare software development. Development against real patient data unnecessarily exposes patient health information (PHI) and personally identifiable information (PII) and cannot be used by developers outside of the VA network. However, fully functional, realistic data sets can be used safely in development, testing, training and other non-production environments in compliance with the Health Information Technology for Economic and Clinical Health Act (HITECH Act) and other regulations. Development against current fabricated data is not useful because the data sets are outdated, which requires development teams to spend time developing data sets to use in lieu of writing code or require licenses and cannot be shared.
Key Items to Focus on
- Think of an intuitive way to let users make configuration options
- Easy and intuitive use for tech and non tech users.
- This will be a web application so user 1280px as your main width.
Required Screens/Functionalities Synthetic Patient Data Configuration
The datasets will be generated through the following concepts:
Population Configuration
This area will allow a user to configure several parameters to influence the generated data.
- Number of patients
Determines the base number of patients generated.
Data Scope
- Start Date
Defaults to the start date of the war era selected. Can be used with the end date to provide a windowed view of patient data.
- End Date
Defaults to the current date. Used with the start date to determine patient age window.
- War Era Selection
Determines the start data of the data. More importantly, it sets up the pre-defined morbidity profiles for the generated data.
Morbidity Configuration
This section allows the user to input several diagnosis codes and configure them against the population. This section will pre-fill based on the war era, however, it will also allow a user to tweak the parameters as needed.
- Diagnosis Code
The diagnosis code for the morbidity. This code will determine the related conditions and encounter/episodes of care.
- % of population with diagnosis
Determines what percentage of the total generated population acquires this diagnosis. The totals of all diagnosis can be over 100%. In other words, it is possible for an individual to acquire more than one morbidity.
- % probability that the above population acquires diagnosis
Inside of the percentage selected above, the % chance that a patient acquires this diagnosis over the course of the date scope. For example, let’s say someone selects that 40% of the generated population could get heart disease. Of that 40%, this parameter will determine what percentage of that 40% will get this diagnosis each year.
- Exclusions
Allows a user to select a set of exclusions for the population. For example: You could have a heart disease diagnostic code, but place an exclusion that no female generated patients will get this disease.
- Related Conditions
Should automatically include any codes for related diagnoses. A user should be able to add/delete from this list as needed, however, we should seed the data based on the selected diagnosis code.
- Encounter/Episodes of Care Profiles
Based on the selected diagnosis, the system should generate the appropriate number of encounters and episodes of care.
Additional Screens
Include a way for the user to save and load their configurations from a file
Feel free to include additional screens that support your idea, such as modals interactions, dropdowns, autofills, etc.
Target Audience
The web site will be used by software developers and The Department of Veterans Affairs final users.
Learn Axure
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/support
Judging Criteria
- User Experience of the application/portal
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Wireframes should be built in HTML or Axure
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.
Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths
We need to see intuitive and easy to use "wireframe concepts" that will let us design and build the final web user interfaces on the next stage of this project. Think on what are the best UI/UX practices when creating this wireframe.
This Studio competition will be run as a two-round tournament with a total prize purse of $2,500.00
Round 1
This Studio competition will be run as a two-round tournament with a total prize purse of $2,500.00.Round One (1)
Submit your initial wireframes for checkpoint review.
1) Synthetic Patient Data Set Configuration
2) Any additional screen that support your idea
Feel free to add any screens which are necessary to explain your concept.
Round 2
Round Two (2)Submit your initial wireframes for checkpoint review.
1) Synthetic Patient Data Set Configuration
2) Any additional screen that support your idea
Feel free to add any screens which are necessary to explain your concept
Background Information
PseudoVet is an automated patient data fabrication engine which provides a set of active synthetic patients and clinical data that can be used for healthcare software development. Development against real patient data unnecessarily exposes patient health information (PHI) and personally identifiable information (PII) and cannot be used by developers outside of the VA network. However, fully functional, realistic data sets can be used safely in development, testing, training and other non-production environments in compliance with the Health Information Technology for Economic and Clinical Health Act (HITECH Act) and other regulations. Development against current fabricated data is not useful because the data sets are outdated, which requires development teams to spend time developing data sets to use in lieu of writing code or require licenses and cannot be shared.
Key Items to Focus on
- Think of an intuitive way to let users make configuration options
- Easy and intuitive use for tech and non tech users.
- This will be a web application so user 1280px as your main width.
Required Screens/Functionalities Synthetic Patient Data Configuration
The datasets will be generated through the following concepts:
Population Configuration
This area will allow a user to configure several parameters to influence the generated data.
- Number of patients
Determines the base number of patients generated.
Data Scope
- Start Date
Defaults to the start date of the war era selected. Can be used with the end date to provide a windowed view of patient data.
- End Date
Defaults to the current date. Used with the start date to determine patient age window.
- War Era Selection
Determines the start data of the data. More importantly, it sets up the pre-defined morbidity profiles for the generated data.
Morbidity Configuration
This section allows the user to input several diagnosis codes and configure them against the population. This section will pre-fill based on the war era, however, it will also allow a user to tweak the parameters as needed.
- Diagnosis Code
The diagnosis code for the morbidity. This code will determine the related conditions and encounter/episodes of care.
- % of population with diagnosis
Determines what percentage of the total generated population acquires this diagnosis. The totals of all diagnosis can be over 100%. In other words, it is possible for an individual to acquire more than one morbidity.
- % probability that the above population acquires diagnosis
Inside of the percentage selected above, the % chance that a patient acquires this diagnosis over the course of the date scope. For example, let’s say someone selects that 40% of the generated population could get heart disease. Of that 40%, this parameter will determine what percentage of that 40% will get this diagnosis each year.
- Exclusions
Allows a user to select a set of exclusions for the population. For example: You could have a heart disease diagnostic code, but place an exclusion that no female generated patients will get this disease.
- Related Conditions
Should automatically include any codes for related diagnoses. A user should be able to add/delete from this list as needed, however, we should seed the data based on the selected diagnosis code.
- Encounter/Episodes of Care Profiles
Based on the selected diagnosis, the system should generate the appropriate number of encounters and episodes of care.
Additional Screens
Include a way for the user to save and load their configurations from a file
Feel free to include additional screens that support your idea, such as modals interactions, dropdowns, autofills, etc.
Target Audience
The web site will be used by software developers and The Department of Veterans Affairs final users.
Learn Axure
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/support
Judging Criteria
- User Experience of the application/portal
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Wireframes should be built in HTML or Axure
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include 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.