Skip to main content
A patient finishes your intake and then nothing arrives. This page is about that gap: where the eligibility decision is actually made, why your integration sees an absence rather than a verdict, and what to put in front of the patient when you cannot yet tell which absence you are looking at.

What you’ll do

1

Submit the intake as usual

POST /v0.1/questionnaire-responses returns 201 with the encounter id — and no verdict.
2

Know what you can see

The response you submitted (GET /v0.1/questionnaire-responses/{id}) and, by arrangement, the prescription webhook events your endpoint receives. Encounters and orders are not readable.
3

Read the absence correctly

No prescription event is not a decision. It says nothing has been prescribed yet, not that a clinician said no.
4

Message from what you know

Tell the patient their intake is with a clinician. Never render “not eligible” from an absence.

Who decides, and when

Eligibility is a clinical decision. A clinician reviews the submitted intake and decides whether to prescribe, after your submit call has returned, out of band from your integration. So the shape of the flow is: your call is accepted, the decision happens later, and the decision itself is not a field you can read today. Everything below is about working honestly inside that constraint.

What the intake submission gives you

POST /v0.1/questionnaire-responses with status: "completed" and a subject returns 201. The data object carries the response id, the questionnaire id, the subject, the answers as submitted, updated_at, and encounter_id — the intake encounter the platform created for you. It carries nothing that says eligible, not eligible, approved or declined. The check below asserts the absence of four candidate field names — eligibility, eligible, decision, outcome — on the submit response. The encounter it created is not readable on the partner surface, so there is no second place to look.
Locked by check submit-returns-no-eligibility-verdict: step submit-carries-no-verdict asserts the four absent names on the 201, and step reread-response asserts the response reads back with the same ids.

Recipe · Know what you can see for the patient

The partner surface gives you one read and one feed for this patient’s progress:
  1. The response you submitted. GET /v0.1/questionnaire-responses/{id} returns the answers and the encounter_id (verified on staging). GET /v0.1/questionnaire-responses also takes a subject filter in the published reference (published, not exercised by these checks).
  2. The prescription webhook events your registered endpoint receives (by arrangement). The first one, prescription.created, arrives only after a clinician has prescribed.
That is all. Encounters and orders are not readable on the partner surface, so there is no collection to poll for “has anything happened yet”.
The response read-back is step reread-response of check submit-returns-no-eligibility-verdict.

Recipe · Tell one absence from another

The clinician’s charting note is what triggers the medication order, and the first prescription webhook event, prescription.created, fires from it — see Integration flow. That ordering is what lets you locate a patient in the flow without ever seeing a verdict: Row two is the whole point of this page. The decision is not a field on the response, and the first artifact a decision produces — the prescription.created event — arrives only once a clinician has prescribed. So a patient still awaiting review and a patient who will not be prescribed present identically. Treat row two as “waiting”, never as “declined”.
Key an event to your patient on data.emr_patient_id when the event carries it. It is your /v0.1 patient id, the id that GET /v0.1/patients/{id} takes, omitted when the id isn’t known, never null. Without it, the event has only data.patient_ref — an opaque reference, not guaranteed to be the /v0.1 patient id, with no email or phone to join on. If your patients exist only through POST /v0.1/patients, agree how such events correlate to them when the endpoint is registered (by arrangement).
That the response carries no verdict is locked by check submit-returns-no-eligibility-verdict. Rows three and four rest on the prescription webhook events (by arrangement), which the conformance runner cannot exercise; see Prescription events.

What comes back

Nothing here carries a verdict, so the table is what each field does tell you — and what it does not. No field named eligibility, eligible, decision or outcome appears on the submit response — asserted by the check above.

What to tell the patient

  1. Never derive a verdict from an absence. No prescription event is exactly what you would see one second after submit.
  2. Say what is true: the intake is with a clinician, and the patient will hear the outcome. Describe your own next step — an email, a status screen — rather than the platform’s.
  3. Do not promise a review time the API cannot confirm. Nothing in the response tells you how long a review takes, or whether one has started.
  4. Put a floor under the silence. Age your own record of the submit: an intake with no prescription.created event after your chosen threshold is a case to escalate, not a case to tell the patient they were declined.
  5. Escalate with ids, not descriptions: the request_id from the submit response, the patient id, and the encounter_id. Storing the response id and encounter_id together at submit is the cheap path, but the encounter_id is recoverable rather than lost: hold the response id and GET /v0.1/questionnaire-responses/{id} returns both.
That the re-read recovers both ids is step reread-response of check submit-returns-no-eligibility-verdict.

Gotchas

A 201 on submit is acceptance of the form, not of the patient. It is returned before any clinician has seen the intake. If your funnel shows a success screen here, word it as “submitted”, never as “approved” or “eligible”.
Do not build a client-side eligibility gate and call it the platform’s answer. You may screen for your own reasons — a state you do not serve, an age range — but that is your rule, not a clinical decision, and a patient you turn away never reaches the clinician who could have reviewed them. Keep the two clearly separated in your copy and in your logs.
Dated 2026-09-11 — expect this page to change. A server-side eligibility verdict on submit is in development: the intake submission would evaluate dob, state, sex and bmi, and return a 400 when one of them is missing, so an ineligible patient is refused at submit rather than in silence. It is not on the partner surface today and nothing on this page anticipates it. Re-read this page before you build eligibility messaging if you are integrating after it ships.
There is nothing to poll. Orders and encounters are not partner-readable, so do not build a loop that waits for them. Wait for the prescription webhook events at your registered endpoint (by arrangement), and age your own record of the submit in the meantime.

Integration flow

The happy path this interrupts: intake, the encounter id it returns, and what comes after

Order status and tracking

Once a clinician prescribes, the prescription webhook events that follow the order