Loading...

XML

Word

Printable

JSON

Specification:

FHIR Core (FHIR)
Raised in Version:

STU3
Work Group:

FHIR Infrastructure
Related Page(s):

Terminologies
Grouping:
- Level3
Resolution Description:
Hide

We will add a section in the 'canonical' section of the references page that highlights two challenges with dealing with canonical resolution:

url + version does not resolve to a single record

url without version does not resolve to a single record and the server deals with resources that have varying or undefined versioning schemes

The gist of the guidance will be "this is up to server policy" (with maybe some examples of where these problems will be unavoidable and how they might be handled).
Show
We will add a section in the 'canonical' section of the references page that highlights two challenges with dealing with canonical resolution: url + version does not resolve to a single record url without version does not resolve to a single record and the server deals with resources that have varying or undefined versioning schemes The gist of the guidance will be "this is up to server policy" (with maybe some examples of where these problems will be unavoidable and how they might be handled).
Resolution Vote:
Rick Geimer/Grahame Grieve: 16-0-0
Change Category:
Clarification
Change Impact:
Non-substantive
Applied for Version:

R5

As discussed on https://chat.fhir.org/#narrow/stream/179166-implementers/topic/identical.20urls.20across.20different.20structuredefinitions , it would prove useful to define a set of rules for different types for FHIR server setups - eg. to define that structuredefs are unique by url on regular clinical instances of FHIR servers whereas uniqueness on urls are not needed on terminology setups