API RESOURCE

Odontogram & Treatment

FDI tooth chart, service/procedure catalog, staged treatment plan and prescription. Tooth states are kept append-only — history is never deleted or overwritten.

Early Access All API

Endpoints

14 endpoint

Endpoints for this resource. Every endpoint is scoped to the clinic data the API key is bound to; write endpoints support the Idempotency-Key header.

GET /v1/patients/{id}/odontogram Retrieves the current FDI tooth chart All authorized roles

POST /v1/patients/{id}/odontogram Adds a tooth state (append-only) admin · physician

GET /v1/patients/{id}/odontogram/{tooth}/history Retrieves the state history of a tooth All authorized roles

GET /v1/services Lists the service/procedure catalog All authorized roles

POST /v1/services Adds a service item admin

PUT /v1/services/{id} Updates a service item admin

GET /v1/patients/{id}/plans Lists the patient's treatment plans All authorized roles

POST /v1/patients/{id}/plans Creates a treatment plan admin · physician

GET /v1/plans/{id} Retrieves treatment plan details All authorized roles

POST /v1/plans/{id}/status Changes the plan status admin · physician

POST /v1/plans/{id}/items Adds a stage/item to the plan admin · physician

POST /v1/plan-items/{id}/status Changes the status of a plan item admin · physician

GET /v1/patients/{id}/prescriptions Lists prescriptions All authorized roles

POST /v1/patients/{id}/prescriptions Creates a prescription admin · physician

Example Usage

Add tooth state (append-only)

Request

curl -X POST https://api.udentiva.com/v1/patients/{id}/odontogram \
  -H "Authorization: Bearer udk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"tooth":"11","state":"caries","surface":"mesial"}'

Response

HTTP/1.1 201 Created
{
  "id": "st-77",
  "tooth": "11",
  "state": "caries",
  "recorded_at": "2026-06-24T09:10:00Z"
}

Security in this resource

Security isn't a feature, it's the architecture itself. The guarantees that apply to this resource:

Tooth state records are append-only: every change is added as a new row, and old records cannot be modified (clinical history integrity).

Treatment plan and prescription creation is open only to the admin/physician role; price and stage logic is executed on the server.

All records are isolated to your clinic; plan-price calculations are not taken from the client but performed on the server with numeric.

Full security model →

Error Format

Errors are returned in a consistent envelope; the code is for the machine, the message for the user. Internal error/stack is never leaked.

{
  "error": {
    "code": "validation_failed",
    "message": "Invalid field: email"
  }
}

Other Resources

患者予約とカレンダー Collections & Finance 在庫 Imaging ラボ Lead & CRM 医療ツーリズム Reporting & BI Webhooks Data Transfer (Export API)

Want early access?

Be the first to know when the API opens.

お問い合わせ