Outpatient Encounter with Diagnoses

return to Main screen return to result list

Example metadata last updated 2017-09-11 05:11:32.269000 UTC

Approval Status: Approved

  • Approval Status: Approved
  • Example Task Force: 5/7/2015
  • SDWG: 5/28/2015
  • SDWG C-CDA R2.1 Upgrade: 2/2/2017

SITE C-CDA Validator

ONC Certification

Comments:

  • This example illustrates how to structure Encounter Diagnosis for the 170.314(b)(2) Transitions of care - L) Encounter Diagnosis

Custodian: Lisa Nelson (GitHub: lisarnelson)

Full sample: Encounter in empty CCD

Example: download example view on GitHub

<section>
    <!-- *** Encounters section (entries required) (V3) *** -->
    <templateId root="2.16.840.1.113883.10.20.22.2.22.1" extension="2015-08-01"/>
    <templateId root="2.16.840.1.113883.10.20.22.2.22.1"/>
    <code code="46240-8" codeSystem="2.16.840.1.113883.6.1" displayName="Encounters"/>
    <title>ENCOUNTERS</title>
    <text>
        <table border="1" width="100%">
            <thead>
                <tr>
                    <th>Encounter</th>
                    <th>Performer</th>
                    <th>Location</th>
                    <th>Encounter date</th>
                    <th>Diagnosis</th>
                    <th>Diagnosis Status</th>
                </tr>
            </thead>
            <tbody>
                <tr ID="Encounter1">
                    <td ID="Encounter1_type">Office outpatient visit</td>
                    <td>Dr. Samir Kahn <content ID="Encounter1_performer_type">Internal Medicine</content> </td>
                    <td>Community Urgent Care (Urgent Care Center)
                        <paragraph>1004 Healthcare Dr.</paragraph>
                        <paragraph>Portland, OR  97005</paragraph>
                    </td>
                    <td>August 15, 2012</td>
                    <td ID="Encounter1_diagnosis">Costal Chondritis</td>
                    <td ID="Encounter1_diagnosis_status">Active</td>
                </tr>
            </tbody>
        </table>
    </text>
    <entry typeCode="DRIV">
        <encounter classCode="ENC" moodCode="EVN">
            <!-- ** Encounter Activity (V3) ** -->
            <templateId root="2.16.840.1.113883.10.20.22.4.49" extension="2015-08-01"/>
            <templateId root="2.16.840.1.113883.10.20.22.4.49"/>
            <id root="2a620155-9d11-439e-92b3-5d9815ff4de8"/>
            <!-- Selected reasonable encounter/code. Not in test data -->
            <code code="99213" displayName="Office outpatient visit 15 minutes"
                codeSystemName="CPT" codeSystem="2.16.840.1.113883.6.12"
                codeSystemVersion="4">
                <originalText><reference value="#Encounter1_type"/>
                </originalText>
            </code>
            <text><reference value="#Encounter1"></reference></text>
            <!-- August 15, 2012 - added time (pacific time) since but not present in test data -->
            <effectiveTime value="201208151000-0800"/>
            <!-- Not specified in test data, but could infer Dr. Khan from the test scenario narrative-->
            <performer>
                <assignedEntity>
                    <!-- Fake Provider NPI "12345678910" -->
                    <id root="2.16.840.1.113883.4.6" extension="12345678910"/>
                    <code code="207R00000X" codeSystem="2.16.840.1.113883.6.101"
                        codeSystemName="Health Care Provider Taxonomy" 
                        displayName="Internal Medicine">
                        <originalText><reference value="Encounter1_performer_type"></reference></originalText>
                    </code>
                    <assignedPerson>
                        <name>
                            <prefix>Dr.</prefix>
                            <given>Samir</given>
                            <family>Khan</family>
                            <!--  Could alternately use <suffix>MD</suffix> -->
                        </name>                                        
                    </assignedPerson>
                </assignedEntity>
            </performer>
            <participant typeCode="LOC">
                <!-- Location is inferred from the care team address in test data -->
                <participantRole classCode="SDLOC">
                    <templateId root="2.16.840.1.113883.10.20.22.4.32"/>
                    <!-- Service Delivery Location template -->
                    <code code="1160-1" codeSystem="2.16.840.1.113883.6.259"
                        codeSystemName="HealthcareServiceLocation"
                        displayName="Urgent Care Center"/>
                    <addr>
                        <streetAddressLine>1004 Healthcare Dr.</streetAddressLine>
                        <city>Portland</city>
                        <state>OR</state>
                        <postalCode>97005</postalCode>
                    </addr>
                    <telecom value="tel:+1(555)555-1004"/>
                    <playingEntity classCode="PLC">
                        <name>Get Well Clinic</name>
                    </playingEntity>
                </participantRole>
            </participant>
            <entryRelationship typeCode="REFR">
                <act classCode="ACT" moodCode="EVN">
                    <!-- Encounter Diagnosis -->
                    <templateId root="2.16.840.1.113883.10.20.22.4.80" extension="2015-08-01" />
                    <templateId root="2.16.840.1.113883.10.20.22.4.80"/>
                    <code code="29308-4" displayName="Diagnosis"
                        codeSystem="2.16.840.1.113883.6.1"
                        codeSystemName="LOINC"/>
                    <!-- This example uses the Problem Status Observation to represent status of the diagnosis.
                                     The statusCode of the encounter diagnosis is an alternative approach.-->
                    <entryRelationship typeCode="SUBJ">
                        <observation classCode="OBS" moodCode="EVN">
                            <!-- Problem Observation -->
                            <templateId root="2.16.840.1.113883.10.20.22.4.4" extension="2015-08-01" />
                            <templateId root="2.16.840.1.113883.10.20.22.4.4"/>
                            <id root="db734647-fc99-424c-a864-7e3cda82e704"/>
                            <code code="282291009" displayName="Diagnosis" codeSystem="2.16.840.1.113883.6.96"
                                codeSystemName="SNOMED CT">
                                <translation code="29308-4" displayName="Diagnosis" codeSystem="2.16.840.1.113883.6.1"
                                    codeSystemName="LOINC"/>
                            </code>
                            <statusCode code="completed"/>
                            <!-- This same data may be represented in the Problem List -->
                            <effectiveTime>
                                <low value="20120815"/>
                            </effectiveTime>
                            <!-- Test data is SNOMED but in practice this is probably an ICD9/10 code -->
                            <value xsi:type="CD" code="64109004" displayName="Costal Chondritis"
                                codeSystem="2.16.840.1.113883.6.96">
                                <originalText><reference value="#Encounter1_diagnosis"></reference></originalText>
                            </value>
                            <entryRelationship typeCode="REFR">
                                <observation classCode="OBS" moodCode="EVN"> 
                                    <!-- Problem Status which is strange on an encounter diagnosis but 
                                                         included due to the test data -->
                                    <!-- C-CDA R2.0 deprecated this template -->
                                    <templateId root="2.16.840.1.113883.10.20.22.4.6"/>
                                    <code code="33999-4" displayName="Status"
                                        codeSystem="2.16.840.1.113883.6.1"
                                        codeSystemName="LOINC"/>
                                    <statusCode code="completed"/>
                                    <value xsi:type="CD" code="55561003" displayName="Active"
                                        codeSystem="2.16.840.1.113883.6.96">
                                        <originalText><reference value="#Encounter1_diagnosis_status"></reference></originalText>
                                    </value>
                                </observation>                                             
                            </entryRelationship>
                        </observation>
                    </entryRelationship>
                </act>
            </entryRelationship>
        </encounter>
    </entry>
</section>
  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.