--- url: "https://dfylegitscript.com/blog/asynchronous-intake-and-the-clinical-encounter-under-review" title: "Asynchronous intake, and proving the prescribing decision is real" description: "An asynchronous telehealth model is workable where the states served permit it, but a LegitScript reviewer assesses whether a genuine prescribing decision happens, and the evidence for that is the intake logic, the contraindication screening and the rate at which prescribers actually decline." published: "2026-05-03T10:00:37+00:00" modified: "2026-05-03T10:00:37+00:00" --- # Asynchronous intake, and proving the prescribing decision is real An asynchronous telehealth model is workable where the states served permit it, but a LegitScript reviewer assesses whether a genuine prescribing decision happens, and the evidence for that is the intake logic, the contraindication screening and the rate at which prescribers actually decline. ## Key takeaways - An asynchronous model is workable where the states served permit it, and the question underneath the review is whether a genuine prescribing decision actually happens. - The rate at which prescribers decline is the proof that the intake does something, because an assessment nobody ever fails is a product selector wearing clinical clothes. - Marketing undoes the clinical work when the funnel names a product before a prescriber has decided, however careful the assessment behind it is. - A synchronous model is not automatically safer, because a video call that reaches a predetermined outcome answers the same question badly. Asynchronous care is now the default in direct-to-consumer telehealth: a patient completes an intake, a licensed prescriber reviews it, and no live consultation happens. The model is legitimate where the states you operate in permit it, and it is not what gets businesses into trouble. What gets businesses into trouble is being unable to show that the prescribing decision is a decision at all. ## The question underneath the question A reviewer is not asking whether asynchronous care is acceptable. That argument is settled in the places it is settled and unsettled in the places it is not. The question is whether this particular implementation involves a clinician exercising judgement, or whether it is a purchase with a clinical step drawn on top. Those two look identical in a screenshot and completely different in the underlying data, which is why the answer is documentation rather than description. ## What the intake has to actually do **Screen for the contraindications the medicine has.** Not generic health questions: the specific ones the preparation requires. If your intake for a category with cardiac considerations never asks about cardiac history, the workflow is not doing the thing it is claimed to do. **Collect enough to decide.** Current medications, relevant history, the measurements the decision depends on, and how those are obtained. Where something is self-reported, say so rather than presenting it as measured. **Handle the answers that should stop the process.** An intake that accepts every answer and proceeds regardless is a form, not an assessment. Somewhere in the logic there has to be a route that ends in "not appropriate", and it has to be reachable. **Record what the prescriber saw.** The record is the evidence. A workflow where a clinician reviews a summary that omits the answers most likely to matter is one that cannot be defended afterwards. ## The decline rate is the proof This is the number worth being able to produce. If prescribers decline, the decision is real. If nobody has ever been declined, that is either a remarkable patient population or a rubber stamp, and a reviewer will assume the second. Alongside it: how many patients are asked for more information before a decision, how many are redirected to synchronous care, and how many are declined for a specific contraindication rather than for a missing detail. Those four figures describe a clinical process more convincingly than any policy document. They are also the figures nobody has, because nobody instrumented for them. That is a reporting job worth doing before you file rather than during a review. ## Where the marketing undoes the clinical work The most common failure in this category is a funnel that describes an automatic outcome while the workflow behind it does something careful. The copy is read as evidence about the model, and it is read first. Language that implies the medicine is already decided before any review happens describes exactly the model the certification exists to screen out. So does a result screen that names a product and a dose before a prescriber has looked at anything. So does a checkout that takes payment for a medicine without saying what happens if a prescriber declines. The fix is not to bury the product. It is to be honest about the sequence: this is an assessment, a clinician reviews it, they may decline, and here is what happens to your money if they do. Brands consistently underestimate how well that converts, which is the argument [the disclosures a clinic owes its patients](/blog/patient-trust-signals-a-certified-telehealth-clinic-owes-its-patients) makes at greater length. ## Three intake patterns that generate the most questions **The quiz that is really a product selector.** Questions that establish preference rather than suitability, ending on a recommendation. It converts well and it describes a purchase. If the questions would be identical for a shopping cart, they are not screening for anything. **The intake that collects but does not act.** Every relevant question is asked, including the ones that should stop the process, and nothing in the logic responds to a concerning answer. This is worse than not asking, because the record shows the business knew. **The intake with a free-text field nobody reads.** A box inviting the patient to describe anything else relevant, whose contents never reach the prescriber's summary. It generates the answer that would have changed the decision and discards it. None of the three is dishonest. All three are what happens when the funnel is designed by people optimising conversion and the clinical logic is added afterwards by people who were not in the room. ## Synchronous care is not automatically safer Brands sometimes propose adding a live consultation as a way to end the question. It does not, on its own. A two-minute call that confirms what the form already said, with no ability to decline and no record of what was discussed, answers less than a well-instrumented asynchronous intake does. What is being assessed is the quality of the decision and the evidence for it, not the medium it was made in. ## Follow-up is part of the encounter An asynchronous model that ends at dispatch is describing a transaction. What turns it into care is what happens next: check-ins at a defined interval, dose adjustment with a clinician involved, a route to raise a problem that does not depend on finding an email address, and a documented path for an adverse event. This is also where the state layer bites hardest. Some jurisdictions have specific expectations about the encounter, and [the coverage matrix](/blog/state-licensure-coverage-for-telehealth-clinics) is where those live alongside the licensure question rather than in a separate document nobody reads. ## What to write down before you file A short clinical workflow document. Four or five pages, current, owned by somebody named. - The intake, question by question, and what each question is for. - The logic: what combinations of answers stop, escalate or flag. - What the prescriber sees, and what they are expected to do with it. - Who supervises the prescribers, and how that is evidenced. - The follow-up cadence and the adverse event route. - The four numbers above, for the last quarter. Supplied with the application, that document answers most of what a reviewer would otherwise ask about the clinical model. Written after the question arrives, it reads as something assembled to answer the question, which is a different thing and it is obvious from the outside. ## Frequently asked questions ### Is an asynchronous model acceptable for certification? It is workable where the states you operate in permit it and where the model is described accurately. What draws scrutiny is an implementation where the prescribing decision is effectively automatic, or marketing that describes it that way regardless of what the workflow does. ### Why does anyone care about my decline rate? Because it is the cleanest evidence that a clinical judgement is being exercised. A workflow in which nobody is ever declined looks like a purchase with a review step drawn on top, and a reviewer has no way to distinguish the two without the number. ### Do I have to offer a live consultation? Not necessarily, and it depends on the states you operate in and the products involved. What matters for certification is that the encounter you do offer screens properly, records what the prescriber saw, and is described on your website the way it actually works. ## Disclaimer LegitScript is a trademark of LegitScript LLC. VeriScripts is an independent application-preparation service. It is not affiliated with, endorsed by, or certified by LegitScript LLC, and claims no sponsorship or partnership with it. We prepare, submit, and manage the application; LegitScript alone decides whether certification is granted. "LegitScript" is used here only to name the certification these applications are for.