Prescription API
Prescriptions
Understand the prescription resource, lifecycle, core fields and the endpoints used to manage electronic prescriptions.
Authentication
OAuth 2.0
Required
Permissions
prescriptions.read
Required
Rate limit
600 requests / min
Default
Caching
30 seconds
Recommended
Response
200 OK
Prescription resource
| Field | Meaning |
|---|---|
| id | Prescription identifier |
| patient_id | Patient reference |
| prescriber_id | Prescriber reference |
| encounter_id | Related encounter |
| status | Lifecycle status |
| items | Prescribed medication items |
| notes | Clinical / pharmacy note |
| signed_at | Signature timestamp |
| routed_pharmacy_id | Destination pharmacy |
| created_at | Creation timestamp |
Lifecycle
draftCreated by provider
clinically_validatedClinically validated
signedDigitally signed
routedSent to pharmacy
dispensedDispensed to patient
Core fields
| Group | Examples |
|---|---|
| Identity | id, patient_id, prescriber_id, encounter_id |
| Clinical | items, dosage, frequency, duration, notes |
| State | status, validated_at, signed_at, routed_at |
| Pharmacy | routed_pharmacy_id, dispensation references |
| Audit | created_at, updated_at, version / snapshot metadata |
Status values
| Status | Meaning |
|---|---|
| draft | Created and editable by the prescriber |
| clinically_validated | Clinical checks completed |
| signed | Immutable signed snapshot created |
| routed | Sent to a pharmacy |
| dispensed | Medication dispensation recorded |
| cancelled | Cancelled before completion |
Clinical safeguards
Signed prescription snapshots are immutable. Changes after signing should create a new clinical artifact rather than mutating the signed record.