Correct a role key on the core practitioner record
PATCH/practitioners/:id/roles/correct
Renames an existing role key on the core practitioner record (for example, renaming PCP to Specialist) while preserving the associated 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 key was recorded incorrectly at the core practitioner level and needs correcting without invoking the termination lifecycle; for correcting a role at a specific group-practitioner-location record, use PATCH /practitioners/practitioner-locations/{id}/roles/correct instead. {id} is the certifyPractitionerId, and the role key being renamed must already exist on the core practitioner record.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 500
Role corrected successfully. practitionerRoles is populated with the corrected core roles map; locationRoles is always empty.
Bad request - Invalid role or role not found
Unauthorized - Authentication required
Forbidden - Insufficient permissions
Practitioner not found
Conflict - New role already exists on practitioner
Internal server error