Practitioner

Correct a role key on a practitioner-location record

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.

patch/practitioners/practitioner-locations/{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

Location role corrected successfully. practitionerRoles is always empty; locationRoles has a single entry keyed by the location ID.

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"
      }
    }
  }
}