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

Make Practitioner.communication consistent with Patient/RelatedPerson.communication

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Triaged (View Workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      STU3
    • Work Group:
      Patient Administration
    • Related Artifact(s):
      Practitioner
    • Change Category:
      Enhancement

      Description

      The practitioner resource has a simple list of communication codes (CodeableConcept), unlike the Patient and RelatedPerson, which have a list of possible languages, along with a boolean for preferred. While the use case for practitioner languages is different (in a different direction) the underlying notion of 'can speak if really necessary' vs 'a language I am comfortable in' still seems applicable. Therefore I propose that for consistency's sake, the structure should be the same.

      Note: this task is created as part of defining a common pattern "HumanActor" which applies to all 3 resources. In the absence of a 'preferred' property, the pattern will have not much option but to mark all the languages as preferred for a practitioner

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            GrahameGrieve Grahame Grieve
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: