Loading...

XML

Word

Printable

JSON

Details

Type: Change Request
Resolution: Unresolved
Priority: Medium

Specification:

FHIR Core (FHIR)
Raised in Version:

R6
Work Group:

FHIR Infrastructure
Related URL:
https://build.fhir.org/subscriptions.html
Related Page(s):

Subscriptions Framework

Description

There were (linked) several trackers submitted against the Subscriptions R5 Backport IG. The dispositions of those trackers should be applied to the FHIR Core spec.

Note: I'm writing this grouper tracker for the core spec instead of writing a duplicate Jira for every issue. Gino said he was going to do a single ticket to do the sync, but we wanted something to track our issues as they related to the core spec.

Attachments

Issue Links

relates to

FHIR-43513 Should conformance require Subscription write?

Triaged

FHIR-43514 Should SubscriptionTopic.read and search be required?

Triaged

FHIR-43563 Subscription lifecycle doesn't account for governance

Triaged

FHIR-43564 Subscription.status with handshake

Triaged

FHIR-43505 Consider describing administratively created subscriptions

Resolved - change required

FHIR-43515 Application vs. Server for subscription authorization

Resolved - change required

FHIR-43516 Subscription notification limitations is included twice

Resolved - change required

FHIR-43610 Make the related query examples consistent

Resolved - change required

(3 relates to)

Activity

People

Assignee:: Unassigned

Reporter:: Cooper Thompson

Watchers:: 1 Start watching this issue

Dates

Created:: 2024-01-11 10:02

Updated:: 2024-01-26 01:55