Using the current state to justify why your future thing is limited, is a gamble. - PCDE #102

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Considered - Question answered
    • Priority: Medium
    • US Da Vinci PCDE (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • Hide

      This business process is similar to sharing a discharge summary for consumption by downstream systems. The "old" payer (possibly informed by the wishes of the patient) determines what data will be shared. This accomodates both the fact that not all data is relevant/appropriate to be shared (the old payer gets to decide) as well as that the "new" payer might not know what to query/look for to find the relevant data. Finally, additional context/narrative can be helpful in understanding the discrete data or summarizing the information in a way that greatly reduces the effort of consuming the data.

      As an example, consider having the ability to query all of the patient's vitals vs. receiving a narrative statement that said "the patient's blood pressure dropped precipitously on day 3 but was stabilized after the administration of X". The latter draws attention to the relevant bits that would require considerable time to extract from the raw data. (And in this payer situation, the raw data - in the form of actual claims/prior authorizations won't necessarily even be shareable.)

      In short, the document function with organized narrative is likely to always be needed in at least some cases, even if payers eventually develop the intelligence to generate it automatically based on their own data structures.

      Show
      This business process is similar to sharing a discharge summary for consumption by downstream systems. The "old" payer (possibly informed by the wishes of the patient) determines what data will be shared. This accomodates both the fact that not all data is relevant/appropriate to be shared (the old payer gets to decide) as well as that the "new" payer might not know what to query/look for to find the relevant data. Finally, additional context/narrative can be helpful in understanding the discrete data or summarizing the information in a way that greatly reduces the effort of consuming the data. As an example, consider having the ability to query all of the patient's vitals vs. receiving a narrative statement that said "the patient's blood pressure dropped precipitously on day 3 but was stabilized after the administration of X". The latter draws attention to the relevant bits that would require considerable time to extract from the raw data. (And in this payer situation, the raw data - in the form of actual claims/prior authorizations won't necessarily even be shareable.) In short, the document function with organized narrative is likely to always be needed in at least some cases, even if payers eventually develop the intelligence to generate it automatically based on their own data structures.
    • Kathleen Connor / Rachael Foerster: 20-0-1

      Existing Wording: While the eventual target of future versions of this IG may be to allow fully automated import and use of the provided payer data, it is likely that at least some cases will always require human review and, in the short term, most/all payers will incorporate human review in the consumption of the data shared. The document approach significantly simplifies this review process.

      Comment:

      Using the current state to justify why your future thing is limited, is a gamble. Assuming a future where import is fully automated and no human review is necessary – what's the optimal integration pattern? Is it still pushing documents around asynchronously?

      Summary:

      Using the current state to justify why your future thing is limited, is a gamble.

            Assignee:
            Unassigned
            Reporter:
            Isaac Vetter
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: