Introduction: Your Monofocal SOP Is Two Pages. Your EDOF SOP Needs Five. Here’s Why.
A well-written monofocal IOL measurement SOP fits on two pages. Load the lens tray. Start the measurement. Record power, cylinder, and axis. Compare to specification. Disposition: pass or fail. The procedure is linear, the decision is binary, and an operator can be trained in one shift.
An EDOF measurement SOP needs five pages-not because the measurement itself is five times longer, but because the procedure includes steps that monofocal SOPs have no equivalent for.
The first difference is verification. Before measuring EDOF production lenses, the operator must verify that the measurement system is correctly configured to capture through-focus data-not just power and cylinder. A system configured for monofocal mode will measure the EDOF lens and return a valid power reading. The power will pass. The through-focus performance will not be evaluated at all. The lens ships without its defining quality characteristic being verified. This is not a hypothetical risk-it is the most common SOP failure mode when facilities transition from monofocal to EDOF production.
The second difference is interpretation. A monofocal pass/fail decision requires no interpretation: the number is above or below the threshold. An EDOF pass/fail decision requires the operator to confirm that the through-focus output is consistent with the design reference-that the plateau is present, centered, and within the expected shape. This is not subjective judgment. It is pattern recognition against a defined reference, but it is a step that must be documented in the SOP and trained.
The third difference is conditional disposition. A monofocal lens either passes or fails. An EDOF lens can pass power and fail plateau, or pass plateau width and fail minimum MTF within the range. Each combination has a different disposition pathway. The SOP must define these pathways explicitly.
This article provides the SOP structure for EDOF measurement, the specific steps that differ from monofocal, and the decision logic that the operator follows. The templates are designed to be adapted to your specific products, instruments, and quality system.
SOP Architecture: The Three Documents
EDOF measurement is not covered by a single SOP. It is covered by a document set of three SOPs, each serving a different purpose and a different frequency of execution.
SOP-1: System Verification (daily, per shift, or per product changeover)
This SOP governs the verification that the measurement system is correctly configured and performing within specification before production measurement begins. It is executed at the start of each shift, after any system maintenance, and after any product changeover.
Monofocal equivalent: the daily gauge verification with a reference lens. EDOF addition: verification that the system is computing through-focus data, that the through-focus output from the reference lens matches the expected profile, and that the acceptance criteria are loaded for the correct EDOF product code.
SOP-2: Production Measurement – Batch Inspection (every production batch)
This SOP governs the measurement of production lenses for pass/fail disposition. It covers lens loading, measurement execution, result recording, and disposition. For facilities using the IOLA MP for 100% batch inspection, this SOP is executed for every batch of every EDOF product.
Monofocal equivalent: the standard production measurement SOP. EDOF additions: through-focus parameter recording, conditional disposition logic, and the escalation pathway when through-focus results are anomalous.
SOP-3: Through-Focus Verification – Sampled Detailed Analysis (per batch or per sampling plan)
This SOP governs the detailed wavefront and through-focus analysis performed on sampled lenses using the IOLA MFD. It covers wavefront capture, Zernike decomposition review, multi-aperture verification, and the data package that feeds the SPC system.
Monofocal equivalent: none. This SOP has no monofocal counterpart because monofocal IOLs do not require through-focus wavefront analysis.
SOP-1: System Verification Procedure
This is the gatekeeper SOP. If it is not executed correctly, every subsequent measurement is suspect.
Table 1: SOP-1 – EDOF System Verification Procedure
| Step | Action | Acceptance Criterion | If Fails | Record |
| 1 | Power on the measurement system. Allow warm-up period per instrument specification (typically 15–30 minutes). | System status indicator shows “Ready.” No error messages. | Do not proceed. Contact maintenance. | Time powered on. Warm-up completion time. |
| 2 | Verify product code selection. Confirm the loaded product code matches the EDOF product to be measured. Verify the product code includes through-focus parameters in the acceptance criteria. | Product code displayed matches batch documentation. Through-focus parameters (plateau width, min MTF) visible in the acceptance criteria screen. | Select correct product code. If through-focus parameters are missing, the product code may be configured for monofocal mode – escalate to process engineer. | Product code confirmed. Screenshot or log entry. |
| 3 | Measure EDOF reference lens (known certified standard). The reference lens must be an EDOF lens with known through-focus characteristics – not a monofocal reference. | Power: within ±0.04D of certified value. Through-focus plateau width: within ±0.15D of certified value. SA coefficients: within ±10% of certified values. | Remeasure. If fails twice: clean reference lens and optical surfaces, remeasure. If fails three times: do not proceed. Initiate calibration verification. | Reference lens ID. Measured power. Measured plateau width. Date/time. Operator ID. |
| 4 | Verify measurement environment. Temperature within 18–28°C. Humidity within operating specification. For wet measurement: liquid medium temperature within specification. | Environmental readings within documented limits. | Adjust environment. Wait for stabilization. Re-verify. | Temperature. Humidity. Wet medium temperature (if applicable). |
| 5 | Record verification completion. Sign and date. Authorize production measurement. | All Steps 1–4 passed. | Any step failed: production measurement may not begin until all steps pass. | Verification log: date, time, operator, all recorded values, authorization signature. |
Critical note for Step 3: The reference lens must be an EDOF reference, not a monofocal reference. A monofocal reference lens verifies power accuracy but does not verify that the system is computing through-focus data correctly. If the system is misconfigured (monofocal mode), a monofocal reference will pass verification while the through-focus computation is inactive. Only an EDOF reference lens with known through-focus characteristics can verify the complete measurement chain.
SOP-2: Production Measurement – Batch Inspection
This is the high-volume SOP executed for every batch. It must be efficient enough for production speed while comprehensive enough to catch EDOF-specific failures.
Measurement execution
Step 1: Confirm system verification (SOP-1) has been completed and is current for this shift and product code.
Step 2: Load the lens tray into the measurement system. For the IOLA MP: up to 50 dry lenses or 12 wet lenses per cycle. For wet measurement of hydrophilic materials: confirm hydration equilibrium has been reached per the material specification (typically 24–48 hours in storage solution). Do not measure partially hydrated lenses.
Step 3: Initiate the batch measurement cycle. The system measures each lens automatically. Do not interrupt the cycle unless an error message appears.
Step 4: Review batch results on the summary screen. The summary displays pass/fail status for each lens, grouped by failure mode.
Disposition logic – the EDOF-specific decision tree
This is where the EDOF SOP diverges most significantly from monofocal. A monofocal disposition is a single pass/fail. An EDOF disposition has four possible outcomes.
Outcome A – Full pass: Power, cylinder, and all through-focus parameters (plateau width, minimum MTF, plateau center position) meet acceptance criteria. Lens advances to next production stage.
Outcome B – Power pass, through-focus fail: The lens meets standard power and cylinder specifications but fails one or more through-focus criteria. This is the EDOF-specific failure mode. The lens would pass monofocal QC but does not deliver the extended range of vision. Disposition: reject from EDOF product line. The process engineer is notified for investigation.
Outcome B is the reason the EDOF SOP exists. Without through-focus verification, every Outcome B lens ships as a “passing” lens. The patient receives a premium EDOF IOL that performs as a monofocal. The surgeon complains. The sales team investigates. The quality system has no record of the failure because the failure parameter was never measured.
Outcome C – Power fail, through-focus pass: The lens fails the standard power specification but delivers acceptable through-focus performance. This is rare but possible when the power error is a systematic bias that shifts the entire through-focus curve without changing its shape. Disposition: reject. Power is a regulatory requirement independent of through-focus performance.
Outcome D – Both fail: The lens fails both standard and through-focus parameters. Disposition: reject. Escalate to process engineer as a potential process upset.
Recording and escalation
Step 5: Record the batch disposition: total lenses measured, total passed, total failed by each outcome category (B, C, D). The through-focus failure category (Outcome B) must be tracked separately from power failures because they indicate different manufacturing issues.
Step 6: If the batch failure rate exceeds the threshold defined in the acceptance criteria (e.g., >3% Outcome B failures in a single batch), escalate to the process engineer. Hold subsequent batches until the root cause is identified.
SOP-3: Through-Focus Verification – Sampled Detailed Analysis
This SOP applies to the sampled lenses measured on the IOLA MFD for detailed wavefront and through-focus analysis. The purpose is not pass/fail disposition (that is SOP-2) but process monitoring and diagnostic data collection.
Sample selection
Select the specified number of lenses per batch per the sampling plan (typically 3–5 lenses per batch for routine monitoring; 100% during process qualification). Select from the center, edges, and middle of the production batch to capture any position-dependent variation.
Measurement execution
Step 1: Load the lens on the IOLA MFD. The system captures the complete wavefront in 9 seconds.
Step 2: Verify the measurement output includes: through-focus MTF at 3mm and 4.5mm aperture, Zernike coefficients (Z₄⁰ through Z₁₀⁰ + parasitic terms), full-aperture power map, and through-frequency MTF at best focus.
Step 3: Compare the measured through-focus profile to the design reference overlay. The design reference is the through-focus curve of a known-good EDOF lens of the same product code. The measured curve should fall within the acceptance band around the reference. If the measured curve deviates from the reference shape (not just magnitude-shape), flag for engineering review.
Step 4: Record the Zernike coefficients for SPC data feed. The Z₄⁰, Z₆⁰, Z₄⁰/Z₆⁰ ratio, and total parasitic RMS values from each measured lens feed the Tier 2 diagnostic control charts.
Step 5: Export the measurement data package. The complete wavefront data, through-focus profiles, and Zernike decomposition are archived for traceability. For lenses that are later the subject of field complaints, this archive provides the optical fingerprint of the lens at the time of measurement.
The Steps Your Monofocal SOP Doesn’t Have – and Why They Matter
Seven specific steps in the EDOF SOP set have no equivalent in monofocal measurement SOPs. Each exists because EDOF measurement has a failure mode that monofocal measurement does not.
Table 2: EDOF-Specific SOP Steps – What Monofocal SOPs Don’t Cover
| EDOF-Specific Step | Which SOP | Failure Mode Prevented | What Happens If Omitted |
| EDOF reference lens verification (not monofocal reference) | SOP-1, Step 3 | System configured for monofocal mode; through-focus computation inactive | All EDOF lenses measured for power only. Through-focus never evaluated. Every Outcome B failure ships as “pass.” |
| Product code verification includes through-focus parameters | SOP-1, Step 2 | Acceptance criteria loaded for monofocal; EDOF criteria not evaluated | System measures EDOF lens against monofocal spec. Power passes. Plateau performance unknown. |
| Hydration equilibrium confirmation for hydrophilic EDOF | SOP-2, Step 2 | Partially hydrated lens measured; SA coefficients do not represent in-eye performance | Through-focus data is invalid. Lens may pass or fail based on a transitional state that has no clinical relevance. |
| Four-outcome disposition logic (not binary pass/fail) | SOP-2, Disposition | Outcome B lenses (power pass, plateau fail) not identified as failures | Premium EDOF lenses ship with monofocal performance. Surgeon dissatisfaction. Complaint investigation finds no QC record of the plateau failure. |
| Separate tracking of through-focus failures (Outcome B) from power failures | SOP-2, Step 5 | Through-focus failure rate invisible in QC data; no trend detection for EDOF-specific process drift | Through-focus failures lumped with power failures or not recorded at all. Process drift that degrades EDOF performance goes undetected. |
| Design reference overlay comparison | SOP-3, Step 3 | Lens passes numerical thresholds but through-focus shape is anomalous (e.g., shifted, asymmetric, or showing unexpected features) | A numerically passing lens with wrong plateau shape ships. Patient may experience unexpected visual behavior not captured by scalar pass/fail criteria. |
| Multi-aperture verification (3mm and 4.5mm) | SOP-3, Step 2 | Lens passes at 3mm but through-focus collapses at 4.5mm; pupil-dependent performance unverified | Patients report excellent daytime vision but poor intermediate in dim lighting. Complaint cannot be reproduced on single-aperture bench test. |
Training Requirements: What Operators Need to Know
An operator trained on monofocal measurement can execute SOP-2 (production measurement) with one additional training session. The measurement itself is similar-load tray, press start, read results. The difference is in the results interpretation and disposition logic.
Training Module 1: Understanding through-focus output (2 hours)
The operator must understand what the through-focus display shows and how to distinguish a passing profile from a failing profile. This does not require optical engineering knowledge. It requires pattern recognition: “this curve matches the reference” vs “this curve does not match the reference.”
Training method: show 10 passing through-focus profiles and 10 failing profiles. The operator identifies which are which. When accuracy reaches 95% (19 of 20 correct), the operator is qualified. This is the same approach used for visual inspection training-pattern recognition against a reference set.
Training Module 2: Disposition logic (1 hour)
The operator must understand the four disposition outcomes and the correct action for each. Training method: present 20 measurement results with various combinations of power pass/fail and through-focus pass/fail. The operator selects the correct disposition for each. When accuracy reaches 100% (all 20 correct), the operator is qualified.
Training Module 3: Escalation criteria (30 minutes)
The operator must know when to escalate to the process engineer: batch failure rate exceeding threshold, anomalous through-focus shape not matching any known failure pattern, or system verification failure. Training method: present 5 escalation scenarios and 5 non-escalation scenarios. The operator identifies which require escalation.
Total additional training time for an experienced monofocal operator: approximately 3.5 hours. The operator does not need to understand wavefront physics, Zernike polynomials, or SA optimization. They need to execute a procedure, recognize patterns, and make documented decisions.
Document Control: Managing the SOP Set
Version control
Each of the three SOPs (SOP-1, SOP-2, SOP-3) is version-controlled independently. When a new EDOF product code is added, SOP-2 is updated to include the new product’s acceptance criteria and disposition thresholds. SOP-1 may need updating if the new product requires a different reference lens. SOP-3 is updated if the sampling plan changes.
Product-code-specific annexes
Rather than embedding product-specific acceptance criteria in the SOP body (which requires a full SOP revision for every product change), use an annex system. The SOP body describes the general procedure. The annexes-one per EDOF product code-contain the specific acceptance criteria, reference values, and disposition thresholds. Adding a new EDOF product requires only a new annex, not a revision to the parent SOP.
Regulatory alignment
For manufacturers operating under ISO 13485, the EDOF SOP set should be referenced in the quality manual as part of the inspection and test procedure documentation. The SOP-1 verification records feed into the equipment qualification documentation. The SOP-2 batch records provide the objective evidence of inspection required by the quality system. The SOP-3 data archive supports the design and process validation records.
For manufacturers with FDA-regulated products, SOP-2 batch records and SOP-3 data archives should be maintained in compliance with 21 CFR Part 11 requirements for electronic records. The automatic data export from the measurement systems to the SPC and archival systems supports this compliance.
Common SOP Gaps That Lead to EDOF Quality Escapes
Gap 1: No EDOF reference lens in SOP-1
The verification procedure uses a monofocal reference lens. The system passes verification. But through-focus computation is not verified. Every EDOF measurement thereafter may be incomplete without anyone knowing.
Fix: procure a certified EDOF reference lens. Include its certified through-focus characteristics in the verification acceptance criteria.
Gap 2: Binary disposition in SOP-2
The SOP has only two disposition outcomes: pass or fail. There is no separate tracking of Outcome B (power pass, through-focus fail). The process engineer cannot distinguish EDOF-specific failures from standard failures in the quality data.
Fix: implement the four-outcome disposition logic. Track Outcome B as a distinct failure category with its own trend chart.
Gap 3: No shape comparison in SOP-3
The detailed analysis SOP checks numerical thresholds (plateau width ≥ 1.5D, min MTF ≥ 0.15) but does not compare the measured through-focus profile shape to the design reference. A lens with the correct width and minimum but an anomalous shape (e.g., double-peaked instead of plateau) passes all numerical criteria but delivers unexpected visual behavior.
Fix: include the design reference overlay comparison as a mandatory step. Train operators to recognize the expected profile shape.
Gap 4: No SOP-3 at all
The facility has SOP-1 (verification) and SOP-2 (batch inspection) but no SOP-3 (detailed analysis). Through-focus parameters are checked at pass/fail level but no Zernike data, no multi-aperture data, and no SPC feed is generated. Process drift that affects the SA recipe goes undetected until it is severe enough to fail the pass/fail thresholds.
Fix: implement SOP-3 with the sampling plan appropriate for your production volume. Even 3 lenses per batch, measured in 27 seconds total, provides the diagnostic data that prevents drift from accumulating into failures.
Conclusion
Writing EDOF measurement SOPs is not about making monofocal SOPs longer. It is about adding the steps that address EDOF-specific failure modes: the verification step that confirms through-focus measurement is active, the disposition logic that separates plateau failures from power failures, and the detailed analysis step that feeds the diagnostic data into the SPC system.
Three SOPs. Seven EDOF-specific steps that have no monofocal equivalent. One EDOF reference lens that prevents the single most common quality escape. Four disposition outcomes that replace the binary pass/fail with a decision tree that captures the full range of EDOF measurement results.
The operator training overhead is 3.5 hours. The document set is five pages per SOP with product-specific annexes. The investment in writing and implementing these SOPs is measured in days. The cost of not having them-Outcome B lenses shipping as passes, EDOF-specific failures invisible in the quality data, process drift undetected until patients complain-is measured in surgeon attrition and regulatory exposure.
A monofocal SOP asks: did the lens pass? An EDOF SOP asks: did the lens pass as an EDOF? The three-letter difference between those questions is the reason the SOP set exists.
Disclaimer: This document is intended for educational use only. It does not represent legal, regulatory, or certification advice, and should not be interpreted as a declaration of compliance or approval by Rotlex or any regulatory authority. SOP templates described are frameworks that must be adapted to your specific products, instruments, quality system, and regulatory requirements.
