wjladams/patient-decisions

Patient Decision Aid Research

Patient Decisions Application

This tablet based application aims to aid patient's make informed decisions about crucial health care choices.

• Thyroid-Prototype The html prototype for Thyroid Cancer.
• Otosclerosis-Prototype The html prototype for Otosclerosis.
• redcap The REDCap versions of the applications.
• storyboard: The storyboard for the application, and extra details around any specific workflows that come up

Useful External Links

The following are some external resources that we have created to help with workflow, screen layouts, design, etc.

• Initial Designs for Screens and Workflow in A Google Doc
• Dr. Natalie Justicz Initial Presentation

Participants in this research project

• Dr. Natalie Justicz was the researcher who started this project for Thyroid Cancer applications:
  • She developed the original prototype
  • She designed the AHP model in conjunction with Bill Adams
  • She designed the original workflow of the information walk through, in conjunction with Bill Adams and David Rodriguez.
• Dr. Nishchay Mehta:
  • Original researcher on the Otosclerosis application
  • Developer an AHP modeling structure for his dissertation that served as the template for both the Otosclerosis model and the Thyroid Cancer model.
  • Lead researcher using this application with patients to help them understand their treatment choices for otosclerosis.
• Dr. Bill Adams on LinkedIn, on Github: performed the following roles
  • Main developer of the web applications for the Thyroid Cancer and Otosclerosis use case.
  • Mathematician who designed and developed the new AHP theoretic calculations required.
  • Guided the design of the AHP models that power the decision for both the Thyroid Cancer and Otosclerosis models.
  • Setup and maintains the github source code repository.
• Dr. Anythony Cheung on LinkedIn:
  • Lead researcher administering the Thyroid Cancer application with patients
  • Lead researcher analyzing the results of the data that the Thyroid Cancer application receives.
• Charles Casper on LinkedIn was the REDCap developer for the Thyroid Cancer application, he:
  • Converted the existing prototype to REDCap
  • Worked in conjunction with Bill Adams, he created the AHP calculation framework in REDCap
  • Created the conditional walk through workflows and HTML screens in REDCap
• Dr. Bo Wang on Github, contributed as a research associate in the project. He is a:
  • Research Fellow in Harvard Medical University, Massachusetts Eye and Ear Infirmary, USA
  • Department of Thyroid and Parathyroid Surgery, Fujian Medical University Union Hospital，China
• David Rodriguez on Github was the lead Designer on both the Thyroid Cancer and Otosclerosis applications:
  • Designed the pairwise comparison screen
  • Designed the css and bootstrap code
  • Helped Dr. Justicz layout the steps of the patient walk through for Thyroid Cancer
  • Contributed greatly to the simplification of the presentation of the material

Analyses

• Analysis of Thyroid Cancer AHP Model Jupyter Notebook
• Analysis of Otosclerosis AHP Model, Jupyter Notebook

patient-decisions's Issues

add pseudo-code for calculation thyroid

dr.html add "delete user" item per user.

favicon for dr.html

Move ahpjs usage to dlens/ahpjs

The ahp functionality in the html version of the app has been moved to its own library. Decision Lens is the new maintainer of the library. We need to remove the ahp library from our source code and instead use the ahp library from github.

Add external links page to wiki

• Any google docs that are used for planning purposes
• any designs done online in external apps, etc.

delete old code base

remove the old react-native apps, they are not actively being developed at all, and have no plans for them to be.
We can always bring it back from before this commit if really wanted :)

first webview screen

We need the ability to load html files from the app "source" directory. I've no idea how that is done.

• Verify which kind of object to use to show HTML, WebView or perhaps a more full featured essentially bundled browser
• Add that object as the current main starting point of the app
• Load an html file from the app source
• Apply a css file to it.
• Get sample html and css

A simple issue

blah

first skeleton of android app

This is simply the skeleton created by android studio, nothing else.

favicon for demographics.html

ahp.js updated after Harker fix is added to that library

stupid isse

please ignore

demographic info for Otosclerosis model

We need a list of demographics and data types. @trotimi you can put the information in a comment on this thread.

demographic input screen

Basic demographic input for hard coded demographics

Export all pairwise, and scores in csv in dr.html

html version of demographic page

Just need a simple html page for the demographic inputs. @karanbagh once this page is done, if you could have it store info in html storage, that would be excellent.

clean up old ahp models in html dir

custom directory for html walk through files and setup in config.json

Have the directory for the walkthrough html customizable via the config.json file.

Additionally have a config.natalie.json and config.tobi.json for each of them.

Wiki quickstart running the app from source

A simple guide to get started running the app from source.

remove all remote javascript imports

This is so the application can be run from downloaded version of the site without any internet connection.
This way everyone can understand that this application sends no data anywhere except in local storage.

decide how we are going to store the multiple html pages

There will be a list of html pages for information, one such list for each type of patient. In other words there will be a list of lists. We want the non-programmers to use some tools to easily design these html pages. Perhaps we could do something to help, using some simple div's with classes and css styling. We could show the doctor's the format, and if they have the css file locally, they could edit and view.

However once we know what that file is, the question is where do we store each one? If the html is simple enough, perhaps we can store it in a list of strings? Or a resource file? We would also need the images referenced from each page (pages will certainly have one or more images...probably not much more than one.

Perhaps separate files for each one, and a "control file" that is a resource (or yaml file) that defines each script in terms of those pages? What do you think?

Order reverse timewise on dr.html export csv

add (i) icon in pairwise to show the longer description of the node being compared

demographic data input config via json file

Instead of hard coded demographic data, demo data should be configurable from a JSON file: There should be a couple of data types:

• Numeric (float)
• Simple string

The JSON info should have a title for the demographic column and the field type.

Thyroid cancer model file v1 in place

• A model csv file in place that has the criteria and alternatives in it.
• Initial estimated data for the alternative scores
• A sample user in the spreadsheet file
• A Jupyter notebook that would load the data.
• Implement wjladams/pyanp#52
• Do a first analysis with Monte Carlo

create apk

First apk created and Bill verifies it works on his virtual machine.

create html for thyroid cancer walkthrough