Multiple Patient Identifiers

back to homepage

Approval Status

  • Approval Status: Approved
  • Example Task Force: 7/27/2017
  • SDWG: 10/5/2017

C-CDA 2.1 Example:

  • 2.16.840.1.113883.10.20.22.1.1:2015-08-01

Reference to full CDA sample:

  • Empty CCD

Validation location

  • https://sitenv.org/sandbox-ccda/ccda-validator

Comments

  • This demonstrates a patient with multiple identifiers from different institutions.

Custodian

  • Lisa Nelson

Keywords

  • recordTarget, patient, identifiers

Permalink

Links

 

Example: download example view on GitHub

<!-- Note: several other data elements are required to meet C-CDA R2.1 requirements -->
    <recordTarget>
        <patientRole>
            <!-- Here is the medical record number of this patient at the nested provider organization.
                 This examples assumes the OID 2.16.840.1.113883.1.111.12345 
                 uniquely identifies the encompassed Provider Organization's local 
                 medical record number assigning system.-->
            <!-- A receiving system only knows this is an MRN by looking up the root oid in a repository. -->
            <id root="2.16.840.1.113883.1.111.12345" extension="12345" 
                assigningAuthorityName="River Valley Health Services Locally-assigned Medical Record Number"/>
            <!-- Here are additional identifiers different care organizations. 
                OIDs are synthetic. Production implementations use the actual OID registered for the assigningAuthority. -->
            <id root="1.3.6.1.4.1.1234.13.20.9999.1.3.7.4" extension="6789" assigningAuthorityName="Lawrence and Memorial: Westerly Hospital locally assigned Medical Record Number"/>
            <id root="1.3.6.1.4.1.1234.13.20.9999.1.3.7.3" extension="2345" assigningAuthorityName="LifeSpan: Buttler Hospital Locally-assigned Patient Account Number"/>
            <id root="1.3.6.1.4.1.1234.13.20.9999.1.3.7.6" extension="06726-161" assigningAuthorityName="Rhode Island Qyality Institute: CurrentCare HIE Locally-assigned Identifier"/>
            <!-- More ids may be used. -->
            <addr>
                <streetAddressLine>1 Happy Valley Road</streetAddressLine>
                <city>Westerly</city>
                <state>RI</state>
                <postalCode>02891</postalCode>
                <country nullFlavor="UNK"/>
            </addr>
            <telecom use="WP" value="tel:+1(401)348-2345"/>
            <telecom use="HP" value="tel:+1(401)641-2345"/>
            <telecom value="mailto:lindanelson@gmail.edu"/>
            <patient>
                <name use="L">
                    <family>Nelson</family>
                    <given qualifier="CL">Linda</given>
                </name>
                <administrativeGenderCode code="F" displayName="Female"
                    codeSystem="2.16.840.1.113883.5.1" codeSystemName="HL7 AdministrativeGender"/>
                <birthTime value="19620828"/>
                <maritalStatusCode code="M" displayName="Married" codeSystem="2.16.840.1.113883.5.2"
                    codeSystemName="HL7 MaritalStatus"/>
                <raceCode code="2106-3" displayName="White" codeSystem="2.16.840.1.113883.6.238"
                    codeSystemName="CDC Race and Ethnicity"/>
                <ethnicGroupCode code="2186-5" displayName="Not Hispanic or Latino"
                    codeSystem="2.16.840.1.113883.6.238" codeSystemName="CDC Race and Ethnicity"/>
                <languageCommunication>
                    <templateId root="2.16.840.1.113883.3.88.11.32.2"/>
                    <languageCode code="eng"/>
                    <preferenceInd value="true"/>
                </languageCommunication>
            </patient>
            <providerOrganization>
                <!-- This is a synthetic OID for the example.  
                    Production implementations use the actual OID registered 
                    for the designated assigningAuthority. -->
                <!-- A receiving system only knows this is an MRN by looking up the root oid in a repository. -->
                <id root="2.16.840.1.113883.1.111.12345" 
                    assigningAuthorityName="River Valley Health Services local patient Medical Record Number" />
                <!-- More ids may be used. -->
                <name>River Valley Health Services</name>
                <telecom use="WP" value="tel:+1(401)539-4321"/>
                <addr>
                    <streetAddressLine>823 Main Street</streetAddressLine>
                    <city>River Valley</city>
                    <state>RI</state>
                    <postalCode>028321</postalCode>
                    <country>US</country>
                </addr>
            </providerOrganization>
        </patientRole>
    </recordTarget>
  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.