Healthcare · HIPAA-Aware

HIPAA-compliant automation for medical, dental, and behavioral-health practices.

Patient intake, reminders, reviews, and secure messaging, built on infrastructure where every vendor that touches PHI signs a Business Associate Agreement. Designed by a founder trained in clinical sciences and I-O Psychology, with peer-reviewed research behind the methods. Delivered remotely, nationwide.

The Reality

The reality at most growing practices.

Your front desk is drowning in paperwork.

Manual intake forms. Insurance verification on hold. Treatment plans that get presented and never followed up. The math: every untracked treatment plan that walks out the door is revenue you'll never see.

After-hours emergencies are walking to competitors.

A patient calls at 8pm with a cracked tooth. Voicemail. Three minutes later they're Googling the next office. By 9pm they're someone else's patient. Every emergency you miss is $300–$2,000+ of revenue lost, and a referral relationship that didn't form.

Your reputation is left to chance.

Happy patients quietly leave. Frustrated patients post publicly. No system catches the difference. Practices with structured review systems consistently outpace competitors with similar care quality, because online perception drives new patient choice.

Not sure the problem is technology at all? Start with the Practice Experience Audit — it finds where the practice leaks patients, with or without automation.

The Trust Gate

HIPAA isn't a checkbox. It's how we architect.

Most “AI for healthcare” pitches use vendors that legally cannot touch patient data. Generic ChatGPT integrations. WhatsApp business accounts. Tools that route patient data through third parties without Business Associate Agreements (BAAs). It's everywhere — and most practice owners don't know to ask.

Every system we build for a healthcare client flows through BAA-signed infrastructure from day one. Not because we read a checklist — because we know what it means when you don't.

What we build with
What we won't touch

AWS End User Messaging BAA-signed

HIPAA-eligible SMS for patient communication, under the AWS BAA.

AWS BAA-signed

Bedrock AI, S3, RDS, Transcribe for compute and storage.

Microsoft 365 / Google Workspace BAA-eligible plans

Office workflows on enterprise tiers that include a BAA.

Self-hosted infrastructure Your account, your control

Where the data sits matters. We default to your tenancy.

WhatsApp Business

Meta won't sign a BAA. Period. It's why our field-ops systems for contractors and our healthcare systems are deliberately different builds.

Vanilla ChatGPT / Claude APIs

Require Enterprise tier with executed BAA before they touch PHI.

Most consumer-grade automation tools

Zapier free tiers, IFTTT, off-the-shelf chatbots — no BAA available.

Tools that route patient data through unverified third parties

Free email-to-text, screen-share apps, photo-sharing apps for x-rays.

Generic AI consultants can't write this table. They don't know what they don't know.

Operational Reality

We didn't add HIPAA to our pitch deck. It's been our operational reality for years.

Most “HIPAA-aware” AI consultants learned compliance from a vendor's marketing page. We learned it three ways.

As an academic discipline: pre-medical biology coursework and Addiction & Rehabilitation Studies, a field operating under federal protections stricter than HIPAA itself. As an operational responsibility: publishing population health data under direct Texas HHSC oversight. And as architectural design: every system we build today, with BAA-signed infrastructure as the only option.

Three layers, one standard.

The Compliance Diagram

Airtight has a shape. We draw it before we build it.

Same schematic language, different argument: the dashed line is the BAA-covered boundary. Watch the patient’s message get encrypted at the door; every system that lights up violet is operating under a signed BAA, and nothing carrying PHI ever crosses back out.

BAA-COVERED BOUNDARY · PHI STAYS INSIDETLS IN TRANSITENCRYPTEDAI SUMMARY · BAAROLE-BASED ACCESSPatientTEXTS THE PRACTICETwilioHIPAA-ELIGIBLE MESSAGING · BAAAptibleHOSTING · AES-256 AT REST · AUDIT LOGSAmazon BedrockHIPAA-ELIGIBLE AI · BAAFront Desk ViewINTAKE DONE BEFORE THE FIRST RINGPHI NEVER CROSSED BACK OUTEVERY VENDOR INSIDE THE LINE SIGNS A BAA
Patient intake · reference architecture for HIPAA-aware practicesDrawn for your practice before anything is built

Illustrative example. The vendors named above (Twilio, Aptible, Amazon Bedrock) are one reference architecture to show the shape of a compliant build. Your actual stack is scoped to your practice. If your business runs on something else, that’s fine. We integrate; you own the keys.

