> ## Documentation Index
> Fetch the complete documentation index at: https://help.elationhealth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# retrieve-ccda

> Retrieve a single patient's ccda

<Note>
  **Allergies and `end_date`.** When you pass `end_date`, an allergy added to the chart after that date is excluded from the returned document. However, an allergy's active/inactive status is not tracked with a point-in-time history: if an allergy was later marked inactive or resolved, the returned document reflects its current status, not necessarily its status as of `end_date`.
</Note>

<Note>
  **Assessment-to-Plan linking depends on the source visit note's format.** In the returned CCDA, a diagnosis (Assessment) is only linked to its specific plan items (Plan of Treatment) when the underlying visit note uses a format with a combined Assessment/Plan section (`Assessplan` category) — see [Visit Note Formats](/articles/rest/patient-document-api/visit-notes/visit-note-formats). For notes using a format with separate Assessment and Plan fields (e.g. **SOAP**), both the diagnosis and the plan content are present in the document, but without a structural link between them.
</Note>


## OpenAPI

````yaml get /api/2.0/ccda/{id}/
openapi: 3.1.0
info:
  contact:
    name: Elation Health
    url: https://www.elationhealth.com/
  description: Elation Health API v2.0
  title: Elation Health API
  version: 2.0.0
servers:
  - description: Sandbox Server
    url: https://sandbox.elationemr.com
  - description: Production Server
    url: https://api.app.elationemr.com
security: []
paths:
  /api/2.0/ccda/{id}/:
    get:
      tags:
        - CCDA
      summary: Retrieve Ccda
      description: Retrieve a single patient's ccda
      operationId: ccda_retrieve
      parameters:
        - description: The end date of the CCDA to retrieve.
          in: query
          name: end_date
          schema:
            format: date
            type: string
        - description: The id of the patient to retrieve the CCDA for.
          in: path
          name: id
          required: true
          schema:
            type: integer
        - description: >-
            A comma-separated list of sections to include in the CCDA. If not
            provided, all sections will be included.
          in: query
          name: sections
          schema:
            items:
              type: string
            type: array
        - description: The start date of the CCDA to retrieve.
          in: query
          name: start_date
          schema:
            format: date
            type: string
        - description: The template used to display the desired information on the CCDA
          in: query
          name: template
          schema:
            enum:
              - generateCCD
              - generateCarePlan
              - generateProgressNote
              - generateReferralNote
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CCDA'
          description: ''
      security:
        - oauth2: []
components:
  schemas:
    CCDA:
      properties:
        base64_ccda:
          format: binary
          readOnly: true
          type: string
        id:
          format: int64
          type: integer
      required:
        - id
      type: object
  securitySchemes:
    oauth2:
      flows:
        clientCredentials:
          scopes:
            act_as_user: >-
              Impersonate a provider via X-On-Behalf-Of (combinable with apiv2
              or system scopes)
            apiv2: Full access to the API
            system/{resource_name}.read: Read access to a specific resource
            system/{resource_name}.write: Write access to a specific resource
          tokenUrl: /api/2.0/oauth2/token/
      type: oauth2

````