Buyer glossary

Health AI terms in plain language.

Definitions that keep product claims, safety, enterprise operations, and market evidence in the same frame.

How to use it

A shared vocabulary improves diligence.

These are working definitions for enterprise research, not legal, professional, or educational advice. Follow the linked category and market guides for context.

Intended purpose

The specific task, user, population, environment, and outcome a product is designed or claimed to support.

Why it matters: A product can be suitable for one intended purpose and unsuitable for another, even when the vendor name and model are the same.

Software as a medical device (SaMD)

Software intended for one or more medical purposes that is not part of a hardware medical device.

Why it matters: The intended purpose, not the marketing label, determines which regulatory, quality, evidence, and post-market questions a buyer must ask.

Clinical safety case

A structured argument, supported by evidence, that a health technology can be used safely in a defined clinical context with risks controlled.

Why it matters: A buyer needs accountable clinical ownership, hazards, mitigations, evidence, and an operational change process rather than a safety slogan.

Model drift

A change in data, population, workflow, prevalence, or performance that makes a model's prior validation less representative of current use.

Why it matters: Drift monitoring, thresholds, incident ownership, revalidation, and rollback should be part of the operating plan.

Human oversight

The people, workflow controls, review opportunities, escalation paths, and accountability that keep an AI-assisted decision within its safe boundary.

Why it matters: Human-in-the-loop is meaningful only when the person has context, time, authority, training, and a way to correct or reject output.

Ambient documentation

A workflow that captures a consented conversation or encounter context and produces a draft clinical note or administrative record for human review.

Why it matters: Measure edit burden, consent, retention, provenance, specialty performance, and final clinician accountability.

Revenue cycle management (RCM)

The operational processes that connect patient access, coding, billing, claims, payment, denials, and financial reporting.

Why it matters: An RCM automation claim needs a baseline, exception design, audit trail, payer context, and evidence of displaced work as well as cash impact.

Evidence maturity

How much relevant, current, independent, external, regulatory, or health-system evidence exists for the exact product, use, workflow, and market.

Why it matters: Evidence maturity is not a clinical superiority score and does not replace formal diligence or local validation.

Market status

The state of documented public evidence for a product's regulatory, deployment, support, language, procurement, and availability context in a named market.

Why it matters: Documented, limited, and verify states prevent a global vendor claim from being mistaken for current local authorisation or availability.

Why read

Use the same words before you compare products.

The short answer: shared definitions help a buyer separate a product's stated purpose from evidence, safety, market, and procurement questions.

Next step: choose a category, open its buyer questions, and ask the vendor to define any term that still means something different in practice.

A practical next step

See what these ideas look like in a working application.

Enterprise AI Group describes a 6–8 week path for a defined business process, with governance, policy management, enterprise security, and Microsoft-tenant deployment considered from the start.

Enterprise AI Group describes a 6–8 week path for a defined workflow. Timing and cost depend on scope, users, integrations, security, governance, and support. These research pages are published by Enterprise AI Group. The implementation links describe optional Enterprise AI Group services; they are not product endorsements or a replacement for local diligence.

Explore workflow automation

Do not include personal health information or other sensitive information in an enquiry.

Keep the useful part

Tell us what you are deciding next.

Send the workflow, market, or category you are researching. We will use it to shape the next clear buyer brief.

Useful detail: include the market, workflow, or category behind a health AI term or category.

Please do not send personal health information or other sensitive health information.