exporting-to-fhir

Convert OpenMed clinical entity spans into standards-conformant FHIR R4 resources.

5.0k|615|Updated Oct 4, 2025

Search Tags:#fhir #healthcare data #medical coding #openmed #clinical interoperability #ehr integration #codeableconcept

Ready to run

npx skills add https://github.com/maziyarpanahi/openmed --skill exporting-to-fhir

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: exporting-to-fhir
Source: https://github.com/maziyarpanahi/openmed/tree/main/skills/exporting-to-fhir
Command: npx skills add https://github.com/maziyarpanahi/openmed --skill exporting-to-fhir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts OpenMed clinical entity output into structured, standards-conformant FHIR R4 resources without requiring manual JSON construction.

Core Features & Use Cases

FHIR Resource Export: Transform disease, medication, laboratory, vital-sign, procedure, and allergy entities into appropriate FHIR resources.
CodeableConcept Construction: Build deterministic coded concepts using RxNorm, LOINC, ICD-10-CM, SNOMED, HPO, MeSH, or custom terminology system URIs.
Interoperability Reporting: Create stable resource references and OperationOutcome issues for incomplete mappings or validation concerns.
Use Case: After extracting entities from a clinical note, create a coded Condition for diabetes, a MedicationStatement for metformin, and an Observation for HbA1c that can be passed to an EHR or FHIR data lake.

Quick Start

Use the exporting-to-fhir skill after OpenMed NER to convert the extracted entities into coded FHIR R4 resources with stable references and warnings for unmapped concepts.

Frequently Asked Questions about exporting-to-fhir

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

FAQPage Schema

How do I convert extracted clinical entities into FHIR R4 resources?▼

You can transform extracted clinical entity spans into coded FHIR R4 resources by applying deterministic CodeableConcept construction and stable fullUrl references, avoiding manual JSON building for EHR interoperability workflows.

What is the best way to build CodeableConcept elements for clinical data exchange?▼

Building deterministic CodeableConcept elements for FHIR exchange involves mapping clinical entities to canonical terminology URIs like RxNorm, LOINC, ICD-10-CM, SNOMED, HPO, or MeSH to ensure standards-conformant coded concepts.

How do I export clinical notes to a FHIR data lake after NER extraction?▼

Exporting clinical notes to a FHIR data lake post-NER involves converting extracted clinical entities into coded Conditions, MedicationStatements, and Observations with stable resource references and OperationOutcome reporting for validation warnings.

Does this approach handle unmapped medical codes during FHIR resource generation?▼

Yes, unmapped medical codes are handled during FHIR resource generation by creating OperationOutcome issues that report incomplete mappings and validation concerns, ensuring terminology-grounded resources for clinical data lakes.

Can I use custom terminology system URIs for clinical interoperability?▼

Yes, you can use custom terminology system URIs alongside standard systems like RxNorm, LOINC, and SNOMED for CodeableConcept construction, enabling flexible clinical interoperability and specialized healthcare exchange workflows.

When do I need OperationOutcome reporting for FHIR resource exports?▼

OperationOutcome reporting is needed for FHIR resource exports when validating incomplete terminology mappings or flagging clinical data concerns, ensuring downstream EHR systems and data lakes receive accurate warnings about unmapped concepts.