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

Update guidance for SubscriptionStatus entry fullUrl

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR R5 Subscriptions Backport (FHIR)
    • current
    • FHIR Infrastructure
    • Topic-Based Subscription Components
    • 5.3
    • Hide

      For a 'true' history Bundle, the expectation would be that every fullUrl would be the fullUrl of the resource we're reporting history of.  We don't think we have good grounds for changing the rules for fullUrl here.  Forcing it to be a urn:uuid would be technically compliant (though surprising to any system that tried to process the Bundle as a true history Bundle).  We accept that as the mechanism for use in R4.  For R5, decide what you want for your new bundle type, and we'll make sure the rules allow it - to be handled under a separate tracker item.

      Show
      For a 'true' history Bundle, the expectation would be that every fullUrl would be the fullUrl of the resource we're reporting history of.  We don't think we have good grounds for changing the rules for fullUrl here.  Forcing it to be a urn:uuid would be technically compliant (though surprising to any system that tried to process the Bundle as a true history Bundle).  We accept that as the mechanism for use in R4.  For R5, decide what you want for your new bundle type, and we'll make sure the rules allow it - to be handled under a separate tracker item.
    • Gino Canessa/Grahame Grieve: 12-0-1

    Description

      In clarification for Bundle.entry.fullUrl, it was brought up that resolvable URLs here must point to the same resource. Given that SubscriptionStatus instances are not persisted, using the $status operation is not valid for a `fullUrl`.

      Propose updating the specification to indicate that implementations SHALL use UUIDs for non-persisted resources such as SubscriptionStatus.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: