Clearly this is an interaction that must be tracked by a Provenance Resource. - HRex #93

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • Financial Mgmt
    • Profile overview [deprecated]
    • Information Exchange
    • Hide

      Provenance instances are not created when data is shared - only when data is being created, updated or deleted.  (AuditEvent gets captured when data is shared.)  The only Provenance that would necessarily be created would be those associated with creating the CommunicationRequest and Communication instances.  These two resources already capture the metadata about who's asking and when and why, so sending Provenance as well wouldn't add useful information.  The place where Provenance is relevant is in sharing the various Provenance resources associated with the data being packaged up and shared - so the receiver understands where the data originally came from and how it might have changed over time.  We will ensure that this expectation for including the Provenance of the information communicated as part of the package in the Communication resource is properly covered in the spec.

      Show
      Provenance instances are not created when data is shared - only when data is being created, updated or deleted.  (AuditEvent gets captured when data is shared.)  The only Provenance that would necessarily be created would be those associated with creating the CommunicationRequest and Communication instances.  These two resources already capture the metadata about who's asking and when and why, so sending Provenance as well wouldn't add useful information.  The place where Provenance is relevant is in sharing the various Provenance resources associated with the data being packaged up and shared - so the receiver understands where the data originally came from and how it might have changed over time.  We will ensure that this expectation for including the Provenance of the information communicated as part of the package in the Communication resource is properly covered in the spec.
    • Richard Esmond / Marti Velezis : 9-0-0
    • Clarification
    • Non-substantive

      Existing Wording: The Request (Solicited Communication) information exchange interaction is an alternative way to handle a Pull interaction for a FHIR APIs.

      It uses the CommunicationRequest Resource to send a message that communicates an information request.

      The CommunicationRequest includes the kind of information requested. It may also information supporting the request and the tasks requested to be performed associated with the information to be returned.

      The Information Request Recipient processes the message payload, performs the tasks based on their business logic and internal processes, then returns the requested information and the completed task information in a Communication Message that is linked to the original Information Request Message through an identifier established in the request.

      The Information Request Recipient acts an an Information Sender and returns the requested information to the Information Recipient(s) identified in the original CommunicationRequest.

      Proposed Wording: The Information Request Recipient acts as an Information Sender and returns the requested information to the Information Recipient(s) identified in the original CommunicationRequest along with a Provenance Resource recording the requested tasks performed.

      Comment:

      Clearly this is an interaction that must be tracked by a Provenance Resource.

      https://build.fhir.org/ig/HL7/davinci-ehrx/StructureDefinition-hrex-provenance.html

      Summary:

      Clearly this is an interaction that must be tracked by a Provenance Resource.

            Assignee:
            Unassigned
            Reporter:
            Kathleen Connor
            Kathleen Connor
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: