health-product-discovery
Skill: health-product-discovery
When To Use
Invoke in explore mode to stress-test a healthcare product idea before committing to a solution, or in document mode to produce a structured strategic planning artifact. Use for early-stage ideation, consulting engagements, pilot scoping, and internal product planning.
Overview
Guide healthcare product discovery through the dynamics that make health products succeed or fail:
- Incentive mapping — the person who uses, buys, benefits from, and pays for healthcare products are almost never the same person
- Adoption physics — clinician burnout, EHR gravity, procurement cycles, and committee-based decisions dominate what ships
- Evidence requirements — healthcare trust runs on clinical evidence and peer validation, not demos and testimonials
- Payment model dependency — fee-for-service vs value-based care changes what's viable, not just what's valuable
- Workflow integration — products that add clinician burden fail regardless of clinical merit
This skill is intended for:
- early-stage ideation and problem framing
More from reason-healthcare/health-skills
health-fhir-api-design
Design FHIR R4 API interactions — search queries, operations ($), validation, workflow patterns, and custom SearchParameter / OperationDefinition resources. The user provides requirements; the skill recommends a concrete R4 approach with trade-offs.
15health-docs
Audit and consolidate documentation for healthcare engineering systems. Supports two modes — analyze (coverage audit — writes only .health-docs/analysis.md) and document (consolidate existing docs + fill gaps). Detects applicable jurisdiction overlays and regulatory regimes from codebase signals, composes existing skills as subagents for deep-dimension analysis, and produces a structured handoff artifact consumed by document mode.
11health-human-factors
Review healthcare and EHR software interfaces against a comprehensive design style guide grounded in NIST, FDA, IEC 62366, ISO 9241, ISO 14971, WCAG 2.1, ONC SAFER, and HL7 FHIR standards. Produces a report-only assessment without modifying code or designs. Use when an agent needs to evaluate clinical UI screens, data display, forms, alerts, or workflows for patient-safety, usability, accessibility, and data-clarity compliance.
11health-refactor
Produce a scope-bounded, plan-only refactoring assessment for healthcare codebases. Resolves a bounded file set via git range, file area, or symbol/dependency context, proposes `us`, `eu`, or `us+eu` overlays from evidence, then orchestrates healthcare-aware refactoring, human-factors review, and regulatory review into a unified plan. Never modifies code.
10health-fhir-modeling
Map domain concepts to FHIR R4 resources and understand profile compliance. Select the right base resources, read US Core and QI Core profile constraints, model relationships, find existing extensions, and apply terminology bindings correctly. Outputs annotated example instances — not StructureDefinition or profile artifacts.
9health-compliance-review
Audit, validate, and enforce regulatory and security controls in healthcare codebases and delivery systems. Selects `us`, `eu`, or `us+eu` jurisdiction overlays from evidence, then delivers deterministic findings across regulatory compliance and security control areas.
8