2015May core #919 - Why are Practitioner.communication and Patient.communication different?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Administration
    • Practitioner
    • Hide

      These fields perform different purposes. On the patient we are able to check to see what languages are required, then on the Practitioner we are using it as a search parameter to locate someone who can speak the language, if it's their preferred language is not really relevant. The proficiency in the language is not recorded. There is an extension for modes of communication under HSPC that covers that also (for read/write/speak/listen) There is also a standard extension on patient indicating that they require an interpreter - meaning they do not speak the implied language commonly used in the organization.

      Show
      These fields perform different purposes. On the patient we are able to check to see what languages are required, then on the Practitioner we are using it as a search parameter to locate someone who can speak the language, if it's their preferred language is not really relevant. The proficiency in the language is not recorded. There is an extension for modes of communication under HSPC that covers that also (for read/write/speak/listen) There is also a standard extension on patient indicating that they require an interpreter - meaning they do not speak the implied language commonly used in the organization.
    • Brian/Alex:4-0-0
    • Clarification

      Existing Wording: Practitioner.communication

      Comment:

      Practitioner.communication is modeled differently from patient.communication. Yet, I am not sure there is strong justification for the difference. I recommend that both be modeled in the same way. After all, a provider may speak different languages and have a preferred one.

            Assignee:
            Unassigned
            Reporter:
            Claude Nanjo (Inactive)
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: