Every prescription on Oasis Liquido begins as a structured record a doctor creates during or after a consultation. The platform immediately generates a unique QR code and attaches it to the prescription. The patient carries this QR code in the app and presents it at any Oasis-linked pharmacy. The pharmacist scans it, sees the exact medicines and quantities authorised, and records fulfillment line by line. Nothing changes hands without a verifiable digital trail.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/FlasheyEstudi/Oasis-Liquido/llms.txt
Use this file to discover all available pages before exploring further.
Full prescription lifecycle
Doctor creates the prescription
The doctor submits a
CreatePrescriptionRequest specifying the patient, clinic, expiration date, and one or more medicine lines. Only users with the doctor role can create prescriptions.QR code is generated
The backend generates a unique
qr_code_data value and stores it against the prescription record. The patient can view and share the QR from within the app immediately.Patient presents QR at the pharmacy
At the counter, the patient opens the prescription detail screen and shows the QR code. No printout is needed.
Pharmacist validates the QR
The pharmacist submits a
ValidatePrescriptionRequest with the scanned qr_data. The API returns the full prescription — patient identity, medicines, quantities, and expiration date — for the pharmacist to review.Prescription status
The status advances automatically as lines are fulfilled, and expires independently of dispensing if theexpiration_date passes.
| Status | Meaning |
|---|---|
active | Valid and not yet dispensed |
partially_fulfilled | At least one line has been partially dispensed |
fulfilled | All lines fully dispensed |
expired | The expiration date has passed without full dispensing |
Creating a prescription
Send aPOST request to /api/v1/prescriptions. Only doctors can call this endpoint.
Fulfillment types
Validate a QR code
Before dispensing, the pharmacist callsPOST /api/v1/prescriptions/validate to authenticate the code and retrieve the prescription record.
Fulfill a prescription
Once validated, submit aPOST request to /api/v1/prescriptions/{id}/fulfill with the items being dispensed in this visit.
Prescription line fields
Each line in thelines array corresponds to one medicine in the prescription. After partial or full dispensing the line reflects how much has been given.
| Field | Type | Description |
|---|---|---|
medicine_id | string | UUID of the medicine |
quantity | number | Total units the doctor authorised |
quantity_fulfilled | number | Units dispensed so far (updated by pharmacy) |
dosage_instructions | string | Free-text instructions for the patient |
Listing prescriptions
Send aGET request to /api/v1/prescriptions. Role-based scoping is applied automatically.
| Query parameter | Type | Description |
|---|---|---|
patient_id | string | Filter by patient |
doctor_id | string | Filter by issuing doctor |
status | PrescriptionStatus | Filter by current status |
date_from | string (ISO date) | Prescriptions issued on or after this date |
page | number | Page number (default: 1) |
limit | number | Results per page (default: 20) |
Prescriptions API
Full endpoint reference for prescription creation, validation, and fulfillment
Pharmacist role
How pharmacy managers operate the Kardex, POS, and QR scanner