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

Give PractitionerRole a name

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • PractitionerRole
    • Hide

      A new property will be added to PractitionerRole:

       

      name 0..1 string

      Definition: A name that describes the intersection of the practitioner, organization, and the role of the practitioner within the organization.  This is not the human name of the practitioner, though the textual representation of that human name may be a part of this property.

      Comments:  The PractitionerRole name may be considered a de-normalized value from Practitioner and/or Organization for the purposes of convenient display in both the PractitionerRole resources and reference to it.  When a system is consuming a PractitionerRole resource and displaying a name to a user, they may choose to use PractitionerRole.name, or they could use one or both of the names from the referenced Practitioner and/or Organization resources along with the role or other relevant properties in PractitionerRole. 

       

      We will add an STU note: "We request feedback on whether implementers have a need for this property and if that need aligns with the proposed element definition." (editor wordsmithing welcome)

      Show
      A new property will be added to PractitionerRole:   name 0..1 string Definition:  A name that describes the intersection of the practitioner, organization, and the role of the practitioner within the organization.  This is not the human name of the practitioner, though the textual representation of that human name may be a part of this property. Comments:   The PractitionerRole name may be considered a de-normalized value from Practitioner and/or Organization for the purposes of convenient display in both the PractitionerRole resources and reference to it.  When a system is consuming a PractitionerRole resource and displaying a name to a user, they may choose to use PractitionerRole.name, or they could use one or both of the names from the referenced Practitioner and/or Organization resources along with the role or other relevant properties in PractitionerRole.    We will add an STU note: "We request feedback on whether implementers have a need for this property and if that need aligns with the proposed element definition." (editor wordsmithing welcome)
    • Brian Postlethwaite / Reinhard Egelkraut : 7-0-0
    • Enhancement
    • Compatible, substantive

    Description

      At present, PractitionerRole has no obvious way to tell what to display to a user when other resources use it to specify who took an action/played a role (unlike all the other resources that serve the same purpose). The proper display can be derived - in theory - from the codes, the linked practitioner details, and possibly the location. If, that is, these are known. But they may not all be known, while the source system may still know a suitable name to use for attribution. Alternatively, it may not be clear how to generate a very concise name (e.g. to display in a grid - a very common operation for attribution resources). Alternatively you could try and extract some meaningful short name from the narrative.... but that would be an unreliable approach.

      The practitionerRole resource should contain a name : String [0..1] to be used as the concise display for this practitioner role, along with a note in the comments that this is effectively a denormalisation for the ease of consumers of the resources.

      Note that this is the only resource that would normally be used for attribution that does not have a name element.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: