reason-healthcare
- 14 skills
- 0 followers
- 1 day ago last updated
- ▌ Health Init 2 · reason-healthcareBootstrap reusable healthcare project context from repository evidence. Use when an agent needs to determine jurisdiction, primary audience, or whether a target repo is greenfield or existing, then persist that context in .health-context.yaml for future skills.
- ▌ Reasonhub Clinical Search · reason-healthcareSearch ICD-10-CM, LOINC, and RxNorm by clinical concept using semantic similarity, then build a property-filtered FHIR ValueSet in the target system. Use when the user wants to find diagnosis codes, lab observation codes, or drug/medication codes from natural language — or when they want to build a ValueSet and the right code system is unclear. Automatically detects which code system fits the query from context signals; prompts the user when ambiguous. For SNOMED CT semantic attribute queries (finding site, causative agent, morphology, procedure site) use the `snomed-semantic` skill instead.
- ▌ Reasonhub Snomed Semantic · reason-healthcareUse SNOMED CT's semantic attribute relationships to answer clinical questions. Finds concepts by relationship attribute (finding site, causative agent, associated morphology, procedure site), navigates the IS-A hierarchy, and composes property-filtered ValueSets. Use when the user asks things like "all disorders of the heart", "all procedures on the kidney", "all conditions caused by bacteria", "subtypes of hypertension", "symptoms of X", "complications of X", or any query that involves clinical relationships between concepts rather than simple text search.
- ▌ Reasonhub Expand Mechanics · reason-healthcareShared reference for ValueSet expansion mechanics used by all reasonhub skills. Covers valueset_expand failures and the CLI fallback, bulk scripting with Python, truncation handling, and a debugging checklist. Not a user-triggered skill — consulted by other skills when they need to expand a ValueSet or debug expansion failures.
- ▌ Reasonhub Terminology Crossmap · reason-healthcareMap a code from any clinical terminology (ICD-10-CM, LOINC, RxNorm) to its SNOMED CT equivalent in order to unlock SNOMED's rich semantic attribute relationships. Use when the user has a code in a non-SNOMED system and wants to explore related concepts, find clinically adjacent codes, understand the semantic meaning, or build a SNOMED-based ValueSet from a non-SNOMED starting point. Always propose this when a user asks about relationships or "what is related to X" and the code is not already in SNOMED.
- ▌ Your Skill Name · reason-healthcare bundleHealthcare-focused skill for <replace-this>. Use when an agent needs support with <replace-this>, especially in healthcare software, digital health product, clinical workflow, interoperability, privacy, security, or operational contexts.
- ▌ Health Docs · reason-healthcare bundleAudit 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.
- ▌ Health Init · reason-healthcare bundleBootstrap reusable healthcare project context from repository evidence. Use when an agent needs to determine jurisdiction, primary audience, or whether a target repo is greenfield or existing, then persist that context in .health-context.yaml for future skills.
- ▌ Health Refactor · reason-healthcare bundleProduce 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.
- ▌ Health Fhir Modeling · reason-healthcare bundleMap 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.
- ▌ Health Human Factors · reason-healthcare bundleReview 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.
- ▌ Health Fhir API Design · reason-healthcare bundleDesign 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.
- ▌ Health Compliance Review · reason-healthcare bundleAudit, 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.
- ▌ Health Product Discovery · reason-healthcare bundleHealthcare product discovery skill that maps incentive structures, adoption dynamics, and clinical workflow constraints before shaping solutions. Uses a jurisdiction-neutral core workflow plus explicit US and EU market overlays. Supports explore and document modes for early-stage ideation, consulting, pilot scoping, and strategic planning.