Resolvable FHIR URIs question

The HL7 ones work by the principles I defined. Default redirects to an HTML page. However, if you set the accept headers asking for FHIR JSON or XML, you'll get those instead. The website has scripts that intercept the call and redirect based on the accept header

Thanks Lloyd.

Just to get us building things in the right direction, is there a set of examples of resolvable URIs that show what would be the standard response expected - or has this even been considered?

Not that we are going to have any reolvable for a while, but it would be good to see if anyone has built something that works well

Redirection is fine. Ideally the server would look at the Accept header and return either HTML or XML or JSON as requested, but that's not required. (Technically even resolution isn't required, though resolution means that the requirement that extension definitions are always available to the recipient can automatically be satisfied.)

Hi all,

I'm looking in to getting Alberta's jurisdiction URIs set up (for the non-common public URIs), and a question came up about the actual URI resolving.

If we had the URI as "fhir.alberta.ca/NamingSystem/ca-ab-someuri", would it be acceptable for that URL to redirect to "some-goa-server.gov.ab.ca/NamingSysetm/ca-ab-someuri"?

And as a secondary question, if the uri was entered as (ignoring redirection) "fhir.alberta.ca/NamingSystem/ca-ab-someuri" would it be a problem if the server returned the page "fhir.alberta.ca/NamingSystem/ca-ab-someuri.html"?

This is an issue because URIs don't have an extension...

Thanks again for any help in clarifying this.

Randy