--- title: Introduction to v1.0 integration with Autoscriber slug: api-docs-v1 docTags: vgl-t_YFhFjtA_SAFi1kZ createdAt: 2025-08-14T07:07:58.069Z --- :::hint{type="danger"} The v1.0 Autoscriber app integration is an out-dated version of the integration. To utilise the latest Autoscriber features, including assistant functionality, standardised data structures and output aligned with the FHIR standard, and more, please navigate to [🚀 Autoscriber v2.0 App Integration](docId\:uM_SjBJ3FHqozXXTUBvLT). ::: ## 📌 Introduction **Autoscriber** app v1.0 is a clinical digital scribe that does far more than just transcribe. It listens to doctor-patient conversations and intelligently generates **structured documentation in real time**. By automating note-taking and form completion, Autoscriber helps clinicians spend less time on documentation and more time on patient care. This guide is designed to help **EHR developers understand the available integration methods** and how to seamlessly incorporate Autoscriber into their platform - whether through a lightweight embedded app, SDK or API. ## 🔁 Integration Methods |
| **Embedded Web App** | **Scribe SDK** | **Scribe API** | | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Use Case Fit** | Perfect for EHRs wanting a simple integration with Autoscriber's digital AI scribe and is happy to embed Autoscriber's UI in an iframe, with the ability to sync the resultant note with the EHR. | Perfect for EHRs wanting full control over the UI, with the ability to utilise a simple integration method that handles the browser recording for you. | Perfect for EHRs wanting full server-side integration with control over workflow and data handling end-to-end. | | **Capabilities** | - Transcribe consultations or medical conversations - Generate structured summaries in the form of medical notes across a variety of specialisms - Can launch contextually (e.g., with patient name and gender) - Return results to EHR via API - Minimal setup with flexible integration points outside the core UI | * Transcribe consultations or medical conversations * Generate structured summaries in the form of medical notes across a variety of specialisms * Seamlessly integrate with existing EHR workflows and UIs via your frontend * Manages the recording for the EHR * Supports automation of form/note population using API responses | - Transcribe consultations or medical conversations - Generate structured summaries in the form of medical notes across a variety of specialisms - Seamlessly integrate with existing EHR workflows and UIs via your backend. - Supports automation of form/note population using API responses | | **Delivery Method** | Embedded via an iframe | Calling SDK methods | RESTful APIs | | **Data Output Format** | Structured JSON | Structured JSON | Structured JSON | | **Authentication** | API Key and token-based authentication | API Key and token-based authentication | API Key and token-based authentication | | **Customisation Options** | Theming, behaviour via config | Full control over integration, UI and data handling | Full backend control; no front-end dependencies. | | **EHR UI Changes** | Minimal, just to create the space for the iframe | EHR manages all UI aspects. | EHR manages all UI aspects. | | **Latency / Real-Time** | Real-time transcription and feedback in iframe, near real-time when synced with EHR | Near real-time processing | Near real-time processing via audio chunks processing, depending on setup. | | **Ideal For** | Fast adoption required with minimal dev resources | Deep integration required where EHR wants control over the UI | EHRs with mature backend infrastructure that want to embed functionality seamlessly into their workflows | | **Environments** | Test & Production, which can be integrated into the EHRs Test and Prod environments | Test & Production, which can be integrated into the EHRs Test and Prod environments | Test & Production, which can be integrated into the EHRs Test and Prod environments | | **Security Considerations** | GDPR, NEN 7510 & ISO 27001 compliant | GDPR, NEN 7510 & ISO 27001 compliant | GDPR, NEN 7510 & ISO 27001 compliant | | **Typical Time to Integrate** | 2-6 weeks | 4-8 weeks (depending on EHR API maturity) | 5-10 weeks (depending on EHR API maturity) | | **Link to Dev documentation** | [Overview](docId\:mH7G2QcLZlLUYFIy3SMgx) | Here | Here | # 🏗️ Architecture Diagrams The three integration methods have different architectures, which may influence which option is chosen. These can be seen below. ## Embedded Web App The embedded web app option will require a section of the EHR real-estate to allow for the embedding of the Autoscriber app via an iframe. ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/65980692ca9db2764426fd7e/images/6853edd00bda0b79f26aac55/file-ulC6CHED2h.png) ## Scribe SDK The scribe API option allows for complete customisation of the EHR UI, which will be populated with the results from the Autoscriber APIs. ![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/65980692ca9db2764426fd7e/images/6853edb2f7524101f69b4715/file-wtX8XWQzQy.png)