Stream: medmorph
Topic: Subscription Backport
Rob Dingwell (Feb 01 2021 at 16:59):
@Nagesh Bashyam as it seems MedMorph will be moving to use the R5 backport for subscriptions will the IG be defining a mapping from events to topic urls for use in the Subscription extension? Or are you expecting sites to provide that mapping for the clients to use?
Edward Castagna (May 14 2021 at 12:42):
Rob Dingwell said:
Nagesh Bashyam as it seems MedMorph will be moving to use the R5 backport for subscriptions will the IG be defining a mapping from events to topic urls for use in the Subscription extension? Or are you expecting sites to provide that mapping for the clients to use?
Rob,Nagesh
Was this question ansered? Should we be building the FHIR servers with R5 rather than R4.0.1?
Rob Dingwell (May 14 2021 at 14:27):
It would not be so much moving from R4 to R5 but instead of using the base R4 Subscription resource utilizing the R5 Subscription Backport IG http://build.fhir.org/ig/HL7/fhir-subscription-backport-ig/StructureDefinition-backport-subscription.html This is an IG that profiles some of the concepts of the R5 Subscription resource onto the R4 Subscription resource.
Gino Canessa (May 14 2021 at 15:07):
As a note, FMG approved adding SubscriptionTopic and SubscriptionStatus to R4B, so the IG will be updated to use those resources instead of the compromises that are in the current version.
The Subscription resource remains unchanged, but this makes moving from R4 to R5 mostly painless.
Rob Dingwell (May 14 2021 at 21:38):
@Gino Canessa so the extensions for things like heartbeat, timeout, payload-content .... Those are not going to be in the backport subscription anymore? OR do you mean that the additional resource have been approved but the current backport Subscription profile remains unchanged?
Gino Canessa (May 14 2021 at 21:41):
The extensions on Subscription will remain as they are today, since the resource is unchanged from R4 to R4B. The difference is that in R4B there will be definitions for SubscriptionTopic and SubscriptionStatus.
On the definitional side, instead of leaving topic definition out of scope, we will be able to link it properly to SubscriptionTopic definitions.
On the notification side, we can get rid of all the profiles on Parameters and just use SubscriptionStatus. Note that the new bundle type could not be added, so it will still be a history bundle in the backport as well.
Last updated: Apr 12 2022 at 19:14 UTC
