Skip to content
Sweet Gum.
All work
Automation · Healthcare · 2026

Medical Practice Automation That Keeps Patient Data Private

Privacy-first automations behind a Tampa medical practice: a lab report formatter, a peptide handout builder, and intake and insurance exception tools for an affiliated practice.

Client

Formation

formationmed.com
  • Lab report formatter that runs fully offline, so patient data never leaves the computer
  • Peptide handout builder that assembles a custom patient handout in one step
  • Patient intake wizard with e-signature that produces HIPAA forms and emails the office
  • A faxed-report OCR experiment we stopped because 95 to 98 percent accuracy is not good enough

Formation is a Tampa plastic surgery and regenerative medicine practice, and we built the automations behind it: tools that remove repetitive paperwork while keeping patient information private. To be clear about scope, we did not build formationmed.com. The practice's public website at formationmed.com is not our work. This page is about the tools that run behind the scenes.

The client and the problem

A busy medical practice generates a steady stream of small, repetitive documents. Lab results arrive as PDFs and have to be compared against the practice's own target ranges. Patients need handouts tailored to their treatment. New patients fill out forms that have to become signed, properly formatted documents. Each of these tasks is manual, easy to get slightly wrong, and slow.

Medical work also adds a hard constraint: patient data is protected health information. Any tool that handles it has to be built with privacy as a starting point, not an add-on.

What we built

Lab report formatter

The practice's provider was downloading lab PDFs from Quest and comparing each result by hand to a spreadsheet of target ranges used for consults. We turned that into a tool. Drop in a Quest or LabCorp results PDF, and it produces a clean report branded for the practice, with each result flagged green, red or gray against the practice's own ranges, not the lab's printed ones.

The key design choice is that it runs entirely offline. It is a single file that opens by double-click in a browser. Nothing is uploaded, nothing is sent to a server, and it works with the wifi switched off. For a tool that touches lab results, that is the simplest privacy guarantee there is: the data has nowhere to go.

Peptide handout builder

The same tool has a second tab for peptide therapy. The provider enters a patient's name and date of birth, checks the therapies, consents and protocols that apply, and generates one branded handout. Optional provider notes print highlighted under any item. Consent forms and lifestyle protocols each get their own page. What used to be assembled by hand from a folder of documents is now one step.

The fax OCR experiment

Our next idea was to automate the intake of lab reports that arrive by fax. Faxes are flattened images, so we built a character-recognition tool to read them. After tuning, accuracy reached 95 to 98 percent.

We stopped there on purpose. For medical data, 95 percent is not good enough: every report would still need a person to check every number, which defeats the purpose and invites a missed error. We had also only seen one faxed sample, so we could not honestly claim the tool was reliable. Digital PDFs with a text layer are different. We can read those with 100 percent accuracy. Our recommendation to the practice was simple: get digital PDFs by email, or accept that fax automation is not safe. We would rather tell a client a project should pause than ship something that looks finished and is not.

Patient intake and insurance exception tools

For an affiliated reflux practice, Tampa Bay Reflux Institute, we built two web apps:

  • Patient intake wizard. A step-by-step form that collects patient information, captures an e-signature (drawn or typed), generates HIPAA authorization and representative forms as PDFs, stores them securely, and emails the office.
  • Insurance network gap exception request. A longer wizard that collects insurance details, clinical history, medications tried and barriers to care, then generates a signed exception request PDF for the office to submit.

How it works

The intake apps validate every field before submission, limit how often a single visitor can submit, and run on secured cloud hosting with secrets kept out of the code. Stored submissions can be set to delete automatically after a short retention window, so records do not sit around longer than needed. File names use a reference code and not the patient's full name.

The offline tools use a different approach: everything the tool needs is packed into one file, so there is no server to secure because there is no server.

Who this is for

Medical, dental and wellness practices, law firms, and any business that handles information customers expect to stay private, and that loses hours each week to the same forms and reports.

What we would tell another business like this

  • Decide where the data lives before you build. Offline-only is the simplest answer for tools that do not need a server.
  • Measure accuracy against the stakes. 98 percent is great for a recipe and unacceptable for a lab value.
  • Start with the task people dread. Hand-comparing results and assembling handouts are classic candidates.
  • Keep the last step human. Our tools produce a draft for a clinician to review, not a decision.
  • Be willing to stop. A paused project is cheaper than a wrong one.

Explore our workflow automation and custom business tools services, or talk to us about the paperwork eating your week.

Want results like these?

Every project on this site started with one conversation. Tell us what your business needs.