sdp_suki_token). Critically, these endpoints return reference metadata. They do not place medication orders in an EHR.
Available endpoints
GET Order Metadata
Purpose: Retrieve supported medication order metadata in one response
GET Order Coding Systems
Purpose: Retrieve supported coding systems for medication orders
GET Order Dosage Units
Purpose: Retrieve supported dosage units for medication orders
GET Order Encounter Relations
Purpose: Retrieve supported encounter relations for medication orders
GET Order Frequencies
Purpose: Retrieve supported frequency values for medication orders
GET Order Timings
Purpose: Retrieve supported medication timing values
GET Order Origins
Purpose: Retrieve supported origin values for medication orders
GET Order Statuses
Purpose: Retrieve supported status values for medication orders
Related guides
Medication Orders
Learn how to convert medication instructions from ambient encounters into structured Medication order data
Ambient Documentation
See how Medication orders fit into the ambient clinical note workflow
Common use cases
Review medication orders your EHR can accept
Use supported order metadata so clinicians select units, frequency, timing, and status values that pass EHR validation.
Keep order catalogs current
Refresh Medication Orders Info on your release cycle so coding systems and timings stay aligned with Suki.
Validate order payloads before write-back
Check ambient-suggested medication orders against supported catalogs before you persist them in the chart.
Support order review across modalities
Use the same order metadata when clinicians review medication suggestions after capture continues across products.