douglasneuroinformatics/opendatacapture

An electronic data capture platform for administering remote and in-person clinical instruments

opendatacapture's Issues

[Feature]: Integrate API spec into GitHub pages site

Investigate OpenAPI standards

https://github.com/OAI/OpenAPI-Specification/
https://www.openapis.org/

Disable autofill on all forms

The same computers will be used for form entry over and over, autofill/autosave of form contents is both annoying and bad.

NEXT_PUBLIC_API_HOST is defined by .env instead of docker-compose

[Discussion]: Drug feature implementation

Orange Book from the FDA

instrument schema: implement optional report rendering feature for a given report

Allow a given instrument to render a printable report, if the rendering code is provided

Setup husky

Move spec into repo

Demographics input from "Add patient" should be reused across forms

Once I input that data once, the instrument page should be prefilled with the same info.

A clear button must be provided, which clears the form and the state.

Implement "pretty" success/failure popups

Currently JS alert like popups are used, does React have pretty ones?

Update NPM to v9x

[Feature]: Implement encryption for personal ID data

For the highest-tier consent for re-contacting for research purposes, the data collected and stored should be encrypted. Find a library that implements this well using some kind of key stored in ENV

Contact form for user feedback

setup structure for deployment

This should include an action with the following details:

• Activated on PR approved to main
• Rerun all tests and linting
• Build docker container for production
• Upload docker container to workplace server (see if this is possible)

Implement unified name for instruments in different languages

Chrome has scrollbars for the sidebar

autogenerate API docs from express code

• find a package that does this
• implement the proper annotations in the code
• integrate into the rest of the docs pages

Should instrument records store a reference to the subject, or the subject at the time the instrument was completed?

Instrument form question groups

Tags, groups

API should include an optional override for the datetime object for data entry

If we are importing historical data, we need a way to add the real datetime to the data instead of the server-computed one

Feedback template

Generate with mailto link with template

Setup docker build with new repo structure

Implement date time zones

Accept any date for API calls, but ensure it is created with UTC time. The client should always get the data in UTC time. Implement tests for this.

Fix security issues with docusaurus

SelectField does not clear on reset method

[Bug]: Website freezes while loading translations

This looks sloppy and should be fixed before the next round of demos. It should be relatively easy to add some kind of fade effect to hide network latency.

Move docs from docs app

Implement individual subject lookup

Similar to "Add Subject" form, do a lookup on the database and return a formatted report.

Implement subject ID as seperate field rather than _id in mongoose

This is due to edge cases such as a legal name change.

[Feature]: Create an interventions module similar in nature to the instruments module

In the sense that the admin, or other trusted users, can create interventions of a given kind which discriminates their data property.

How to do logging?

Official docs: https://docs.nestjs.com/techniques/logger

Consider this: https://github.com/winstonjs/winston

Initial error on running because utils must be built first

BUG - .env.local file is required due to old env system

Replace Joi with Zod for config validation

This is the only reason we use Joi

Setup automerge for dependabot PRs

Once build workflow is done, implement the following action:

1. Trigger on PR from dependabot
2. Trigger the CI pipeline
3. If the build passes and the dependency is not a major update by NPM convention, then merge into main

Show big popup at start that this is not for for day-to-day clinical use

Users need to click through and ok that this is not for first-line clinical use, its for data collection.

[Discussion]: Potential form instruments

• https://dcf.psychiatry.ufl.edu/files/2011/05/HAMILTON-DEPRESSION.pdf
• https://cgatoolkit.ca/Uploads/ContentDocuments/MMSE.pdf
• SAPS
• SANS
• https://www.cambridge.org/core/journals/the-british-journal-of-psychiatry/article/abs/new-depression-scale-designed-to-be-sensitive-to-change/94D3798EAE4FD0EF2FC50FF671E9AE5D#

[Discussion]: How to expand demographics spec to include possibility of contact information

Since we're thinking about consenting, lets allow storage of

• name
• email
• phone

This info would go through a separate consent to enable re-contacting for targeted recruitment. I think this is a particular want of some clinics for recruiting for pharma studies.

BUG - yarn dev will fail on first attempt on new install due to common library not being built

Packages that depend on other internal packages should wait for their complication prior to running command. Check turbo docs.

Ask for subject for session immediately after login

This can happen at the same time the user identifies their group, as we previously discussed.

Spec feedback

• use present tense everywhere
• add details of salt in hashing details
• [Forward Sortation Area](/_glossary?id=forward-sortation area) broken in Subject Registration
• document which funding source
• try to use inline code formatting when referring to tools
• translation should be mentioned

Instruments should not include sex

The Happiness index should not include sex

Expand non-identifiable demographics

• first three digits of postal code
• Ethnicity
• Life/Family status
• Married/relationships
• Children
• Living with people
• Employed

BUG - typechecking for client-side code is not enforced prior to commit

[Discussion]: Investigate interface for shareable one-off forms

Idea:
I want to send the happiness index form to a specific patient for them to fill out.

They should get a clickable URL that sends them straight to the form, which is pre-filled (or perhaps the state is pre-filled, but the fields are hidden), they then complete the form. The URL after this is no longer valid.

Are there libraries for this?

Instrument organization

Tags, groups

[Discussion]: Consider how to track and present consent forms

We need a way to present consent forms, and to renew consent if a new version is needed.

This seems like a mostly front-end issue? How do we conceptualize this for API/Backend?

[Feature]: Sort Table

Thinking something like this:
https://www.ag-grid.com/javascript-data-grid/component-filter/

Happiness index slider bugs

• value starts at NA instead of 5
• value is not shown on page

Implement environment variables for branding customization

• logo file
• "platform title"
• ADDMOREHERE