Authorized purpose: Analyzes CT or MR pixel data to create anatomical descriptors for export and to help identify images, series, and studies.
Clinical role
Software that analyzes CT or MR pixel data to create anatomic descriptors exported to integrated healthcare systems as supplemental metadata, so providers can rapidly identify images, series or studies of interest; it works in parallel to standard workflow.
Clinical detailsPurpose, workflow fit, evidence, and safety record
Workflow navigation pilot
Workflow role has not yet been reviewed for this navigation pilot.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: Analyzes CT or MR pixel data to create anatomical descriptors for export and to help identify images, series, and studies.
Which images or clinical context are in scope?Modality: CT/CTA; MRI Anatomy or clinical context: Abdomen; breast (MR only); calf; chest; elbow; foot; forearm; hand; head; arm; knee; neck; pelvis; shoulder; cervical spine; thoracic spine; lumbar spine; thigh Input: CT or MR DICOM image, series, and study pixel data.
Who uses it?Intended users: Physicians and other healthcare providers; descriptors are exported to integrated systems.
What does the software produce?Output: JSON anatomical descriptors per image or study as supplemental metadata; original images are not altered.
What is its most important limitation?Key limitation: Not indicated for patients under 18; descriptors are supplemental metadata and do not alter the original image.
Clinical takeaway. Clinical role: Analyzes CT or MR pixel data to create anatomical descriptors for export and to help identify images, series, and studies.
Evidence takeaway. Evidence from the reviewed source record: FDA-reported retrospective validation used separate training, validation, and test sets by modality, no repeat or temporal studies in validation/test, 27 institutions, and age-18-plus subjects.
Evidence context
Evidence context not reviewed for this FDA record.
Public-label constraints
Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.
Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.
Purpose
Analyzes CT or MR pixel data to create anatomical descriptors for export and to help identify images, series, and studies.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Software that analyzes CT or MR pixel data to create anatomic descriptors exported to integrated healthcare systems as supplemental metadata, so providers can rapidly identify images, series or studies of interest; it works in parallel to standard workflow.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Change Healthcare Anatomical AI is intended to analyze pixel data from CT or MR images to create comprehensive anatomic descriptors for export to integrated healthcare systems." … "The application is intended to enable physicians, or other healthcare providers as well as integrated healthcare systems to rapidly identify images, series, and / or studies of interest.". Read from the exact FDA decision document on 2026-11-14.
Patients aged 18 years or older with CT or MR images (not indicated for patients under the age of 18 years old); the FDA document does not specify a facility type.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Change Healthcare Anatomical AI is not indicated for patients under the age of 18 years old." … "Change Healthcare Anatomical AI is intended to analyze pixel data from CT or MR images to create comprehensive anatomic descriptors for export to integrated healthcare systems.". Read from the exact FDA decision document on 2026-11-14.
FDA-reported retrospective validation used separate training, validation, and test sets by modality, no repeat or temporal studies in validation/test, 27 institutions, and age-18-plus subjects.
Exact FDA submission
Checked 2026-09-19
Submission evidence only; no security or clinical decision-support claim.
Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.
Evidence summary
FDA-reported retrospective validation used separate training, validation, and test sets by modality, no repeat or temporal studies in validation/test, 27 institutions, and age-18-plus subjects.
FDA source
Exact FDA submission
Checked 2026-09-19
Submission evidence only; no security or clinical decision-support claim.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Change Healthcare Anatomical AI regulatory performance study summary
DesignStand-Alone Performance
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K210719
Sites27
IndependenceIndependence not established
K210719
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K210719. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
IT implementationDeployment, interfaces, data handling, and support
System and version relationships
Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.
No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.
Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.
Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner
No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.
Acquisition/source
Source context, not route validation: CT or MR DICOM image, series, and study pixel data.
Scope: Exact FDA submission. FDA packet input scope.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references DICOM and JSON in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. A legacy catalog deployment category, normalized to fixed categories, was not traced to the exact FDA decision document it cited, so it is not published as verified. Confirm the deployment model, hosting, data flow, and current commercial configuration with the vendor or an exact-submission source that states it.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-11-13 ·
Returned objects
Source context, not route validation: JSON anatomical descriptors per image or study as supplemental metadata; original images are not altered.
Scope: Exact FDA submission. FDA packet output scope.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: JSON anatomical descriptors per image or study as supplemental metadata; original images are not altered.
Scope: Exact FDA submission. FDA packet output scope.
Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
Planned local route tests
No tests below have been performed or accepted.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.
Local implementation checklist
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
The exact-submission ACR model card explicitly references DICOM and JSON in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Exact FDA submission
Checked 2026-09-01
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
ACR AI Central provides an exact-submission model card for Change Healthcare Anatomical AI; FDA labeling remains controlling for clinical use, limitations, and performance.
Sources & review detailsFDA identity, research record, source ledger, and history
Regulatory identity
FDA record and catalog context
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
This audit distinguishes completed source review from fields that have not yet been researched.
Exact FDA record reviewedStatus
2026-09-20Last searched
25Fields reviewed
10Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 PubMed and 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.
Source classes: fda ai list, fda decision summary, acr ai central product, fda device recall, literature index, trial registry, fda decision summary packet, pubmed, clinical trials, openfda device recall
Field review details
Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.
Public pricing: Not verified - checked 2026-09-09 - Exact FDA submission
No public price or quote for the exact K210719 configuration was established in this review.
Pricing model: Not yet reviewed
Setup and integration fees: Not yet reviewed
Recurring fees: Not yet reviewed
Minimum commitment: Not yet reviewed
Contract duration: Not yet reviewed
Renewal terms: Not yet reviewed
Cancellation terms: Not yet reviewed
Support and service terms: Not yet reviewed
Trial or pilot terms: Not yet reviewed
Reimbursement: Not publicly available - checked 2026-09-09 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
Deployment: Not verified - checked 2026-11-13 - Exact FDA submission
A legacy catalog deployment category, normalized to fixed categories, was not traced to the exact FDA decision document it cited, so it is not published as verified. Confirm the deployment model, hosting, data flow, and current commercial configuration with the vendor or an exact-submission source that states it.
Data hosting location: Not yet reviewed
Data retention: Not yet reviewed
Documented data use: Not yet reviewed
Hardware requirements: Not yet reviewed
Network requirements: Not yet reviewed
Identity and access: Not yet reviewed
Security: Not verified - checked 2026-09-09 - Exact FDA submission
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: View, post-process, and qualitatively and quantitatively evaluate cardiovascular MR and CT images in DICOM format to obtain diagnostic information as part of a comprehensive diagnostic decision-making process.
Modality
CT/CTA; MRI
Anatomy
Cardiovascular system; heart, coronary and adjacent vessels, and cardiac valves
Authorized purpose: Create, review, analyze, annotate, export, and use 3D cardiac models to support reading, reporting, and therapeutic-intervention planning.
Modality
CT/CTA; MRI
Anatomy
Cardiac structures, including the aorta, atria, ventricles, pulmonary artery trunk, and right atrium/inferior vena cava structures described in the FDA performance table
Authorized purpose: Process, review, analyze, communicate, and exchange multidimensional CT or MR images, including preliminary segmentation of normal anatomy, for preoperative surgical planning and intraoperative display; healthcare professionals make all final patient-management decisions. Machine-learning algorithms are for adults aged 22 years and older, while images for patients under 22 or of unknown age are generated without machine learning.
Modality
CT/CTA; MRI
Anatomy
Multi-region normal anatomy represented in CT or MR images; validated examples include prostate, bladder, neurovascular bundles, kidney, artery, and vein
Authorized purpose: Analyzes functional, dynamic, and derived CT or MRI datasets for brain perfusion, vascular assessment, tissue blood volume, and related parametric maps to assist physician diagnosis.
Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.
Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.
Accepted repository change history
No entry has been added to this scoped change history for this record. This is not proof that the record never changed.