Correct a role key on a practitioner-location record
PATCH/practitioners/practitioner-locations/:id/roles/correct
Renames an existing role key on the specified practitioner-location association record (for example, renaming PCP to Specialist) while preserving all existing role metadata such as effectiveDate and terminationDate. This is a data-correction operation — it does not trigger termination events or lifecycle changes. Use it when a role was recorded with the wrong key at the group-practitioner-location level and needs correcting in place; for correcting a role key at the core practitioner level, use PATCH /practitioners/{id}/roles/correct instead. {id} is the GroupPractitionerLocation record identifier, obtained from the practitioner's location relationship data, and the role key being renamed must already exist on the record.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 500
Location role corrected successfully. practitionerRoles is always empty; locationRoles has a single entry keyed by the location ID.
Bad request - Invalid role or role not found
Unauthorized - Authentication required
Forbidden - Insufficient permissions
Location not found
Conflict - New role already exists on location
Internal server error