Stream: smart
Topic: Smart Configuration Location
Benjamin Langley (May 03 2021 at 19:49):
According to http://www.hl7.org/fhir/smart-app-launch/conformance/index.html#using-well-known
FHIR endpoints requiring authorization SHALL serve a JSON document at the location formed by appending /.well-known/smart-configuration to their base URL. Contrary to RFC5785 Appendix B.4, the .well-known path component may be appended even if the FHIR endpoint already contains a path component.
I know some servers distinguish their FHIR base url from their base url. Can the /.well-known/smart-configuration be served from the base url (i.e. http://example.org/.well-known/smart-configuration) even if the FHIR base url is http://example.org/fhir?
Robert Scanlon (May 03 2021 at 20:16):
My understanding is that "base URL" in this context is simply short for "FHIR base URL". So if the FHIR base URL for the FHIR endpoint is "http://example.org/fhir" then the FHIR endpoint SHALL serve the JSON document at "http://example.org/fhir/.well-known/smart-configuration".
Cooper Thompson (May 03 2021 at 20:21):
I think this kinda came up before on this topic
Josh Mandel (May 03 2021 at 20:35):
Indeed: if you have multiple endpoints you can alias a bunch of /:endpoint/.well-known/smart-configurations to the same file under the covers, but those individual URLs need to work.
Last updated: Apr 12 2022 at 19:14 UTC
