rt4914/KlinicCon-Backend

[Feature Request]: Create API for DoctorProfile

Opened this issue · 1 comments

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

We need CRUD APIs for DoctorProfile

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, years_of_experience, year_of_completion, specialisation_name, institute_name, degree_name
  • 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 check if degree_name is already available in Degree model, if yes get the degree_id, if no add to degree table and then get the id. At this point you should have degree_id. Apply same concept for institute and specialisation too.
  • Once you have all the associated IDs too, create the DoctorProfile
  • Make sure User model also has a entry to connect doctor profile.
  • Return the created object in json response.

UPDATE

  • In this the api will accept following things: user_id*, name, name*, gender dob, blood_group, years_of_experience, year_of_completion, specialisation_name, institute_name, degree_name
  • The header will contain user related information, verify that this user is authorised. Basically this will help you fetch the doctor_profile_id
  • Update the required details.
  • 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 doctor_profile_id
  • If authorised, delete the DoctorProfile.
  • Return success related message.

GET ALL

  • NO AUTHORISATION REQUIRED.
  • This api will accept any type of filter params like name, years_of_experience, year_of_completion, specialisation_name, institute_name, degree_name, 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 doctor_profile_id
  • If authorised, return the doctorprofile.

Describe alternatives you've considered

No response

Additional context

No response

here, @rt4914 I am waiting for #67 this issue to be solved first and get merged after review. then it will be easier to work on this. thanks!