latestOpenAPI 3.1.02026-08-194237902.5 MB

563848e0ecc0

Facility

Correct a facility-level specialty record

Updates a TenantFacilitySpecialty record (Level 1) by replacing the tenant_specialty_id, updating the effective date, or both. At least one of newTenantSpecialtyId or effectiveDate must be provided. Use this for data-correction scenarios where a facility's direct specialty association needs to be updated without triggering credentialing lifecycle events — it does not propagate changes to group, location, or network specialty records. For corrections that need to cascade to group-level records, use PATCH /facilities/tenant-group-facility-specialties/specialty instead. Does not trigger termination events or lifecycle changes. Returns the raw updated record (id, tenantSpecialtyId, data) as an untyped JSON object, not a curated response DTO.

patch/facilities/tenant-facility-specialties/specialty

Headers

tenant-idstring

Request body

tenantFacilitySpecialtyIdstring required

ID of the existing TenantFacilitySpecialty record to update

newTenantSpecialtyIdstring

ID of the new TenantSpecialty to replace the current one. Optional if effectiveDate or isPrimary is provided.

effectiveDatestring

New effective date for the specialty record in ISO format (YYYY-MM-DD). Optional if newTenantSpecialtyId or isPrimary is provided.

isPrimaryboolean

Whether this specialty should be marked as primary. Optional if newTenantSpecialtyId or effectiveDate is provided.

changeReasonstring

Optional human-readable reason for the change, captured for audit trail.

Example request

{
  "tenantFacilitySpecialtyId": "tfs_abc123",
  "newTenantSpecialtyId": "ts_xyz789",
  "effectiveDate": "2026-01-15",
  "isPrimary": true,
  "changeReason": "Correcting specialty mapping per annual review"
}

Response

Specialty updated successfully

object required