assembling-fhir-bundles

Package FHIR R4 resources into transaction or batch Bundles with deterministic fullUrls.

5.0k|615|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/maziyarpanahi/openmed --skill assembling-fhir-bundles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assembling-fhir-bundles
Source: https://github.com/maziyarpanahi/openmed/tree/main/skills/assembling-fhir-bundles
Command: npx skills add https://github.com/maziyarpanahi/openmed --skill assembling-fhir-bundles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill packages multiple standalone FHIR R4 resources into a single valid Bundle, rewrites internal references safely, and prepares transaction or batch payloads for submission to an EHR.

Core Features & Use Cases

  • Deterministic Bundling: Generates stable urn:uuid fullUrls from a document identifier and resource index for reproducible output.
  • Reference Resolution: Rewrites references such as Patient/id to matching in-Bundle fullUrls while preserving external references.
  • Transaction Preparation: Adds request blocks for transaction and batch Bundles, supports conditional create, and highlights validation and de-identification handoffs.
  • Use Case: Combine a de-identified Patient, Condition, and MedicationStatement into an atomic transaction Bundle that can be posted to a FHIR server with resolvable internal references.

Quick Start

Use the assembling-fhir-bundles skill to package the provided FHIR resources into a deterministic transaction Bundle for posting to the target EHR.

Frequently Asked Questions about assembling-fhir-bundles

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

FAQPage Schema
How do I package multiple FHIR R4 resources into a single transaction Bundle?

To create a FHIR transaction Bundle, you package standalone resources like Patient, Condition, and Observation together, generate deterministic urn:uuid fullUrls, and add request blocks for atomic submission to an EHR.

How does reference rewriting work when building a FHIR Bundle?

Reference rewriting in a FHIR Bundle replaces internal references such as Patient/id with matching in-Bundle fullUrls, ensuring all resource links resolve correctly within the transaction payload while preserving any external references.

What is the difference between a FHIR transaction Bundle and a batch Bundle?

A FHIR transaction Bundle processes all resources as a single atomic unit that succeeds or fails together, while a batch Bundle processes each resource independently, allowing partial success across the submitted payload.

Can I use conditional create when submitting FHIR resources to an EHR?

Yes, conditional create is supported for FHIR transaction and batch Bundles by adding optional request parameters, allowing the EHR server to only create resources if specific criteria are not already met.

Why do my FHIR Bundle internal references fail to resolve on the target server?

FHIR Bundle reference resolution fails when internal references like Patient/id are not rewritten to match the deterministic urn:uuid fullUrls generated for each resource within the assembled transaction payload.

Do I need a stable document identifier to generate FHIR Bundle fullUrls?

Yes, a stable document identifier combined with the resource index is required to generate deterministic urn:uuid fullUrls, which ensures reproducible FHIR Bundle output for clinical interoperability workflows.