fhir-data-model-design
FHIR Data Model Designer
Design a FHIR R4 data model for your digital health app. Ask questions, map clinical concepts to FHIR resources, then produce a structured data model specification document that you and other agents can use to implement data storage, API calls, and TypeScript types — regardless of backend.
Background
FHIR (Fast Healthcare Interoperability Resources) R4 is the standard for healthcare data exchange. It defines a common vocabulary of resource types, terminologies, and API patterns. Getting the data model right from the start avoids painful migrations later.
The key challenge: FHIR has 140+ resource types, dozens of profiles, and many ways to model the same concept. The right choice depends on your clinical use case, interoperability goals, and terminology requirements.
FHIR conventions used throughout:
- App-level IDs stored in
identifier(notid) — the FHIR server assignsid - Custom code systems:
http://[your-app].com/fhir/CodeSystem/[name]
More from stanfordspezi/spezivibe
digital-health-ux-planning
Plan user journeys, onboarding flows, engagement strategies, and day-to-day workflows for digital health products.
63digital-health-compliance-planning
Plan healthcare privacy, research, and regulatory compliance for a digital health product, including HIPAA, IRB, FDA, GDPR, governance, and operational controls.
60keep-a-changelog-generator
Generate changelog entries from git history using Keep a Changelog structure and user-facing release language.
58biodesign-needs-finding
Guide a user through Stanford Biodesign's needs-finding process to define, scope, and refine a rigorous health-app need statement without jumping prematurely to solutions.
57spezi-platform-selection
Ask about an app's requirements, explain the tradeoff between the React Native Template App and the Spezi Template Application for Apple Platforms, clone the right repository, and hand off to the cloned project's local skills and instructions.
57release-notes-generator
Create release notes that summarize features, fixes, and migration guidance for software releases.
57