iSchemaView RAPID

K182130

iSchemaView, Inc. · cleared 2018-12-27 · product code LLZ · Radiology

FDA 510(k) summary for iSchemaView RAPID (K182130)

Constat organizes this clearance into predicate context, validation evidence, reported performance, postmarket signals, and reimbursement links. Each extracted claim stays tied to the public FDA source; missing fields remain explicitly unstated.

Validation studies
2
Cited predicates
1
Performance observations
0
Product code
LLZ

Premarket evidence — what FDA accepted

Device typesamd
source quote (p.5)
“RAPID is a software-only device consisting of one or more RAPID Servers (dedicated or virtual and an iSchemaView Server).”
AlgorithmThe algorithm is characterized by its modules (DWI Module, Dynamic Analysis Module) which visualize local water diffusion properties and dynamic imaging data, and calculate parameters related to tissue flow (perfusion) and tissue blood volume.
source quote (p.3)
“The DWI Module is used to visualize local water diffusion properties from the analysis of diffusion - weighted MRI data. The Dynamic Analysis Module is used for visualization and analysis of dynamic imaging data, showing properties of changes in contrast over time. This functionality includes calculation of parameters related to tissue flow (perfusion) and tissue blood volume.”
Adaptive (vs locked)FDA source did not state this
PCCPFDA source did not state this
Cybersecurity addressedYes
source quote (p.6)
“It connects to a firewalled Data Center Network and has its own firewall for additional cyber/data security. The iSchemaView Server connects to one or more RAPID Servers via WAN. Available types of connection include VPN (Virtual Private Network - RFC2401 and RFC4301 Standards) Tunnel and SSH (Secure Shell).”

Validation studies (2)

Bench

sample size not stated

standards: EN ISO 14971:2012, IEC 62304:2015, IEC 62366:2015, NEMA PS 3.1 - 3.20

Retrospective clinical

sample size not stated

Reported performance (0 observations)

FDA source did not state a quantitative performance metric — non-reporting is itself the signal.

Each value carries its own analysis unit and task — never compare or pool across devices. Source: 510(k) summary PDF.

Predicate network

Postmarket — what happened after clearance

25
recalls in product code, 24mo
397
MAUDE reports in code, 12mo
+963%
vs code's own 3-yr baseline
32
drift signals on this device
  • predicate_cohort_contagion

    K182130 shares predicate K172477 with K233512 (Rapid (6.0)), whose product code QIH recorded 1 recall event(s) in the trailing 24 months.

    first seen 2026-09-02 · predicate:K172477 sibling:K233512

  • re_clearance

    The FDA AI/ML device list shows a newer 510(k) K233512 (decision 2024-01-16) from iSchemaView, Inc. for a matching device line ("Rapid (6.0)") — a new clearance for the same line is a change event.

    first seen 2026-07-08 · k_number:K233512

  • recall_reason_pattern

    Software/algorithm-related recall in product code LLZ (Merge Healthcare, Inc., initiated 2026-07-22): "Software issue may cause measurements to be displayed inaccurately." Recalling firm is another firm in the same product code.

    first seen 2026-09-02 · recall res_event_number:99520

  • recall_reason_pattern

    Software/algorithm-related recall in product code LLZ (FUJIFILM Healthcare Americas Corporation, initiated 2026-07-22): "Software issue may cause the ruler measurement to be inaccurate." Recalling firm is another firm in the same product code.

    first seen 2026-09-02 · recall res_event_number:99529

  • recall_reason_pattern

    Software/algorithm-related recall in product code LLZ (Merge Healthcare, Inc., initiated 2026-06-30): "Merge Healthcare has identified a potential issue that may cause thumbnails from a previously opened patient study to be displayed in the Thumbnail Bar while a different patient st" Recalling firm is another firm in the same product code.

    first seen 2026-09-02 · recall res_event_number:99391

  • recall_reason_pattern

    Software/algorithm-related recall in product code LLZ (Boston Scientific Corporation, initiated 2026-06-19): "Software anomaly occurs when a user adds one or more vials to the cart and subsequently returns to the Activity Calculator to modify one or more input. When a user modifies an inpu" Recalling firm is another firm in the same product code.

    first seen 2026-09-02 · recall res_event_number:99236

  • …and 26 more.

Recall and MAUDE counts are product-code-level (reports aren't reliably attributable to one device); a recall is shown as device-attributed only when the recall record itself lists this clearance number. Signals are descriptive observables with sources — never a judgment that the device is unsafe or drifting. Snapshot 2026-09-02.

Reimbursement — how devices like this got paid

Not yet tracked — no payment pathway indexed for this clearance (the reimbursement corpus is a growing seed set).

Applicable FDA guidance — what the submission is measured against

FDA guidance documents and guiding principles applicable to 510(k) AI/ML devices in the Radiology panel. A curated reference index, not legal or regulatory advice — each item states its own status, and a draft is never binding.

Applicability is derived from the device's FDA advisory panel and pathway — cross-cutting guidances apply to every AI/ML device; panel-specific ones are flagged. Titles, dates, and links verified against fda.gov as of July 2026.

Related FDA clearances

These are recent clearances in the same FDA product-code category. Shared classification does not by itself make a device an appropriate predicate.

Constat Precedent · public FDA/CMS data · descriptive decision-support, not regulatory or reimbursement advice. Share this page: constat.dev/precedent/device/K182130