Skip to content

AI for Healthcare

AI for healthcare, pilot to production, with a clinician still in the loop

Take documentation, coding, prior authorization, access and record review off your teams, with a person still approving anything that touches a patient or a claim. Clinical-adjacent and administrative, not autonomous diagnosis.

Healthcare AI spending reached $1.4B in 2025, nearly 3x 2024 (Menlo Ventures via HC Innovation, Oct 2025).

  • 40+ products since 2017
  • 20+ engineers
  • 5.0 on Clutch
  • 4.8 on Google
  • 93% on-time
  • UK, EU and USA

Last updated: November 2026

AI for healthcare means using machine learning and language models to take documentation, coding, prior authorization, access and record review off clinical and administrative teams, with a person still approving anything that touches a patient or a claim. The value today is clinical-adjacent and administrative, not autonomous diagnosis.

JoulesLabs is an AI product and systems engineering partner that takes healthcare AI from pilot to production with the human checkpoint and the governance built in. One scope note up front: we have not shipped a healthcare AI system to a named client. AI has shipped in production only as features inside products (contract-clause detection, review-reply generation), with Meetense launching in December 2026, so this page is our approach and production-readiness method, not a healthcare case study we are dressing up. JoulesLabs' CEO signs this page for providers and payers in the UK, EU, GCC and USA.


Healthcare AI spending reached USD 1.4 billion in 2025, nearly three times the 2024 total, with providers supplying USD 1 billion of it (Menlo Ventures, 2025 State of AI in Healthcare).


Why now: the EU AI Act's high-risk obligations reach healthcare AI in two steps, Annex III systems from 2 December 2027 and AI inside regulated medical devices from 2 August 2028 (Regulation (EU) 2026/1744), and US payers must run FHIR prior-authorization APIs from 1 January 2027 (CMS-0057-F), so the governance and admin-automation work cannot wait.

Reviewed by Arifur Rahman Naim, CEO, JoulesLabs
Last updated: November 2026

The map What can AI actually do across healthcare today?

WHERE AI WORKS TODAY
5
PRODUCTS SINCE 2017
40+
CLIENT HEALTHCARE AI SHIPPED YET
0

The AI that is working today clusters into five areas, and the useful way to read it is by where your pressure sits (CFO cost, clinician burden, or regulatory exposure), not by vendor category.

  • Safe to start
  • Build next
  • You stay in control

Start here Which healthcare workflow should you automate first?

The first workflow to automate is the one where your dominant pressure already lives. This guide maps the pressure to the first workflow and the human checkpoint it needs.

  1. CFO squeezing administrative cost

    The revenue cycle (coding, billing, denials)

    The human checkpoint: a coder reviews the complex and ambiguous cases.

  2. Clinicians drowning in notes

    Clinical documentation

    The human checkpoint: the clinician edits and signs the note.

  3. Compliance is the blocker

    Stand up governance first

    The human checkpoint: a governance board and an approved-tools list.

The revenue cycle is where administrative cost sits, so it is where a CFO's first AI project usually lands. If you want help picking the first move, that is what the Free AI Readiness Assessment is for.

Administrative How AI takes the administrative load off, safely

Three high-volume workflows, each with its human checkpoint and a route to the capability that builds it.

  • How does AI cut the clinical documentation burden?

    AI captures the patient and clinician conversation and drafts a structured, review-ready note, so the clinician edits and signs rather than types from scratch. The draft is a starting point for clinician review, not a signed record, and that review step is the compliance boundary. Kaiser Permanente rolled out ambient AI documentation across its 40 hospitals and more than 600 medical offices (Kaiser Permanente newsroom, August 2024). This runs on document AI for healthcare.

  • Can AI code encounters and run the revenue cycle without adding risk?

    AI can code well-documented encounters and move claims through the revenue cycle, lifting first-pass acceptance, while a coder reviews the complex and ambiguous cases. Coding and billing automation drew USD 450 million of healthcare AI spend in 2025, the second-largest category (Menlo Ventures, 2025). Measure first-pass acceptance rather than raw automation rate. This is intelligent automation for the revenue cycle.

  • How do AI agents handle prior authorization and denials?

    An AI agent gathers the documentation, validates it against payer rules and drafts the clinical rationale for prior authorization, flagging the gaps that cause denials before a claim is submitted, with a person approving the submission and any appeal. The forcing function is regulatory: US federal prior-authorization APIs are required from 1 January 2027, so the agent must slot into that API path rather than bolt onto a legacy portal (CMS Interoperability and Prior Authorization final rule, CMS-0057-F). Built with agentic systems engineering.

The clinical line What can AI do for patient access, and where does imaging and decision support stop?

