Ambiguous location of requester

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • ServiceRequest (Diagnostic/Procedure/ReferralRequest)
      Request Pattern
    • Hide

      There are use-cases where it's appropriate to point to an Organization by itself and forcing the creation of a PractitionerRole solely to point to the Organization would be inappropriate overhead and result in a resource that is not necessary. E.g. a test ordered by an insurer or government agency. At the same time, there are also situations where you need the full PractitionerRole as you need the Organization + Practitioner + the role the practitioner was actually acting in at the time the order was made (especially where interpretation might be different depending on the 'hat' the person was wearing).

      The result is that if the system needs to find the responsible organization, the system will need to look in two places. It's possible to tighten this down with profiles if the specific use-case allows (e.g. "in this profile, we'll only ever point to an Organization and won't ever use Practitioner or PractitionerRole")

      Show
      There are use-cases where it's appropriate to point to an Organization by itself and forcing the creation of a PractitionerRole solely to point to the Organization would be inappropriate overhead and result in a resource that is not necessary. E.g. a test ordered by an insurer or government agency. At the same time, there are also situations where you need the full PractitionerRole as you need the Organization + Practitioner + the role the practitioner was actually acting in at the time the order was made (especially where interpretation might be different depending on the 'hat' the person was wearing). The result is that if the system needs to find the responsible organization, the system will need to look in two places. It's possible to tighten this down with profiles if the specific use-case allows (e.g. "in this profile, we'll only ever point to an Organization and won't ever use Practitioner or PractitionerRole")
    • Jose Costa Teixeira/Victor Vaysman: 8-0-1
    • Clarification

      ServiceRequest.requester can lead to documenting the practitioner or organization in different locations:

      .requester(Pratitioner) or .requester(PractitionerRole.practitioner(Practitioner))

      .requester(Organization) or .requester(PractitionerRole.organization(Organization))

      There should be one place to put etiher the requesting practitioner and/or organization to avoid conditions such as "if only practitioner is known, use .requester(Practitioner), but is organization is also known, use .requester(Organization)"

      Options to resolve:

      • only have PractitionerRole as a choice rather than three (ignoring the other, still valid choices)
      • maker .requester 0..* and drop PractitionerRole for the purpose of associating the practitioner with the organization on who's behalf/under who's auspices s/he requested the service.

      Additionally, the definition of PractitionerRole does not really support this linking, but per discussions it appears that is acceptable. Therefore, if truly the intent and based on the disposition of this tracker, PractitionerRole scope and purpose needs to be updated.

            Assignee:
            Unassigned
            Reporter:
            Hans Buitendijk
            Hans Buitendijk
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: