Medical robotics

Scalix future-vision: AI-enabled surgical vision PCCP & ACP checklist for Canadian hospitals

· 10 min read · Scalix, Calgary

Published by Scalix. For questions or corrections, contact us.

Quick answer

This Scalix future-vision brief translates Health Canada SaMD interpretation and international PCCP guidance into practical RFP language for AI-enabled intraoperative computer vision. It lists SaMD classification cues, PCCP/ACP elements buyers should request, expected imaging outputs and PACS/VNA integration patterns (DICOM SR, secondary capture, DICOMweb), minimal premarket validation and postmarket monitoring evidence, privacy/data-residency considerations for Canadian contexts, and a one-page procurement checklist with a short ACP seed vendors must fill. Use this brief to prepare RFP evidence requests or to book a Scalix free audit to map your hospital’s PACS/VNA/OR-video topology and vendor evidence package. Limitations and dated assumptions are explicit (snapshot: 2026-11-15).

Executive summary (future-vision)

Scalix translates Health Canada SaMD signals and international PCCP guidance into concise RFP evidence asks so Canadian hospitals can require vendor-ready PCCP/SPS and a practical Algorithm Change Protocol (ACP) seed before procurement. This brief (snapshot 2026-11-15) offers a one-page procurement checklist, an ACP seed vendors must fill, and integration asks for DICOM/PACS/VNA and OR-video pipelines.

This is a future-vision exploration, not a regulatory ruling. Buyers must verify licence numbers and regulator expectations at the time of RFP drafting and treat the ACP seed as a negotiable contract appendix.

  • Regulatory signal: software that acquires, processes or analyzes medical images often meets SaMD criteria — request declared SaMD classification and licence evidence.
  • PCCP/ACP ask: request SaMD Pre-Specifications (SPS) and an auditable, versioned ACP that defines permitted changes, metrics, monitoring and rollback triggers.
  • Integration ask: require explicit DICOM/DICOMweb outputs, event timestamps, and a PACS/VNA conformance test plan with a dry‑run using de‑identified cases.

Quick regulatory read: SaMD classification cues for surgical vision

Health Canada regards software with medical intent — e.g., analysis, measurement or guidance from imaging — as SaMD when the intended use impacts clinical decisions. For intraoperative vision, language that states or implies decision support, guidance or automated annotations increases SaMD likelihood.

Procurement should require vendors to declare the exact intended-use statement submitted to regulators, their Health Canada device licence number (if available), and whether SaMD Pre-Specifications (SPS) or PCCP-style documents were part of the submission.

  • Ask vendors to supply the exact intended-use language and the Health Canada device licence number for the marketed configuration.
  • Request a concise mapping table of software features (e.g., tool tracking, tissue classification, annotation overlays) to claimed clinical risk (inform/assist/automate).
  • Do not assume classification is fixed across jurisdictions; require evidence for the specific marketed device build and region.

PCCP / ACP: expected elements to request from vendors

International practice (FDA, Health Canada and MHRA signals) frames PCCP/ACP content as focused, risk‑based and lifecycle‑oriented. Buyers should require an ACP that is machine‑versioned, auditable, and linked to production monitoring and rollback criteria.

Use PCCP principles to shape contract language: define permitted change types, evidence needed per change type, monitoring cadence, notification timing and emergency rollback processes.

  • SPS scope: list features covered, dataset provenance limits and intended‑use boundaries for changes (e.g., parameter tuning vs. training-data expansion).
  • ACP required fields: change description, acceptance criteria, validation dataset provenance, test protocol, pass/fail thresholds, monitoring signals, notification and approval workflow.
  • Performance & safety metrics to require: AUROC/ROC, task sensitivity/specificity, calibration checks, distribution‑shift detection and logged false‑positive/false‑negative counts.
  • Operational controls: immutable model-version tags, input/output hashing, provenance logs and a documented emergency rollback procedure with maximum remediation windows.

Interoperability and imaging pipeline expectations (DICOM, PACS, VNA, OR video)

Hospitals will expect surgical‑vision outputs to integrate with enterprise imaging: DICOM SR or Secondary Capture for frame annotations, time‑stamped events for surgical logs, and DICOMweb/WADO or secure streaming for OR video transfer. Specify exact output formats and require a conformance test plan.

