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

Provenance expectations need more clarity

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Decision Support
    • Documentation Templates and Rules Implementation Guide Home Page
    • Hide

      Will remove all references to Provenance since the extension recording source of information provides the "provenance" that is necessary to document the origin of the responses in the QuestionnaireResponse.

      We have defined "rules" as the CQL provided by the Payer (or the source of the questionnaire) used to prepopulate the relevant Questionnaire items directly from the patient record via APIs required by regulation.

      Will standardize on the following 'labels' throughout specification, and will define the meaning of each on first use in the IG:

      • DTR Native App
      • DTR Smart App
      • Payer DTR API
      Show
      Will remove all references to Provenance since the extension recording source of information provides the "provenance" that is necessary to document the origin of the responses in the QuestionnaireResponse. We have defined "rules" as the CQL provided by the Payer (or the source of the questionnaire) used to prepopulate the relevant Questionnaire items directly from the patient record via APIs required by regulation. Will standardize on the following 'labels' throughout specification, and will define the meaning of each on first use in the IG: DTR Native App DTR Smart App Payer DTR API
    • Bob Dieterle / Howard Strasberg: 13-0-2
    • Clarification
    • Non-substantive

    Description

      The section on Provenance isn't sufficiently clear.  What does the Provenance need to reflect?  What data elements are mandatory vs. optional?  Do we want one Provenance per query performed?  Per question asked?  What is the objective?  (If you make something a SHOULD, you need to provide an explanation of the benefits doing it and the costs of not  doing it when they're not obvious - and they're not obvious here.)  Does Provenance get stored on the Payer as part of the DocumentReference for work-in-progress?  How is it recorded in the EHR as part of the final results (whether QuestionnaireResponse or DocumentReference?  Are we using a transaction?  The 'header' Provenance mechanism?  A separate RESTful call?  Also "the source of the rules" is totally ambiguous.  We need standard 'labels' for each of the four system types involved in the DTR workflow and need to use those consistently throughout the spec.  E.g. "Light DTR client" (uses SMART app), "Full DTR client" (no smart app), "DTR Smart app", and "DTR payer".

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: