Why do some of our OCT scans not show up in FORUM or the EHR?▼
Usually because the transfer failed and the image saved locally on the device workstation. Causes include network interruptions, a full archive, patient demographic mismatches or a stalled interface service. These failures are often silent, so images sit on the device until someone notices a gap. We monitor transfers, alert on studies that don't arrive and fix the underlying causes on the network and server side. Interface or matching issues inside the vendor software get escalated to the vendor with clear evidence.
Can you work on our diagnostic devices?▼
We work on the IT around them: acquisition workstations, network connections, accounts, backups and security. The instruments themselves, including firmware, calibration and proprietary software, belong with the manufacturer or its authorized service provider. We coordinate with those vendors, plan network changes with them and document their support requirements. That approach keeps your service agreements valid and avoids untested changes on equipment you depend on for diagnosis. If a device problem looks network-related, we prove it either way before calling the vendor.
How should we protect biometry data sent to the surgery center?▼
Make sure it travels over an encrypted, reliable path and arrives unchanged. Depending on your setup, biometry may move through an interface, an image management system, a shared portal or exported files. We review how it moves today, secure that path, protect the accounts involved with MFA and help confirm data integrity on arrival. Clinical verification of lens calculations remains with your surgeons and staff, but the technology shouldn't introduce any doubt about the numbers they're reviewing.
Do you support Nextech and ModMed EMA for ophthalmology?▼
We support the infrastructure they depend on: workstations, tablets, network, printers, device interfaces and security. Nextech and ModMed handle their own application issues, including templates, billing rules and integrations on their side. When something breaks, we determine whether it's the device, the network, the interface or the software, fix what's ours and open a clear ticket with the vendor for what isn't. We also verify imaging integration after updates on either side.
How much storage does an ophthalmology image archive need?▼
It depends on your devices, patient volume and how long you keep images, so we measure rather than guess. We look at current archive size, growth over recent months and planned additions like new OCT units or widefield imaging. Then we plan storage and backup capacity ahead of need, so you're not scrambling when the server fills. We also check that backup windows still fit as the archive grows, since a backup that can't finish overnight isn't really protecting you.
We also do refractive surgery. What changes for IT?▼
Somewhat. Refractive practices often add cash-pay financing, marketing and patient consultation tools, and they take card payments for procedures. That brings PCI DSS considerations, more marketing platforms with access to patient inquiries, and laser equipment with its own vendor support. We isolate payment devices, secure consultation and marketing accounts and coordinate with laser manufacturers on network and remote-access requirements, while leaving the equipment itself to them. Consultation calendars and financing portals get the same MFA as the rest of the practice.