Challenge Summary
Welcome to “PseudoVet - Wireframe 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 that provides to the 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 an 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.
1) Login with error messages/alerts
2) Synthetic Patient Data Sets
3) Any additional screen that support your idea
Feel free to add any screens which are necessary to explain your concept.
1) Login with error messages/alerts
2) Synthetic Patient Data Sets
3) 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 used by software developers at the VA. It 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.
VHA Innovation has always utilized synthetic data provided by VA Electronic Health University (VeHU), in the Future Technologies Laboratory. The data is static and does not allow for real time or real world scenarios to occur over time for any modality. Furthermore,it is often the case that Developers will develop a handful of patients for the specific problems they have been contracted to solve. In this regard, there is no sure way to evaluate the validity and accuracy of the data as they are hand tooled by the Contractors to work with their systems.
This challenge proposed the method of populating fields into the synthetic data sets.
Initial Data Sets (Morbidity Data) - As reference
Areas of focus for this initial data generation and mapping exercise include Morbidities and Co-Morbidities for the following:
- Era-specific Veteran ailments (Agent Orange, Gulf War Syndrome, etc.)
- WWII Exposures
- Korean War Exposures
- Vietnam War Exposures
- Gulf War Exposures
- High Focus Morbidities and Co-Morbidities or Hearing Loss Leg, Knee, Ankle and Joint Injuries
- - Rheumatoid arthritis
- - Amputation
- - Osteoarthritis
- - Osteomyelitis/septic arthritis
- - Osteoporosis
- - Multiple joint disease o Diabetes
- - Cancer
- - Mental Health
- - - PTSD
- - - Suicide
- - Traumatic Brain Injury (TBI)
- - Spinal Cord Injuries (SCI)
Key Items to Focus on
- Focus on general navigation between data sets.
- Look for the best way to build generative models, which will be used to produce new synthetic datasets..
- A description of what those fields are, beyond the manifest already provided, can be obtained from the VA’s VistA Data Library (VDL) http://www.va.gov/vdl
- Please refer to https://github.com/OSEHRA/VistA as a reference system for this effort. This is to be an open source development effort with synthetic data. There is no need to enforce privacy regulations for data that is not real.
- Creates the mapping that generates relevance through the association of profile data fields) (ex: profile of healthy patient....what happens when variables are applied, changes the overall profile).
- Allow configuration, ingestion, extensibility, export and synchronization of PseudoVet as a whole.
- 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
1) Login
- Create a simple login that allows users access the application.
- Use common login features: email, password, remember, forgot password.
- Do not use social media login on this application.
- Show how the error messages/alerts should work.
2) Synthetic Patient Data Sets
- The following is an example of data that needs generation through these web-services:
PATIENT SEED DATA:
- Names: Last, First, Middle, Suffixes (last names should be not real)
- Phone
- Number
- Email
- Address
- Social Security Numbers (Must be valid but from deceased or otherwise assignable for development and testing purposes. Can use 000 or 666)
- Occupation and Incomes
- Gender
- Race
- Height
- Weight
- Religion
- Language
- Next of Kin
- Emergency Contact
- Smoking and Alcohol History
- ICN: Local and National
- Allergies / Drug Sensitivities
- Medications
- Vital Signs
- Military Service
- Service Connected and Non-Service Connected Disabilities:
- Locations (Address data)
- War Eras
- - WWII, Korea, Vietnam, Gulf War
- ICD-10, SNOMED Diagnosis, DSM and Procedure Codes
- TIU Note Templates
- Lab Value Mapping
- Diagnosis Mapping
- Family History Data
- Immunizations
- Genetic Diagnosis Information
- Hospitalizations
- Insurance Data
- Consent
- Social History
- Problem
- Advance Directives
- Encounter Data (Outpatient/Inpatient)
- Appointments
- Procedures (Clinical, Surgical, Physical)
- Facility Name
- Facility Address
- Primary Care Provider Assignment
- Providers (Other) Assignment
- Clinics
- Consults
- Referrals
- Clinical Instructions
- Medications Administered
- Location of Admission and Discharge
- Health Plan Authorization Act
- Mapping between Lab Values and Diagnosis
- Mapping between Diagnosis and Procedure Codes
HEALTHCARE PROVIDER SEED DATA:
(i.e. Clerical, Nursing, Physician, Radiologist, Social Work, Laboratory, et al)
- Address
- Room Numbers
- Clinic Locations
- Clinical Hours
- Clinic Types (Initial)
- Internal Medicine
- Primary Care Outpatient
- Audiology
- Mental Health
- ENT
- Optometry
- Dental
- Cardiology
- Emergency Room
3) Additional Screens
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 an 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
Submit your initial wireframes for checkpoint review.1) Login with error messages/alerts
2) Synthetic Patient Data Sets
3) Any additional screen that support your idea
Feel free to add any screens which are necessary to explain your concept.
Round 2
Submit your final wireframes for checkpoint review.1) Login with error messages/alerts
2) Synthetic Patient Data Sets
3) 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 used by software developers at the VA. It 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.
VHA Innovation has always utilized synthetic data provided by VA Electronic Health University (VeHU), in the Future Technologies Laboratory. The data is static and does not allow for real time or real world scenarios to occur over time for any modality. Furthermore,it is often the case that Developers will develop a handful of patients for the specific problems they have been contracted to solve. In this regard, there is no sure way to evaluate the validity and accuracy of the data as they are hand tooled by the Contractors to work with their systems.
This challenge proposed the method of populating fields into the synthetic data sets.
Initial Data Sets (Morbidity Data) - As reference
Areas of focus for this initial data generation and mapping exercise include Morbidities and Co-Morbidities for the following:
- Era-specific Veteran ailments (Agent Orange, Gulf War Syndrome, etc.)
- WWII Exposures
- Korean War Exposures
- Vietnam War Exposures
- Gulf War Exposures
- High Focus Morbidities and Co-Morbidities or Hearing Loss Leg, Knee, Ankle and Joint Injuries
- - Rheumatoid arthritis
- - Amputation
- - Osteoarthritis
- - Osteomyelitis/septic arthritis
- - Osteoporosis
- - Multiple joint disease o Diabetes
- - Cancer
- - Mental Health
- - - PTSD
- - - Suicide
- - Traumatic Brain Injury (TBI)
- - Spinal Cord Injuries (SCI)
Key Items to Focus on
- Focus on general navigation between data sets.
- Look for the best way to build generative models, which will be used to produce new synthetic datasets..
- A description of what those fields are, beyond the manifest already provided, can be obtained from the VA’s VistA Data Library (VDL) http://www.va.gov/vdl
- Please refer to https://github.com/OSEHRA/VistA as a reference system for this effort. This is to be an open source development effort with synthetic data. There is no need to enforce privacy regulations for data that is not real.
- Creates the mapping that generates relevance through the association of profile data fields) (ex: profile of healthy patient....what happens when variables are applied, changes the overall profile).
- Allow configuration, ingestion, extensibility, export and synchronization of PseudoVet as a whole.
- 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
1) Login
- Create a simple login that allows users access the application.
- Use common login features: email, password, remember, forgot password.
- Do not use social media login on this application.
- Show how the error messages/alerts should work.
2) Synthetic Patient Data Sets
- The following is an example of data that needs generation through these web-services:
PATIENT SEED DATA:
- Names: Last, First, Middle, Suffixes (last names should be not real)
- Phone
- Number
- Address
- Social Security Numbers (Must be valid but from deceased or otherwise assignable for development and testing purposes. Can use 000 or 666)
- Occupation and Incomes
- Gender
- Race
- Height
- Weight
- Religion
- Language
- Next of Kin
- Emergency Contact
- Smoking and Alcohol History
- ICN: Local and National
- Allergies / Drug Sensitivities
- Medications
- Vital Signs
- Military Service
- Service Connected and Non-Service Connected Disabilities:
- Locations (Address data)
- War Eras
- - WWII, Korea, Vietnam, Gulf War
- ICD-10, SNOMED Diagnosis, DSM and Procedure Codes
- TIU Note Templates
- Lab Value Mapping
- Diagnosis Mapping
- Family History Data
- Immunizations
- Genetic Diagnosis Information
- Hospitalizations
- Insurance Data
- Consent
- Social History
- Problem
- Advance Directives
- Encounter Data (Outpatient/Inpatient)
- Appointments
- Procedures (Clinical, Surgical, Physical)
- Facility Name
- Facility Address
- Primary Care Provider Assignment
- Providers (Other) Assignment
- Clinics
- Consults
- Referrals
- Clinical Instructions
- Medications Administered
- Location of Admission and Discharge
- Health Plan Authorization Act
- Mapping between Lab Values and Diagnosis
- Mapping between Diagnosis and Procedure Codes
HEALTHCARE PROVIDER SEED DATA:
(i.e. Clerical, Nursing, Physician, Radiologist, Social Work, Laboratory, et al)
- Address
- Room Numbers
- Clinic Locations
- Clinical Hours
- Clinic Types (Initial)
- Internal Medicine
- Primary Care Outpatient
- Audiology
- Mental Health
- ENT
- Optometry
- Dental
- Cardiology
- Emergency Room
3) Additional Screens
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.