extracting-pii-entities

Detect PHI and PII spans in clinical text without modifying the original.

5.0k|615|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/maziyarpanahi/openmed --skill extracting-pii-entities
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extracting-pii-entities
Source: https://github.com/maziyarpanahi/openmed/tree/main/skills/extracting-pii-entities
Command: npx skills add https://github.com/maziyarpanahi/openmed --skill extracting-pii-entities

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects sensitive PHI and PII in clinical text while preserving the original content, giving you precise spans and labels for review, auditing, or downstream redaction.

Core Features & Use Cases

  • Entity Detection: Identify names, dates, medical record numbers, phone numbers, addresses, emails, SSNs, and other identifiers.
  • Span Inspection: Return entity text, labels, confidence scores, and character offsets without altering the source text.
  • Label Normalization: Map inconsistent model outputs to OpenMed’s canonical taxonomy for stable downstream processing.
  • Use Case: Review detected identifiers in a clinical note before sending selected spans to a custom anonymizer or OpenMed’s deidentification workflow.

Quick Start

Use the extracting-pii-entities skill to detect and list all PHI and PII spans in the provided clinical text without redacting it.

Frequently Asked Questions about extracting-pii-entities

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect PII and PHI entities in clinical text without modifying the original content?

To detect PII and PHI entities without modifying clinical text, you can use a detection interface that returns precise character spans, labels, and confidence scores. This approach preserves the source text for review, auditing, or downstream redaction pipelines.

What is span offset extraction for deidentification previews?

Span offset extraction is the process of identifying the exact character start and end positions of sensitive identifiers in clinical documents. It allows you to preview PHI locations and review detected entities before applying any actual redaction.

Can I filter PII detection results by confidence scores and language?

Yes, you can filter PII detection results using configurable confidence thresholds and language selection. This allows you to control the precision of extracted entities and process multilingual clinical documents effectively.

How do I normalize inconsistent entity labels for privacy compliance audits?

You can normalize inconsistent entity labels by mapping varying model outputs to a canonical taxonomy. This ensures stable downstream processing and consistent categorization of PHI identifiers during privacy compliance audits.

Does on-device inference support smart span merging for clinical text redaction pipelines?

Yes, on-device inference supports configurable models with smart span merging for clinical text redaction pipelines. This allows you to process sensitive documents locally while accurately combining overlapping entity spans.

What is the best way to extract medical record numbers and dates for custom redaction workflows?

The best way to extract medical record numbers and dates for custom redaction workflows is using an entity recognition interface that outputs character offsets. This enables precise extraction of identifiers without altering the source text.