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

Reference to non-existant feature

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • Synchronization considerations [deprecated]
    • 4.2.2.3
    • Hide

      We will update the sync considerations page to both more accurately name the "resend relevant event feature" as well as hyperlink it to: https://build.fhir.org/ig/HL7/fhircast-docs/2-4-Subscribing.html#current-context-notification-upon-successful-subscription.

      We'll also reference the GetCurrentContext API, with a hyperlink, in these same two sections as well.

      Show
      We will update the sync considerations page to both more accurately name the "resend relevant event feature" as well as hyperlink it to: https://build.fhir.org/ig/HL7/fhircast-docs/2-4-Subscribing.html#current-context-notification-upon-successful-subscription . We'll also reference the GetCurrentContext API, with a hyperlink, in these same two sections as well.
    • Catie Ladd / Nick Radov : 5-0-1
    • Clarification
    • Non-substantive

    Description

      Confirm feature name.

      Also in section 4.2.2.6

      Existing Wording:

      The resend relevant event feature will make sure the application will come back into sync.

      (Comment 43 - imported by: Lloyd McKenzie)

      Attachments

        Activity

          People

            Unassigned Unassigned
            esilver Elliot Silver
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: