The biggest AI opportunity in healthcare isn't in the exam room.

It's in the work around the care: credentialing, chart audits, scheduling, revenue cycle, reporting and staffing. Practical playbooks for using operational AI safely, written by an operator for operators.

A new playbook every other Tuesday on LinkedIn.

Patientcare Credentialing Chart audits Scheduling Revenue cycle Reporting Staffing THE WORK AROUND THE CARE
20+ yearsin healthcare operations
3 → 13+locations, up from 3 offices before the PE partnership
40+providers across the practice
PE-backedplatform integration I led, in 2021

Definition

What is operational AI?

Operational AI is AI applied to the business side of healthcare, not to diagnosis or treatment.

It covers the work around the care: insurance credentialing, chart audits and documentation QA, scheduling, revenue cycle, reporting, staffing and multi-site growth.

Clinical AI reads scans and drafts notes. Operational AI decides how many patients a practice can actually serve, and it's where most practices see a return first.

Why operations

Growth is rarely limited by clinical capacity. It's limited by everything else.

Ask any practice administrator what keeps them from opening the next location or adding the next provider. The answer is almost never clinical.

  • Credentialing checked and re-checked across every payer and location
  • Chart audits that pile up faster than anyone can clear them
  • Schedule gaps nobody sees until the day is already lost
  • Reports pulled by hand from three, four or five systems
  • Follow-ups and handoffs that fall through the cracks

None of this is patient care. All of it decides how many patients a practice can care for.

That's why operational AI pays off first. The problems are well defined, the results are measurable within months, the barrier to entry is lower than clinical AI, and the people doing the work want the help.

In a multi-site organization the friction compounds. Every new location multiplies the administrative load, unless the operations are built to scale.

Playbooks

Where operational AI earns its keep

The best first use case is high volume, rules-based and measurable. These are the workflows the series covers.

Credentialing

Treat it as a data problem

Reconcile enrollment against appointment data across locations and catch gaps before they become denied claims.

Documentation QA

Chart audits that keep up

Review documentation consistently so issues are corrected early, not found months later in a billing review.

Scheduling

See the gaps in advance

Spot open time, no-show patterns and template problems before the day is already lost.

Revenue cycle

Protect what you've earned

Surface the patterns behind denials and follow-up backlogs so the team works the right accounts first.

Reporting

Stop pulling reports by hand

Replace spreadsheets stitched together from several systems with visibility leaders can act on.

Multi-site growth

Scale without scaling headcount

Standardize and automate the playbook so each new location adds capacity, not chaos.

AI + HIPAA

Safe AI shouldn't require an enterprise budget

The free and standard consumer versions of AI chatbots are not HIPAA compliant. There's no Business Associate Agreement, and what you type may be stored or used outside your practice's control, so patient information never goes into them. Enterprise AI with a BAA is often priced for health systems, which leaves small and mid-size practices stuck in between.

There are affordable, compliant paths. The series covers each one:

Start with non-PHI work: SOPs, policies, templates, aggregate reports
Check whether AI in your EHR or PM system is covered by your existing BAA
Properly de-identify data (HIPAA Safe Harbor) before using a standard tool
Use pay-as-you-go AI from a major cloud platform that signs a BAA
Run an open model locally, inside your own environment

General information, not legal advice. Confirm any approach with your compliance lead before using it with patient data.

The series

A new playbook every other Tuesday

Thirteen articles on LinkedIn, from the case for operational AI to measuring its return.

02Where to Start: 5 Operational Workflows Ready for AI TodayThe case
03Credentialing Is a Data Problem. AI Solves Data Problems.Playbook
04AI Phone Systems: The Good, the Bad and What to Ask Before You BuyPlaybook
05AI Chart Audits: Catching Documentation Issues Before They Cost YouPlaybook
06HIPAA-Compliant AI Without an Enterprise BudgetResponsible AI
07Build vs. Buy: Why I Built My Own Operations PortalPlaybook
08From 3 to 13+ Locations: Scaling De Novo Growth Without Scaling HeadcountScaling
··Plus PE diligence, reporting, what not to automate, the operator-builder and measuring AI ROI

