Patient profile creation

boyle / 2018-measure-stress

Using machine learning to investigate sympathetic activation of the autonomic nervous system (SAANS) during the treatment of mild traumatic brain injury, chronic pain, and post-traumatic stress disorder.

3 stars 1 forks source link

Patient profile creation #19

Closed fcharih closed 5 years ago

fcharih commented 5 years ago

Users should be able to create a new patient profile within the application. This can likely be done with a form. Fields to be collected will be specified in a JSON document and rendered as input boxes, radio buttons, etc.

fcharih commented 5 years ago

What is useful information that might be worth storing in a patient profile?

Gender
Reason for referral
?

boyle commented 5 years ago

reason for referral = diagnoses (chronic pain, post traumatic stress, brain injury) + severity
height + weight ( = estimate BMI, validate force plate/3d point cloud geometry... in theory we can calculate these from the instrumentation)
heart condition (any previous heart diagnoses which might affect interpretation of the heart beat data)

Should this information be stored in the "user" configuration or with the patient data? If with the user data, it could be stored as a JSON file per patient (e.g. p12.json). (Currently there is no place to put "common" patient data between sessions.)

fcharih commented 5 years ago

Ideally, it would be in a file for data that is persistent for a patient across sessions. That would be ideal. Otherwise, we can also store it in the suggested format "patient_1234.json" in the user's directory as you suggest. Let's go with that for now. These files will live alongside the user-specific config.json file.

boyle commented 5 years ago

Sounds good. We can migrate later, if that makes sense. This method does facilitate looking up a list of patient numbers for a user: they can look at the JSON files in the user config dir that match a particular pattern: p[0-9]+.json

fcharih commented 5 years ago

Not an issue.