fhir-data-model-design

Map clinical concepts to FHIR R4 resources and output a Data Model Specification document.

22|5|Updated Nov 4, 2025
One-click install
npx skills add https://github.com/StanfordSpezi/SpeziVibe --skill fhir-data-model-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fhir-data-model-design
Source: https://github.com/StanfordSpezi/SpeziVibe/tree/main/skills/fhir-data-model-design
Command: npx skills add https://github.com/StanfordSpezi/SpeziVibe --skill fhir-data-model-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design a robust FHIR R4 data model for healthcare applications by translating clinical concepts into interoperable resources, terminology bindings, and implementation-ready relationships.

Core Features & Use Cases

  • Guidance to map clinical concepts to appropriate FHIR resources (e.g., Observation, Condition, QuestionnaireResponse) with rationale and suggested profiles.
  • Clear strategy for terminology bindings (LOINC, SNOMED CT, RxNorm, ICD-10-CM) and implementation guidance for resource relationships and data flows.
  • A structured workflow to produce a complete data model specification document ready for implementation, including data-flow diagrams and API patterns.

Quick Start

Provide clinical requirements and constraints, and I will output a complete FHIR data model specification document ready for implementation.

Frequently Asked Questions about fhir-data-model-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map clinical concepts to FHIR R4 resources for a healthcare app?

To map clinical concepts to FHIR R4 resources, you translate clinical requirements into appropriate resources like Observation or Condition, complete with terminology bindings and implementation-ready TypeScript types.

What is the best way to design a FHIR data model with LOINC and SNOMED CT bindings?

Designing a FHIR data model with LOINC and SNOMED CT bindings requires specifying terminology bindings, resource relationships, and data flows to produce a complete, interoperable Data Model Specification document.

Can I generate TypeScript types and API patterns from a FHIR R4 data model?

Yes, generating TypeScript types and API patterns is part of the FHIR R4 data modeling process, which outputs implementation-ready relationships and structured data flow diagrams for healthcare applications.

Does this FHIR data modeling approach support EHR integration and multiple clinical domains?

Yes, this FHIR data modeling approach supports EHR integration and multiple clinical domains by mapping clinical concepts to standards-based FHIR R4 resources with specified profiles and data flows.

How do I structure a complete FHIR data model specification document for implementation?

To structure a complete FHIR data model specification document, you provide clinical requirements and constraints to generate required resources, terminology bindings, profiles, and data-flow diagrams ready for implementation.

When do I need to use FHIR profiles and terminology bindings for healthcare interoperability?

You need to use FHIR profiles and terminology bindings for healthcare interoperability when your application requires standards-based data storage, structured API calls, and integration with external EHR systems.