RetinaLyze API: A new face of the RetinaLyze algorithm
The RetinaLyze API
We are excited to present a fantastic new product in the RetinaLyze portfolio. We have been working on it for quite some time, and are looking forward to the new possibilities the product creates. The product enables a third-party to make a built-in feature in an already existing system such as a Patient Administration System, Optician Software or other software, where the
service could be added.
The new product is called RetinaLyze API, but has the flexibility to be white labeled to any vendor and enables the vendor to customize their own software entirely. The product delivers a simple analysis to the end-user without other information than the result. The vendor can customize the look and feel of their own software and embed the screening functionality and result from the RetinaLyze API.
What is an API?
In computer programming, an application programming interface (API) is a set of subroutine definitions, protocols, and tools for building application software. In general terms, it is a set of clearly defined methods of communication between various software components. A good API makes it easier to develop a computer program by providing all the building blocks, which are then put together by the programmer.
The RetinaLyze API is basically a standardized way for other programs or devices to communicate directly with the RetinaLyze algorithm. The RetinaLyze API makes it possible for a third-party to create eye-screening software or add automated screening of retinal images as added functionality in their existing/new software or device.
So how does this differ from the RetinaLyze Web application? While utilizing the same algorithm, the RetinaLyze API is not directly accessible through a browser and cannot function on its own. It needs a third-party software to send it pictures for analysis and to receive and show the results. The communication (sending of images and receiving results) happens over the internet (and not on local hardware such as a PC or device).
Since the RetinaLyze API utilizes the same algorithm as the RetinaLyze Web application, the documentation and certifications already in existence can also be used for this service.
Target group and intended uses
The main target groups are third parties interested in providing automated retinal screenings to their clients. This will most likely happen on a white label basis (meaning the RetinaLyze brand is never mentioned in the customers software). This main target group could consist of:
- Manufacturers of EHR/EMR systems for hospitals and clinics
- Manufacturers of EMR/Booking systems for opticians/optometrists
- Manufacturers of PACS systems for hospital chains/regions
- Manufacturers/Providers of telemedicine software/services aiming to provide the automated screening to their graders or their customers directly
- Manufacturers of other automated screening software wanting to add extra functionality quickly
- Manufacturers of retinal cameras wanting to add functionality to their camera software
Please do remember that the target group does not exclude larger hospitals and chains of clinics aiming to add this functionality in their existing self-developed software.
What are the main benefits of using the RetinaLyze API?
- Fast, easy and cheap automated DR and AMD screenings
- Automatic image quality assessment
- Integration in your software to enable white label automated DR/AMD screenings, such as:
- Fundus camera software suites (or directly in the camera firmware)
- Electronic Patient Journals
- Fundus Image Database software
- Your own screening software for eye exams or diabetes patients
- RetinaLyze can also be used as an image and result database for your fundus images, if you do not wish to store them on your servers (optional feature).
Support and Contact
We want it to be as easy as possible to reach us when needed. You can reach us on our main phone number +45 71 990 321. Press 1 for Sales and 2 for Support.
You can also reach us on mail: email@example.com.
If you wish to read the documentation, we’ve made a documentation page in a readable format and a json format, just for you.