If you're developing an EHR and are looking to integrate with Nabla Copilot, you may pick one of the strategies below.

Get in touch if you wish to discuss your use case in more detail.

Method	For	Pros	How
Front-end integration	Web-based EHRs	Simple and straightforward flow, great for proof-of-concept and simple integrations. No need to set up the Nabla API. Ability to leverage the existing Nabla UI.	Using the Chrome extension or embedding copilot.nabla.com as an iframe in your EHR. On your EHR domain, you may request the "Copy" button from the extension or the iframe to be replaced with an "Export to <YOUR_EHR>" button. In that case, Nabla Copilot will export the generated note and structured information via JavaScript. The EHR web app should listen to window events to receive the required information when the button is clicked, and fill the right fields in the EHR.
Hybrid Front-end / back-end integration	Web-based EHRs	More robust than the above. Ability to leverage the existing Nabla UI.	Same as above, except the note and structured information is sent directly to your server via a webhook. The target identifier (typically patient / encounter identifier) is passed by the EHR web app to Nabla Copilot via a front-end message.
Back-end integration	All EHRs including ones available on mobile apps	For deep UI integration. Highly customizable.	Server-side integration using Nabla Copilot APIs.