setup-openmed

Generate a deterministic DEID-POLICY.md draft from five bounded de-identification decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Privacy decisions for clinical de-identification are often implicit and unrecorded, making pipelines hard to review and audit. This Skill turns five explicit policy choices into a reviewable, deterministic DEID-POLICY.md draft before any privacy work begins.

Core Features & Use Cases

  • Bounded decision collection: Captures exactly five canonical choices (jurisdiction, recall floor, surrogate strategy, model policy, audit location) with strict normalization and rejection of free-form values.
  • Deterministic template rendering: Fills a versioned local template so identical inputs produce byte-for-byte identical output, with atomic file replacement and symlink protection.
  • Human approval gate: Writes a DRAFT status that requires explicit human review before the policy controls any de-identification run.
  • Use Case: Before running a clinical text de-identification pipeline, a project owner answers the five policy questions and receives a DEID-POLICY.md draft that downstream skills apply, transform against, and audit.

Quick Start

Ask the assistant to set up an OpenMed de-identification policy for your project directory and answer the five decision prompts.

Frequently Asked Questions about setup-openmed

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

FAQPage Schema
How do I create a de-identification policy for clinical text?

Run this setup workflow in your project directory and answer five bounded questions covering jurisdiction, recall floor, surrogate strategy, model policy, and audit location. It writes a DEID-POLICY.md draft that a human must approve before any de-identification run.

What decisions does an OpenMed de-identification policy require?

Exactly five: jurisdiction or operating context (us, eu, canada, research, organization-defined), recall floor (0.90, 0.95, 0.99), surrogate strategy (mask, remove, replace, hash), model policy (local-preinstalled, local-user-supplied, rules-only), and audit location.

Does the policy setup require a network connection or model download?

No. The setup is local-first and deterministic with no mandatory network call. It never downloads a model or calls a hosted service; local model availability is verified separately by the project owner.

Can the generated DEID-POLICY.md be used without human review?

No. The template always writes a DRAFT — HUMAN APPROVAL REQUIRED status. A reviewer must inspect the five choices and explicitly approve the policy through the project's review process before it controls a run.

What happens if I enter an invalid policy value?

The workflow stops before writing anything and reports only the field name and its allowed canonical choices. Free-form values are never accepted, and answers are normalized by trimming, case folding, and treating spaces or underscores as hyphens.