Healthcare practices and clinics

How work moves in a practice or clinic

A patient's path starts before the visit. A referral arrives from another provider by fax, by portal or through the EHR. Someone at the front desk checks insurance, confirms whether the visit or procedure needs a prior authorization, and schedules the patient. Intake forms go out and come back, sometimes on paper at the front counter.

The visit itself runs inside the EHR: the clinical team documents, orders tests, writes prescriptions and refers onward. After the visit, the work splits again. Orders and referrals go out and need results back. Coding turns the visit into a claim. Billing submits it, works the denials that come back, and posts payments from payers and patients. Somewhere in the middle, the patient calls to ask what happens next.

The roles are front desk and scheduling staff, referral and authorization coordinators, medical assistants and nurses, providers, coders, billers and a practice manager who sees the whole thing only in pieces. In a multi-location group, each site often does the same work its own way.

Where it usually breaks

Referrals and authorizations live in a queue nobody can see

A fax comes in, gets printed and goes into a tray. An authorization request goes into a payer portal and waits. The status of each one sits in a coordinator's spreadsheet or memory, and the patient finds out it stalled when they call. That is the invisible queue. The guide on spreadsheets that became the system of record shows how to find them.

Intake is typed in twice

The patient fills out a form. Someone keys it into the practice management system, then copies part of it into the EHR, then retypes insurance details into a payer portal. Every copy is another chance for a wrong date of birth or member number to deny the claim later. That is the re-entry trap.

Denials pile up as one-off exceptions

Each denial looks unique, so each is worked by hand by whoever knows that payer. Nobody counts which reasons repeat, and the same missing modifier or expired authorization denies the next claim too. That is the exception swamp.

Orders go out and results do not come back

A test is ordered or a patient is referred onward. Whether the result came back, and whether anyone looked at it, depends on someone remembering to check. When it falls through, it is found weeks later. That is the handoff gap, and it is where a workflow problem becomes a patient problem.

Working inside the rules

Before we arrive on site, we learn the rules the practice's work runs under, and the build is designed inside them. For health information that starts with the HIPAA Privacy and Security Rules in 45 CFR Part 164: the minimum necessary standard in section 164.502(b), which asks that a use or disclosure of protected health information be limited to what its purpose needs, and the technical safeguards in section 164.312, including access control and audit controls. It also covers the practice's own policies and any state rules its privacy officer points us to.

In practice that shapes the design from the first day. The Spec records which fields each step of the workflow actually needs, and the build carries those and nothing more. Each person sees what their role needs, and the tool keeps a record of who touched what. Patient information stays in the systems the practice already runs wherever the workflow allows. Every design choice that touches patient information goes to the people at the practice who own those decisions.

The first workflow we usually look at

Usually the path from a referral or order arriving to the patient being scheduled with everything in place: insurance verified, authorization approved, intake complete. It touches the front desk, the coordinators, the clinical team and billing, and every gap shows up as a patient who waited, a visit that had to be moved or a claim denied for something that was knowable in advance.

We sit with the front desk and the coordinators, follow a set of recent referrals from arrival to visit, and count how long each one waited and where. If denials or results follow-up cost the practice more, the Spec says so and focuses there.

The systems in the picture

A practice or clinic usually runs some mix of these:

• An EHR, often with practice management and scheduling built in or attached
• A clearinghouse and payer portals for eligibility, authorizations and claims
• A fax line or e-fax inbox that still receives much of the referral traffic
• A patient portal and a phone system
• Spreadsheets for referral tracking, authorization status and denial work
• An accounting system and payroll, separate from clinical billing

What a Workflow Spec looks like here

A Workflow Spec for a practice or clinic is priced by deployment, and takes up to five business days on site, scheduled around clinic hours. We sit with the front desk on a full morning, with the coordinators while they chase authorizations, and with billing while they work denials, and we interview the people who touch a patient's path outside the exam room. You get the workflow map, the business case, an adoption design built for the staff who would use the tool, and a fixed proposal for the build. The answer can be not to build. Details are on how we work.