1. Classify Services by Criticality

Possible connected services include:

• Clinical workstations
• Staff and guest Wi-Fi
• Voice services
• IP cameras
• Access control interfaces
• Administrative systems
• Digital signage
• Patient entertainment
• Building-management interfaces
• Telemedicine endpoints

For each service, record:

• Availability target
• Bandwidth profile
• PoE demand
• Security zone
• Maximum acceptable outage group
• Backup-power requirement
• Approved network architecture

2. Control Failure Domains

One OLT port and splitter group can serve many ONTs. In a hospital, ask:

• How many rooms depend on one feeder?
• Does one splitter cross clinical departments?
• What happens if an OLT card fails?
• Are critical and noncritical services mixed?
• Is the splitter accessible during infection-control restrictions?
• Can restoration occur without entering treatment spaces?

Smaller split groups or separate PON ports may be justified for critical zones even when a larger ratio is technically supported.

3. Plan Redundant Paths Where Required

Redundancy options can include:

• Diverse feeder routes
• Spare feeder fibers
• Separate OLT cards or chassis
• Dual-input architectures where supported
• Redundant power supplies
• Central UPS-backed remote power
• Separate splitter groups for critical areas

The APOLAN technical specification notes that dual splitter inputs may be used when active-headend redundancy or feeder diversity is desired. The complete design must be coordinated with the active vendor.

4. Use Accessible, Controlled Splitter Locations

Suitable locations may include:

• Main equipment rooms
• Secure telecommunications rooms
• Controlled floor distribution rooms
• Accessible zone cabinets outside treatment spaces

Avoid placing splitters where service requires ceiling access in sterile or restricted rooms. The passive location must provide bend control, labeling, environmental protection and future module space.

5. Build the Healthcare POL BOM

6. Select Fiber and Cable for the Environment

Specify:

• OS2 fiber category
• G.657.A1/A2 for compact routes where appropriate
• Required plenum, riser or LSZH performance
• Indoor/outdoor construction for campus transitions
• All-dielectric cable in high-EMI areas
• Cleanable or protected pathways
• Low-smoke and fire documentation required by the jurisdiction

The fiber recommendation does not replace local building, fire or healthcare-facility requirements.

7. Engineer ONT and Endpoint Power

The ONT must remain powered for connected services to operate. Options include local AC, remotely delivered DC or hybrid fiber-and-power cabling.

Define:

• UPS runtime
• Power-source redundancy
• Voltage drop
• ONT consumption
• PoE load
• Heat and enclosure ventilation
• Emergency-power connection
• Maintenance isolation

Some enterprise ONTs provide PoE for cameras, phones and wireless access points. Use the selected manufacturer's actual power limits rather than assuming every ONT provides the same output.

8. Separate Network, Cabling and Life-Safety Decisions

POL may transport enterprise IP traffic associated with security or building systems, but it does not automatically satisfy the pathway, survivability or certification requirements of fire alarm, emergency communication or other life-safety systems.

Keep separate:

• Code-mandated life-safety cabling
• Hospital clinical engineering requirements
• Enterprise IP network services
• Building automation networks
• Medical-device manufacturer requirements

This boundary protects both compliance and article credibility.

9. Testing and Commissioning

Healthcare acceptance should include:

• Connector inspection and cleaning
• Route and label verification
• OLTS loss testing
• OTDR traces where specified
• Splitter and spare-fiber verification
• ONT registration and receive-level check
• PoE load test
• Failover and backup-power test where required
• As-built route diversity records
• Change-control handover

The BICSI Optical LAN Council promotes standards-aligned Optical LAN design and education, while APOLAN provides a useful technical-specification baseline. Project-specific healthcare rules remain authoritative.

10. Restoration Planning

Keep:

• Spare splitters by installed type
• Spare patch cords and adapters
• Approved restoration cable
• Spare trays and sealing parts
• Accessible route drawings
• Critical-service contact list
• Defined isolation and infection-control procedures
• Baseline test records

The restoration plan should state who can access each distribution point at any hour.

11. Common Mistakes

• Maximizing split ratio without outage analysis
• Sharing one feeder across unrelated critical departments
• Locating splitters inside restricted treatment areas
• Treating ONT power as a minor electrical detail
• Omitting spare fibers and diverse-route documentation
• Assuming enterprise POL covers regulated life-safety cabling
• Testing optical loss without failover and power scenarios
• Delivering contractor records that hospital operations cannot use

Conclusion

Healthcare POL must be designed around risk zones, maintenance access, power continuity and fault containment. The passive layer can be simple in principle while still requiring disciplined route separation and documentation.

ZION's role is to supply and configure the approved passive infrastructure—ODFs, single-mode cables, splitters, terminals and assemblies—within a system design controlled by the hospital, consultant and active-platform provider.

References

1. APOLAN — Passive Optical LAN Technical Specification
2. BICSI — Optical LAN Council
3. Nokia — Optical LAN for Enterprise Sectors Including Hospitals
4. ITU-T G.657 — Bend-Insensitive Single-Mode Fiber
5. ZION — Optical Distribution Network Solution