Assess
Map the workflows in scope, the people who run them, and the decisions a person still has to make.
Justin Ingram consults on healthcare operations. The work is an assessment, a department-by-department discovery, and a written roadmap. Tools come after a person accepts the scope.
Written by Justin Ingram, healthcare AI consultant. Reviewed November 9, 2026.
A healthcare AI consultant should be able to describe the work in operating terms: who does the task today, where it stalls, what a person must still approve, and which systems are allowed to see patient information. Justin Ingram does that work with practice owners and with leaders of healthcare organizations.
He opened and operated clinics in weight loss and regenerative medicine starting in 2017, then founded ModFX Media. This page describes the consulting engagement. It does not publish client names, revenue figures, or a practice count.
Practice owners usually start with a front desk, documentation, billing, or recall problem. Organization leaders usually start with a wider question: which departments are actually ready, and what has to be true before any tool is connected. Both paths use the same gates. The educator page for the compliance question is the HIPAA compliant AI guide. Multi-site groups can use the executive workflow assessment or healthcare operations consulting. Healthcare nonprofits can start at AI for nonprofits. Clinical and diagnostic labs can start at AI for clinical labs.
Practice owners and administrators who need a named person to review workflows before a vendor demo turns into a purchase.
CEOs, COOs, and operations leaders at multi-site groups, MSOs, and other healthcare organizations. The focus is nonclinical operations: scheduling, intake, billing follow-up, referral handling, staff communication, and the handoffs between them.
Security, compliance, and procurement leads who need the BAA and access questions answered before a pilot, not after staff have already pasted charts into a consumer chatbot.
The assessment is a working session, not a software tour. Justin asks what the organization is trying to change, which roles touch the work, and which systems already hold the data.
For a clinic, that often means the front desk, the provider schedule, the billing queue, and the recall list. For a larger organization, it means the same questions asked of the operating leaders who own those functions across sites.
You leave with a written list of workflows in scope, workflows out of scope, and the decisions a person still has to make. Nothing on that list is a promise of hours saved or revenue recovered.
Discovery walks one department at a time. Each pass records the current steps, the system of record, the people who approve exceptions, and the patient information the step can see.
Departments that are not in the written scope are not "phase two" by default. They stay out until a leader adds them. That keeps a pilot from spreading into clinical documentation or a second location because a tool happens to offer the feature.
Discovery is also where staff describe the tasks they will not hand to software. Those tasks stay manual on purpose.
The roadmap names the workflow, the department, the system it has to sit next to, the human approval step, and the stop condition. If the stop condition is hit, implementation pauses.
Implementation means configuring the agreed workflow, training the people who will use it, and watching the first real cases with those people in the loop. It is not a login and a slide deck.
A larger rollout is a separate written scope. The first roadmap does not authorize it.
Human oversight: a named person accepts the output or the next step before it changes a schedule, a claim, a chart, or a message to a patient. The consultant does not replace that person.
Security: the workflow is rejected if the vendor cannot say where data is stored, who can access it, and whether the organization can get logs. Marketing language about certifications is not accepted as evidence.
BAA gate: if the workflow can include protected health information, a signed Business Associate Agreement is required before the tool is used. No BAA, no pilot.
These gates are the consulting method. They are not a claim that Justin Healthcare AI holds a SOC 2 report or a HITRUST certification.
No published case studies, client logos, or outcome statistics. If a number is not on this page, it is not an offer.
No price list. Scope and cost are discussed on the discovery call after the workflows are named.
No clinical advice and no unsupervised clinical documentation. Clinical tools stay behind the same human review and BAA gates as everything else.
A proven approach to help healthcare practices adopt AI with confidence and achieve measurable growth.
Map the workflows in scope, the people who run them, and the decisions a person still has to make.
Write what will change, what stays manual, and which steps need a signed BAA before they proceed.
Configure only the accepted workflow and train the people who use it. A wider rollout needs a new scope.
Tell us about your practice and we'll show you exactly where AI can save you time and money.
Justin reviews how the practice or organization actually runs, writes the workflows that are in scope, and implements only those workflows after a person accepts the plan. Patient information stays behind a signed BAA.
No. Practice owners use the same method as operations leaders at multi-site groups. The organization version spends more time on department discovery and on who is allowed to approve a rollout past the first site.
A vendor demo starts from the product. This engagement starts from the workflow and can end with no purchase. If a tool is recommended, it still has to pass the human review, security, and BAA gates.
No. This site does not publish client names, revenue results, awards, or a count of practices served.
Book the AI readiness assessment. It is the discovery call for both practice owners and organization leaders. Multi-site groups that want the longer briefing can use the enterprise page after that, or instead of it if procurement needs the briefing format.
The discovery call names the workflows in scope. You can accept the written scope, revise it, or stop.
Discovery call. No patient information on the form.
Strategy, implementation, and fractional AI leadership for medical practices. Explore cluster guides in this silo, then jump to sibling pillars.
Disclaimer:The consulting services described on this page are advisory and operational in nature. They do not constitute medical advice, clinical decision-making support, or legal advice. AI implementation decisions should involve your practice's clinical, compliance, and legal stakeholders. This page does not publish client results. An example is not a promised outcome.
Discover how AI can reduce admin, improve patient experiences, and help your practice grow with confidence.
Ready when you are. Free audit
Book audit