Social Work: Add ability for documenting family information for a patient

[blestab]

🚀 Feature Proposal

There should be the ability to document a Social Work information for a patient. This issue MUST be completed before #2488

Social Work tab

There should be a new tab called Social Work on the patient profile screen. Under this tab there will be two sections, one titled Family Information and the other titled Expenses. This issue deals with the Family Information section

Family Information

When the Social Work tab is active, there should be a button labelled "Add Family Member", that allows a user to add a new family member. The Social Work tab should also display a table of information showing the already entered family members.

IMPORTANT NOTE: The images below is just for illustration purposes only. Styling must be as per the existing styles for forms, tables and buttons in other parts of the application.

When the user clicks on the Add Family Member button, they should be prompted to enter the following information:

name: string
age: number
civilStatus: string
relationship: string              NOTE: labelled as "Relationship to Patient"
education: string
occupation: string
income: number
insurance: string

This should create a family object entry under the patient

A family entry should also contain the following information that is auto generated by the system:

id: string
createdAt: string
updatedAt: string

• The table of family members should show the name, age, relationship to patient, occupation, income and insurance.
• The user must be able to edit or delete each entry listed in the table.

Technical Notes

• The routing should work similarly to the care plan routing

Motivation

Social Determinants of Health (SDOH) are important to capture as they help give the healthcare workers a better idea of factors that could potentially affect the patient's well being

[AashaiAvadhani1]

Hi,

I can work on this feature!

Thank you, Aashai Avadhani

[blestab]

Sure @AashaiAvadhani1 , thank you

[aostheory]

Hi @blestab, both myself and @jennifferyang will be working on this issue as a group with @AashaiAvadhani1. Can we also be added as assignees to the issue

[blestab]

Hi @blestab, both myself and @jennifferyang will be working on this issue as a group with @AashaiAvadhani1. Can we also be added as assignees to the issue

I have added you @AosTheory but I believe @jennifferyang needs to comment here for me to be able to pick her up as an assignee

[jennifferyang]

Hi, can you add me as an assignee as well? Thank you!

[blestab]

Hi, can you add me as an assignee as well? Thank you!

Done @jennifferyang

[blestab]

Hi @jennifferyang @AashaiAvadhani1 @AosTheory , compliments of the season and best wishes for 2021! Just checking how this work is going.

[AcharyaS97]

Is there work done on this issue? I picked up the backend ticket wanted to connect if there was already stuff done for the frontend, or i can take this over as well.

[matteovivona]

@AcharyaS97 unfortunately it seems to be at a standstill

[AcharyaS97]

I can take this over and start from scratch to implement the ticket per the spec?

[matteovivona]

I can take this over and start from scratch to implement the ticket per the spec?

Yep

[AcharyaS97]

Should this be integrated with the existing notion of a Related Person or be something completely separate? In the former case it would make sense because a lot of the existing stuff can be reused. The related person modal can be changed so that you can make clear that the related individual is/was a patient, or an untracked family member

[matteovivona]

It may be an idea, yes. In this case, all the information of the related person would be easily visible

[danny-sallis]

@tehKapa @jackcmeyer @fox1t I would like to take on this task please!

[acolmena]

Hi @tehKapa @jackcmeyer @fox1t, I will be working with @danny-sallis on this task. Could you add me as an assignee?