Installation

@cosyte/ccda is a TypeScript C-CDA toolkit for Node.js. It ships dual ESM + CJS builds with per-condition type declarations, so it works from either module system without configuration, and it has a single exact-pinned runtime dependency: the hardened W3C-DOM substrate @xmldom/xmldom (C-CDA is XML, so a DOM is unavoidable).

Status: published on npm and public, still pre-alpha on the cosyte 0.0.x version ladder (0.0.x until first alpha). This page names no version number: run npm view @cosyte/ccda version for the current one. The install command below is live.

Prerequisites

• Node.js >= 22. The whole @cosyte/* suite targets ES2023 / Node 22+.
• A package manager: pnpm, npm, or yarn.
• One runtime dependency. @xmldom/xmldom (exact-pinned) is the only runtime dep; the parser caps itself at ≤ 3 justified deps. There is no native build and no post-install script.

Install

npm install @cosyte/ccda

Smoke test

Confirm the package resolves and a real entry point is callable. Parse the smallest valid US Realm ClinicalDocument and read its recognized document type back:

import { parseCcda } from "@cosyte/ccda";

// Synthetic header-only CCD: invented patient, fake OIDs. No real PHI.
const xml = `<?xml version="1.0" encoding="UTF-8"?>
<ClinicalDocument xmlns="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <realmCode code="US"/>
  <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="2.16.840.1.113883.19.5.99999.1" extension="DOC-0003"/>
  <code code="34133-9" codeSystem="2.16.840.1.113883.6.1"/>
  <title>Synthetic CCD</title>
  <effectiveTime value="20240101"/>
  <recordTarget><patientRole>
    <id root="2.16.840.1.113883.19.5" extension="MRN-0001" assigningAuthorityName="Sample Hospital"/>
    <patient>
      <name><given>Jane</given><family>Doe</family></name>
      <administrativeGenderCode code="F" codeSystem="2.16.840.1.113883.5.1"/>
    </patient>
  </patientRole></recordTarget>
</ClinicalDocument>`;

const doc = parseCcda(xml);

doc.documentType; // => "ccd"
doc.header.title; // => "Synthetic CCD"
doc.getPatient()?.name?.family; // => "Doe"
Array.isArray(doc.warnings); // => true

If that resolves and returns, the install is good. Head to the Quickstart.

Module systems

@cosyte/ccda is "type": "module" and exposes both conditions, so both of these resolve to the right build without extra configuration:

// ESM / TypeScript
import { parseCcda, serializeCcda } from "@cosyte/ccda";

// CommonJS
const { parseCcda, serializeCcda } = require("@cosyte/ccda");

The single top-level entry point (@cosyte/ccda) publishes per-condition types (.d.ts for import, .d.cts for require), gated by attw on every release. Editor IntelliSense matches the build you actually load.

PHI discipline

Every example in this documentation uses synthetic fixtures: an invented patient, obviously-fake OIDs and MRNs. Do the same in your own tests: a C-CDA document is a clinical record, and a real one committed to a repository is a PHI leak the moment it publishes. The parser helps: every warning and error message comes whole from a frozen registry and interpolates nothing at all, so no attribute value, coded token or element name from your document can reach one. See Troubleshooting for the full posture, including what changed and when.