Design Your Integration

The first step to take when integrating Blueprint into your application is to choose an integration method:

Integration Method	How it Works	Pros and Cons
UI Only	You embed the Blueprint UI as an HTML element in your application. Your application front end configures the UI and listens to events from Blueprint via JavaScript. Blueprint handles audio capture and the clinician uses the embedded Blueprint UI to review and edit the clinical artifacts. The artifacts are inserted into your application via front end code.	Minimal development time, easy to integrate quickly. Leverage the existing battle-tested Blueprint audio capture technology. Less customizable.
UI + API	You embed the Blueprint UI as an HTML element in your application. Your application front end configures the UI via JavaScript. Your application backend calls Blueprint APIs to exchange data. Blueprint handles audio capture. Customization of the clinical artifacts can be done by the clinician via the embedded Blueprint UI or via API calls. The artifacts are inserted into your application via API calls or webhooks.	Requires some development time. Leverage the existing battle-tested Blueprint audio capture technology More customizable.
API Only	You implement your own UI. Your application backend calls Blueprint APIs to exchange data. You handle audio capture and call Blueprint APIs to upload audio and generate clinical artifacts. The artifacts are inserted into your application via API calls or webhooks.	Requires significant development time. Need to rebuild audio capture technology in your own system. Most customizable.