cda-ccda

Create, validate, and transform CDA and C-CDA clinical documents.

1|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/aks-builds/healthcareskills --skill cda-ccda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cda-ccda
Source: https://github.com/aks-builds/healthcareskills/tree/main/skills/cda-ccda
Command: npx skills add https://github.com/aks-builds/healthcareskills --skill cda-ccda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive support for handling Clinical Document Architecture (CDA) and Consolidated CDA (C-CDA) documents, crucial for healthcare software development, ensuring accurate creation, validation, and transformation of clinical documents.

Core Features & Use Cases

  • CDA/C-CDA Creation and Validation: Author, parse, validate, and transform CDA and C-CDA documents with precision.
  • Document Structure Expertise: In-depth knowledge of CDA/C-CDA document structure, including headers, body sections, and entries.
  • TemplateId Management: Ensures correct use of TemplateIds for document validation and conformance.
  • USCDI Alignment: Ensures alignment with US Core Data for Interoperability (USCDI) standards.
  • Use Case: Develop a FHIR-to-CDA transformation pipeline for interoperability between FHIR and C-CDA formats.

Quick Start

Use the cda-ccda skill to validate the CDA document 'patient-discharge_summary.cda'.

Frequently Asked Questions about cda-ccda

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

FAQPage Schema
How do I validate a C-CDA document for USCDI compliance?

To validate a C-CDA document for USCDI compliance, you need to parse the clinical document structure, verify header and body sections, and ensure correct TemplateId management for interoperability conformance.

What is the best way to transform FHIR data into a C-CDA format?

Transforming FHIR data into a C-CDA format requires mapping resource fields to CDA headers and body entries while ensuring the resulting document adheres to clinical document standards and USCDI requirements.

How does TemplateId management work in CDA document validation?

TemplateId management in CDA validation ensures correct template identifiers are applied to document sections and entries, verifying that the clinical document conforms to required structural and interoperability standards.

Do I need to understand CDA headers and body sections to author C-CDA documents?

Yes, authoring C-CDA documents requires in-depth knowledge of CDA structure, including how to correctly construct headers, body sections, and entries to meet clinical document architecture standards.

Can I parse and validate CDA documents without external dependencies?

Yes, you can parse and validate CDA documents using built-in scripts and references without external dependencies, ensuring accurate handling of clinical document architecture and interoperability standards.

Why does my C-CDA document fail interoperability checks?

C-CDA documents fail interoperability checks when TemplateIds are mismanaged, document structure is incorrect, or the content lacks alignment with US Core Data for Interoperability standards.