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

Submit-attachment operation should require either an OrganizationId or ProviderId, Not both

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Applied (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Da Vinci CDex (FHIR)
    • 2.0.0-ballot
    • Patient Care
    • STU
    • Submit Attachment Operation
    • Hide
      1. Update operation to require at least a provider or organization ID (technically this means each parameter is min = 0 and will document that at least one is required).
      2. The second issue is to resolve any ambiguity if a request is sent to a common endpoint for more than a single organization where a  practitioner could belong to more than one organization.   We will update both Task profile's .owner element to add a choice of a reference to PractitionerRole - which contains both organization and practitioner (technically add a choice of a reference to a contained PractitionerRole composed of a reference identifier to both organization and practitioner)

      Show
      Update operation to require at least a provider or organization ID (technically this means each parameter is min = 0 and will document that at least one is required). The second issue is to resolve any ambiguity if a request is sent to a common endpoint for more than a single organization where a  practitioner could belong to more than one organization.   We will update both Task profile's .owner element to add a choice of a reference to PractitionerRole - which contains both organization and practitioner (technically add a choice of a reference to a contained PractitionerRole composed of a reference identifier to both organization and practitioner)
    • Eric Haas/Jay Lyle: 7-0-1
    • Enhancement
    • Non-compatible
    • Yes

    Description

      Currently, the Submit Attachment Operation requires both a provider ID and an Organization ID. This should be updated to be either or, not both.

      The reasoning behind this is two-fold:

      1.) A prior auth submission may not always have a provider associated with it beyond the ordering provider. This ordering provider may not be the one that is actually trying to obtain authorization and the attachment would not be coming from them.

      2.) The solicited request for documentation only has a single Task.owner(http://hl7.org/fhir/us/davinci-cdex/2022Sep/StructureDefinition-cdex-task-attachment-request-definitions.html#Task.owner), which is either a US Core Practitioner or a US Core Organization. The wording on the "OrganizationId" and "ProviderId" parameters states that "For solicited attachments this value is communicated to the provider through the request." Since the Task.owner only allows 1, returning both of these on the submission would not be possible.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              abarbieri Andrew Barbieri
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: