Model Practitioner.communication like Patient.communication - STU #18

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • Practitioner
    • Hide

      The language property on the practitioner and patient resources are there for very different purposes, and therefore are structured differently.

      On the Patient it is used to determine how to communicate with them, including things like if an interpreter may be required.

      Where on the Practitioner, this is used from a registry style perspective to be able to locate someone that can fit the need to interact with a patient. So there is no need for preferred flag on the practitioner.

      Show
      The language property on the practitioner and patient resources are there for very different purposes, and therefore are structured differently. On the Patient it is used to determine how to communicate with them, including things like if an interpreter may be required. Where on the Practitioner, this is used from a registry style perspective to be able to locate someone that can fit the need to interact with a patient. So there is no need for preferred flag on the practitioner.
    • Cooper Thompson/Alex de Leon: 6-0-0
    • Enhancement

      Comment:

      Consider modeling the communication element like the Patient communication element (with a preferred indicator boolean

      Summary:

      Model Practitioner.communication like Patient.communication

            Assignee:
            Unassigned
            Reporter:
            corey_spears#1
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: