Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-40773

Preferred Language vs Communication Language

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Core (FHIR)
    • 5.0.1
    • Cross-Group Projects
    • US Core Patient Profile
    • Hide

      Background:

      This interpretation of USCDI preferred language has stayed the same since Argonaut Data Query (Feb 15, 2017).

      Decision:

      Add to Profile Specific Implementation Guidance:{}

      The Communication.preferred element MAY be used when multiple languages are indicated.  

       

      Show
      Background: This interpretation of USCDI preferred language has stayed the same since Argonaut Data Query (Feb 15, 2017). Decision: Add to Profile Specific Implementation Guidance: { } The Communication.preferred element MAY be used when multiple languages are indicated.    
    • Eric Haas/Brett Marquard: 17-0-0
    • Clarification
    • Non-substantive

    Description

      This is an issue with most (all?) versions of US Core.

      USCDI defines "Preferred Language": https://www.healthit.gov/isa/taxonomy/term/751/uscdi-v1

      US Core Patient has, under "Additional USCDI Requirements", "a communication language". US Core Patient has constrained Patient.communication.language, but there is no constraint on the boolean Patient.communication.preferred.

      Actually not sure if this is an issue with USCDI (The data element isn't well defined - is the element correctly named as "Preferred" Language?) or an issue with US Core.

      Attachments

        Activity

          People

            Unassigned Unassigned
            minigrrl Sarah Gaunt
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: