Challenge Overview
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.
Challenge Requirements
We’ve run multiple challenges for this project so far to build an algorithm for generating aging and morbidity data. We first launched a challenge to build an algorithm for generating patient data. This was followed up with another challenge to convert the algorithm to use an updated dataset that includes morbidity data. We then ran a challenge to build APIs on top of this algorithm.
Recently, we’ve needed to add additional output formats for the datasets. This new output format is called FHIR. You can find information about FHIR format here: https://www.hl7.org/fhir/overview.html
Generated data should be validated using the methods described here: https://www.hl7.org/fhir/validation.html
and here: http://fhirtest.uhn.ca/home?encoding=json&pretty=true
We have updated the UI prototype to include a drop-down to select from several formats when creating a new dataset, and a column on the dashboard to tell the user which format the dataset generation file is in. Now we need to update/add new API endpoints as well as ensure the data generation engine can output to the new FHIR format in both XML and JSON.
Please check the forum for instructions on getting access to the github repo and for a link to the github issue describing his challenge.
Coding Standard
Follow python coding best practices : PEP 8 for the main text, and PEP 257 for docstring conventions
Documentation
Please document any new endpoints you create and what they do.
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.
Challenge Requirements
We’ve run multiple challenges for this project so far to build an algorithm for generating aging and morbidity data. We first launched a challenge to build an algorithm for generating patient data. This was followed up with another challenge to convert the algorithm to use an updated dataset that includes morbidity data. We then ran a challenge to build APIs on top of this algorithm.
Recently, we’ve needed to add additional output formats for the datasets. This new output format is called FHIR. You can find information about FHIR format here: https://www.hl7.org/fhir/overview.html
Generated data should be validated using the methods described here: https://www.hl7.org/fhir/validation.html
and here: http://fhirtest.uhn.ca/home?encoding=json&pretty=true
We have updated the UI prototype to include a drop-down to select from several formats when creating a new dataset, and a column on the dashboard to tell the user which format the dataset generation file is in. Now we need to update/add new API endpoints as well as ensure the data generation engine can output to the new FHIR format in both XML and JSON.
Please check the forum for instructions on getting access to the github repo and for a link to the github issue describing his challenge.
Coding Standard
Follow python coding best practices : PEP 8 for the main text, and PEP 257 for docstring conventions
Documentation
Please document any new endpoints you create and what they do.
Final Submission Guidelines
- Updated README to include information about the new endpoints and data format
- Updated Postman collection
- Demo video of your code exporting to the new format