Challenge Overview
Detailed Requirements
Welcome to the “Pseudovet Angular Frontend App Integration with Python Backend API 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. We then followed it up with a challenge to improve the accuracy of the APIs of these APIs.
The APIs are documented in the following artefacts
-
TCUML
-
Swagger
-
Algorithm & API code (available in our repo)
We’ve also built a UI Prototype which we want to integrate with the provided backend APIs. Details about the prototype are available in the forums.
The final deliverable should be a single Python Flask project which integrates the provided UI prototype with the backend APIs.
The API to prototype mapping should be obvious from the Swagger & prototype pages, but if anything is not clear - please ask in the forums. If we find any discrepancies in the backend/ frontend from a mapping perspective, these will require to be fixed as part of this challenge.
Coding Standards - Backend
Backend - Follow python coding best practices : PEP 8 for the main text, and PEP 257 for docstring conventions
Coding Standards - Frontend
-
There should be no W3C errors or warnings in the frontend code
-
All files & methods must be well documented
Final Submission Guidelines
Final Submission Guidelines
-
Integrated project with backend API + prototype
-
Demo video of how to configure and run your submission
-
Configuration & Deployment guide to configure and run your submission
-
If updates are made to any backend API which require Swagger changes, you will need to submit the updated swagger as well