A Clinic Intake That Routes the Patient to the Right Person

Replace the clinic Typeform with one intake that routes a message to the right person. A compliance program stays with the clinic's lawyer, not the form.

By Muhammad Saif and Aashan Khan · Techtribe co-founders

The clinic already has a form. It might be Typeform, a PDF, or a page on the website that lands in a shared inbox. Patients fill it. Someone on staff reads it when they can, and sometimes the dermatology question sits with the front desk until the right person happens to look. The job to buy is smaller than a hospital system. One intake. The answers land in one place you control. A route sends the message to the role that should see it. A person still answers.

The guides for the two halves are replace Typeform in your clinic intake and patient replies that reach the right doctor. This article is the scope around those guides: what the first workflow is, what it will not store, and who owns the compliance questions. That owner is the clinic's lawyer and the clinic. A vendor that says the form makes you compliant is selling a sentence. We will not say that sentence.

One intake, not a record system

List the questions you already ask. Identity as you need it to know who is writing, the reason they are writing, and the facts a coordinator uses to pick a person. Stop there. A first build that also becomes the chart, the prescription log, and the billing file is three products. Clinics buy the three because the form felt like a doorway into everything. The doorway can be built. The building behind it is a different quote.

The patient finishes on a phone. The confirmation says what will happen next, in the clinic's words: someone will read this, in what hours, and what to do if the matter is urgent. The urgent sentence is clinical policy. We will put the sentence you provide on the screen. We will not invent the sentence. If you do not have one, the form is not ready to collect symptoms. A form without an urgent path teaches patients to type emergencies into a queue.

Staff see a queue, not a decorated inbox. Each submission shows the answers and the route: front desk, a named clinic role, a nurse pool. The route is a rule you can read. "If the patient chose this location and this type of request, it goes to this role." A model may suggest the route when the patient writes in sentences instead of picking a type. The suggestion is marked. A person can move it. On the first release the person confirms the route when the cost of a wrong room is anything you would apologize for. Unattended routing of clinical mail is a later decision, if it is a decision you make at all.

What we will not build into this form is a diagnosis, a triage score presented as medical advice, or a reply the patient sees without a person. The patient-replies guide is about the message reaching the right doctor, not about the model being the doctor. An AI support agent allowed to do three things is the commercial version of the same limit: draft, look up one record, stop. A clinic draft, if you add one later, is still a draft. The send stays with staff.

What is not stored

Write the no list next to the question list. Photos you do not need. Documents you do not need. A free-text box that invites a life story you then have to protect. If the route only needs the location, the type of request, and a phone number, do not ask for the story "in case it helps." The story becomes your obligation the moment you keep it.

Say where a submission lives: which account, which region, whose key if a model reads the text to suggest a route. A model call is a disclosure. The clinic decides if that disclosure is acceptable, with counsel, before we wire it. If the decision is no, the route is a set of choices the patient picks, and no model sees the text. That version is often the right two-week product. It is less magical and much easier to explain.

Retention is a number you choose. We can delete on that number, or export and delete, if you have defined it. We cannot pick the number. "Keep it until we figure it out" is how a prototype inbox becomes an archive. The first build can refuse to become the archive: staff copy what they need into the system they already trust, and the intake store expires. That handoff should be explicit. Two stores, forever, means two places to look when a patient asks what you hold.

Access is a staff account, not a shared password on a tablet at the desk. Two roles at minimum if two roles exist: the person who can see this location, and the person who cannot. Test it. A shared login is not a role, and it will not survive the first leaver. If the clinic is three people and one login is the honest current practice, say so. We can still build a form. We should not pretend you have an access-control program because the form has a password field.

The lawyer's work, named so we do not take it

Techtribe is not a HIPAA certifier, a covered-entity program, or the clinic's privacy officer. We do not sign a document that says you are compliant because you paid for a build. If your counsel wants a specific agreement with vendors, a specific region, a specific list of subprocessors, or a decision not to use a model at all, those are inputs. Bring them before kickoff. Discovered in week three, they change the architecture, and the date moves with them.

AI-built apps and GDPR is a different law and a useful posture: if data is exposed, someone still has to explain, and that someone is the controller, not the prompt. The same posture applies here even when the statute is different. The clinic is responsible for the patient relationship. The form vendor, us included, is responsible for building what was agreed and not quietly widening it. Widening is a model that starts answering, a log that starts keeping full text, a tool that starts emailing the patient. Each of those is a change of scope and a change of risk. Each needs a yes.

We will not hide clinical text in a personal model account, a chat transcript on a laptop, or a builder's preview you do not control. If the intake began life in a vibe-coded app, the move onto a clinic-controlled host is part of the job, and the general version of that move is repair or rewrite. A Typeform you already pay for may be acceptable to your counsel. Replacing it is then about the route and the queue, not about a belief that custom code is inherently safer. Safer is the access rule, the retention number, and the absence of a model you did not approve.

Identity documents, insurance cards, and prescriptions are neighboring products on this site: identity check and prescriptions. They are not included because you booked an intake. A photo of an identity document is a collection decision. Do not add the upload because the form had a spare button.

Routing without pretending to practice medicine

The rule prefers choices over prose. A menu of request types you defined, a location, a preferred person if the patient already has one. The route is then a table, testable without a model. Use the table. A model that reads a paragraph and picks a specialist will be wrong on the paragraph you did not foresee, and the patient will not know it was wrong. If you still want a suggestion, it sits beside the table's answer, and a person confirms.

Urgency is a menu too, plus the sentence that tells the patient not to use the form for an emergency. The menu does not score risk. A score looks like a clinical opinion. An opinion needs a clinician and a product you are not buying in this scope. If a submission says, in free text, that the matter is urgent, the queue can pin it for a person. Pinning is not a diagnosis. It is a sort.

