latestOpenAPI 3.1.02026-08-194237902.5 MB

563848e0ecc0

Practitioner

Correct a role key on the core practitioner record

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.

patch/practitioners/{id}/roles/correct

Path parameters

idstring required

Headers

tenant-idstring

Request body

existingRole'PCP' | 'Specialist' | 'Hospitalist' | 'Hospital-based Provider' required

Current role to correct

newRole'PCP' | 'Specialist' | 'Hospitalist' | 'Hospital-based Provider' required

New role to replace the existing one

Example request

{
  "existingRole": "PCP",
  "newRole": "Specialist"
}

Response

Role corrected successfully. practitionerRoles is populated with the corrected core roles map; locationRoles is always empty.

practitionerRolesobject

Updated practitioner roles map from core_practitioners

locationRolesobject

Updated practitioner roles map from group_practitioner_locations, keyed by groupPractitionerLocationId

Example response

{
  "practitionerRoles": {
    "pcp": {
      "effectiveDate": "2026-01-10",
      "terminationDate": "2026-02-02"
    },
    "specialist": {
      "effectiveDate": "2026-01-01"
    }
  },
  "locationRoles": {
    "550e8400-e29b-41d4-a716-446655440000": {
      "pcp": {
        "effectiveDate": "2026-01-10",
        "terminationDate": "2026-02-02"
      }
    }
  }
}