hl7 / fhir-subscription-backport-ig

Backporting R5 Subscriptions To R4 Implementation Guide

Subscription R5 Backport IG Info

The Subscription R5 Backport Implementation Guide enables servers running verions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way.

About This Guide

• Project Overview

More Information

• code: subscription-backport
• canonical: http://hl7.org/fhir/uv/subscription-backport
• Publication Request documentation on Confluence

FHIR® is the registered trademark of HL7 and is used with the permission of HL7.

fhir-subscription-backport-ig's Issues

Make it clear how to group filters and criteria with the resources they apply to

Related jira for R5: https://jira.hl7.org/browse/FHIR-28490
Related conversation from connectathon: https://chat.fhir.org/#narrow/stream/179229-subscriptions/topic/Modeling.20resource.20triggers

Thoughts for R4 Backport approach:
Need to decide on syntax
(1) keep multiple values in critieria with an additional separator: "Observation?patient=123 | Encounter?patient=123"
Note that common separators are not available since they are allowed in the values (e.g., patient=123,456 or category=system|code)
(2) leave the first criteria in 'Subscription.criteria' and put additional ones in an extension on that field
(3) assign static text to 'Subscription.criteria' and put all filters in an extension

Change reference to SubscriptionTopic to canonical

Related R5 Jira: https://jira.hl7.org/browse/FHIR-28491

Change http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-topic-canonical from valueUri to valueCanonical.

Bug in text

In

fhir-subscription-backport-ig/input/pagecontent/components.md

Line 63 in 1037e74

In order to support topic-based subscriptions in R4, this guide defines several extensions for use on the [R4 Subscription](http://hl7.org/fhir/subscription.html) resource. A list of extensions defined by this guide can be found on the [Artifacts](artifacts.html#3) page. Note that the future FHIR R5 publication may define capabilities included in this specification as cross-version extensions. Since the FHIR R5 is currently under development, there are no guarantees these extensions will meet the requirements of this guide. In order to promote widespread compatibility, cross version extensions SHOULD NOT be used on R4 subscriptions to describe any elements also described by this guide

and

fhir-subscription-backport-ig/input/pagecontent/conformance.md

Line 108 in 1037e74

Note that the future publication of FHIR R5 may define capabilities included in this specification as cross-version extensions. Since FHIR R5 is currently under development, there are no guarantees these extensions will meet the requirements of this guide. In order to promote widespread compatibility, cross version extensions SHOULD NOT be used on R4 subscriptions to describe any elements described by this guide.

-the text says "Since FHIR R5 is currently under development" - ... I don't think thats the case anymore.