Quick facts
- Retinal diagnostic software reads a fundus image and reports a finding; when it flags diabetic retinopathy it is sold to a screening programme rather than to a single patient.
- United States: it is a named device at 21 CFR 886.1100, titled "Retinal diagnostic software device", placed in Class II, and the openFDA classification API lists the diabetic-retinopathy use under product code PIB.
- Canada: dedicated software is a device in its own right. An active diagnostic device that supplies energy for the purpose of imaging or monitoring a physiological process is Class II under Rule 10(1) of Schedule 1 to the Medical Devices Regulations, SOR/98-282.
- Rule 10(2) lifts that software to Class III if it is intended to diagnose a disease and erroneous readings could result in immediate danger — a hook the United States does not write in the same place.
- The two countries land on Class II for the common screening use and part on how far the class can be raised by the consequence of an error.
- The entry and rule text below were checked against the current CFR and the Regulations on 2026-10-09.
Software that reads a retinal image is the clearest test of how each country handles a device that has no housing and no patient contact. This article sets out what the software is, how each country files it, what the Canadian rules add through the error-consequence hook, and what a screening programme or a clinic should be able to point at when the software is procured.
What is retinal diagnostic software?
The software takes an image of the retina from a fundus camera or an equivalent capture device and applies an algorithm to report a finding — for example whether signs of diabetic retinopathy are present, and whether the case should be referred to an ophthalmologist. It may sit on the camera, on a workstation, or in a network service that returns a report.
The article that decides the classification is the software itself, not the camera. The camera is a separate device with its own entry, while the software that reads the image and reports a finding is a device on its own, and that is the point both countries act on.
How does the United States file retinal diagnostic software?
In the United States the software is a named device. 21 CFR 886.1100 covers a "Retinal diagnostic software device" and places it in Class II. The openFDA classification database lists the diabetic-retinopathy use under product code PIB, with the device name written as "Diabetic Retinopathy Detection Device".
A Class II device of this kind reaches the market under general and special controls rather than under premarket approval. The special controls mean a maker has to show performance testing — sensitivity and specificity against a clinical reference — before the software can be marketed for the intended use, and the software has to carry the labelling and the limitations that testing supports.
How does Canada classify retinal diagnostic software?
Canada treats dedicated software as a device, and it classifies the software by what it does. An active diagnostic device, including dedicated software, that supplies energy for the purpose of imaging or monitoring a physiological process is Class II under Rule 10(1) of Schedule 1 to the Medical Devices Regulations, SOR/98-282.
The hook that raises the class is Rule 10(2): a device described in subrule (1) is classified as Class III if it is intended to be used to monitor, assess or diagnose a disease, a disorder, an abnormal physical state or a pregnancy, and erroneous readings could result in immediate danger. For screening software that only triages the case to a human reader, that hook does not bite and the software stays in Class II; for software that reports a diagnostic result on which treatment is started without a human read, the hook can lift it to Class III and a device licence under section 32 follows.
| Item | Canada | United States |
|---|---|---|
| Named entry | None; classified by rule | 21 CFR 886.1100 |
| Class | Class II by Rule 10(1); Class III by Rule 10(2) | Class II |
| Basis of the class | The rule that fits an active diagnostic device, plus the error-consequence hook | The named entry the software is filed under |
| Product code | Not applicable | PIB |
| Error-consequence hook | Rule 10(2) lifts the class to Class III | Special controls set the evidence bar within Class II |
| Premarket route | Device licence under section 32 for a Class II device | General and special controls |
| Quality system | CAN/CSA-ISO 13485 certificate behind the licence | Quality system regulation |
The two countries agree on Class II for a triage tool and part on the ceiling. A programme that procures screening software against a Canadian purchase order should expect the file to state the rule the software was classified under, because the rule — not the name — is what carries the class and the evidence bar.
Which standards sit behind the software?
The class says how the software is regulated; the standards say how it has to behave. IEC 62304:2006 is the software life-cycle basis behind the design and maintenance of the code. ISO 14971:2019 is the risk-management basis behind the hazard file, and ISO 13485:2016 is the quality-management basis behind the licence.
| Element | What it covers | Why it matters at the programme level |
|---|---|---|
| Intended use | The population and the finding reported | A triage use and a diagnostic use do not carry the same class |
| Performance data | Sensitivity and specificity against a reference | A false negative in screening is the outcome that is measured |
| Software life cycle | Design, change control and maintenance | A model update can change the device without changing the box |
| Image input | The capture device and its constraints | Software validated on one camera is not validated on another |
| Labelling | Limitations and the referral rule | The operator has to know when to overrule the report |
| Traceability | Version and release record | A finding cannot be reconciled to a model version without it |
A deployment that cannot name its software version and the camera it was validated on cannot be reconciled with the licence behind it.
What should a programme check with a procurement?
Screening software bought on a Canadian purchase order and the same software bought in the United States are the same code with two rule paths behind them. The ways to reconcile them are the same on both sides of the border: an intended use, a version record, the performance data and the labelling. A programme that asks for those four fields is asking for the traceability the device rules require, whatever the software is called.
The one place the two markets part is the error-consequence hook. A Canadian programme should expect the file to state the rule the software was classified under, and to say whether an erroneous reading could lift the class, while a programme in the United States should expect the file to read against the special controls. Neither file is wrong; each is answering the question its own market asked.
What else sits beside the screening station?
A retinal screening lane is stocked as a system rather than as a single item. A Snellen and Amsler chart set is used to record the visual acuity the report is read against, and a USB heated eye mask supports the comfort checks that keep a screening list moving. Clinics that also reprocess instruments pair the lane with the sterilization monitoring collection for their own load records. Multi-site groups ordering at case level use the wholesale ordering page, and the B2B wholesale collection lists the lines held for institutional buyers. Reselling? become a distributor.
Sources
- 21 CFR 886.1100, Retinal diagnostic software device
- 21 CFR 886.1600, Home monitoring ophthalmic OCT
- IEC 62304:2006, medical device software life cycle
- ISO 14971:2019, risk management
- ISO 13485:2016, quality management
- Health Canada, medical devices
- Canadian Association of Optometrists
- College of Optometrists of Ontario
- CCOHS, OSH answers
- WHO laboratory biosafety manual
- Electronic Code of Federal Regulations, Title 21
- US FDA, device classification database (cfPCD)
- US FDA, 510(k) premarket notification database (cfPMN)
- US FDA, device registration and listing (cfRL)
- openFDA device classification API
A screening lane is audited on paper as often as it is audited on the image. The printable equipment and follow-up log centre carries a blank sheet with columns for the software version, the camera used, the reading and the date, so a programme can reconcile the report it issued with the record it keeps.
The log sheet generator on the same page sizes the sheet to the number of screening lanes a site runs, so a single-lane clinic and a multi-site programme print the same form at two different volumes.
Every programme and every deployment differs. Ask a compliance specialist and you will get a written answer specific to your equipment and province, with the regulation or standard it is based on cited.
Related reading
- Ophthalmic cameras in Canada vs the US: which class applies
- Visual field screening in Canada vs the US: which perimeter rules apply
- Exophthalmometers in Canada vs the US: which class applies
CliniEco Medical supplies eye care, laboratory and dental consumables of the kind described in this article. MDEL #35334. This article is written for optometry, laboratory and procurement professionals and is not legal advice; the class of a device and the records kept by a practice belong to the manufacturer and to the requirements that apply to it.
Frequently Asked Questions
Is retinal screening software a medical device?
Yes, in both countries. Dedicated software that reads a retinal image and reports a finding is treated as a device; in Canada it is an active diagnostic device classified by rule, and in the United States it is a named device at 21 CFR 886.1100.
What class is retinal diagnostic software in the United States?
It is Class II at 21 CFR 886.1100, with the diabetic-retinopathy use listed under product code PIB. It reaches the market under general and special controls rather than under premarket approval.
Does Canada class retinal software as Class II or Class III?
It depends on the use. Screening software that only triages a case to a human reader is Class II under Rule 10(1). Software intended to diagnose where erroneous readings could result in immediate danger is Class III under Rule 10(2).
Why does the United States not have the same escalating hook?
Because the United States sets the bar through the named entry and its special controls within one class, while Canada writes the error-consequence escalation as a separate rule that can move the software between classes.
What is the difference between the software and the fundus camera?
They are separate devices. The camera is the capture device with its own entry, and the software that reads the image and reports a finding is a device on its own with its own route and its own evidence.
What should a programme keep with the software?
An intended use, a version record, the performance data behind the claim and the labelling, plus the licence number and the quality-management certificate behind it. Those are the fields that let a report be reconciled to a device.
Does the software need a quality-management certificate?
The certificate sits with the manufacturer rather than with the programme. Asking for the CAN/CSA-ISO 13485 certificate and the software life-cycle file is the way a buyer sees that the design and the records behind the software are in place.
0 commentaire