Talk to an Expert

Tell us about your stack and the privacy problems you're trying to solve. We typically respond within one business day.

Prefer to skip the form? Pick a time on our calendar →
or send a message

Please do not enter PII or PHI in this form. If you need to share an example, use a sanitized one.

← All lenses

PII Lens

Hospital Identifiers

Narrower healthcare-adjacent lens for environments where hospital and room identifiers are the binding constraint — bed-management systems, patient-flow analytics, discharge planning tools.

  • Status available
  • License Apache-2.0
  • Version 1.0.0
  • Updated 2026-05-22
  • PhEye compatibility >=1.0.0
  • Languages en
  • Model size 95 MB
  • Author Philterd

Entities detected

  • HOSPITAL
  • CLINIC
  • DEPARTMENT
  • ROOM_NUMBER
  • BED_IDENTIFIER
  • WARD

When to load this lens

Load this lens when room numbers, bed identifiers, and ward designations need to be recognized as distinct entities — typically alongside the broader Healthcare lens, not in place of it.

Pairs well with

  • Healthcare — Clinical-text lens trained for entities that matter in EHR exports, clinical notes, discharge summaries, and medical-chatbot transcripts — higher recall than general NER on the healthcare-specific surface.
  • General Purpose — Broad PII baseline for documents that don't fit a specific domain — customer-support tickets, internal correspondence, generic business records. The default lens loaded by PhEye when no other is specified.

What this lens detects

Six entity classes tightly scoped to the physical / organizational topology of a healthcare facility:

  • Hospital names — full institutional names plus the common-usage shorthand (Mercy, St. Luke's North).
  • Clinic names — outpatient clinics, urgent-care branches, specialty practices affiliated with a hospital.
  • Department namesCardiology, ED, OR, ICU, etc., as contextual labels.
  • Room numbersRoom 412, 412B, 4-North-22, the variations real hospitals use.
  • Bed identifiers — bed-level identifiers used by bed-management systems.
  • Ward designations — ward / unit / floor-level designations distinct from individual rooms.

This is a narrower lens than Healthcare. It doesn’t try to find providers, medications, or symptoms — just the spatial / organizational identifiers. Load it in addition to Healthcare when those identifiers are the binding constraint of your workload.

When to use this

  • Bed-management and patient-flow analytics — the analytics pipeline needs room and ward identifiers redacted before landing in the warehouse.
  • Discharge-planning and care-coordination tools — outbound messages to home-health agencies, transportation services, or family members should not carry room and bed identifiers.
  • Hospital security and incident reporting — incident reports often mention exact location; redaction-by-room avoids re-identifying patients via location.
  • Operations-research data sharing — sharing operational data with academic partners or vendors for capacity-planning research; room and ward identifiers are quasi-identifiers under the HIPAA Safe Harbor “addresses” clause.

Always combine with Healthcare for full clinical-text coverage.

Known limitations

  • Numeric overlap. Room number patterns (3-4 digits, sometimes with letter suffixes) overlap with other numeric sequences in clinical text. The lens uses surrounding context to disambiguate; recall against a labeled corpus is still the calibration step.
  • Institution-specific room schemes. Some hospitals use highly idiosyncratic room-numbering (4-NW-22b-1); coverage is good on the common patterns and degrades on the unusual ones. Add a custom-identifier regex in the policy layer for the institution-specific scheme.
  • English-only. Bilingual hospital signage / chart notation isn’t trained.

Use this lens with PhEye, Phileas, or Philter

PhEye loads this lens at configuration time and exposes it to Phileas and Philter automatically. Have questions about a specific deployment? Talk to the team.

About PhEye →