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

[Feature Request]: Create API for PatientProfile #71

Open
rt4914 opened this issue Nov 5, 2024 · 0 comments · May be fixed by #76
Open

[Feature Request]: Create API for PatientProfile #71

rt4914 opened this issue Nov 5, 2024 · 0 comments · May be fixed by #76
Assignees
Labels
feature Building something new

Comments

@rt4914
Copy link
Owner

rt4914 commented Nov 5, 2024

Is your feature request related to a problem? Please describe.

We need CRUD APIs for PatientProfile

Describe the solution you'd like

Only authorised users can call these APIs

I have added * with some params which means its required/mandatory.

CREATE

  • In this the api will accept following things: name*, gender dob, blood_group, address_line_1*, address_line_2, city*, state*, country*, pincode*
  • The header will contain user related information, verify that this user is authorised. Basically this will help you fetch the user_id
  • Now based on these params, first add the address details to Address model and then use that address_id in establishment model.
  • Make sure User model also has a entry to connect patient profile.
  • Return the created object in json response.

UPDATE

  • In this the api will accept following things: user_id*, name, gender dob, blood_group, address_line_1, address_line_2, city, state, country, pincode
  • The header will contain user related information, verify that this user is authorised. Basically this will help you fetch the patient_profile_id
  • Now update whichever is required either in PatientProfile model or in Address model.
  • Return the updated object in json response.

DELETE

  • This api will accept: user_id
  • The header will contain user related information, verify that this user is authorised. Basically this will help you fetch the patient_profile_id
  • If authorised, delete the PatientProfileId.
  • Return success related message.

GET ALL

  • NO AUTHORISATION REQUIRED.
  • This api will accept any type of filter params like name, city, state, country, pincode, doctor_profile_id (via header).
  • Based on any of these params filter should get applied and corresponding results should be returned.

GET

  • NO AUTHORISATION REQUIRED.
  • This api will accept: user_id
  • The header will contain user related information, verify that this user is authorised. Basically this will help you fetch the patient_profile_id
  • If authorised, return the PatientProfile.

Describe alternatives you've considered

No response

Additional context

No response

@rt4914 rt4914 added the feature Building something new label Nov 5, 2024
@rray524 rray524 self-assigned this Nov 13, 2024
@rray524 rray524 linked a pull request Dec 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Building something new
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants