1. Identify the processing boundary

AIR Recon DL K252379 describes a reconstruction feature integrated into GE MR system software with purchasable options. SubtleMR 2.3.x K223623 describes MRI image enhancement. These records illustrate different processing boundaries; they do not establish interchangeable eligibility or performance.

  • Is the proposed feature part of scanner reconstruction, image post-processing, or another workflow? Draw its input and output boundary.
  • Which exact scanner model, software build, field strength, coil, sequence and licensed option are covered by the current offer and labeling?
  • Who will reconcile the proposed version with the exact FDA materials, and which requested protocols remain outside the documented scope?

Source context: FDA K252379: AIR Recon DL · FDA K223623: SubtleMR 2.3.x

2. Define the image and workflow evaluation

Read the endpoint and test conditions for the exact record before translating an image-quality claim into a protocol change. The public FDA summary is a starting point; local protocol decisions require the responsible clinical team.

  • What reference images, clinical tasks and reader assessment will your team use for the proposed protocol? Set acceptance criteria before testing.
  • How will image appearance, diagnostic limitations, failed processing, reruns and the unprocessed image path be reviewed?
  • How will protocol changes be versioned, approved and reversed, and who will reassess them after scanner or AI upgrades?

Source context: FDA K252379: AIR Recon DL · FDA K223623: SubtleMR 2.3.x · FDA list of artificial intelligence enabled medical devices

3. Purchase the complete configuration

The AIR Recon DL summary describes software option keys, including a separate additional option for its phase-correction enhancement. Use that distinction to request the complete configuration and costs. No public list price or realized time saving is supplied by this guide.

  • Does the quote itemize required scanner upgrades, option keys, interfaces, hardware, service, training and future renewal or upgrade costs?
  • If a shorter acquisition is proposed, what constrains the full appointment and which additional examinations could actually be scheduled and staffed?
  • Who will confirm the complete cost basis? Track scanner-capacity assumptions separately: the directory scenario models interpretation support, not MRI acquisition time or scanner throughput.

Source context: FDA K252379: AIR Recon DL

4. Work a fictional evaluation

A fictional purchasing team wants to evaluate an MRI processing proposal. It has not decided whether its task belongs inside reconstruction or after image formation, and has no verified offer or installed configuration. Synthetic buyer inputs only. No product winner, clinical approval, offer or local acceptance is implied. Use the worked links below.

  1. Define the processing boundary first. K252379 and K223623 illustrate different reconstruction/image-enhancement contexts, not a head-to-head winner or disease-detection authorization.
  2. Open exact identities, label constraints and evidence-context cards. Preserve each tested version, input, comparator and endpoint; do not pool unlike processing tasks.
  3. Use comparison caveats to document why the records may not be substitutable. FDA decisions do not prove current availability, license scope or a supported installed configuration.
  4. Ask for the complete implementation/offer and local test plan. Separate protocol/acquisition evaluation from interpretation-workflow assumptions. Platform availability and image output support remain questions until exact-scope evidence closes them.
  5. Prepare a private checklist and committee packet with open questions. If modeling interpretation time, saved capacity is not guaranteed money and does not establish MRI scan acceleration. Keep assumptions and action owners private.

Source context: FDA K252379: AIR Recon DL · ACR ARCH-AI: governance and implementation context · ACR Assess-AI: clinical performance-monitoring context

Take the next step

Inspect the exact example records

Examples illustrate the questions above. They are not a ranking, equivalent alternatives, confirmed offers or the complete market.

Documented family navigation: AIR Recon DL · SubtleMR image enhancement. Confirm each record's own scope.

Explore a private interpretation-capacity and cost scenario · Read a fictional committee packet · Check system compatibility scope

The linked scenario models interpretation support. It does not model MRI acquisition time, protocol acceleration or scanner throughput; evaluate those assumptions separately.

The worksheets and scenario use your assumptions. Save or attach private inputs explicitly; public evidence does not turn those inputs into verified results. The public sample uses fictional facility values.

Sources and scope

Sources anchor the stated regulatory or interoperability context. The questions are original editorial prompts; a citation does not validate a financial assumption or establish local fit. Source dates below apply to this guide, not the whole directory.

  1. FDA K252379: AIR Recon DL

    PDF pages 4-5: device description and software options. Checked .

    Exact reconstruction and option context; no offer price, protocol approval or installed eligibility is established.

  2. FDA K223623: SubtleMR 2.3.x

    PDF pages 3 and 5: indications and device description. Checked .

    Exact image-enhancement context; no equivalence to scanner reconstruction or another version is asserted.

  3. FDA list of artificial intelligence enabled medical devices

    About this list and public decision summaries. Checked .

    Regulatory source context; not local protocol or purchasing approval.

  4. ACR ARCH-AI: governance and implementation context

    Requirements At a Glance: governance team, inventory, testing and workflow integration. Checked .

    General governance resource only. Linking does not certify this directory, a device or a local site; no affiliation or endorsement.

  5. ACR Assess-AI: clinical performance-monitoring context

    Real World Data and monitoring: model inputs, versioning and concordance. Checked .

    General post-deployment monitoring resource only. No participation, coverage for an example device, certification, affiliation or endorsement is claimed.

Dataset and maintenance dates · Methods · Submit a source-backed correction