Create a Clinical Document Architecture Document

You can create a clinical document architecture (CDA) document in a project or a standalone environment (outside of a project). You then select the document in a healthcare action in an integration.

  1. To create a CDA document in a project:
    1. In the navigation pane, click Projects.
    2. Click the project in which to create the CDA document.
    3. Click Healthcare Healthcare icon.
    4. In the CDA documents section, click Add.
  2. To create a CDA document in a standalone environment:
    1. In the navigation pane, click Healthcare, then Schemas.
    2. On the Schemas page, click Create.
  3. Enter the following details.
    Element Description
    Name Enter a CDA document name.
    Identifier This field is automatically populated with a unique schema identifier based on your CDA document name. You can manually change this value, if needed.
    Description Enter an optional description of this CDA document.
    Standard View the HL7v3 CDA (with extensions) document standard. Only CDA is available and it cannot be deselected.
    Version Select the CDA document version to use.
    • R2 (Normative - No Extensions): The Release 2 (R2) version of the standard consisting of the officially recognized elements, data types, and structures. The standards published by the governing body are followed and there are no additional elements or customizations included.
    • R2 SDTC Approved Extensions: The R2 standard that includes the officially recognized elements, data types, and structures, along with a set of extensions approved by the Standards Development and Testing Committee (SDTC) for specific purposes. These are not arbitrary or custom extensions, but are officially sanctioned, providing additional functionality or compatibility (for example, to support regulatory requirements or specific workflows).
    Type View the document type. Only ClinicalDocument (Base document type for CDA) is available and it cannot be deselected. This type is the root XML element for all CDA documents, and provides a standardized structure for the exchange of clinical documents such as discharge summaries, progress notes, and continuity of care documents.
    Schema View the schema standard. Only Standard is available and it cannot be deselected.
    Identification expression (XPath) If you want to distinguish between different types of CDA XML documents, use this XPath expression and provide an identification value in the Identification value field (for example, 34133-9). This value is consumed by the 'code' parameter in the XPath expression. This value distinguishes between different types of CDA documents because the structure of CDA is the same.
    /*[local-name()='ClinicalDocument']/*[local-name()='code']/@code
    If you do not want to distinguish between the different types, then use the default CDA document root element of ClinicalDocument:
    /*[local-name()='ClinicalDocument']
    Identification value Optionally enter an identification value if you want to distinguish between different types of CDA XML documents in the Identification expression (XPath).
    Optional Schematron [Validation] Files (zipped) You can customize the CDA document with localized extensions and upload an XSD zip file.


    The Create CDA document shows the Name, Identifier, Description, Standard, Version, Type, Schema, Identification expression (XPath), Identification value, and Optional Schematron [Validation] Files (zipped) fields. You can drag and drop a zip file into this last field.

  4. Click Create.
    The CDA document selection is displayed. You can edit this document, as needed. See Edit or Clone a Clinical Document Architecture Document.

The created CDA document is now selectable in the healthcare action in the integration canvas. No explicit adapter configuration is required. The REST Adapter is implicitly used to pass the CDA document through the healthcare action. Because the CDA document is already in XML format, no translation is required.