FHIR Client App Developers
Applications that will rely on a patient's credentials assigned by the health system where data access is requested (for example, patient portal credentials used by patients for access to health data one patient at a time) can register at the EMR Direct website to obtain a client ID and secret and become listed in this App Gallery. In this case, let us know you require a "Client ID and Secret for Patient Access" when registering your app to use it with authorization code flow according to the SMART App Launch framework. The resulting client ID can then be used at any EMR Direct-supported FHIR endpoint.
Apps intending to make Bulk Data requests or that will access data for professional purposes can register your app the same way and will also be listed on the App Studio site, but will want to instead let us know you require a "Digital certificate for a UDAP FHIR client workflow" when registering on the EMR Direct website; the UDAP certificate can then be used in UDAP JWT-Based Client Authentication at any EMR Direct-supported FHIR R4 endpoint or a FHIR STU3 endpoint that has elected to enable client credentials grant, and for which the data holder authorizes access. In either case, the data holder must also authorize the app itself.
App Onboarding Process Overview
Requirements for Client Registration
Register as a FHIR Client App developer for access to a UDAP trusted app certificate or client ID and secret.
Connecting to a FHIR Datasource
Determining the baseOAuthURL
FHIR Endpoint Directory (Coming Soon!)
Branding Guidelines (Coming Soon!)
Additional Questions? Visit the HealthToGo FHIR developer group or UDAP Community group