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

Under-represented implications to the spec

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • STU
    • Content Sharing
    • Hide

      Over the course of the resolution process, the content sharing specification has been increasingly integrated into the rest of the FHIRcast spec. For example, I believe that the specific example cited by Gino has since been clarified in the content-sharing page – https://build.fhir.org/ig/HL7/fhircast-docs/2-10-1-ContentSharingFHIRcastMessaging.html#processing-update-events

      To comprehensively address the commenter's point, we will: 

      1. Finish outstanding Jira resolutions from STU3 ballot
      2. Reballot as STU3.1 
      3. Restructure Chapter 2 into
        1. Infrastructure: authnz, subscribing, events, websockets, conformance, etc.
        2. Context Synchronization (using the FHIRcast infrastructure)
        3. Content Sharing (using the FHIRcast infrastructure)
      Show
      Over the course of the resolution process, the content sharing specification has been increasingly integrated into the rest of the FHIRcast spec. For example, I believe that the specific example cited by Gino has since been clarified in the content-sharing page – https://build.fhir.org/ig/HL7/fhircast-docs/2-10-1-ContentSharingFHIRcastMessaging.html#processing-update-events To comprehensively address the commenter's point, we will:  Finish outstanding Jira resolutions from STU3 ballot Reballot as STU3.1  Restructure Chapter 2 into Infrastructure: authnz, subscribing, events, websockets, conformance, etc. Context Synchronization (using the FHIRcast infrastructure) Content Sharing (using the FHIRcast infrastructure)
    • Bas van den Heuvel / Trent Nolin: 7-0-0
    • Correction
    • Non-compatible

    Description

      I feel like this has a lot of implications across the rest of the specification and I cannot fully process the scope of changes because it has been included as separate page. For example, section 2.3.3 specifies that hubs need only return the data specified by the required elements of an event, but this seems to contradict that.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ginocanessa Gino Canessa
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: