Except for this newly introduced paragraph including multiple normative requirements, the consistent expectation for content sharing was that it was only possible for currently open contexts. This is clearly illustrated by the spec's implicit but consistence equivalence of "anchor context" and "current context", and the process for establishing it to be an -open event.  We will update the new paragraph here – https://build.fhir.org/ig/HL7/fhircast-docs/2-10-1-ContentSharingFHIRcastMessaging.html#processing-update-events-and-current-context, to:  Experimental Capability – Update events outside of current context <Implementer Feedback Solicited banner> Towards enabling greater workflow flexibility and greater convenience of subscribers, Subscribers MAY send a [FHIR resource] -update event, that is unrelated to the current context (e.g. an update event in which the anchor context referenced differs from the current context). Subscribers SHALL NOT send select events unrelated to the current context. If the event recipient supports receiving and processing update events outside of the current context, the event SHALL be processed in scope of the referenced context (not the current context) following the same rules as if the referenced context were the current context. If the event recipient does not support update events outside of the current context, the recipient SHALL respond with an appropriate [event notification] (2-5-EventNotification.html#event-notification-response). This capability is deemed experimental due to low production adoption and evaluation of potential risk patient safety. This capability may change or be removed in future versions of this specification.