You can run Dragon Copilot inside your own healthcare application. Microsoft publishes the tools. The four building blocks and the first decision on each follow in the table in the third section.
Can you integrate Dragon Copilot into our own custom healthcare application?
Yes. Microsoft publishes the Dragon Copilot Developer Kit for this work. It includes a JavaScript SDK, mobile SDKs for ambient recording, and REST APIs for sessions, configuration, and data exchange. Access to the REST APIs runs through Microsoft’s approval, so settle early who holds that relationship.
What does Microsoft provide for building Dragon Copilot into an application?
Microsoft calls it the Dragon Copilot Developer Kit. The kit is a set of development tools for embedding the Dragon Copilot web UI in your electronic health record app, or integrating Dragon Copilot functionality with your EHR’s UI.
If your organization runs its own clinical application, these are the pieces you would work with. Microsoft lists four: the web app embed, a JavaScript SDK, mobile SDKs, and REST APIs for partners.
What are the four building blocks, and what do you decide first on each?
Each block puts Dragon Copilot in a different place in your application. Each block also asks your team for a different first decision.
Four Dragon Copilot Developer Kit building blocks and the first decision on each
| Building block | What it gives your application | What your team decides first |
|---|---|---|
| Web app embed | The Dragon Copilot web UI inside your application, launched by SMART on FHIR or token authentication | Which launch method your application supports and where the Dragon Copilot panel sits in the clinician’s screen |
| JavaScript SDK | Dragon Copilot functionality built into your own web application | Which screens in your application need Dragon Copilot functions |
| Mobile SDKs | Ambient recording inside your Android or iOS application | Whether clinicians record on a phone or tablet in your application |
| REST APIs for partners | License checks, ambient sessions, configuration, audio, and data exchange between your service and Dragon Copilot | Who holds the Microsoft approval and which identity solution signs your access tokens |
Pick the block by where clinicians work. Settle the Microsoft approval before you plan the build.
Sources: Microsoft Developer Kit and Dragon Copilot APIs for partners documentation. Table by Saisystems Technology.
What does the REST API route require?
Microsoft describes the APIs as a set of REST APIs that enable healthcare IT partners to integrate with Dragon Copilot. Every call needs an access token issued by your identity solution. Microsoft recommends Microsoft Entra ID.
Your identity solution must be added to Microsoft’s allow list. Microsoft says to give the required details to your Dragon partner relations team. You also need a partner ID.
Microsoft’s page does not say whether a health system can build against these APIs directly. Ask Microsoft before you plan the work. The answer decides who owns the approval.
What flows between your application and Dragon Copilot?
Microsoft’s partner APIs cover the full loop of an ambient session:
- Your application checks whether a clinician has a Dragon Copilot license.
- Your application sends patient context, such as demographics and encounter details, before recording starts.
- Audio reaches Dragon Copilot through streaming, or through file upload with the Audio Service, which Microsoft labels preview.
- Configuration, including custom field mappings, travels through the configuration service.
- Artifacts such as transcripts and AI-generated notes return to your application through data exchange.
The last step matters most to your clinicians. The note comes back into your application, where they review it.
How do you choose where to start?
Start from the clinician’s screen. If clinicians already work in a web application you control, begin with the web app embed or the JavaScript SDK. If they record at the bedside on a phone or tablet, begin with the mobile SDKs. If you need your own service to control sessions and move data, plan for the REST APIs and the approval they require.
You can combine blocks. Pick the first one that puts Dragon Copilot in front of a small group of clinicians, then expand. Test the workflow fit with that group before you commit the full build.
What does Saisystems Technology do?
Saisystems Technology is a Microsoft Solutions Partner for Cloud and AI Platforms. Our technical team can help you integrate Dragon Copilot into a custom healthcare application. We can embed the Dragon experience or integrate the specific capabilities you need, such as ambient documentation, dictation, authentication, and clinical data exchange. We handle the technical integration and fit it to your clinicians’ existing workflow.
Bring four answers to the first conversation:
- Which application do your clinicians use, and who builds and maintains it?
- Where do clinicians work: a desktop browser, a phone, or a tablet?
- Which identity solution signs in your users?
- Who on your team can work with Microsoft on the approval?
Where should you read next?
Read the Microsoft Dragon Copilot overview for the product. If your clinicians use a commercial EHR rather than your own application, read Using Dragon Copilot Without Replacing Your EHR.
An integration is one phase of a larger plan. What it takes to deploy Microsoft Dragon Copilot covers all of them. Dragon Copilot admin roles covers who runs it after go-live.
What is your next step?
CIOs and VPs of IT: request the three-week Dragon Copilot trial license and see what Dragon Copilot produces for your clinicians.