About

Scott Goldman, healthcare operations executive and author of The Healthcare Operator

I'm Scott Goldman, an operator who builds.

I've spent more than 20 years in healthcare operations, consulting and management. I led a dermatology practice's 2021 integration into a PE-backed platform and helped grow it from 3 offices to 13+ locations and 40+ providers through de novo expansion. Today I lead regional operations and own a regional P&L.

Most voices in healthcare AI are vendors or consultants. I've spent years on both sides of the work, and I build my own tools. Goldman Technology, my company since before the 2021 partnership, started as an IT company for healthcare organizations, which meant seeing how their offices really ran day to day, not the version staff put on for management.

Since then, it has built software where nothing on the market fit:

  • A multi-office medical imaging system (PACS) for a vascular group
  • Touch-screen patient check-in kiosk software for a growing practice
  • Maintenance-request and tenant-question software for a medical office building
  • A practice operations portal, co-developed with a physician partner and deployed at two specialty organizations
  • HIPAA-compliant AI on a practice-sized budget

The Healthcare Operator is where I share what's worked, what hasn't, and how to do it safely.

Multi-site growth PE integration Credentialing Documentation QA HIPAA-compliant AI Operator-built software Multi-office PACS Check-in kiosks

FAQ

Questions practice leaders ask most

What is operational AI in healthcare?

Operational AI is artificial intelligence applied to the business and operations side of healthcare rather than to diagnosis or treatment. It covers work such as insurance credentialing, chart audits and documentation QA, scheduling, revenue cycle, reporting, staffing and multi-site growth: the work around the care that decides how many patients a practice can serve.

Why should a medical practice start with operational AI instead of clinical AI?

Operational problems are well defined, high volume and rules-based, which is what AI and automation handle well. The results are measurable within months (hours saved, errors caught, schedule utilization), the barrier to entry is lower because reconciling a credentialing file doesn't need FDA clearance, and the staff doing the work want the help.

Are free AI chatbots HIPAA compliant?

No. The free and standard consumer versions of AI chatbots are not HIPAA compliant. Their providers don't sign a Business Associate Agreement (BAA) for those versions, and what you type may be stored or used outside your practice's control. Never paste protected health information (PHI), such as patient notes, schedules or claims, into them. This is general information, not legal advice.

How can a small or mid-size practice use AI safely without an enterprise budget?

Enterprise AI with a BAA is often priced for health systems, but there are affordable paths: start with non-PHI work such as SOPs, policies, templates and aggregate reports; check whether AI built into your EHR or practice management system is covered by your existing BAA; properly de-identify data using the HIPAA Safe Harbor method before using a standard tool; use pay-as-you-go AI through a major cloud platform that signs a BAA; or run an open model locally. Confirm any approach with your compliance lead.

What is a good first AI use case for a medical practice?

Pick work that is high volume, rules-based and measurable. A useful test: ask what work your best people hate doing and what it costs you. Credentialing reconciliation, chart audits and hand-pulled reports are common starting points.

Who is Scott Goldman?

Scott Goldman is a healthcare operations executive with more than 20 years of experience. He helped grow a dermatology practice from 3 offices before its 2021 PE partnership to 13+ locations and 40+ providers through de novo expansion, led its integration into a PE-backed platform where he now leads regional operations, and founded Goldman Technology before 2021. It began as an IT company for healthcare organizations and has built a multi-office PACS imaging system for a vascular group, custom touch-screen check-in kiosk software, maintenance-request software for a medical office building, and a practice operations portal co-developed with a physician partner, deployed at two specialty healthcare organizations. He writes The Healthcare Operator, a series on operational AI.

Follow along

The practices that win won't just have the best clinicians. They'll have the best-run operations.