After hours, the confirmation and the route still have to be true. If nobody reads the queue until morning, the screen says morning. A form that implies a doctor is watching tonight, when nobody is, is a harmful interface. Copy is the feature. We will implement yours. We will flag ours if we drafted a sentence that promises a watch you do not run.

The reply, when staff send one, can be a template you wrote. Templates are not model prose unless you explicitly add a draft later. A draft that rewrites a clinician's meaning is a bad trade. The maintain standard still holds: someone at the clinic can change a template without us. Auth, retention, and any model key stay with a person who understands they are not labels.

A short form, or a longer one, with no clinic exception

The work does not grow because the user is a patient. A short build is one flow, a live URL, and the code in your repository. For a clinic that is one form, a confirmation, a queue, and a route from choices you listed. One connection if the queue must land in a system you already use, such as the inbox tool you will not abandon. No model, unless the one suggestion you want has already been cleared with counsel. No claim of a compliance program. The short shape is one flow for a reason. A clinic platform does not fit in it. A form does. Book the call if you are unsure which of those sentences is yours.

A longer build is staff accounts with two roles, the route tested, design in the clinic's brand because patients will see it, a few connections, and a way for a lead to reassign. A check on the path if a model is actually in it. An evaluation set made of example messages you invented or properly cleared, not a dump of real patient text into a ticket tracker. A patient portal, scheduling, billing, and the chart are not hiding inside "a queue." If those are what you want, say them on the call so we can tell you they are not this form.

A team that stays is for when the form is the first workflow and the clinic has named the next ones. It is the wrong way to discover the urgent-care sentence. Discover that with the people who practice there, then book. When to hire a dedicated AI team assumes a roadmap. A single location with one form may not have one. That is a successful small build, not a failed large one.

Say so when many locations have different rules, when counsel's requirements change the hosting, or when the "intake" is already a full front office. Bring the locations as a number. Two locations with the same form can still be one build. Twenty with different records systems are not a quiet version of the same form. The call is where that number gets heard.

A launch that does not collect more than you can answer

Turn the form on for one location, or one type of request. Read every submission the first days. Fix the question people misunderstand. Then widen. A form launched to every campaign on the same morning will produce a queue you do not have the staff to route, which is the old inbox with a nicer font.

Keep Typeform, or the old page, up until the new queue has handled a real day, then redirect. Two forms collecting at once will split the patients. Tell the front desk which screen is real. The old export can be imported only if you actually want those rows in the new store. Wanting them means keeping them under the retention rule. If you do not want that, leave them where they are and let the old tool expire on its own schedule.

Measure the route, not a vanity completion rate. How many submissions a person had to reroute. How many came in after hours against a promise you should not have made. How many patients wrote an emergency into a box you tried to forbid. Those numbers tell you whether to change the copy, the menu, or the staffing. They do not tell you to add a model. Add a model only if the menu cannot express the sort, and only after counsel has agreed the text may be read by one.

What to bring to the call

The current form, the questions you want to keep, and the questions you want to drop. The route as a small table: this choice, this role. The urgent sentence you already use on the phone. The system the queue must join, if it must. The name of the person who will read the queue next week. A yes or no, from counsel if you have it, on whether any text may be sent to a model.

If you do not have counsel's view yet, the build that does not use a model can still proceed, and the model stays a later yes. Do not wait to replace a messy inbox if the replacement is a menu and a queue. Do wait to wire a model if you have not decided the disclosure.

Leave the chart, the prescription pad, and the insurance upload off the agenda, or mark them as other projects. The intake that routes is finished when the right person sees the message and the wrong person does not. That is the whole first product.

If this is your app, send the repo.

A 30-minute scope call. We read what is live, name what is dangerous, and quote a fixed scope.

How Techtribe builds a clinic intake

We replace the scattered form with one intake, a confirmation in your words, and a queue that routes by a rule a person can check. We store only what you listed, in a place you named, for as long as you specified. We do not diagnose, we do not send patient replies unattended, and we do not claim the clinic is compliant. Your lawyer owns that program. If a model is not approved, the route is a menu.

One form and one route can be a short build. Staff roles, your brand, and a few connections are a longer one. A series of clinic workflows is a team that stays. We say which on the call, and we will say if what you brought is a records system wearing a form. The guides are clinic intake and patient replies. The service page is SaaS development.

The scope call is 30 minutes with a founder. Bring the current form and the routing table. That meeting is how the route gets agreed before a patient types into it.

Questions

Can an intake form replace Typeform in a clinic?

Yes, when the job is one form, one place the answers land, and a route to the right person on the staff. The form collects what you name. It does not diagnose, prescribe, or store a record you have not agreed to keep.

Does building this make the clinic HIPAA compliant?

No. Techtribe does not certify a clinic, and a form is not a compliance program. What you collect, where it lives, who may open it, and how long you keep it are decisions for the clinic and the clinic's lawyer. We implement the decisions you make.

Will the model reply to the patient on its own?

Not in the first build. The intake can structure the message and point it at the right role. A person sends any reply. An unattended clinical answer is a different product and not one we will fold into a two-week form.

How do we know the intake is one form and not a records system?

Book the scope call with the current form and the routing table. One form, one route, and a live URL can stay a short build. Staff accounts and a reviewed routing rule are a longer one. A chart, scheduling, and billing are a different product, and we will say that before the form grows into them.

Book a free call

Have a vibe-coded app in production?

30-minute free call. We'll read what you have, name what is dangerous, and quote a fixed scope.