exporting-to-fhir
把NER结果结构化为可交换的FHIR资源，便于下游系统接入。
需保证实体映射的临床准确性与术语编码合规。
将OpenMed的实体输出封装为FHIR R4资源（Condition等）并编码。
把 openmed.analyze_text 抽出的实体（NER spans）包装成合规的 FHIR R4 资源（如 Condition、MedicationStatement、Observation），生成 CodeableConcept、确定性 fullUrl 并产出 OperationOutcome 报告。在完成实体抽取后、需要把结果以标准 FHIR JSON 回写 EHR 或做互操作时使用。内置 openmed.clinical.exporters，能生成带 RxNorm/LOINC/ICD-10/SNOMED 编码的可验证资源。
▸ 展开 SKILL.md 英文原文
Convert OpenMed NER output (entities from openmed.analyze_text) into FHIR R4 resources — Condition, MedicationStatement, Observation — using OpenMed's built-in FHIR R4 export helpers in openmed.clinical.exporters. Covers the verified CodeableConcept builder (coding, codeable_concept, system_uri), deterministic fullUrl references, and OperationOutcome reporting. Use after running OpenMed NER when the user wants standards-conformant FHIR JSON, mentions FHIR, Condition/Observation/MedicationStatement, CodeableConcept, RxNorm/LOINC/ICD-10/SNOMED coding, or interoperability with an EHR. Pairs after extracting-clinical-entities; feeds assembling-fhir-bundles and validating-us-core.
帮我安装这个 skill：https://raw.githubusercontent.com/maziyarpanahi/openmed/master/skills/exporting-to-fhir/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/maziyarpanahi/openmed/master/skills/exporting-to-fhir/SKILL.md"# Exporting to FHIR OpenMed's NER (`openmed.analyze_text`) returns spans — text, label, offsets, confidence. To make those spans interoperable you wrap each clinically relevant span in a **FHIR R4 resource** (`Condition`, `MedicationStatement`, `Observation`, ...) carrying a coded `CodeableConcept`. OpenMed ships the **mechanical** R4 export helpers for this in `openmed.clinical.exporters`; you own the small amount of clinical mapping (which span becomes which resource). ## When to use Use this after NER, when the consumer is a FHIR system (an EHR, a registry, a data lake on FHIR). Reach for it when the user says "export to FHIR", "make a Condition/Observation", "build a CodeableConcept",