smart-launcher
smart-launcher copied to clipboard
smart-on-fhir
Launcher for SMART apps
Notably, for backend service auth, the HL7 spec states (http://hl7.org/fhir/smart-app-launch/client-confidential-asymmetric.html#discovery-requirements) that backend services must advertise support for asymmetric keys in .well-known/smart-configuration by: 1. Including "client-confidential-asymmetric" 2. token_endpoint_auth_methods_supported that include private_key_jwt...
Launching a FHIR server with this configuration: https://smart.argo.run/?auth_error=&client_secret=&fhir_version_2=r4&iss=&jwks=&jwks_uri=&launch_pt=1&launch_url=&patient=&prov_skip_auth=1&provider=&pt_skip_auth=0&public_key=&redirect_uris=&sde=&token_lifetime=15&user_pt=&validate_pkce=1&validation_method=none I'm imagining there should be some kind of error when I try and obtain the authorization code without using PKCE but it...
https://launch.smarthealthit.org/v/r4/fhir/.well-known/smart-configuration doesn't contain `jwks_uri`, like the OIDC one: https://launch.smarthealthit.org/v/r4/fhir/.well-known/openid-configuration also `issuer` is missing: can you please add it?
There were a few issues with the pagination unit test for the proxy. * it started with a relative URL and then used a full url to follow the 'next'...
The us-core-race and us-core-ethnicity extensions both use a nested extension structure: https://hl7.org/implement/standards/fhir/us/core/STU2/StructureDefinition-us-core-race.html http://hl7.org/implement/standards/fhir/us/core/STU2/StructureDefinition-us-core-ethnicity.html However, some of the https://r3.smarthealthit.org synthetic Patient data uses (incorrectly) valueCodeableConcept for those extensions. For example, in...
Hi, I am using the SMART App Launcher. When I launch with "Simulate launch within the EHR user interface" checked it seems that my cookies do not persist between the...
I am getting compile errors with ursa when running npm install with node 12. I was able to get it to build and run with node 8. If a specific...
Search fails during the authorization process, with a "please try again later" error.
