Loading...

XML

Word

Printable

JSON

Specification:

FHIR R5 Subscriptions Backport (FHIR)
Raised in Version:

0.1.0 [deprecated]
Work Group:

FHIR Infrastructure
Related URL:
http://hl7.org/fhir/uv/subscriptions-backport/2021JAN/conformance.html
Related Page(s):

Conformance
Grouping:
- Block-Vote-2
Resolution Description:
Hide

Note: discussed on May 19 call.

General consensus was that is something that sounds nice to have, but that we don't have enough implementation experience to determine. Specifically:

Server implementers will document their support, so developers can discover this out of band.

Client implementers are unlikely to implement more than a couple of options, so there is not much to "try and error" on.

Long term (R5+), there will be new functionality in Capability Statement which will likely address this
Show
Note: discussed on May 19 call. General consensus was that is something that sounds nice to have, but that we don't have enough implementation experience to determine. Specifically: Server implementers will document their support, so developers can discover this out of band. Client implementers are unlikely to implement more than a couple of options, so there is not much to "try and error" on. Long term (R5+), there will be new functionality in Capability Statement which will likely address this

How can a client discover which Payload Types and Channel Types are supported by a server?

(Comment 34 - imported by: Gino Canessa)

is voted on by

BALLOT-15816 Affirmative - Christopher Schaut : 2021-Jan-FHIR IG R5 SUBSCR 2R4 R1 STU