Patient onboarding
before they walk in.
Patient intake clogs the front desk. Forms get printed, scanned, mistyped, lost. A Loomal agent owns the intake conversation by email, gathers the right info, verifies insurance, and books the first visit — with every action audited against an identity HIPAA can defend.
API Primitives used
mail_sendReach out to new patients
Welcome message goes from a real clinic identity with the intake form, insurance fields, and first-visit prep.
mail_list_messagesCatch the response
Patient replies with the form. extractedText feeds clean data into the intake workflow without OCR brittleness.
calendar_createBook the visit
Once intake is complete, agent books the first appointment on the right provider's calendar with full context.
Intake is a paper-era workflow.
Patient intake still runs on paper forms in 2025. Patients show up early to fill them out, the front desk types the answers into the EMR, and 30 minutes of clinic time evaporates per new patient. Multiply across a busy clinic and intake alone consumes a full FTE that should be doing patient care.
An agent fronts the entire workflow over email. The patient gets the intake form before they ever arrive, the data lands clean in the clinic system, and the visit starts on time. The front desk gets back to the work that needs them in person.
How to build it.
mail_sendSend the intake email
Agent reaches out the moment a new patient is referred or self-schedules, with the intake form and insurance fields.
mail_list_messagesCollect the response
Agent reads the reply, validates required fields, and chases anything missing in-thread.
calendar_createBook the visit
Once intake is complete, agent finds the right provider slot and books the appointment.
Example prompt
“For every new patient referral, send the intake form, validate insurance against our covered list, and book a first visit with the matching provider — all from my clinic agent address.”
What clinics build.
Self-scheduled intake
Agent runs intake for self-scheduled patients before they arrive, eliminating front-desk bottleneck.
Referral handoffs
Referrals from partner clinics trigger an intake email with the right context and provider routing.
Insurance verification
Agent reads insurance details, checks against covered carriers, and flags ineligibility before booking.
Multi-language intake
Different patient populations get intake in their language from regional clinic identities.
Pre-visit prep
Agent sends visit-specific prep instructions based on the appointment type.
Why intake needs a defensible identity.
Healthcare workflows need provable identity for every system that touches patient data. HIPAA mandates unique user identification — and most AI integrations skirt the requirement by using a shared technical account. That's exactly the thing a regulator will flag.
Loomal gives the intake agent its own identity with a full delegation chain back to the clinician who authorized it. Every email, every read, every booking is logged against an identifiable agent. The clinic gets automation; HIPAA gets the attribution it requires.
Patient data scoped
Intake responses live in the clinic identity's inbox, not a third-party form vendor.
HIPAA-grade audit
Every action is logged with the agent identity and human delegation — defensible attribution.
Identity-scoped access
Each clinic or specialty can run on its own agent identity with isolated patient data.