Stream: smart
Topic: SMART on FHIR v1 System Links Broken
Cille Kissel Watkins (Feb 02 2022 at 20:27):
Hi all - We were alerted today that the system links used in the SMART on FHIR 1.0.0 metadata are no longer working which causes our server to fail a FHIR conformance test. Specifically, the links http://hl7.org/fhir/restful-security-service and http://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris generate 404s. You can see where these links are provided in the spec here: http://hl7.org/fhir/smart-app-launch/1.0.0/conformance/index.html#example
I recognize that there is a v2 of the spec now, but many servers in the US are likely still using v1. Particularly of note, the CMS Interoperability requirement requires use of the SMART on FHIR v1 (at a minimum) for US insurers who offer government sponsored health plans. Is there any way we can get these links back to working order?
Adam Culbertson (Feb 02 2022 at 20:31):
Great question
Josh Mandel (Feb 02 2022 at 21:03):
I'm pretty sure that the "fhir-registy.smarthealthit.org" link never resolved at any point in the past. Can you clarify what conformance tests are failing?
Josh Mandel (Feb 02 2022 at 21:04):
SMART v1 is of course still widely used and supported, and we certainly don't expect that to change very soon
Josh Mandel (Feb 02 2022 at 21:06):
We're also in the process of preparing some technical corrections to the SMART v2 spec, and can potentially make adjustments if we identity an issue
Cille Kissel Watkins (Feb 02 2022 at 21:24):
Thanks, @Josh Mandel. We were running a Touchstone Aegis conformance test against our metadata endpoint and were alerted to the link http://hl7.org/fhir/restful-security-service being an unrecognized system URL. That led us to test that link and the other one and found the 404s. I can follow up with Touchstone folks if this just needs to be fixed in their test scripts.
Josh Mandel (Feb 02 2022 at 22:16):
Thanks! That sounds like a good place to start. http://hl7.org/fhir/restful-security-service notably is not something defined or required by SMART (v1 or v2), though it does appear in an example CapabilityStatement from the v1 spec. http://build.fhir.org/valueset-restful-security-service.html has the current ValueSet for http://build.fhir.org/capabilitystatement-definitions.html#CapabilityStatement.rest.security.service (you'll notice the system has migrated to http://terminology.hl7.org/CodeSystem/restful-security-service) -- but again, populating this field is not required by SMART.
Last updated: Apr 12 2022 at 19:14 UTC
