Fig. 4 — retinal-oct-privacy
Retinal OCT Privacy Utility
This utility supported safer research use of retinal OCT exports by identifying and removing specified patient-identifying fields before any downstream handling. It was a working implementation in a research environment, it aligned the export workflow with practical privacy needs in a regulated setting, and it reduced manual de-identification effort before research use.
Facts
Role: Working implementation in research environment
Type: Privacy / data handling utility
Stack: Health-data workflow logic, export review, de-identification support
No public link
What I built
- Built a utility to identify and remove patient-identifying fields from retinal OCT exports.
- Focused on reducing manual de-identification effort before research use.
- Aligned the workflow with practical privacy needs in a regulated environment.
- Supported cleaner downstream handling of imaging data.
Why it mattered
- Reduced manual privacy-review work.
- Lowered the risk of avoidable identifying data passing downstream.
- Improved consistency in export handling.
- Supported research workflow efficiency without bypassing privacy needs.
Relevant skills
- Privacy-aware workflow design
- Health data handling
- Operations support
- Compliance-minded process improvement
- Clinical research systems