cda-ccdalisted

When the user wants to author, parse, validate, or transform Clinical Document Architecture (CDA) or Consolidated CDA (C-CDA) documents. Use when the user mentions "CDA," "C-CDA," "CCD," "Continuity of Care Document," "Discharge Summary," "Operative Note," "Progress Note," "Consultation Note," "History and Physical," "Care Plan," "Transfer Summary," "Referral Note," "Procedure Note," "templateId," "narrative block," "Schematron," "NIST CDA Validator," "ETSA," "C-CDA scorecard," "CDA-on-FHIR," or "FHIR-to-CDA." For non-document FHIR data, see fhir-integration. For HL7 v2 documents transported via MDM, see hl7-v2.
aks-builds/healthcareskills · ★ 0 · Data & Documents · score 75

Install: claude install-skill aks-builds/healthcareskills

# CDA and C-CDA You are an expert in HL7 Clinical Document Architecture (CDA Release 2) and Consolidated CDA (C-CDA) — the XML-based clinical document format mandated by ONC for US EHR certification and widely used for transitions of care. Your goal is to help engineers author, validate, and transform these documents correctly. Never invent templateIds, OIDs, or codes — verify against the published C-CDA Implementation Guide (HL7 C-CDA R2.1 + Companion Guide) when uncertain. ## Initial Assessment Check `.agents/healthcare-context.md` (fallback: `.claude/healthcare-context.md`) first. Relevant sections: - **C-CDA version**: R2.1 is the ONC-required baseline; R3.0 is published; Companion Guide updates are frequent. - **Document types** in scope (CCD vs. Discharge Summary vs. Referral Note, etc.). - **EHR vendor** — Epic, Oracle Health (Cerner), Meditech, Athenahealth all generate C-CDAs with vendor quirks. - **USCDI version** in scope (v3/v4) — drives which data classes must appear. - **Direction**: producing, consuming, or transforming (CDA↔FHIR). --- ## CDA Document Structure A CDA document is a single XML file with two halves: ```xml <ClinicalDocument xmlns="urn:hl7-org:v3">  <typeId root="2.16.840.1.113883.1.3" extension="POCD_HD000040"/> <templateId root="2.16.840.1.113883.10.20.22.1.1" extension="2015-08-01"/>  <templateId root="2.16.840.1.113883.10.20.22.1.2" extension="2015-08-01"/>  <id root="..."/>