Authorized purpose: RayCare is an oncology information system used to support workflows, scheduling, and clinical information management for oncology care and follow-up. It may transfer, store, convert, and display patient data in cancer care including radiation therapy, medical oncology, and surgical oncology. RayCare is not intended for diagnostic activities.
Clinical role
Oncology workflow, scheduling, clinical information management, transfer, storage, conversion, and display support.
Images and patients
Radiological images; modality varies or is not specified in FDA list · Patient data across radiation, medical, and surgical oncology care; no diagnostic anatomy
Key limitation
Keep in mind: The exact indication excludes diagnostic activities; do not treat RayCare as a diagnostic-imaging, treatment-selection, or clinical-outcome product based on this submission.
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: RayCare is an oncology information system used to support workflows, scheduling, and clinical information management for oncology care and follow-up. It may transfer, store, convert, and display patient data in cancer care including radiation therapy, medical oncology, and surgical oncology. RayCare is not intended for diagnostic activities.
Which images or clinical context are in scope?Modality: Radiological images; modality varies or is not specified in FDA list Anatomy or clinical context: Patient data across radiation, medical, and surgical oncology care; no diagnostic anatomy Input: Patient data and oncology-care information from supported clinical workflows.
Who uses it?Intended users: Cancer-care clinical, technical, and administrative personnel within the labeled workflow.
What does the software produce?Output: Oncology workflow records, schedules, converted data, and displayed patient information for care teams.
What is its most important limitation?Key limitation: The exact indication excludes diagnostic activities; do not treat RayCare as a diagnostic-imaging, treatment-selection, or clinical-outcome product based on this submission.
Clinical takeaway. Clinical role: RayCare is an oncology information system used to support workflows, scheduling, and clinical information management for oncology care and follow-up. It may transfer, store, convert, and display patient data in cancer care including radiation therapy, medical oncology, and surgical oncology. RayCare is not intended for diagnostic activities.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports non-clinical performance data: verification and validation of RayCare 2.3 based on the intended use and functionalities of a standard oncology information system and on the standards ISO 14971, IEC 61217, IEC 62304 and IEC 62366; the summary of the performed non-clinical tests states RayCare 2.3 is as safe and effective and performs as well as the predicate device. Results are as reported in the FDA submission, not independent validation.
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
RayCare is an oncology information system used to support workflows, scheduling, and clinical information management for oncology care and follow-up. It may transfer, store, convert, and display patient data in cancer care including radiation therapy, medical oncology, and surgical oncology. RayCare is not intended for diagnostic activities.
The exact indication excludes diagnostic activities; do not treat RayCare as a diagnostic-imaging, treatment-selection, or clinical-outcome product based on this submission.
The exact FDA document reports non-clinical performance data: verification and validation of RayCare 2.3 based on the intended use and functionalities of a standard oncology information system and on the standards ISO 14971, IEC 61217, IEC 62304 and IEC 62366; the summary of the performed non-clinical tests states RayCare 2.3 is as safe and effective and performs as well as the predicate device. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "5.11 Assessment of non-clinical performance data" … "The verification and validation of RayCare 2.3 is based on the intended use and functionalities included in a standard oncology information system, and on the standards ISO 14971, IEC 61217, IEC 62304 and IEC 62366.". Read from the exact FDA decision document on 2026-11-14.
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
The exact FDA document reports non-clinical performance data: verification and validation of RayCare 2.3 based on the intended use and functionalities of a standard oncology information system and on the standards ISO 14971, IEC 61217, IEC 62304 and IEC 62366; the summary of the performed non-clinical tests states RayCare 2.3 is as safe and effective and performs as well as the predicate device. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "5.11 Assessment of non-clinical performance data" … "The verification and validation of RayCare 2.3 is based on the intended use and functionalities included in a standard oncology information system, and on the standards ISO 14971, IEC 61217, IEC 62304 and IEC 62366.". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Specificity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K191384 FDA decision evidence package for RayCare 2.3
DesignFDA decision evidence and product verification described in the exact submission or PMA decision record.
PopulationPatient data across radiation, medical, and surgical oncology care; no diagnostic anatomy
Scopeexact submission
Tested versionRayCare 2.3 configuration described in K191384
IndependenceSponsor or vendor study
K191384
FDA decision material is manufacturer-submitted regulatory evidence. It is not independent clinical validation unless the exact source expressly establishes that distinction; local technical, clinical, privacy, security, and workflow acceptance remains necessary.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K191384 by exact native submission identifier. This does not exclude product-family, later-version, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-04
Exact-identifier review does not prove absence of all product-family safety signals.
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: Patient data and oncology-care information from supported clinical workflows.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact public FDA decision material does not establish a complete integration contract. Confirm supported inputs, outputs, identity, routing, archive behavior, audit behavior, and downtime locally.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-04 ·
AI processing
Source context, not route validation: The exact FDA package describes RayCare as software with a client part and a server part for processing and storage; servers are located within the hospital IT environment and clients are used on the internal or secure wireless hospital network. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "RayCare is a software-only system with a client part that allows the user to interact with the system and a server part that performs the necessary processing and storage functions." … "RayCare servers are located within the hospital IT environment. RayCare clients are used within the internal hospital network or within a secure wireless network in the hospital.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Unresolved route: Oncology workflow records, schedules, converted data, and displayed patient information for care teams.
Scope: Exact FDA submission.
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 FDA package describes RayCare as software with a client part and a server part for processing and storage; servers are located within the hospital IT environment and clients are used on the internal or secure wireless hospital network. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "RayCare is a software-only system with a client part that allows the user to interact with the system and a server part that performs the necessary processing and storage functions." … "RayCare servers are located within the hospital IT environment. RayCare clients are used within the internal hospital network or within a secure wireless network in the hospital.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Only cancer-care clinical, technical, and administrative personnel within the labeled workflow should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K191384 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: The exact indication excludes diagnostic activities; do not treat RayCare as a diagnostic-imaging, treatment-selection, or clinical-outcome product based on this submission.
Exact FDA submission
Checked 2026-09-04
This is buyer-facing monitoring guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.
The exact public deployment topology remains incomplete; establish hosting responsibility, data flow, availability, upgrade, service, and downtime boundaries locally.
exact submission · checked 2026-09-04
FDA-described topology does not establish current hosting contracts, security controls, uptime, or local qualification.
The exact public integration contract remains incomplete; establish and test supported input, output, identity, routing, archive, and downtime behavior locally.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. The exact indication excludes diagnostic activities; do not treat RayCare as a diagnostic-imaging, treatment-selection, or clinical-outcome product based on this submission.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
exact submission · checked 2026-09-04
No exact-product price or reimbursement determination was promoted.
Monitor K191384 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: The exact indication excludes diagnostic activities; do not treat RayCare as a diagnostic-imaging, treatment-selection, or clinical-outcome product based on this submission.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
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
27Fields reviewed
9Source 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, fda decision material, fda device recall, literature index, trial registry, 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 publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared or authorized configuration was found. Obtain a written quote separating license or hardware basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
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-04 - Exact FDA submission
No exact-product reimbursement determination was promoted in this timeboxed review. Verify payer, site-of-service, coding, coverage, and local payment assumptions independently.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact public FDA decision material does not establish a complete integration contract. Confirm supported inputs, outputs, identity, routing, archive behavior, audit behavior, and downtime locally.
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 publicly available - checked 2026-09-04 - Exact FDA submission
Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
Authorized purpose: Cercare Neurosuite with Capillary Function and Oncology Virtual Expert processes CT or MR information to provide perfusion, tissue-blood-volume, diffusion, labeling, and quantification support for adult brain glioma workflows.
Modality
Radiological images; modality varies or is not specified in FDA list
Authorized purpose: HistoSonics Planning Tool is a stand-alone visualization and comparison tool for CT and MR studies used to plan histotripsy target localization, treatment volume, acoustic path, and patient position.
Modality
Radiological images; modality varies or is not specified in FDA list
Beijing Infervision Healthcare Medical Technology Co., Ltd.
Authorized purpose: InferCare RECIST is a post-processing application for longitudinal medical-image display, lesion measurement, registration, tracking, segmentation, three-dimensional reconstruction, and RECIST reporting by trained professionals.
Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Tumors and lesions in adult patients age 21 and older
Authorized purpose: MI View&GO is a medical diagnostic application for viewing, manipulating, quantifying, analyzing, and comparing PET, nuclear-medicine, CT, and MR images across one or more time points, including labeled oncology, cardiology, neurology, organ-function, and radiotherapy-planning workflows.
Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Whole body, organs, tumors, heart, brain, and oncology regions
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.