On the clinical side, the line is drawn deliberately.

  • Patient access

    AI rebuilds the digital front door (scheduling, reminders, triage and routine questions) and deflects contact-centre volume to virtual agents, sending anything clinical or complex to a person. A healthcare virtual agent is judged by how reliably it hands off, not by how much it answers alone. Patient engagement was one of the two fastest-growing healthcare AI categories in 2025 (Menlo Ventures, 2025). This is conversational AI for patient access.

  • Imaging and record review

    AI summarises records across EMRs and compares prior and current scans to flag what a clinician should look at, and the clinician makes every final decision, through computer vision for imaging review.

  • Decision support, not diagnosis

    For diagnosis, AI can stratify risk and surface options for a clinician to evaluate (decision support), and it stops short of making the diagnosis. The FDA's revised Clinical Decision Support Software guidance, issued 6 January and re-issued 29 January 2026, applies the device exclusion function by function, so AI that presents options for independent clinician evaluation may fall outside device regulation (FDA, 2026). JoulesLabs builds only the support side, via predictive AI for decision support.

  • Research and the data foundation

    AI drafts early-phase clinical-trial protocols and task-specific models accelerate research steps, with a scientist reviewing and owning every output. Research is the lower-risk entry point, because outputs go to an expert for review before use, so generative models can move faster here than at the bedside. Domain-specific AI tools reached 22% of healthcare organisations in 2025, a tenfold rise since 2023 (Menlo Ventures, 2025). This is ML model development. Underneath all of it, healthcare AI agents need a clean, FHIR-interoperable data foundation with governed access to the EHR, because fragmented data is the core problem agents have to solve before they can be trusted. The build-vs-buy line on data: buy point tools, but own the FHIR data foundation and MLOps, because it is the asset every future agent depends on.

Governance How do you meet EU AI Act, MDR and FDA obligations for healthcare AI?

Meeting the obligations means classifying each system by risk, keeping a human reviewing high-impact outputs, and standing up a governance board and an approved-tools list, because medical AI is high-risk by default when it is part of a regulated device.

Medical AI that is a component of a device under Notified Body review is high-risk under Annex I, and those obligations apply from 2 August 2028; Annex III systems apply from 2 December 2027 (EU AI Act as amended by Regulation (EU) 2026/1744).

The governance checklist for every workflow: risk class, human checkpoint, approved-tools list and audit trail. This is AI security and governance work, and it is where most healthcare AI programmes are thinnest.

A hospital can trust a first project when nothing the AI produces reaches a patient or a claim without a named person signing it. We start on the administrative side, where a coder or clinician already reviews the work. We classify each system by risk first, then run it beside the current process until the numbers match.

Arifur Rahman Naim, CEO, JoulesLabs

Why JoulesLabs Why work with JoulesLabs on healthcare AI, and what has it shipped?

JoulesLabs has shipped 40+ products since 2017 and takes AI into live products as features. To be straight with you: no healthcare AI system has shipped to a named client yet, our first client agents are at proof-of-concept, and this page is our approach and production-readiness method, not a healthcare case study. 30% of US payers will address interoperability with AI and agentic AI by 2027, cutting manual workloads by 40%, and success depends on data quality, governance and human oversight (Gartner, Predicts 2026: U.S. Healthcare Payers Bet Big on Agentic Workforce, 15 December 2025). In place of a borrowed case study, a first project is scoped to de-risk it:

  • You own the IP and the FHIR data foundation

    That we build.

  • A scoped pilot

    With a fixed goal.

  • A parallel run

    Against your current process before cutover.

  • Milestone billing

    Tied to accepted outcomes.

Getting a pilot into production is pilot-to-production rescue work. First contracts are typically USD 20,000 to 50,000, scoped to the work.

Start where your pressure is, with the human checkpoint built in

Revenue cycle for cost, documentation for clinician burden, or governance if compliance is the blocker. A short call, or the free readiness assessment, is the fastest way to decide.

Start with a free readiness assessment

No obligation. You leave knowing which workflow to automate first and where the human stays in the loop.

FAQ Healthcare AI, common questions

Have you deployed AI in healthcare before?

No healthcare AI system has shipped to a named client yet. AI has shipped in production as features inside products (contract-clause detection, review-reply generation), and our healthcare work is our approach. We offer a scoped, de-risked first build instead of a borrowed case study.

Will AI make clinical decisions?

No. AI here is clinical-adjacent and administrative: it drafts notes, codes well-documented encounters, prepares prior authorizations and surfaces options for review. A clinician or coder approves anything that touches a patient or a claim.

Is it compliant with the EU AI Act and FDA rules?

We classify each system by risk and keep a human reviewing high-impact outputs. Medical AI is high-risk by default when it is part of a device, and decision-support that presents options for independent clinician evaluation may fall outside device regulation under the FDA's 2026 guidance. Governance is built in, not bolted on.

What does a first engagement cost, and do we own it?

A first contract is typically USD 20,000 to 50,000, scoped to the work, and you own the IP and the FHIR data foundation we build.

Where should we start?

Where your dominant pressure sits: the revenue cycle for cost, documentation for clinician burden, or governance if compliance is the blocker. The start-here guide above maps each to its first workflow and human checkpoint.

Healthcare AI is safe when the clinician keeps the decision and the system keeps the record. We build the draft, the flag and the checklist; a clinician or coder signs every output that touches a patient or a claim. Governance comes first, the model second, and we run both in parallel before anything goes live.

Arifur Rahman Naim, CEO, JoulesLabs