Step-by-step guide to getting a practice to enable your FHIR app in their eCW instance.
Common Blocker
This is likely why "FHIR app authentication is not enabled" appears. Each practice must independently activate your app in their eCW instance before any API calls will work.
Registers app, publishes to production, shares activation code, approves connection.
Generates activation codes, validates connections, enables FHIR access.
Enters activation code in EMR, activates app, manages user access.
Developer submits the app for production approval in the Dev Portal. App must pass all validation checks.
Upon approval, the eCW system generates a unique activation code for the app.
Developer shares the activation code with the practice administrator (via email, portal, or direct communication).
Practice admin logs into eCW EMR and navigates to Admin > Production Activation.
In the Production Activation screen, click the Settings button to access FHIR API configuration.
Select the appropriate app category (Provider Apps or Backend Apps) and click "Set up" to begin configuration.
Paste the activation code provided by the developer and click "Add" to register the app with the practice.
Developer receives a notification and must approve the connection request in the Dev Portal.
After developer approval, the practice admin clicks Activate to enable the app.
Practice admin configures which EHR users can access the FHIR app. Only authorized users will be able to launch or use the app.
Sandbox Testing Limitation
For sandbox testing: Standalone apps must be tested via Postman. Only EMR launch apps have built-in sandbox testing in the Developer Portal.