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

The POU for an Attachment Request is unclear

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci CDex (FHIR)
    • 2.0.0-ballot
    • Patient Care
    • CDex Task Attachment Request Profile
    • Hide

      The attachments request is designed to be:

      1. compatible with x12 transactions (no explicit POU in the these transactions)
      2. the POU is implicit to be Payment related for a Pre-Auth or Claim. However, the attachments could also be used for other activities as well such as Quality Measures - in other words - Operations)

      Adding a POU input parameter as an optional element to the attachment profile would provide the same benefit of being able to narrow the POU beyond TPO on a per-transaction basis.

      Will add an optional POU input parameter to the Attachment Profile as we did for the Task-based query profile.

      Show
      The attachments request is designed to be: compatible with x12 transactions (no explicit POU in the these transactions) the POU is implicit to be Payment related for a Pre-Auth or Claim. However, the attachments could also be used for other activities as well such as Quality Measures - in other words - Operations) Adding a POU input parameter as an optional element to the attachment profile would provide the same benefit of being able to narrow the POU beyond TPO on a per-transaction basis. Will add an optional POU input parameter to the Attachment Profile as we did for the Task-based query profile.
    • Eric Haas/Jay Lyle: 7-0-1
    • Enhancement
    • Compatible, substantive

    Description

      The CDex Task Data Request Profile includes a POU in the Task.input as a slice.  The CDex Task Attachment Request Profile does not.  Shouldn't that include as well?  If not, where is then the POU communicated on an Attachment request as the attachment can be for multiple purposes still.  And if POU is introduced to enable finer grained purposes than just "Payment and Operations", that seems reasonable to include as well.

      Attachments

        Activity

          People

            Unassigned Unassigned
            hbuitendijk Hans Buitendijk
            Hans Buitendijk
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: