latestOpenAPI 3.1.02026-08-194237902.5 MB

563848e0ecc0

Practitioner

Associate a practitioner with a specialty

Associates the practitioner with a specialty at the tenant level, with best-effort cascade to group, location, and network levels. The practitioner-level specialty is always attempted first; lower-level associations are created on a best-effort basis, and failures at those levels do not cause the overall request to fail. Use this when a practitioner gains a new specialty that should be recorded across all applicable levels. {practitionerId} is the certifyPractitionerId, and the request body must identify the specialty to associate: either tenantSpecialtyId or practitionerRole must be present, and data is required only when tenantSpecialtyId is supplied.

post/practitioners/{practitionerId}/specialties

Path parameters

practitionerIdstring required

ID of the practitioner to associate with the specialty

Headers

tenant-idstring required

The tenant identifier

Request body

tenantSpecialtyIdstring

ID of the specialty; required if practitionerRole is not provided

tenantGroupPractitionerIdstring

ID of the tenant group practitioner

tenantGroupPractitionerLocationIdstring

ID of the tenant group practitioner location

networkIdstring

ID of the tenant group network

groupSpecialtyEffectiveDatestring

Group specialty date

locationSpecialtyEffectiveDatestring

Location specialty date

networkSpecialtyEffectiveDatestring

Network specialty date

practitionerRolestring

Practitioner role; required if tenantSpecialtyId is not provided

practitionerRoleEffectiveDatestring

Practitioner role date

specialtyOrPractitionerRolePresentboolean
dataPresentWhenSpecialtyPresentboolean

Response

Practitioner specialty created. Response includes created specialties per level and, when applicable, 'notCreated' listing levels that could not be created (e.g. missing group/location/network associations) with reason and message.