Loading...

XML

Word

Printable

JSON

Specification:

FHIRCast (FHIR)
Raised in Version:

2.1.0-ballot [deprecated]
Work Group:

Infrastructure & Messaging
Related Artifact(s):

FHIRcastCapabilityStatement
Related Page(s):

Conformance
Related Section(s):
2.1, 2.7.1 Wellknown endpoint
Grouping:
- block-vote-6
Resolution Description:

Hide

Agree with commenter that a robust Hub will probably need to support multiple versions of FHIRcast. Hubs should do this via multiple endpoints, such that any given synchronized session uses a single, specific FHIRcast version.

We will keep the fhircastVersion element with a maximum cardinality of 1.

Show
Agree with commenter that a robust Hub will probably need to support multiple versions of FHIRcast. Hubs should do this via multiple endpoints, such that any given synchronized session uses a single, specific FHIRcast version. We will keep the fhircastVersion element with a maximum cardinality of 1.
Resolution Vote:
Jonathan Whitby/Bas van den Heuvel: 6-0-1
Change Category:
Clarification
Change Impact:
Non-substantive
Pre Applied:
Yes

In principle a hub could support multiple version of the standard (e.g. STU2 and STU3) .

For that reason the optional fhircastVersion parameter in Wellknown endpoint discovery response should be an array of strings.

is duplicated by

FHIR-37884 Request endpoint should (optionally) contain the version of the standard