bayeshack2016/vetafi

#VA

Vetafi

Vetafi is a powerful, easy-to-use web-app that improves health claim filing experiences for U.S. veterans.

We can help you...

• Research and manage your health file claims
  • Learn about your health benefits and entitlements
  • Track the status of your claims, including ones you have already filed. Never lose your documents again!
• File your health claims quickly and efficiently
  • We streamline complex health & military forms into simple questionnaires so they are easy to understand and you don't have to re-fill information.
• Automatically generate VA forms with your information already filled out!

Demo

For our hackathon demo, please visit: http://vetafi.herokuapp.com/
Our production site is coming soon! 😄

Developing

Currently we use VirtualBox / vagrant for development. Please see installation instructions for vagrant and VirtualBox below:

Setup AWS Credentials

All of the below steps assume that you have access to the vetafi AWS account.

In order to get access, an account will be created for you by the admins and you will be given an API key.

The api key is expected to be stored in ~/.aws/credentials under the [default] section.

Contact [email protected] to get an account created for you.

OS X

If you are on OSX the easiest was to get setup is to use the brew package manager.

• brew cask install virtualbox
• brew install vagrant

Windows

Please see https://www.vagrantup.com/downloads.html for instructions.

Setup Vagrant Box

Before using the vagrant development environment for the first time, you must setup with:

vagrant plugin install vagrant-s3auth
vagrant up

To install the vetafi vagrant box.

One you are setup you can run vagrant ssh to shell into the development environment. This environment will allow you to run the app and tests locally, described further in hardhome/README.md.

Brought to you by:

• Aaron Hsu
• Jeff Quinn
• Bayes Impact (www.bayesimpact.org)

vetafi's Issues

formTemplateService isn't found when running gulp

gulp build

only preprocesses files and moves them all into the build folder.

gulp

runs a local webserver that hosts the webapp. gulp build is one of its tasks. For some reason, angular cannot find formTemplateService. This slows down front-end web dev on my end. :/
Would be great to figure this out

Real Terms of Service

For a site like ours, there are two places where Terms of Service appears.

One is right before a user starts a claim, which is that popup. The other should be accessible through one of the footer links.

Both ways should direct to show the same ToS string. However, in the former case (popup), is the only place where we choose we "accept" the Terms. The latter case (single page) is just so people can read it.

Confirm and View Claim need some fixing

those pages don't fetch real user's claims yet

Aaron's biscuit is bad

I have to comment out biscuit related things in order to run our server, even on vagrant.

I get the following errors:

1|Express  | environment: "local"
1|Express  | Listening on port 3999. Winter is coming!
1|Express  | Redis connected at localhost:6379
1|Express  | Database connection opened at 0.0.0.0:27017
1|Express  | Error: Command failed: biscuit get -f /vagrant/config/biscuit/secrets.yaml 'local::lob-api-key'
1|Express  | Warning: decryption under kms failed: NoCredentialProviders: no valid providers in chain. Deprecated. 
1|Express  |    For verbose messaging see aws.Config.CredentialsChainVerboseErrors
1|Express  | Warning: decryption under kms failed: NoCredentialProviders: no valid providers in chain. Deprecated. 
1|Express  |    For verbose messaging see aws.Config.CredentialsChainVerboseErrors
1|Express  | Warning: decryption under kms failed: NoCredentialProviders: no valid providers in chain. Deprecated. 
1|Express  |    For verbose messaging see aws.Config.CredentialsChainVerboseErrors
1|Express  | NoCredentialProviders: no valid providers in chain. Deprecated. 
1|Express  |    For verbose messaging see aws.Config.CredentialsChainVerboseErrors
1|Express  |     at ChildProcess.exithandler (child_process.js:202:12)
1|Express  |     at emitTwo (events.js:100:13)
1|Express  |     at ChildProcess.emit (events.js:185:7)
1|Express  |     at maybeClose (internal/child_process.js:850:16)
1|Express  |     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)

Address Not Populated for Claim Submit Page

Even after filling out address information in a form, the user address is not populated for the claim submit page.

Form Page Sometimes Does not Calculate Number of Answered Questions

After autocomplete it seems like the count of answered questions is sometimes wrong, which prevents users from submitting the completed form. Need to reexamine the client side logic in winterfell/webapp/src/js/formCtrl.js

Keypress Enter Seems to Not Submit Login/Signup Form

Note to self to look into this

Allow for Optional Questions in Form

Some questions, like second address should be made optional. Currently the form logic requires all questions to be answered.

Server-side password needs to be hashed in db

Production submit claim does not work

It works locally, so I suspect it could be something to do with mailingService.
Maybe the production logs will tell us the error

Backend overwriting user_values is weird

Real FAQ

A lot of the logic for the FaQ page is available (the search functionality).

We should just have ways to make the resource content actually helpful - it's still dummy strings.

Cannot find module 'underscore'

What is the purpose of this line: https://github.com/bayeshack2016/vetafi/blob/master/winterfell/app.js#L13

Getting the following exception when I try to run the server:

Error: Cannot find module 'underscore' at Function.Module._resolveFilename (module.js:438:15) at Function.Module._load (module.js:386:25) at Module.require (module.js:466:17) at require (internal/module.js:20:19) at Object.<anonymous> (/Users/jeffreyquinn/Code/VA_hackathon/vetaffi/winterfell/middlewares/passport.js:1:71) at Module._compile (module.js:541:32) at Object.Module._extensions..js (module.js:550:10) at Module.load (module.js:456:32) at tryModuleLoad (module.js:415:12) at Function.Module._load (module.js:407:3)

Support Page

If people have any issues, they should be able to contact someone? Should we leave that out for now?

Can we have a [email protected] email?
Whenever emails get sent to that, we get notified as well?

Beta-mode banner

in header or front page-only?

Address Edit Box on Claim Confirm Page In Wrong Order

winterfell/webapp/src/templates/modals/confirmClaimModifyAddress.pug lists element form inputs in a non standard order, with country coming before postal code.

Select Forms Page doesn't show any forms to select

Created a new user.
Started a Claim. Clicked on Proceed, and got passed ToS.
When I'm on Select Forms page, I don't see any forms to select.

0/0 required forms, so I can click Submit even though I shouldn't

how to tell if a form a user filled out is complete?

I would like to know if a form is partially/not filled or done.
Basically how can we track states of a form?