Start with the exact FDA record
Each directory entry represents one FDA submission. A commercial product may have several submissions, versions, or licensed modules. A mapped product family helps navigation; it does not transfer evidence or establish that an older version has been replaced.
Regulatory status describes the recorded decision. It does not establish local compatibility, current commercial availability, a purchase recommendation, or performance in your department. Read the FDA information.
Keep the source and scope visible
- FDA-supported facts
- Facts linked to the exact submission's public decision materials.
- Vendor statements
- Supplier claims shown with their scope. A vendor-wide statement is not an exact-product attestation or local acceptance test.
- Study-reported findings
- Evidence tied to the endpoint, population, and tested version. Unlinked research leads remain outside the product evidence display.
- Buyer assumptions and calculations
- Facility inputs and modeled results remain separate from reported evidence. The private scenario model covers one interpretation workflow. Net return and ROI require complete costs and benefit inputs; capacity-only cases establish no cash benefit or ROI. Modeled ROI is not a verified product outcome.
Read review labels literally
Field-derived summaries assemble sourced facts. FDA-bounded overviews restate FDA-supported information. Source-reviewed content can be reviewed by an agent and is not necessarily clinician-reviewed. Clinician-reviewed labels require a recorded human reviewer. Supporting-fact changes can put an overview back into review.
Body-region mappings remain an automated draft. Reviewed workflow tags cover a small pilot, identify documented roles, and do not establish local workflow fit. Entries without a reviewed role remain explicitly unreviewed.
Evaluation guides and family navigation
The evaluation pilot reuses current source-reviewed summaries and adds exact-record scope conditions and questions. Its eight examples are an editorial starting point; a live traffic baseline and new buyer sessions have not informed selection. Agent source review is not clinician review, a purchase recommendation or local acceptance.
Guide conditions are withheld when supporting facts, summary wording, family context or referenced source URLs change. Family maps are partial and explicitly sourced. Each submission retains its own evidence, pricing and compatibility boundaries; a mapped FDA decision does not establish an installed or commercially available release.
The buyer learning guides provide original evaluation questions with dated FDA and interoperability source context. Their review binds the wording, source metadata and reviewer identity; changes require review before a build can publish them. Exact-record example links require the current pilot review. A guide's source date does not refresh all linked records.
System compatibility and local acceptance
Compatibility reviews distinguish documented support, conditional support, documented incompatibility and not reviewed. Documented support requires current technical evidence for the exact AI and system version scopes. Product-family statements and marketplace listings cannot qualify a confirmed pairing.
The pilot prioritizes Merge PACS, Visage 7, Sectra IDS7, AGFA Enterprise Imaging and Intelerad IntelePACS. Site builds are unspecified; the reviewed public sources do not establish fully versioned supported pairs for them. Current vendor context stays labeled by its broader scope. Broad DICOM support does not establish a named viewer build's compatibility.
Every relationship retains its configuration, geography, source-review date and local test. Changed supporting facts, versions, system definitions or source metadata can withhold a prior conclusion. The local checklist asks for routing, output, latency, security, ownership, training and rollback evidence; checking a box does not create an acceptance receipt.
Unknown is useful information
Not yet reviewed, not publicly available, awaiting confirmation, not applicable, withdrawn, and conflicting information have different meanings. Open the review details to see what was checked. An unknown price is not zero; an unknown integration is not confirmed support.
Compare prices in their proper context
Public procurement prices require a resolved source, date, currency, unit, geography, and applicable product or offer scope. Patient charges, reimbursement, foreign observations, different versions, and economic models remain pricing context. They are not interchangeable quotes.
Time saved is capacity, not automatically cash savings. A purchase evaluation must establish costs, demand, bottlenecks, and a way to realize a financial benefit without counting the same benefit twice.
Dates describe different checks
The dataset date identifies the FDA snapshot. Field and source dates identify later reviews. Neither a new site build nor the latest FDA decision establishes a current installed release or commercial offer.
Dataset and review dates shows the inherited snapshot date and recorded file identities. A file-identity check detects changed bytes; it does not independently reverify the FDA corpus. A refresh requires an explicit snapshot date and review of affected claims.
Funding and corrections
The directory offers disclosed sponsorship. Payment can change labeled placement and buyer links, but does not change the source standard or purchase factual verification. Sponsored placement must be distinguishable from the directory's ordinary results. Read the sponsorship terms.
Anyone can submit a source-backed correction. Include the FDA submission and exact version. Publisher and contact information.