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

Clarify Figure 4 and associated text in 2.6.2

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Da Vinci CDex (FHIR)
    • 1.1.0-ballot [deprecated]
    • Patient Care
    • STU
    • Background
    • Hide

       

      Fix Figure 4 as proposed - (preapplied)

      also based FHIR-37563 will incorporate attachment request into this diagram and mark as Draft content

       

      Re:

       Suggest that the term attachment is used for a subset of supporting information that does have a manual review.

      Will edit the guide to limit use of the term attachments to a subset of additional information that are:

      1. documents defined by the document ontology but not  necessary require manual review
      2. supporting information that are individual data elements ( like a a1c value) but are signed and hence a document.

      Will refer to other supporting information as data elements

      Show
        Fix Figure 4 as proposed - (preapplied) also based FHIR-37563 will incorporate attachment request into this diagram and mark as Draft content   Re:  Suggest that the term attachment is used for a subset of supporting information that does have a manual review. Will edit the guide to limit use of the term attachments to a subset of additional information that are: documents defined by the document ontology but not  necessary require manual review supporting information that are individual data elements ( like a a1c value) but are signed and hence a document. Will refer to other supporting information as data elements
    • Eric Haas/Bob Dieterle: 8-0-3
    • Clarification
    • Non-substantive

    Description

      Figure 4 gives the impression that the provider submits attachments and data elements.  That would imply that attachments and data elements are two different things, while the text below the figure indicates that attachments are either supporting information or data elements where data elements are data such as member id and claim id.  Suggest to only use "attachments" in the figure to enable it to cover supporting information and data elements.

      The figure also uses the term "re-association" which is ambiguous.  The title indicates for attachments, which would imply it is not only for additional data (which would require "re-association") but also on the original submission.  Suggest to drop "for re-association" in the figure.

       The term Attachment is earlier defined in 2.6 as supporting information, not using the term data elements.  In this context it would seem that supporting information can only go as attachments, which seems to imply a signed/reviewed document.  However, the intent of ePA is that data is gathered and submitted automatically within an agreed to trust framework thus supporting information could be pushed as a data set wtihout manual review, without e-signature by a user, and without it being packaged as a document as that has no relevance.  Suggest that the term attachment is used for a subset of supporting information that does have a manual review, person's e-signature, and document format requirement to avoid encumbering all prior-auth submissions to have to increase documentation burden on the provider when data can be gathered and submitted automatically.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: