Prescription workflows

Prescription integrations combine prescription requests with indication-survey operations. They provide a structured workflow for collecting the information required by the configured prescription journey, tracking the request, and returning the outcome when available.

Form-based prescriptions

A form-based prescription is a guided, asynchronous medical consultation. The user completes a structured digital form describing their symptoms and medical history, and a licensed doctor reviews the submitted information before issuing a prescription or clinical advice. The workflow does not require a live video or voice consultation.

The user-completed questionnaire is called an indication survey. Its questions and answer choices are configured for the relevant prescription journey, then reviewed by the doctor as part of the request. See the create prescription request operation for the request and response contract.

Product model

An indication survey is the question set used to collect the information needed for a prescription request. A prescription request is tied to the relevant user and can progress through the states defined by the API. Where a prescription file is available, it is returned as part of that request’s documented response—not as an integration-managed file store.

Survey responses include the survey category, refill status, title, display order, questions, choices, and exit logic. Submit the survey identifier and the answer identifiers selected from the returned template; do not manufacture identifiers or reuse a template from another journey.

Typical flow

1. Retrieve the available indication surveys.
2. Retrieve the selected survey template.
3. Collect and validate answers in your approved user journey.
4. Create the prescription request with the required user and survey data.
5. Retrieve its current state and any available prescription file.
6. Cancel or close the request when the documented state rules allow it.

The prescription request includes the Abi user identifier, medical question, and required serialized indication-survey payload. You can also provide the normalized survey object returned by the survey workflow; when supplied, Abi validates it and uses it to build the stored survey payload. A pharmacy identifier is supplied only when the configured journey requires it. Returned prescription records can include the consultation status, prescription file URL, survey URL, and any available professional response.

Prescription files can be returned through short-lived URLs. Treat them as sensitive health information: do not persist signed URLs in logs, examples, analytics, or client-visible error messages.

Use the API reference for current survey structures, request schemas, and states.