XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • Approaches to Exchanging FHIR Data
    • 3.0.3.20 Push Notifications
    • Hide

      This whole section deals with the technical mechanisms for sharing and doesn't deal with "what" is to be shared (or why) at all. As such, this language is inappropriate, particularly to be inserted in a narrow section when the principle would apply to all information exchange.

      However, we will add the following language to the introduction of the exchanging section (as it applies to all exchange mechanisms, not just 'push'):

      "This section focuses on the technical alternatives that enable exchange between data sources and data consumers.  All such exchanges, and the decisions about the mechanisms used, will also need to take into account the creation of and adherence to regulations, contracts, business arrangements and other conventions and ensure that the information shared is 'appropriate' to the use-case.  Implementers and designers may want to consult legal counsel as part of their design process.

      This section also does not address expectations around security or authentication (except where specific exchange mechanisms have specific tradeoffs around what security or authentication mechanisms are possible).  Designs will need to ensure that appropriate security mechanisms are in place for whatever data is shared.  (Refer to the [security checklist] for additional considerations in this space.)"

      Show
      This whole section deals with the technical mechanisms for sharing and doesn't deal with "what" is to be shared (or why) at all. As such, this language is inappropriate, particularly to be inserted in a narrow section when the principle would apply to all information exchange. However, we will add the following language to the introduction of the exchanging section (as it applies to all exchange mechanisms, not just 'push'): "This section focuses on the technical alternatives that enable exchange between data sources and data consumers.  All such exchanges, and the decisions about the mechanisms used, will also need to take into account the creation of and adherence to regulations, contracts, business arrangements and other conventions and ensure that the information shared is 'appropriate' to the use-case.  Implementers and designers may want to consult legal counsel as part of their design process. This section also does not address expectations around security or authentication (except where specific exchange mechanisms have specific tradeoffs around what security or authentication mechanisms are possible).  Designs will need to ensure that appropriate security mechanisms are in place for whatever data is shared.  (Refer to the  [security checklist] for additional considerations in this space.)"
    • Marti Velezis / Jimmy Tcheng : 6-0-1
    • Clarification
    • Non-substantive

    Description

      Add language to section.

      Existing Wording:

      The final approach is the least work for the data source initially - it does not even have to identify the impacted records, only that something has happened. However, it is more work subsequently as the data consumer must use appropriate query parameters to find the relevant data - it cannot search by id. Other benefits are like the second approach.

      Proposed Wording:

      The final approach is the least work for the data source initially - it does not even have to identify the impacted records, only that something has happened. However, it is more work subsequently as the data consumer must use appropriate query parameters to find the relevant data - it cannot search by id. Other benefits are like the second approach.
      Data consumers should limit the request for information to that required to address the specific, stated purpose of the data exchange or prearranged, agreed- upon purposes. For instance, trading partners will use data use agreements (DUAs), business associate agreements (BAAs) and/or contracts per the Da Vinci Guiding Principles.

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: