Introduction This tool allows providers to track cognitive assessments for high-risk MCI patients. This open-source project is designed to provide a standarized modular environment for digital psychometric analysis. The goal of this tool is to assist PCPs, Specialists, and Researchers obtain assessment data outside of the hospital environment at set frequencies. The software is not meant to replace existing providers, but provide additional data points to support a diagnosis.

How it Works This software is a web-based application that provides a portal for both patients and providers to access and perform assessments or assign assessments depending on their user rights. Each user will create a de-identified User Name in the hospital setting with the provider which will then be linked to their patient record through an EMR. The software does not contain PHI, rather it only tracks the measures which are assigned. The results of the measures will be accessible via the application for the individual user thorugh a reporting page. Providers can access the data through a secure API or directly through the application.

This web-based application is intended to be run on touch-enabled devices which include laptops and other mobile devices, not excluding other modalities which allow for a touch experience and have a modern browser.

Presentation: Slide Deck

GitHub Repo: Fish Dreams Analysis Tool

Demo Images:

Development The software is designed to be a mobile-first responsive web application. The following technologies are being utilized:

1. Bootstrap
2. Datatables.net
3. Jquery
4. Responsive design
5. Mobile ready

1. .Net Core 2.2
2. MongoClient

1. MongoDb

In order to create the standard that will be used for all assessment types, a commonly utilized script type should be used. In this case we are using the JavaScript Object Notation (JSON) format. Due to the anticipated dynamic nature of each assessment this is expected to evolve prior to the release of version 1.0. The goal is to establish a template that can vary greatly but using common elements and steps.

The following example is the current state of the template for a mock test containing 4 questions:

{
    "AssessmentId": "ABCD",
    "Name": "Mock Stroop Test",
    "Version": "1.0.0",
    "Instructions": "Press the letter corresponding color shown (r = RED, g = GREEN, b = BLUE, y = YELLOW). Press the appropriate key when the text shows.",
    "Steps": [
        {
            "StepNumber": 1,
            "Name": "Question 1",      
            "InformativeText": "Step 1 Instruction", 
            "PossiblePoints": 1,      
            "DisplayParams": {
                    "DisplayType": "text",
                    "Content": "Blue",
                    "Css": "color:Purple; font-size:72px" 
                }, 
            "ResponseParams": { 
                "ResponseType": "text",                 
            }            
        },
        {
            "StepNumber": 2,
            "Name": "Question 2",      
            "InformativeText": "Step 2 Instruction", 
            "PossiblePoints": 1,      
            "DisplayParams": {
                    "DisplayType": "text",
                    "Content": "Yellow",
                    "Css": "color:Blue; font-size:72px" 
                }, 
            "ResponseParams": { 
                "ResponseType": "True or False",                 
            }            
        }

    ]
}

The application leverages Microsofts Identity Service for user management supported on MongoDb. Support for MongoDb is provided by AspNetCore.Identity.MongoDbCore written by Alexandre Spieser.

Two roles exist in this application an Administrator and a Particpant. Since no user at this time will be a super user, the Administrator will be the researcher/provider user type. The Particpant will be the user taking the assessments.

In development mode, a seed service adds the following default users:

User Type: Administrator
User Name: admin
Email: admin@nowhere.com
Password: Test123!

User Type: Participant
User Name: bob
Email: bob@nowhere.com
Password: Test123!

Milestone 1

Planning - 2/1/2019 - 4/12/2019

• Concept Approval
• Identify Requirements
• Establish Risks
• Identify Tools
• Develop Budget
• Receive Grant/Award

Milestone 2

Research and Development - 2/1/2019 - 6/30/2019

• Identify Subject Matter Experts
• Research Cognitive Assessments
• Identify Assessments
• Develop Standard Assessment Template
• Implement Requirements
• Configure and Implement CI/CD
• Develop Software
• Develop Static Project Site

Milestone 3

Verification Testing - 7/1/2019 - 7/31/2019

• Perform Test Cases
• Perform Hotfixes

Milestone 4

User Acceptance Testing - 8/1/2019 - 8/23/2019

• Deploy to Demo Site
• Collect User Experience Data
• Evaluate Results
• Perform Hotfixes

Milestone 5

Release Documentation - 8/24/2019 - 8/31/2019

• User Guide
• Release Notes

Milestone 6

Release - 9/1/2019

• Roll-out v1.0 with Disclaimer

Milestone 7

Next Steps - 9/2/2019 - *

• Discuss v2.0 as Product
• FDA Requirements
• Research Assessment Licenses

• Sarah Price - sarah.price@utexas.edu
• Adriana Cardenas - adri.cardenas@utexas.edu
• CJ Fraher - fraher@gmail.com

We would first like to thank the LifeSci Hack conference organizers for giving us the opporunity to help the community and open-source healthcare world. These members are: Sarah Sharif, Suliman Sharif, Scott Collins, and Amanda Ross

http://www.lifescihack.com/

This project could not have started without the wonderful work and effort of the hackathon team, FishDreams!

• Jessica Moore Bonner
• Reva Schweitzer
• Sarah Price
• Adriana Cardenas
• Christopher J Fraher

This project continues today through grants supported by the following, a special thanks to you all:

Moz://a

And to those who supported the LifeSci Hack 2019 event!

• The Leona M. and Harry B. Helmsley Charitable Trust
• SXSW
• wework
• L7 Informatics
• Swyft

Royalty free test images currently in use are provided through Unsplash

MIT License