Introduction to v1.0 integration with Autoscriber

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 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