health-fhir-modeling
FHIR R4 Modeling
When To Use
Invoke to map a domain concept to the correct FHIR R4 resource(s), understand applicable profile constraints, model relationships, and choose terminology bindings. Use this skill before writing a search query or REST call — this skill handles the modeling layer; health-fhir-api-design handles the interaction layer.
Overview
Help software developers building healthcare apps answer the question: "What FHIR resources represent my domain concept, and what constraints do I need to satisfy?"
This skill is for app developers who know their domain but are new to FHIR. It covers resource selection, profile compliance, relationship modeling, extension usage, and terminology — everything needed before writing a search query or a REST call.
This skill is advisory only. It does not modify repository files, application code, or FHIR artifacts.
Relationship to health-fhir-api-design: This skill handles the modeling layer (what shape is my data?). health-fhir-api-design handles the interaction layer (how do I exchange it via REST?). Use this skill first; switch to health-fhir-api-design once the resource model is settled.
This skill is grounded in FHIR R4 (v4.0.1): https://hl7.org/fhir/R4/
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-product-discovery
Healthcare 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.
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-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