Planned Encounter - Referral

back to homepage

Approval Status

  • Approval Status: Approved
  • Example Task Force: 9/24/2015
  • SDWG: 10/15/2015
  • SDWG C-CDA R2.1 Upgrade: 2/2/2017

C-CDA 2.1 Example:

  • 2.16.840.1.113883.
  • 2.16.840.1.113883.
  • 2.16.840.1.113883.
  • 2.16.840.1.113883.
  • 2.16.840.1.113883.
  • 2.16.840.1.113883.
  • 2.16.840.1.113883.

Reference to full CDA sample:

  • Empty CCD

Validation location


  • This example illustrates how to structure a Referral for the 170.314(b)(2) Transitions of care - N) Referral


  • ONC


  • George Cole


  • Planned Encounter, Reason for Referral




Example: download example view on GitHub

<!-- Transition of Care snips to show Referral from test data for 170.314b2 Ambulatory
N)	Referral
 - Pulmonary function tests, Dr. Penny Puffer, Tel: 555-555-1049, 1047 Healthcare Drive, Portland, OR 97005, Scheduled date: Test date + 2 days 
The minimal content to include for the stated test data is text in the Reason for Referral section, and that is shown below as the first section of this example.

This example also includes details of the referral as text and Planned Encounter discrete entry in the Plan of Treatment section. Depending upon how the test data are interpreted,
there are systems that might very well represent the data in the Plan of Treatment section, based upon the test data statement about Scheduled date.

    <!-- This ClinicalDocument's structure is stubbed with the minimum elements necessary
         to demonstrate the locations of the entries across multiple different sections;
         however, required content like the document header and section LOINC codes
         has been omitted. -->
            <!-- here is the minimally necessary Reason for Referral section with the text showing the scheduled referral
            			note: depending upon how the test data are interpreted the content of the text may vary as regards the Scheduled date.
                    <templateId root=""/>
                    <code code="42349-1" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" displayName="Reason For Referral"/>
                    <title>Reason For Referral</title>
                    <text>Pulmonary function tests, Dr. Penny Puffer, Tel: 555-555-1049, 1047 Healthcare Drive, Portland, OR 97005, Scheduled date: 08/17/2012</text>
            <!-- here is the optional section for Plan of Care with the Planned Encounter -->
                    <templateId root="2.16.840.1.113883." extension="2014-06-09"/>
                    <templateId root="2.16.840.1.113883."/>
                    <code code="18776-5" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" displayName="Plan of care note"/>
                    <title>Plan of Care</title>
                    <!-- one Planned Encounter in the human readable text and as a discrete entry -->
                        <!-- this section may contain many different Planned items, so we use the table caption to help identify each -->
                            <caption>Planned Encounters</caption>
                                    <td ID="ID0EFFFFFFCA">
                                        <content ID="ID0EFAAAAACA">Pulmonary Function Tests; Dr. Penny Puffer, Tel: 555-555-1049, 1047 Healthcare Drive, Portland OR 97005</content>
                                    <td ID="ID0EAAAAAAAAACA">Indication: Costal Chondritis</td>
                    <!-- a planned encounter entry -->
                        <!-- encounter with moodCode indicating Intent -->
                        <encounter classCode="ENC" moodCode="INT">
                            <!-- Planned Encounter templateId -->
                            <templateId root="2.16.840.1.113883." extension="2014-06-09"/>
                            <templateId root="2.16.840.1.113883."/>
                            <id extension="52487" root=""/>
                            <!-- templateId and id are all that are required or specified in C-CDA R1.1; with C-CDA R2.0 the documentation changes quite a bit -->
                            <!-- code from the Planned Encounter Type value set; 11429006 is reflective of the example data, but local policy and use may result in selection of a different code -->
                            <code codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT" code="11429006" displayName="Consultation">
                                <!-- referencing back to the text of the type-->
                                    <reference value="#ID0EFAAAAACA"/>
                                <!-- referencing the entire text -->
                                <reference value="#ID0EFFFFFFCA"/>
                            <statusCode code="active"/>
                                <!-- appointment requested for Test date + 2 days , so 8/17/2012 -->
                                <low value="20120817"/>
                            <!-- the requested Penny Puffer provider -->
                            <performer typeCode="PRF">
                                    <id extension="3333333333" root="2.16.840.1.113883.4.6"/>
                                        <streetAddressLine>1047 Healthcare Dr</streetAddressLine>
                                    <telecom value="tel:+1-(555)555-1049"/>
                            <!-- Penny Puffer office location as a service delivery location -->
                            <participant typeCode="LOC">
                                <participantRole classCode="SDLOC">
                                    <templateId root="2.16.840.1.113883."/>
                                    <code code="1212-0" codeSystem="2.16.840.1.113883.6.259" displayName="Mixed Age Mixed Acuity Unit"/>
                                    <telecom nullFlavor="UNK"/>
                                    <playingEntity classCode="PLC">
                                        <name>Dr. Penny Puffer Office</name>
                            <!-- this references the indication (reason) for the planned encounter; example data suggests the reason was the encounter diagnosis
            					L)	Encounter Diagnosis
            						 - Costal Chondritis, [SNOMED-CT: 64109004], Start: 8/15/2012, Active
                            <entryRelationship typeCode="RSON">
                                <observation classCode="OBS" moodCode="EVN">
                                    <templateId root="2.16.840.1.113883." extension="2014-06-09"/>
                                    <templateId root="2.16.840.1.113883."/>
                                    <id extension="45678" root=""/>
                                    <code codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT" code="282291009" displayName="Diagnosis interpretation"/>
                                        <reference value="#ID0EAAAAAAAAACA"/>
                                    <statusCode code="completed"/>
                                        <low value="20120815"/>
                                    <!-- includes the code for Costal Chondritis -->
                                    <value xsi:type="CD" code="64109004" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT" displayName="Costal chondritis"/>
  1. C-CDA Example Search Help

    C-CDA Example Search Results
    This screen displays the results of executing the example search criteria against the existing examples recorded in the example database.

  2. Search Criteria Panel

    This panel allow you to further refine your queries and narrow the results

  3. Text Search Words

    Use this field to enter words related to your search. These words can appear in the title, the comments or as part of a special list of keywords associated with the example. The search words should be entered with spaces separating the items.

  4. Filter by example status

    By selecting the various statuses, the search results can be limited to only the example that are set to the selected status(es). By removing all status selections, the filtering is removed and examples from all statuses will be returned (based on any other filtering).

  5. Select only ONC Certified examples

    These are samples referenced in a government rule or certification companion guide.

  6. Execute the search based on the criteria entered (or retrieve all examples if no criteria specified).

  7. The number of results that match the query parameters can be found here.

  8. Use this link to jump back to the initial page of the application (that lists the sections).

  9. This columns list the names of the examples that match the criteria (and the comment for each example).

  10. This columns lists the area in the C-CDA specification (the specification is broken into distinct topics for the various exchangeable documents, the common header, and the sections that occur within the exchangeable documents) that the example demonstrates.

  11. This columns lists the state of the example in the example verification and approval process.

  12. You can select to download the examples directly or navigate to page with the full detailed description of the example.

  13. Tour Complete

    Return to the C-CDA Example Search Results page.