hims-fhir-specialist

Map and validate FHIR R4/R5 resources for HIMS interoperability with ABDM.

Updated Jan 3, 2026
One-click install
npx skills add https://github.com/CJCreator-New/care-harmony-hub --skill hims-fhir-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hims-fhir-specialist
Source: https://github.com/CJCreator-New/care-harmony-hub/tree/main/.agents/skills/hims-fhir-specialist
Command: npx skills add https://github.com/CJCreator-New/care-harmony-hub --skill hims-fhir-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexities of implementing and validating Fast Healthcare Interoperability Resources (FHIR) standards within Hospital Information Management Systems (HIMS), ensuring seamless data exchange for national health ecosystems.

Core Features & Use Cases

  • FHIR Resource Modeling: Assists in correctly modeling core FHIR resources like Patient, Encounter, and Observation.
  • Data Mapping & Validation: Facilitates mapping between internal HIMS data models and FHIR profiles, including ABDM-specific requirements.
  • Terminology Binding: Guides the correct use of standard terminologies such as SNOMED, LOINC, and ICD-11.
  • Security & Compliance: Provides insights into SMART on FHIR, OAuth 2.0, and consent management.
  • Bundle Management: Advises on creating effective FHIR bundles for transactions and search results.
  • Use Case: A developer needs to ensure that patient demographic data exported from their HIMS conforms to the ABDM FHIR Patient profile, including correct use of extensions and required fields.

Quick Start

Use the hims-fhir-specialist skill to validate a FHIR R4 Patient resource against ABDM profiles.

Frequently Asked Questions about hims-fhir-specialist

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

FAQPage Schema
How do I validate a FHIR R4 Patient resource against ABDM profiles?

To validate a FHIR R4 Patient resource against ABDM profiles, map your internal HIMS data to FHIR profiles, apply ABDM-specific extensions, and verify required fields to ensure national health ecosystem interoperability.

How do I map internal HIMS data models to FHIR resources?

Mapping internal HIMS data models to FHIR resources requires aligning your internal fields with FHIR profiles, applying terminology binding for standard codes like SNOMED and LOINC, and structuring data into transaction bundles.

What is terminology binding in FHIR and how does it work with ICD-11?

Terminology binding in FHIR links resource elements to standard clinical vocabularies. You bind ICD-11 codes to specific fields like Condition.code, ensuring standardized diagnosis data exchange across HIMS platforms.

Does SMART on FHIR work with OAuth 2.0 for HIMS security?

SMART on FHIR integrates with OAuth 2.0 to secure HIMS applications, managing authentication, API access scopes, and patient consent protocols for protected health data exchange.

When do I need ABDM-specific extensions for FHIR resources?

ABDM-specific extensions for FHIR resources are required when integrating with Indian national health ecosystems, ensuring local demographic fields and identifiers meet Ayushman Bharat Digital Mission compliance standards.

How do I create FHIR bundles for HIMS transaction processing?

Creating FHIR bundles for HIMS transaction processing involves grouping multiple resources like Patient and Encounter into a single transaction or search result bundle, ensuring atomic processing and data consistency.