feat(health): Add healthcare organization plugin foundation#48
feat(health): Add healthcare organization plugin foundation#48edithatogo wants to merge 58 commits intoanthropics:mainfrom
Conversation
…tracks, 30 skills, 14 commands) - Add conductor project structure (index, product, tech-stack, workflow, guidelines) - Create health-plugin meta-track for program coordination - Add 17 implementation tracks across 4 phases: Phase 1: health-core (foundation) Phase 2: complaints, incidents, risk, information, coding Phase 3: governance, credentialing, procurement, quality, financial, evidence, data-analysis Phase 4: ethics, economics, manuscripts, grants, medicolegal - Add index.md navigation to all tracks - Reference NSQHS, NICE, PBAC frameworks - Document skill adaptations from existing plugins
- Create health/ directory structure with .claude-plugin/ - Add plugin.json manifest (v0.1.0, healthcare workflows) - Add README.md documenting 17 planned domains across 4 phases - Add CONNECTORS.md with SharePoint, Jira, FHIR connector guides - Add .mcp.json with 3 connector templates (disabled by default)
There was a problem hiding this comment.
Pull request overview
Introduces a new health/ plugin foundation plus accompanying “conductor” planning/docs to scaffold a multi-track healthcare workflow program.
Changes:
- Added
health/plugin skeleton (manifest, README, connectors doc, MCP config template). - Added “conductor” project documentation (workflow, tech stack, product definition/guidelines, project index).
- Added health program track registry + per-track specs/plans/metadata to coordinate planned implementation work.
Reviewed changes
Copilot reviewed 84 out of 84 changed files in this pull request and generated 19 comments.
Show a summary per file
| File | Description |
|---|---|
| health/README.md | Health plugin overview, install/config instructions, planned domains/skills list |
| health/CONNECTORS.md | Health connector categories + setup examples |
| health/.mcp.json | MCP server config templates for SharePoint/Jira/FHIR |
| health/.claude-plugin/plugin.json | Health plugin manifest |
| conductor/workflow.md | Development workflow documentation |
| conductor/tech-stack.md | Repo tech stack + file format conventions |
| conductor/product.md | Product definition (vision/scope/metrics) |
| conductor/product-guidelines.md | Content and organization guidelines for plugins |
| conductor/index.md | Conductor documentation index + active plugins list |
| conductor/tracks.md | Health program execution phases + track registry |
| conductor/tracks/health-core/spec.md | Health-core track spec (plugin skeleton expectations) |
| conductor/tracks/health-core/plan.md | Health-core track plan/checkpoint |
| conductor/tracks/health-core/metadata.json | Health-core track metadata/status |
| conductor/tracks/health-core/index.md | Health-core track index page |
| conductor/tracks/health-plugin/spec.md | Health program spec (phases, tracks, totals) |
| conductor/tracks/health-plugin/plan.md | Health program coordination plan |
| conductor/tracks/health-plugin/metadata.json | Health program meta-track metadata (tracks, totals) |
| conductor/tracks/health-plugin/index.md | Health program track index page |
| conductor/tracks/health-complaints/spec.md | Complaints track specification |
| conductor/tracks/health-complaints/plan.md | Complaints track plan |
| conductor/tracks/health-complaints/metadata.json | Complaints track metadata |
| conductor/tracks/health-complaints/index.md | Complaints track index |
| conductor/tracks/health-incidents/spec.md | Incidents track specification |
| conductor/tracks/health-incidents/plan.md | Incidents track plan |
| conductor/tracks/health-incidents/metadata.json | Incidents track metadata |
| conductor/tracks/health-incidents/index.md | Incidents track index |
| conductor/tracks/health-risk/metadata.json | Risk track metadata |
| conductor/tracks/health-risk/index.md | Risk track index |
| conductor/tracks/health-information/spec.md | Health information management track spec |
| conductor/tracks/health-information/plan.md | Health information management track plan |
| conductor/tracks/health-information/metadata.json | Health information management track metadata |
| conductor/tracks/health-information/index.md | Health information management track index |
| conductor/tracks/health-coding/spec.md | Clinical coding track specification |
| conductor/tracks/health-coding/plan.md | Clinical coding track plan |
| conductor/tracks/health-coding/metadata.json | Clinical coding track metadata |
| conductor/tracks/health-coding/index.md | Clinical coding track index |
| conductor/tracks/health-governance/spec.md | Governance track specification |
| conductor/tracks/health-governance/plan.md | Governance track plan |
| conductor/tracks/health-governance/metadata.json | Governance track metadata |
| conductor/tracks/health-governance/index.md | Governance track index |
| conductor/tracks/health-credentialing/spec.md | Credentialing track specification |
| conductor/tracks/health-credentialing/plan.md | Credentialing track plan |
| conductor/tracks/health-credentialing/metadata.json | Credentialing track metadata |
| conductor/tracks/health-credentialing/index.md | Credentialing track index |
| conductor/tracks/health-procurement/spec.md | Procurement track specification |
| conductor/tracks/health-procurement/plan.md | Procurement track plan |
| conductor/tracks/health-procurement/metadata.json | Procurement track metadata |
| conductor/tracks/health-procurement/index.md | Procurement track index |
| conductor/tracks/health-quality/spec.md | Quality & performance track specification |
| conductor/tracks/health-quality/plan.md | Quality & performance track plan |
| conductor/tracks/health-quality/metadata.json | Quality & performance track metadata |
| conductor/tracks/health-quality/index.md | Quality & performance track index |
| conductor/tracks/health-financial/spec.md | Financial track specification |
| conductor/tracks/health-financial/plan.md | Financial track plan |
| conductor/tracks/health-financial/metadata.json | Financial track metadata |
| conductor/tracks/health-financial/index.md | Financial track index |
| conductor/tracks/health-evidence/spec.md | Evidence synthesis track specification |
| conductor/tracks/health-evidence/plan.md | Evidence synthesis track plan |
| conductor/tracks/health-evidence/metadata.json | Evidence synthesis track metadata |
| conductor/tracks/health-evidence/index.md | Evidence synthesis track index |
| conductor/tracks/health-data-analysis/spec.md | Data analysis track specification |
| conductor/tracks/health-data-analysis/plan.md | Data analysis track plan |
| conductor/tracks/health-data-analysis/metadata.json | Data analysis track metadata |
| conductor/tracks/health-data-analysis/index.md | Data analysis track index |
| conductor/tracks/health-ethics/spec.md | Ethics track specification |
| conductor/tracks/health-ethics/plan.md | Ethics track plan |
| conductor/tracks/health-ethics/metadata.json | Ethics track metadata |
| conductor/tracks/health-ethics/index.md | Ethics track index |
| conductor/tracks/health-economics/spec.md | Economics/HTA track specification |
| conductor/tracks/health-economics/plan.md | Economics/HTA track plan |
| conductor/tracks/health-economics/metadata.json | Economics/HTA track metadata |
| conductor/tracks/health-economics/index.md | Economics/HTA track index |
| conductor/tracks/health-manuscripts/spec.md | Manuscripts track specification |
| conductor/tracks/health-manuscripts/plan.md | Manuscripts track plan |
| conductor/tracks/health-manuscripts/metadata.json | Manuscripts track metadata |
| conductor/tracks/health-manuscripts/index.md | Manuscripts track index |
| conductor/tracks/health-grants/spec.md | Grants track specification |
| conductor/tracks/health-grants/plan.md | Grants track plan |
| conductor/tracks/health-grants/metadata.json | Grants track metadata |
| conductor/tracks/health-grants/index.md | Grants track index |
| conductor/tracks/health-medicolegal/spec.md | Medicolegal track specification |
| conductor/tracks/health-medicolegal/plan.md | Medicolegal track plan |
| conductor/tracks/health-medicolegal/metadata.json | Medicolegal track metadata |
| conductor/tracks/health-medicolegal/index.md | Medicolegal track index |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
conductor/tracks/health-core/plan.md
Outdated
| - [x] Create `health/.claude-plugin/plugin.json` (524aca0) | ||
| - Acceptance: Valid JSON, installs successfully | ||
| - [x] Create `health/README.md` (524aca0) | ||
| - Acceptance: Documents 7 planned domains (complaints, incidents, risk, governance, ethics, compliance, procurement) |
There was a problem hiding this comment.
This plan’s acceptance criteria says the Health README documents 7 planned domains, but health/README.md in this PR lists a much larger set of domains. Update the acceptance criteria to reflect the current README scope (or reduce the README scope if 7 is the intended target for this phase).
| - Acceptance: Documents 7 planned domains (complaints, incidents, risk, governance, ethics, compliance, procurement) | |
| - Acceptance: Documents the planned health domains (complaints, incidents, risk, governance, ethics, compliance, procurement) |
health/CONNECTORS.md
Outdated
| | Connector | Use Case | Authentication | | ||
| |-----------|----------|----------------| | ||
| | SharePoint | Microsoft 365 environments | OAuth 2.0 / Entra ID | | ||
| | Box | Cloud content management | OAuth 2.0 / JWT | | ||
| | Egnyte | Hybrid cloud storage | OAuth 2.0 / API Key | | ||
| | Google Drive | Google Workspace | OAuth 2.0 | |
There was a problem hiding this comment.
The connector tables use || at the start of each row, which will render as an extra blank column in most Markdown renderers. Switch to standard Markdown table formatting (single leading |) to avoid malformed tables.
| ## MCP Integration | ||
|
|
||
| Servers configured in `.mcp.json`: | ||
| ```json | ||
| { | ||
| "servers": { | ||
| "server-name": { | ||
| "type": "stdio|sse|http", | ||
| "command": "...", | ||
| "args": [...] | ||
| } | ||
| } | ||
| } | ||
| ``` |
There was a problem hiding this comment.
The .mcp.json example uses a top-level servers key, but the rest of this repo (and the referenced MCP examples) use mcpServers. This is likely to mislead plugin authors; update the example to match the actual config format used elsewhere.
| A comprehensive healthcare plugin ecosystem comprising 17 tracks delivering 27 skills and 13 commands for healthcare organizations. | ||
|
|
||
| ## Program Goals | ||
|
|
||
| 1. **Operational Excellence** - Complaints, incidents, risk, credentialing | ||
| 2. **Governance & Compliance** - Policies, procedures, quality, ethics | ||
| 3. **Research & Academic** - Evidence synthesis, economics, manuscripts, grants | ||
| 4. **Financial & Data** - Payer contracts, coding, analysis | ||
|
|
||
| ## Track Summary | ||
|
|
||
| ### Phase 1: Foundation | ||
| | Track | Skills | Commands | | ||
| |-------|--------|----------| | ||
| | health-core | - | - | | ||
|
|
||
| ### Phase 2: Core Workflows | ||
| | Track | Skills | Commands | Adapts From | | ||
| |-------|--------|----------|-------------| | ||
| | health-complaints | complaints-management | /submit-complaint | customer-support/ticket-triage | | ||
| | health-incidents | incident-reporting | /report-incident | customer-support/escalation | | ||
| | health-risk | clinical-risk, worker-risk, enterprise-risk | /assess-risk | legal/legal-risk-assessment | | ||
| | health-information | release-of-information, consent-management | /process-roi | legal/compliance | | ||
| | health-coding | clinical-coding | /validate-coding | data/data-validation | | ||
|
|
||
| ### Phase 3: Extended Workflows | ||
| | Track | Skills | Commands | Adapts From | | ||
| |-------|--------|----------|-------------| | ||
| | health-governance | policy-development, procedure-development, guideline-development | - | legal/compliance | | ||
| | health-credentialing | credentialing, privileging | /verify-credentials | productivity/memory-management | | ||
| | health-procurement | device-procurement, business-case | /procurement-request, /business-case | legal/contract-review | | ||
| | health-quality | quality-improvement, accreditation-prep | /qi-project | product-management/roadmap-management | | ||
| | health-financial | payer-contracts, charge-capture | /review-payer-contract | legal/contract-review, finance | | ||
| | health-evidence | systematic-review, evidence-synthesis | /start-review | bio-research | | ||
| | health-data-analysis | health-data-report | /analyze-health-data | data | | ||
|
|
||
| ### Phase 4: Research/Academic | ||
| | Track | Skills | Commands | Adapts From | | ||
| |-------|--------|----------|-------------| | ||
| | health-ethics | research-ethics, clinical-ethics | /ethics-review | bio-research | | ||
| | health-economics | health-econ-eval, hta-submission | /economic-evaluation | data, finance | | ||
| | health-manuscripts | manuscript-prep | /prepare-manuscript | scientific-writing | | ||
| | health-grants | grant-writer | /grant-application | research-grants | | ||
|
|
||
| ## Total Deliverables | ||
|
|
||
| - **27 Skills** across 16 implementation tracks | ||
| - **13 Commands** for key workflows | ||
| - **1 Plugin** installable as `health` |
There was a problem hiding this comment.
This spec’s headline counts (tracks/skills/commands) don’t match the rest of the PR. conductor/tracks.md and health-plugin/metadata.json describe 18 total tracks (1 meta + 17 implementation) and 30 skills / 14 commands, while this spec says 17 tracks and 27 skills / 13 commands. Please reconcile these numbers so the program documentation is internally consistent.
health/CONNECTORS.md
Outdated
| | Connector | Use Case | Authentication | | ||
| |-----------|----------|----------------| | ||
| | Jira | IT service management | API Token / OAuth | | ||
| | ServiceNow | Enterprise service management | OAuth 2.0 / Basic | | ||
| | Azure DevOps | Development tracking | PAT / OAuth | | ||
|
|
There was a problem hiding this comment.
The Issue Tracking connectors table also uses || at the start of each row, which typically renders as an extra empty column. Use standard Markdown table syntax (single leading |) so the table displays correctly.
| "dependencies": ["health-core"], | ||
| "deliverable": "payer-contracts, charge-capture, grant-management skills", | ||
| "adapts_from": ["legal/contract-review", "finance/reconciliation"] |
There was a problem hiding this comment.
deliverable includes a grant-management skill, but the corresponding track spec only defines payer-contracts and charge-capture skills (and there’s no planned work item for grant-management in this track). Align the metadata deliverable with the spec/plan, or add the missing skill to the spec/plan if it’s intended.
health/README.md
Outdated
| | Domain | Skills | Status | | ||
| |--------|--------|--------| | ||
| | complaints | complaint-analysis, response-drafting | Planned | | ||
| | incidents | root-cause-analysis, cap-writing | Planned | | ||
| | risk | risk-assessment, mitigation-planning | Planned | |
There was a problem hiding this comment.
The skills table is using || at the start of each row, which renders as an extra empty column in most Markdown parsers. Use standard Markdown table syntax with a single leading | per row so the table renders correctly.
health/CONNECTORS.md
Outdated
| # Health Plugin Connectors | ||
|
|
||
| This document describes the connector categories and setup instructions for the health plugin. | ||
|
|
||
| ## Connector Categories | ||
|
|
There was a problem hiding this comment.
This CONNECTORS doc doesn’t follow the established repo convention of documenting tool placeholders (e.g., ~~cloud storage, ~~project tracker) and listing connectors by category in a single table. Aligning the structure with other plugins’ CONNECTORS.md makes customization consistent across the repo.
| This is a meta-track coordinating 11 implementation tracks. No direct implementation work - that's delegated to individual tracks. | ||
|
|
There was a problem hiding this comment.
The plan states this meta-track coordinates 11 implementation tracks, but the metadata/spec/tracks registry in this PR list 17 implementation tracks. Update the plan to reflect the actual number of coordinated tracks.
- Update health-core plan acceptance criteria to match README scope - Update health-core spec to list actual connectors provided - Add health to Active Plugins table in index.md - Remove 'disabled' field from .mcp.json (not standard) - Change author to object format in plugin.json for consistency - Rewrite CONNECTORS.md to follow repo convention (~~category format) - Fix track counts in health-plugin spec (30 skills, 14 commands) - Add health-medicolegal to Phase 4 table - Update Adapts From references to match actual skill paths - Fix health-financial metadata to match spec deliverables - Remove .mcp.json.template reference from README (file doesn't exist)
|
@copilot open a new pull request to apply changes based on the comments in this thread |
- Remove non-existent health-compliance dependency from health-information spec - Fix tech-stack.md MCP example to use mcpServers (not servers)
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
@copilot open a new pull request to apply changes based on the comments in this thread |
…ments - Add spec.md with 14 improvement areas and quality standards - Add plan.md with 4 phases covering 50+ skills - Define standard skill structure with 8 required sections - Include plugin-specific improvement recommendations - Add quality gates and success metrics
- Rename to health-skill-quality in metadata - Rewrite spec.md with healthcare-specific requirements: - Regulatory context (HIPAA, HITECH) - Clinical accuracy standards - Privacy & PHI considerations - Healthcare workflow integration - Rewrite plan.md to support health track implementations - Update to 12 required sections, 11 quality gates - Add domain-specific improvements for all health tracks - Minimum 200 lines per health skill (vs 150 general)
- Rename to health-skill-quality in metadata - Rewrite spec.md with healthcare-specific requirements: - Regulatory context (HIPAA, HITECH) - Clinical accuracy standards - Privacy & PHI considerations - Healthcare workflow integration - Rewrite plan.md to support health track implementations - Update to 12 required sections, 11 quality gates - Add domain-specific improvements for all health tracks - Minimum 200 lines per health skill (vs 150 general)
…ety guardrails - Created health-specific skill standards with 14-section architecture mandate - Established interoperability standards (FHIR, SNOMED-CT) and hybrid evidence management - Implemented AU/NZ-first jurisdictional strategy with US/EU-lite portability - Mandated Standard and Lite operating modes for all health skills - Propagated new quality gates and clinical guardrails across all 20 health implementation tracks
- Added ICD-10, SNOMED, and PubMed connectors to .mcp.json - Documented new connector categories in CONNECTORS.md - Updated coding, evidence, data analysis, economics, manuscripts, and grants track plans with new tool requirements
…cases' as complete
…d accreditation guidance
- Add review-payer-contract command with contract intake workflow - Include comprehensive contract analysis sections: - Executive summary and risk assessment - Financial and operational terms analysis - Compliance and risk assessment - Negotiation priorities and decision matrix - Contract intake workflow with action items - Approval checklist - Reference health/payer-contracts skill for analysis framework - Arguments: payer_name, contract_type, effective_date, key_concerns - Follow health command structure with validation, skill invocation, output generation, routing, and guardrails
- Mark review-payer-contract command as complete with commit hash 98561cc - Health financial track now fully complete with all three phases
Implement all remaining health plugin conductor tracks: - health-evidence: systematic-review, evidence-synthesis skills, /start-review command - health-ethics: research-ethics, clinical-ethics skills, /ethics-review command - health-economics: health-econ-eval, hta-submission skills, /economic-evaluation command - health-manuscripts: manuscript-prep skill, /prepare-manuscript command - health-doc-coauthoring: clinical-doc-coauthoring skill, /coauthor command - health-grants: grant-writer skill, /grant-application command - health-medicolegal: medicolegal-reports, child-protection, affidavit-drafting skills, /prepare-report command - skill-quality: health skill templates, validation checklist, validate_health_skills.py script Also implement missing pieces: - health-data-analysis: /analyze-health-data command - health-public-health: notifiable-diseases, public-health-surveillance skills, /report-notifiable command Track infrastructure: - Move health-core, health-coding, health-governance from archive to tracks - Update all track metadata to 'complete' status - Fix tracks.md format for validator compatibility - All 14 tracks now pass validation (0 errors) Total: 34 skills, 19 commands, 12,000+ lines of documentation All skills follow 14-section health skill standards with AU/NZ defaults
Summary
health/plugin skeleton for healthcare organization workflowsPlugin Scope
This foundation plugin supports:
Files Added
health/.claude-plugin/plugin.jsonhealth/README.mdhealth/CONNECTORS.mdhealth/.mcp.jsonTesting
Notes
This is a foundation PR. Individual domain tracks will be submitted as separate PRs following this skeleton.
Related Issue:
Closes #56