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

mismatching integer types for counts on subscriptionStatus

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIR R5 Subscriptions Backport (FHIR)
    • 0.1.0 [deprecated]
    • FHIR Infrastructure
    • Backported R5 Subscription Notification Status [deprecated]
    • Hide

      Note: discussed on May 19 call.

      Use 'string' type for int64 in R4B.  All else being equal, the JSON format will remain unchanged between R4B and R5.  Since the SubscriptionStatus resource is used in notifications (which may not go to a FHIR server at all), this is a great benefit.

       

      Other options discussed (and discarded):

      • Leave as uint32 with a note about overflow.
      • Use both: uint32 for lower 32 bits, and a string with the entire value.
      Show
      Note: discussed on May 19 call. Use 'string' type for int64 in R4B.  All else being equal, the JSON format will remain unchanged between R4B and R5.  Since the SubscriptionStatus resource is used in notifications (which may not go to a FHIR server at all), this is a great benefit.   Other options discussed (and discarded): Leave as uint32 with a note about overflow. Use both: uint32 for lower 32 bits, and a string with the entire value.
    • Gino Canessa / Yunwei Wang : 10-0-0
    • Correction
    • Non-compatible

    Description

      eventsSinceSubscriptionStart and eventsInNotification are both unsignedInt in the R4 backport, but int64/int respectively in R5 build. Is this to account for the new int64 type?

      (Comment 40 - imported by: Gino Canessa)

      Attachments

        Activity

          People

            ginocanessa Gino Canessa
            weiyuzh Weiyu Zhang
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: