Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database schema and CRUD for Patients #5

Open
3 of 6 tasks
Tracked by #7 ...
moozeq opened this issue Jan 13, 2023 · 0 comments
Open
3 of 6 tasks
Tracked by #7 ...

Database schema and CRUD for Patients #5

moozeq opened this issue Jan 13, 2023 · 0 comments
Labels
8 8 SP BE Back-end S2 - High Issue with high severity T1 - Feature Issue of feature type

Comments

@moozeq
Copy link
Owner

moozeq commented Jan 13, 2023

Description

Create basic back-end part for Patients (they are not Users and they can't log in the application) and they can be added by Users with "doctor" Role.

Prerequisites

Acceptance criteria

  • Create database schema for Patient class using sequelize-typescript with fields:
    • ssn Social Security number (or any other unique country-specific ID)
    • status - patient's status, allowed values: waiting, in-progress, completed, discontinued
    • name
    • surname
    • telephone? (optional)
    • email? (optional)
    • address? (optional)
    • medicalHistory - description of medical history of the patient
    • files - medical reports, column needs to be encypted!
    • meta - metadata dictionary where other less specific information can be stored
  • Add CRUD for Patients but only accessible for authorized Users with "doctor" Role
  • Add association one-to-many for Facilities (Database schema and predefined Facilities #4) and Patients
@moozeq moozeq added 8 8 SP S3 - Medium Issue with medium severity T1 - Feature Issue of feature type labels Jan 13, 2023
@moozeq moozeq added this to the [Sprint #1] Basic ClinOps milestone Jan 13, 2023
@moozeq moozeq added S2 - High Issue with high severity BE Back-end and removed S3 - Medium Issue with medium severity labels Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8 8 SP BE Back-end S2 - High Issue with high severity T1 - Feature Issue of feature type
Projects
None yet
Development

No branches or pull requests

1 participant