Open TuyizereBapt opened 2 years ago
@dexios1 let's look at this tomorrow to get it out of way
Hi @TuyizereBapt please take Dadson through the integration of this
Hi @TuyizereBapt please take Dadson through the integration of this
Yes. @pkdadson should let me know any challenges he might face while integrating this. I remember he was the one who raised this issue.
Describe the bug There is a mismatch between the backend implementation and front-end usage of the API endpoint for editing an insurance beneficiary (https://serenity-health.readme.io/reference/insurance-clients-and-payments#edit-an-insurance-beneficiary)
Impact What is the impact of this problem?
To Reproduce Steps to reproduce the behavior:
Note that, although an employee can also be an insurance beneficiary with a SELF (independent) relationship, there are other patients who can be insurance beneficiaries with DEPENDENT relationship
Expected behavior The insurance beneficiary should successfully be updated
Screenshots/Screencast![image](https://user-images.githubusercontent.com/37751827/160933878-058ee11f-84fb-4eab-aad4-736b90c5c611.png)
Request payload. From the request payload below, it is clear that what's being sent is an employee's data![image](https://user-images.githubusercontent.com/37751827/160931897-c8599d7b-d453-4d26-8912-e31308706df4.png)
What the API expects![image](https://user-images.githubusercontent.com/37751827/160931959-b671a36a-be56-4970-a04a-841e4ec30ec4.png)
Additional context N/A