Procurement should ask for a sample integration diagram (vendor → PACS/VNA/OR video) and a dry‑run conformance test using representative de‑identified cases mapped to local AE Titles, ports and firewall rules.

  • Require explicit output formats: DICOM Structured Report for structured findings; DICOM Secondary Capture or encapsulated video for annotated frames; DICOMweb/WADO for retrieval.
  • Ask for event timestamps and a mapping table so results correlate to OR video and perioperative records.
  • Request a PACS/VNA conformance test plan, sample integration diagram showing firewalls and AE Titles, and a defined dry‑run schedule.
  • Include acceptance tests for retrieval (WADO/DICOMweb) and for inserting SR/SC objects into the VNA with expected metadata.

Privacy, cybersecurity and minimal procurement evidence pack

Buyers should require statements on data residency, de‑identification steps for training data, consent models for OR video capture, and a privacy‑impact assessment aligned to PIPEDA and applicable provincial laws (e.g., PHIPA in Ontario). If vendor adaptation uses Canadian patient images, require contractual limits on transfer and clear consent trails.

Cybersecurity evidence should include network diagrams, DICOM transport security (TLS/DICOMweb), identity/authentication integration, logging/auditing of model usage, and a vulnerability/patching policy with timelines.

  • Privacy asks: storage location, de‑id method, consent model for intraoperative capture, and a vendor PIA summary or equivalent.
  • Cybersecurity asks: network architecture diagram, DICOMweb/TLS config, RBAC/identity integration (LDAP/SAML) and centralized logging with retention windows.
  • Minimal evidence pack for RFP: Health Canada licence numbers, clinical‑validation summary, validation dataset descriptions, ACP/PCCP summary, PACS/VNA conformance plan and security attestations.

Procurement checklist, ACP seed (fillable fields) and a short hypothetical example

Below is a concise procurement checklist and a short ACP seed buyers can paste into an RFP or request during a Scalix free audit. A brief hypothetical example illustrates how a vendor might populate the ACP seed (illustrative only). Scalix can run a free audit to map your PACS/VNA/OR‑video topology, validate integration tests, and produce an RFP‑ready evidence bundle.

Treat the ACP seed as a negotiable appendix and require that vendor responses be machine‑readable (JSON or versioned PDF) and traceable to production logs.

  • One‑page procurement checklist (fields to request): Health Canada device licence number and declared SaMD class; exact intended‑use statement and labelled functions; SPS / PCCP summary and full ACP; clinical evidence summary (study types, populations, datasets, key metrics).
  • ACP seed (3–5 required sections vendors must fill): 1) Change type & scope (e.g., model retrain, parameter update, dataset expansion), 2) Acceptance criteria & test datasets (dataset provenance, performance metrics, pass/fail thresholds), 3) Monitoring & alerts (production metrics, thresholds.
  • Hypothetical example (illustrative only): Vendor X supplies licence HC‑XXXX, declares SaMD class II for decision‑support overlays. Planned weekly calibration updates non‑decision overlays only. Acceptance: AUROC drop <0.03 on withheld set; drift alert if sensitivity falls >5% over 24h.

Common questions

What elements should an RFP require to demonstrate a Health Canada–aligned PCCP and ACP for intraoperative computer vision?
Require the vendor’s Health Canada device licence number, declared SaMD class, a SaMD Pre‑Specification (SPS) summary, the full ACP/PCCP document with change categories, acceptance tests, monitoring signals, rollback triggers and audit logs mapping model versions to retraining events.
How should surgical‑vision outputs be delivered and archived to integrate with PACS and VNA?
Specify exact output formats: DICOM Structured Report for structured findings; DICOM Secondary Capture or encapsulated video for annotated frames; DICOMweb/WADO endpoints for retrieval; and event timestamps. Request a PACS/VNA conformance test plan and an integration diagram.
What minimal premarket and postmarket evidence should procurement ask for?
Ask for a clinical‑validation summary (study types, populations, key metrics such as AUROC and sensitivity/specificity by task), validation dataset provenance, postmarket monitoring metrics and reporting cadence, and a named safety contact for incidents.
What privacy and data‑residency asks should buyers include if vendor adapts models with Canadian patient images?
Require explicit statements on data residency, consent obtained for OR capture or training use, de‑identification steps, and a privacy‑impact assessment aligned to PIPEDA and applicable provincial laws. Confirm contractual limits on onward transfer and secondary use.

Find your biggest time-saver

Book a free AI audit, or call our 24-hour line at (825) 782-4956.

More articles

Start a call24-hour line