Healthcare Services

What we build for growing practices.

Three featured services. More available — every system designed for the way your front desk actually works.

Patient experience & review system

Post-visit messaging asks every patient how their visit went — nothing clinical, ever. Everyone receives the same public review invitation; we never gate. Patients who report a bad experience are heard first through service recovery and reach your team the same day, then get the same invitation as everyone else. Sequenced, not filtered.

Protects existing rating. Compounds over time. Already running for our first dental client.

After-hours AI receptionist & voicemail triage

Patient calls at 8pm with a cracked tooth. AI triages urgency, sends emergency alert to the on-call clinician's phone, books non-urgent for next morning. HIPAA-aware end to end.

Captures an estimated $300–$2,000+ per emergency case currently going to competitors.

Treatment plan follow-up & patient reactivation

30–50% of presented treatment plans never get scheduled. We systematically follow up with calibrated, sentiment-aware outreach, so revenue doesn't walk out the door.

Even a 5 to 10% lift in case acceptance is $20 to 50K a year for a typical practice.

Revenue figures are illustrative ranges drawn from practice work and published dental industry benchmarks. Your numbers depend on volume and case mix.

Also available

  • Internal staff knowledge bot (SOPs, fee schedules, instant Q&A — zero PHI, easiest entry point)
  • Insurance verification automation
  • Patient intake compressor (text-to-form, OCR-driven)
  • Bilingual patient communications layer
  • Daily morning brief for the doctor (production, schedule, reviews — one SMS at 8am)
  • Post-op care follow-up sequences
The Background

Why our background matters for your practice.

Undergraduate — In Progress

B.S. Biology, Biological Sciences Concentration — UTRGV

Pre-medical-track curriculum spanning anatomy, physiology, biochemistry, microbiology, and human systems, in progress in the top GPA tier. The clinical workflows we automate are workflows we studied the science behind.

Graduate — Full Scholarship

Industrial-Organizational Psychology — SUNY Albany

Doctoral-level training in organizational behavior, change adoption, training transfer, and human factors. Most healthcare automation fails because staff doesn't adopt it — not because the tech is broken. We design for how your team actually works, not how a software vendor imagines they do.

Published Work — Regulated Health Data

Healthcare data under Texas HHSC oversight

Published a 219-page population health assessment for Texas HHSC's Prevention Resource Center 11, covering substance use, mental health, and demographic data across 19 South Texas counties. Compliance with the strictest tier of US health data wasn't theoretical. It was the job.

2023 Regional Needs Assessment: read the full 219-page report (PDF).

Peer-Reviewed Publications

Cognitive Psychology & I-O Psychology research

Published research in cognitive psychology and Industrial-Organizational Psychology. Peer review is a discipline: hypothesis-driven design, evidence-based methods, measurable outcomes. We hold our healthcare automation to the same standard.

Most AI consultants pitching healthcare have none of this. They learn HIPAA from blog posts. We learned the underlying science (clinical, behavioral, regulatory) over a decade.

The full research background, including the New York State clinical-skills engagement across 1,000+ providers, lives on our science page.

Delivered remotely, built bilingual

Built remotely, delivered to practices anywhere in the U.S. Bilingual by default.

Bilingual isn't an upgrade, it's the default. Your Spanish-speaking patients deserve the same patient experience as your English-speaking ones. We design every patient-facing system bilingual from day one: language detection automatic, cultural calibration native, no extra cost, no afterthought translation. That is a workforce capability we bring to every practice, not a filter on who we serve.

Discovery and rollout run over video, so your team never waits on a site visit. Whether you are down the street or across the country, you get the same strictest-domain rigor and the same responsiveness. Forged in one of the country's hardest markets, delivered to any U.S. market that needs it.

The Engagement

How working with us actually works.

01

Free 30-min discovery

We map your highest-leverage automation opportunity. Practice-specific, ROI-anchored. No commitment. No sales pressure.

02

Custom build proposal

Fixed scope, fixed price, clear timeline. You review and approve before any work starts. Most practices start with one or two systems, not all of them.

03

Build, deploy, document, train

Typical timeline: 3–6 weeks per system. We don't disappear after deployment — we stay until your staff has actually adopted what we built. That's how I-O Psychology research changes outcomes: training transfer is the bottleneck, not technology.

Currently Active

Currently in active deployment.

We're currently building out our first dedicated healthcare engagement with a leading practice. The case study publishes once the deployment is fully operational and the practice approves what we share.

