You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy the existing two assign patient API endpoints to use new urls on the /person namespace
Details / Tasks
POST /patient/<patient_reference_id>/person -> POST /person
Copy the functionality of assigning a patient (or list of patients) to a new person cluster using POST /person, this endpoint should accept a list of patient reference ids (eg '{"patients": ["<patient-reference-id>"]}')
PATCH /patient/<patient_reference_id>/person -> PATCH /person/<person-reference-id>
Copy the functionality of assigning a patient (or list of patients) to an existing person cluster using PATCH /person/<person-reference-id>, this endpoint should accept a list of patient reference ids (eg '{"patients": ["<patient-reference-id>"]}')
In the API docs, mark the existing /patient/X/person endpoints as "DEPRECATED".
NOTE: At this time, do not delete the existing /patient endpoints that we are copying, although they will be deleted in the future.
Summary
Copy the existing two assign patient API endpoints to use new urls on the /person namespace
Details / Tasks
POST /patient/<patient_reference_id>/person
->POST /person
Copy the functionality of assigning a patient (or list of patients) to a new person cluster using
POST /person
, this endpoint should accept a list of patient reference ids (eg'{"patients": ["<patient-reference-id>"]}'
)PATCH /patient/<patient_reference_id>/person
->PATCH /person/<person-reference-id>
Copy the functionality of assigning a patient (or list of patients) to an existing person cluster using
PATCH /person/<person-reference-id>
, this endpoint should accept a list of patient reference ids (eg'{"patients": ["<patient-reference-id>"]}'
)In the API docs, mark the existing
/patient/X/person
endpoints as "DEPRECATED".NOTE: At this time, do not delete the existing /patient endpoints that we are copying, although they will be deleted in the future.
Related Issues/PRs
#155
Notes / Comments
This work will complete use cases 1, 2, 3 and 6 specified in #155
The text was updated successfully, but these errors were encountered: