DeepScribe
DeepScribe · Ambient AI medical scribe
Public sources reviewed . Risk classification and recommended policy are Ayliea's subjective assessments — not vendor certifications.
Scope of this recommendation
Contracted DeepScribe clinical documentation workflow; current security evidence needed before PHI approval.
Public documentation review only. Current audit reports, certificate scope, executed contracts and customer settings were not independently examined. An omitted assurance claim is not evidence that the vendor lacks it.
- Storage and processing locations
- Current location and subprocessor boundaries were not established from accessible public documentation; obtain written confirmation.
- Retention and ZDR scope
- No fixed audio/transcript/note schedule or ZDR commitment established from the accessible security page; confirm retention and termination deletion contractually.
- Vendor-reported audits / certifications
- Not established in this public-source review
Why this rating
DeepScribe describes encryption, access controls and healthcare safeguards. The public trust-center content could not be inspected in this review, so earlier audit dates, exact region and named model-provider claims are not repeated as verified facts.
Considerations before deploying
- Execute the applicable BAA and document recording notice/consent before patient use.
- Obtain current product-scoped assurance, subprocessor/data-flow details and contractual training/secondary-use terms.
- Validate audio, transcript, note and backup retention, deletion and EHR access; require clinician review before finalizing documentation.
Sources
- DeepScribe security practices (www.deepscribe.ai)
- DeepScribe Trust Center (report access required) (trust.deepscribe.ai)
Need a vendor review for your use case?
A scoping call defines the systems, data flows and vendor evidence to review for your use case.