Frequently asked questions

Retinar is a teleophthalmology platform that uses artificial intelligence to support retinal disease screening, such as diabetic retinopathy and glaucoma, enabling decentralized capture and referral of at-risk cases.

Both. Retinar is designed for public providers, primary care networks, and private organizations, with capture workflows operated by technicians and reading by professionals.

Retinar adds capture quality control, automatic pre-diagnosis, prioritization of referable cases, traceability, and a secure professional review workflow.

It is a case identified by the system as potentially at risk and therefore referred for professional confirmation, reducing the burden of mass reading.

No. At-risk cases are referred to ophthalmologists who confirm or rule out findings and recommend treatment.

The main use case is diabetic retinopathy, but Retinar also supports opportunistic detection of other conditions such as glaucoma.

Yes. It uses distributed telemedicine, with local capture, remote reading, and AI support to expand access.

It was born in Argentina and is designed to scale across LATAM with multi-institution, multi-device, and campaign-based operation.

It is a diabetes complication that can progress without symptoms and cause vision loss. That is why regular checkups and early detection strategies are recommended.

In general, guidelines recommend a comprehensive eye exam at diagnosis of type 2 diabetes, at 5 years for type 1 diabetes, and then periodic follow-up, usually yearly or according to clinical judgment.

No. It is a screening strategy based on fundus imaging with remote reading and AI to improve access. With findings, symptoms, or higher risk, a full professional evaluation is required.

Retinar supports detection of signs compatible with glaucoma and opportunistic screening of additional conditions.

Symptoms require in-person or specialist clinical evaluation. Retinar is designed for screening and prioritization, not to replace care in symptomatic cases.

Retinar supports detection of multiple conditions. Exact scope depends on active modules and the intended use agreed with each institution.

It depends on the program and intended use. In general, diabetes screening focuses on adults and protocols should be defined for each scenario.

Decentralized capture, assisted quality control, instant pre-diagnosis, referral of referable cases, professional reporting, and patient notifications.

Retinar is designed for trained technicians to capture images in decentralized settings.

With short training and clear protocols, staff can capture and obtain instant pre-diagnosis with AI support.

Yes. Retinar indicates image quality in real time and suggests improvements to avoid patient revisits.

The institution can configure email notifications about study progress and result.

Registered professionals can confirm diagnosis and report. There is also support to improve reporting with lesion and sign detection.

Yes. Retinar is designed for population screening campaigns focused on at-risk groups with controlled operating costs.

Automated screening helps professionals focus on at-risk cases, reducing reading burden for normal studies.

No. A core advantage is capture without an on-site specialist, followed by remote reading.

Not necessarily. Retinar works with widely used mydriatic and non-mydriatic cameras, integrating into existing workflows.

It is designed to work with common market models. Exact compatibility is validated based on device and image export mode.

It depends on the camera, clinical protocol, and capture quality. Retinar supports both mydriatic and non-mydriatic cameras.

Yes. The approach is designed for trained staff capture outside specialized centers.

Stable connectivity is recommended to upload images and use the web platform. In low-connectivity areas, an adapted workflow can be defined.

It depends on camera and integration path. Compatible export format is confirmed during technical assessment.

Yes. The design is intended to scale screening networks with node traceability and remote reading.

It is a web platform and is typically accessed via browser, without heavy workstation installation.

Yes. Retinar supports API integration and interoperable flows according to each institution's system.

Retinar works on interoperability in the public ecosystem. If your jurisdiction uses HSI, integration is assessed according to local technical context.

Typically study status, metadata, screening result, and, when applicable, professional report.

It is a common requirement. It is defined according to each customer's reporting and document-archive workflow.

Yes, access and report version traceability can be configured as part of institutional setup.

Retinar reports performance comparable to experienced professionals for screening, reinforced by professional review of at-risk cases.

Yes. The system can support reading by highlighting signs and lesions to assist clinical reporting.

With AI-assisted capture that detects issues instantly and recommends recapture before closing the study.

Retinar has been presented in Buenos Aires Province in initiatives for retinopathy follow-up with territorial implementation.

