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.

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.

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.

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.