Create a new practitioner for the tenant
POST/practitioners
Creates a new practitioner record scoped to the requesting tenant. Use this when onboarding a new provider who does not yet exist in the system; if the practitioner already exists for this tenant, the server returns 409 — use PUT /practitioners/{id} to update an existing record instead. The request body accepts three payload shapes: a wrapped object with a top-level data field, a direct practitioner object, or an extended form that also includes groups and networks for simultaneous association; the payload is validated against the practitioner JSON schema before persistence. Tenant UDF values go under data.userDefinedFields, keyed by the field names returned by GET /udf-schemas/entity-type/practitioner; UDF keys sent at the top level of the practitioner object are rejected with 400. Creating a practitioner here does not itself trigger a downstream credentialing workflow.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 500
The created practitioner record, including the server-assigned certifyPractitionerId.
Invalid request body (e.g., schema validation failed), or unsupported source type
Unauthorized - Authentication required
Forbidden - Insufficient permissions
Conflict - Practitioner already exists for this tenant
Internal server error during request processing (e.g., network timeout, etc.)