Academy
⌘K
Getting Started
  • Platform Overview
  • AWS Marketplace Setup
  • Quickstart Guide
Connections
  • Overview
Workflow Builder
  • Overview
  • Nodes Catalog
Helix AI Assistant
  • Overview
Mapping Engine
  • Overview
Workflow Library
  • Overview
  • HL7
  • FHIR
  • Insurance
  • Agentic
  • Mapping
Security & Infrastructure
  • Architecture
  • HIPAA Compliance
  • Performance & Scalability
← Back to ConnectHealth
Get Started
Back to Nodes
CCDA1 input → 1 output

CCDA Parse

payload (string)CCDACCDA Parsepayload (object)ch.ccda.operat… (string)ch.ccda.output… (string)Data flowProperty

Parses a CCDA (C-CDA) XML document — any genuine C-CDA document type (CCD, Discharge Summary, Referral Note, ...) — into structured JSON, with an optional FHIR Bundle output.

Inputs

payload string
Raw CCDA (C-CDA) XML document text.

Outputs

payload object
Structured JSON (default) or a FHIR Bundle, per the Output format setting.
ch.ccda.operation string
Always "parse".
ch.ccda.outputFormat string
"structured" or "fhir".
ch.ccda.parsed object
Deep copy of the parsed output (same content as payload) — kept here so it survives msg.payload being overwritten by a later node further along the flow.

Details

Any genuine C-CDA document type is accepted — CCD, Discharge Summary, Referral Note, etc. are all structurally identical CDA R2 documents at the level this node validates (a structured body and a patient record), so no document-type gating is applied. This checks structural CDA R2 validity only, not per-document-type business rules (e.g. it doesn't check that a Discharge Summary carries the specific sections ONC expects of one).

The raw XML parse alone is not directly usable by most workflows — code systems come through as bare OIDs and the entry structure is deeply nested. Selecting the FHIR Bundle output resolves code systems into standard FHIR coding (e.g. http://snomed.info/sct), with no extra mapping work required.

Error Handling

Reports a structured, non-crashing error for:

  • Empty or non-string input
  • Input that isn't XML, or has no <ClinicalDocument> root
  • Input that doesn't identify as an HL7 CDA R2 ClinicalDocument
  • A document missing a structured body or patient (recordTarget)