---
title: "Correct specialty on a tenant practitioner specialty record"
method: PATCH
path: "/practitioners/tenant-practitioner-specialties/specialty"
tags: ["Practitioner"]
---

# Correct specialty on a tenant practitioner specialty record

`PATCH /practitioners/tenant-practitioner-specialties/specialty`

Replaces the specialty identifier on a tenant practitioner specialty record. This is a data-correction operation — it does not trigger termination events, lifecycle changes, or downstream notifications. Use it when the wrong specialty was recorded and needs correcting without invoking the termination lifecycle; do not use it to end a practitioner's association with a specialty, use `PUT /practitioners/tenant-practitioner-specialties/terminate` for that. The specialty record must already exist, and the replacement specialty must be a valid, active tenant specialty.

## Headers

- `tenant-id` string

## Request body

- CorrectPractitionerSpecialtyRequest
  - `tenantPractitionerSpecialtyId` string, required — ID of the existing TenantPractitionerSpecialty record to correct
  - `newTenantSpecialtyId` string, required — ID of the new TenantSpecialty to replace the current one

## Response `200`

Specialty corrected successfully. The response is a flat JSON object with `id`, `tenantSpecialtyId`, and `data` keys.

- object

## Other responses

- `400` — Bad request - Invalid input
- `401` — Unauthorized - Authentication required
- `403` — Forbidden - Insufficient permissions
- `404` — Tenant practitioner specialty not found
- `409` — Conflict - Practitioner already has this specialty
- `500` — Internal server error

---

[API](https://skmtc.net/certifyos/apis/certify-api-layer.md) · [All operations](https://skmtc.net/certifyos/apis/certify-api-layer/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/certifyos/certify-api-layer/revisions/563848e0ecc0/schema)