Free Service · No Commitment

Free HIPAA Stack Audit

Most healthcare practices don't realize how many of the tools they already use put patient data at risk. WhatsApp for staff communication. Free email-to-text services. AI assistants without Business Associate Agreements. Photo-sharing apps for x-rays.

We'll audit your current automation, communication, and data-handling tools, flag what puts you at compliance risk, and give you a written report. Free. No commitment. Roughly 30–45 min of your time.

This isn't a sales gimmick. It's a service we can provide quickly because we've spent years thinking about exactly this problem in regulated contexts.

Before the fit check

What practices ask before trusting anyone with patient data.

Compliance questions tend to get vague answers in this industry, usually because vague is safer for the vendor. Here are ours, in plain language.

[+]

What is a Business Associate Agreement, and why does it keep coming up?

It is the contract that makes a vendor legally accountable for patient data. Under HIPAA, any outside party that stores, transmits, or processes protected health information on a practice’s behalf has to sign one, and it binds them to safeguard that data and to report a breach. A vendor who will not sign one cannot lawfully touch patient information, however good the software is. It is also a private contract: nothing is filed with any agency, and there are no government fees.

[+]

Are you HIPAA certified?

There is no such thing — not for us, not for anyone. No government agency certifies HIPAA compliance, and any badge sold as one is paper. Real compliance is four concrete things: signed business associate agreements with every vendor that touches patient data, written privacy and security policies, a risk assessment, and technical safeguards actually in place. Ask any vendor to show you those four. Ask us.

[+]

Can we just use WhatsApp or ChatGPT for patient communication?

Not for anything carrying patient information. Meta does not sign business associate agreements for WhatsApp, and consumer AI tools require an enterprise tier with an executed agreement before they can lawfully process protected health information. These tools are genuinely useful, and we build with them in other industries, which is exactly why practices assume they are fine here. The gap tends to stay invisible until the day it is not.

[+]

Whose accounts does the system run in?

Yours, by default. Infrastructure is set up in the practice’s own tenancy wherever possible, so the data sits in an account the practice controls and keeps if the relationship ends. Where the data lives is not a technical detail. It decides who can reach it, who can revoke access, and what happens on the day you want to walk away.

[+]

Are you attorneys? Is any of this legal advice?

No, and no. We architect and build systems against HIPAA’s technical and administrative requirements, and we sign business associate agreements for the work we do. We are not your counsel, and nothing we provide replaces a healthcare attorney reviewing your agreements, policies, and risk assessment. A vendor who blurs that line is telling you something about how they handle the rest.

[+]

Our staff has abandoned new software before. Why would this be different?

Because adoption is treated as the actual problem rather than an afterthought. Most healthcare automation fails at training transfer, not at the technology: the system works, and the team quietly routes around it. Builds are designed around how a front desk really operates, and the engagement continues past deployment until the workflow has genuinely been absorbed. That emphasis comes from graduate training in Industrial & Organizational Psychology, applied to the part most vendors skip.

[+]

Is our practice too small for this?

Size is the wrong test. The real question is whether one specific process — missed calls, unscheduled treatment plans, front-desk hours lost to paperwork — is costing enough to be worth automating. Most practices start with a single system rather than a platform, and the smallest useful build is smaller than people expect. Part of the fit check’s job is to tell you when the answer is no.

[+]

How long does a build take, and how is it priced?

Typically three to six weeks per system, always fixed scope at a fixed price, and always quoted after discovery rather than off a menu. You review and approve the proposal before any work begins. What it costs depends on what the system has to do and how many people it has to serve, so a number quoted before understanding the practice would be a guess wearing the costume of a quote.

[+]

Do you work with practices outside Texas?

Yes. Discovery and rollout run over video, so nothing waits on a site visit, and delivery is nationwide. Every patient-facing system is also built bilingual from the first day, English and Spanish, with language handling designed in rather than translated on afterward.

[+]

What is the free HIPAA Stack Audit, and what is the catch?

There is no catch and no obligation. We review the automation, communication, and data-handling tools your practice already uses, flag the ones creating compliance exposure, and send back a written report. It costs you roughly thirty to forty-five minutes. We offer it free because it is fast for us and because most practices genuinely do not know everything sitting in their stack — and if the report finds your stack is clean, that is the report you get.

Ready to build healthcare automation right?

Delivered remotely. HIPAA-aware. Designed for the way your practice actually works.