Build a prototype page for managing medical problems -- 2

A newer method of medical documentation is called the problem oriented medical record (POMR). It focuses on a patient's medical problems and omits all the extraneous, unnecessary information that's in traditional medical charts. As the name implies, it's focused around the patient's medical problems so that documentation can occur quickly and care be delivered logically. Thus, each patient record would consist of a list of medical problems and their corresponding codes from and ICD-10 database. For starters, the software should be able to create a list of medical problems from an ICD 10 database. Problems will be added via several methods: • Search box; • Multi-select dropdown; • Macro whereby several problems can be added at once. For example, in medicine we often see the same problems in the same person. So the macros might look like:  Hypertension  Hypertension, obesity  Hypertension, obesity, diabetes mellitus  Hypertension, obesity, diabetes mellitus, dyslipidemia Each active problem is displayed in a list fashion and highlighted by a heading. Within the heading, several icons/options/controls will exist for that particular medical problem: • Headings could be color-coded, with active problems being green (green = go) • Problem name and IDC 10 code would be displayed: "Hypertension (i10)" • Problem can be designated active or inactive • Active problems will appear at the top and inactive problems will appear at the bottom • Views can be toggled to display all problems or only active problems • Arrows will exist within problem heading allowing it to be moved up and down. Drag and drop will also be allowed to move problems around on the list • A dropdown will exist beside the problem that will show associated diagnoses. This list is created elsewhere. If/when the problem needed to be changed then the new selection could take it’s place • Problems will allow brief and detailed view with the ability to quickly change. At the top there will be a toggle to show brief and detailed view of ALL problems. For example, say we’ve added the problem “coronary artery disease”. Then the brief view will only show “coronary artery disease (I25.1)”. But when we select the detailed view, we’ll see further description about that problem: Coronary artery disease (I25.1) --Presented 8/06 with chest pain and nuclear study and catheterization showed occlusion in RCA --Presented 10/07 with chest pain and nuclear study negative --Presented 4/10 with chest pain and cath showed new LAD lesion which was stented • An "x" to delete problems when necessary Within each problem, the SOAP concept will be used (though not all components will be filled in for each visit): S: Subjective O: Objective A: Comment/concern/DDx P: Plan/Orders (disposition, diet, medications, labs, imaging, nursing, referral, instructions, misc, etc) • Within the "O" component (objective), show current and historical data such as physical exam findings, lab studies, and imaging studies • For now, we’ll just have a blank field beside each of the 4 elements (SOAP) above. We will be adding other functionality to this section later Please keep in mind that the listed budget for this project is for the LARGER PROJECT. In other words, the project described above is a small part of the larger project. I'm looking to find a developer that I can work with long term to continually build and improve this application. I can send more information about the larger project to those who might be interested. But I figure the smaller project will be a trial to see if we are mutually compatible. I will send more information about the larger project to select developers who may be interested. Please address specifically how you would approach this project. The larger project has been started in Node/React with the Fuse template. Hoping to use MYSQL for the DB. I can send the code for what's been done. Thanks for your interest.