International guidelines recognize that retinal imaging with remote reading and validated AI algorithms can improve coverage and access for diabetic retinopathy screening.

The workflow prioritizes risk-based referral and professional confirmation, maintaining clinical oversight.

Continuous performance monitoring by use context is recommended, with follow-up plan adjustments in each implementation.

Access, retention, and security policies are defined together with the institution, including confidentiality and data protection agreements.

In Argentina, implementation is structured so the institution can comply with current regulations on roles, consent, safeguards, access, and retention.

It depends on project and customer requirements. Managed infrastructure and own infrastructure can both be evaluated.

Access is configured by capture, reading, and coordination roles, aligned with clinical workflow.

Yes. A workflow with pseudonyms or IDs can be designed for campaigns and research, according to use case.

This is recommended practice in clinical environments and can be included as a project security requirement.

It depends on camera, connectivity, training, and referral workflow. It is usually implemented in pilot, stabilization, and scale stages.

Yes. Pilot scope, objectives, volume, and exit criteria are jointly defined with the institution.

Technical assessment, clinical workflow definition, training, end-to-end testing, and initial follow-up.

Yes. Operations rely on trained technicians and registered professionals within the workflow.

Support is contract-defined, including channels, schedules, severity levels, and clinical/technical escalation.

Yes. It is designed for mass campaigns and decentralized nodes with centralized follow-up.

Contingency is designed according to operational context, for example local capture and deferred upload when applicable.

In Retinar workflow, at-risk cases are reported by professionals who confirm or rule out findings and recommend care.

It depends on reader availability and volume. Risk prioritization helps reduce response times.

That is one key goal of screening, to refer mostly at-risk cases and optimize specialist scheduling.

It is co-designed with the institution by defining destination, priority, contact, scheduling, and information return to origin node.

Yes. This is part of the teleophthalmology model for remote reading of prioritized cases.

Yes. It adapts to population strategies and primary care networks with centralized reading.

Yes. It was presented in Buenos Aires Province and linked to retinopathy follow-up initiatives in Tandil.

It depends on each jurisdiction. It can be implemented through tender, agreement, or service contracting according to local framework.

Yes. This is the recommended approach to ensure operational quality, adoption, and traceability while scaling.

Yes. It enables technician capture and concentrates specialist time on higher-risk cases.

Yes. It enables scalable, traceable screening for diabetic populations, improving access and continuity of care.

Yes. Reports, indicators, and clinical evidence can be configured for audit and management.

Not necessarily. It can complement existing scheduling systems, prioritizing risk-based referrals.

Modalities are offered according to volume and B2G/B2B scenario. The most common are node-based subscriptions or study packages.

It depends on the project. Integration, training, and configuration may be included as initial setup.

Usually yes, for multisite deployments or high study volumes.

Duration, study count, support, and evaluation criteria are agreed with each institution.

Retinar presents itself from Tandil, with institutional roots in Argentina's health innovation ecosystem.

Through the website contact section, where institutional communication channels are listed.

Yes. It has been presented in provincial initiatives related to diabetic retinopathy control.

Yes. Technical, regulatory, and operational requirements are assessed to design a local deployment plan.

Institution type, number of sites, available fundus camera, estimated volume, and referral workflow.

ANMAT incorporated the MERCOSUR Technical Regulation through Provision 64/2025, updating the framework for medical device registration in Argentina.

A central standard is IEC 62304 for medical software lifecycle processes, along with other standards depending on risk and scope.

Yes. An evidence package on safety, traceability, and validations can be agreed based on customer type and project scope.

It is a picture of the back of the eye. It is usually a quick and non-invasive study, though experience may vary by device and protocol.

Because diabetic retinopathy can progress without early symptoms. Periodic screening helps detect risk early.

Yes. With teleophthalmology and fundus imaging, access can be expanded beyond specialized centers through local capture and remote reading.

In Retinar workflow, the institution can notify progress and study results by email.

The case is referred to a professional for diagnostic confirmation and to define treatment or follow-up.