Allowed user types

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Considered - Question answered
    • Priority: Highest
    • CDS Hooks patient-view [deprecated] (FHIR)
    • 1.0 [deprecated]
    • Clinical Decision Support
    • index
    • Context
    • Hide

      Hey Nick,

      Excellent question! Two of the other comments on this ballot address this question. 

      Dennis' FHIR-25762 recommends the ability to use a Person resource (following SMART's example) and my FHIR-25761 requests PractitionerRole. 

      Thus far, we have not seen requests for Organization or Device. Overall, the scope of CDS Hooks, since the beginning has been real-time, provider-facing, remote CDS. Even the inclusion of a patient user in the spec doesn't really match what's happening in production environments. 

      Do you have additional use-cases?

      Isaac 

      Show
      Hey Nick, Excellent question! Two of the other comments on this ballot address this question.  Dennis'  FHIR-25762 recommends the ability to use a Person resource (following SMART's example) and my  FHIR-25761 requests PractitionerRole.  Thus far, we have not seen requests for Organization or Device. Overall, the scope of CDS Hooks, since the beginning has been real-time, provider-facing, remote CDS. Even the inclusion of a patient user in the spec doesn't really match what's happening in production environments.  Do you have additional use-cases? Isaac 

      Are Practitioner, Patient, and RelatedPerson the only allowed FHIR resource types? Would it ever be valid for the current user to be a PractitionerRole, Organization, or Device?

      Existing Wording:

      The id of the current user.
      For example, if the user represents a FHIR resource on the given FHIR server, the resource type would be one of Practitioner, Patient, or RelatedPerson.
      If the user was a Practitioner, this value would be Practitioner/123

            Assignee:
            Unassigned
            Reporter:
            Nick Radov
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: