Skip to main content

Create a new medical specialty record

POST 
/specialties

Creates a new medical specialty record for the tenant and returns the created object with server-assigned fields.

When to use: Use this endpoint to add a new specialty to the tenant's catalog. For NUCC taxonomy-specific entries use POST /specialties/nucc instead.

Preconditions: Requires the CREATE_SPECIALTY permission. The tenant-id header must be supplied. The request body must include a data object that is validated against the Specialty JSON Schema before the record is stored — a validation failure returns 400. The body may optionally include nuccSpecialtyId, abmsSpecialtyId, and hsdSpecialtyId to associate the specialty with external taxonomy references; all three are optional and independent of one another.

Result: On success returns 201 with the created specialty object, including the server-assigned id (a UUID-format string generated by the data layer). Not idempotent — repeat calls with the same payload create duplicate records. Errors: 400 is returned either for request-body JSON Schema validation failure or for a downstream data-layer error.

Request​

Responses​

The specialty was created; the response body is the new record with its server-assigned ID.