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

Not clear where to get Requester Organization when creating PAS request

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.1.0-ballot [deprecated]
    • Clinical Decision Support
    • How DTR passes information to PAS, PAO or other exchanges [deprecated]
    • Hide

      Create profiles for ServiceRequest, DeviceRequest, MedicationRequest, and NutritionOrder to ensure that the Ordering Provider and Organization are available to DTR for the requested service by requiring that requestor reference is to US Core Practitioner Role profile. 

      This should apply to both stand-alone launch and launch from CRD.

      Show
      Create profiles for ServiceRequest, DeviceRequest, MedicationRequest, and NutritionOrder to ensure that the Ordering Provider and Organization are available to DTR for the requested service by requiring that requestor reference is to US Core Practitioner Role profile.  This should apply to both stand-alone launch and launch from CRD.
    • Bob Dieterle / Howard Strasberg: 13-0-2
    • Enhancement
    • Non-compatible

    Description

      When a DTR app wants to create a PAS Bundle for submission is not clear where to get the required PAS Requestor Organization. A request such as ServiceRequest contains a property called "requester" that can be an Organization or a PractitionerRole, but it seems more likely to be a Practioner. The PAS Encounter contains a "serviceProvider" property, but it is not required. It would be helpful if the DTR IG could provide some guidance on where to locate the required information for PAS.

      Attachments

        Activity

          People

            Unassigned Unassigned
            brian_lind1 Brian Lind
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: