Associate a practitioner with a specialty
POST/practitioners/:practitionerId/specialties
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.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 500
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.
Bad request - Invalid input
Unauthorized - Authentication required
Forbidden - Insufficient permissions
Practitioner or specialty not found
Conflict - Practitioner already associated with specialty
Internal server error