Requirements for Client Registration
To register a client application for use with EMR Direct Interoperability Engine FHIR endpoints, see the public API documentation which references RFC 7591 for Dynamic Client Registration, found at
HealthToGo App Studio.
Whether registering dynamically or through manual registration on our website, the following data elements listed in RFC 7591 are required, at a minimum, to obtain a client certificate for use with UDAP workflows or a client ID and client secret from EMR Direct:
redirect_uris: one or more URI strings*
client_uri: web page providing information about the client application and the organization operating it
logo_uri: URI for an image corresponding to the client application*
contacts: a valid email address containing a top level domain that matches one of the domains in the redirect_uris or client_uri
tos_uri: URI that points to the app's terms of service
client_name: name of the client application
*Please also note the following:
- The logo_uri, redirect_uris, and client_uri must point to actively-hosted public URLs (without redirecting to different URLs).
- The redirect_uri and logo_uri must be hosted securely (i.e. served over an HTTPS connection).
- The Dynamic Client Registration workflow supported by EMR Direct Interoperability Engine does not accept custom URL schemes (eg. x-argonaut-app). For applications that use custom/private-use URI schemes, loopback interface redirection, client credentials grant, or if the client does not support Dynamic Client Registration, register the client application manually instead at the EMR Direct website.
- When manually registering for client credentials grant, look for the developer registration option that will allow you to obtain a UDAP client certificate for use in UDAP JWT-Based Client Authentication.
Did this article answer your question? If not, please contact us.