voize
voize is a German voice documentation company built for nurses and caregivers rather than physicians, and it is the only vendor in this category running its model ON DEVICE. Founded in 2020 by three systems engineering students at the Hasso Plattner Institute after one founder's grandfather moved into a nursing home, it now serves more than 75,000 nurses across over 1,100 care facilities in Germany and Austria, and raised a 50 million dollar Series A led by Balderton Capital in November 2025 to expand across Europe and enter the United States. Its large language model runs locally on the caregiver's smartphone and works without a constant internet connection, which the company frames as simultaneously a privacy, reliability and accuracy decision. It covers the nursing workflow rather than the office visit, spanning documentation, shift handovers, wound documentation and imaging, vital signs, medication administration, scheduling and emergency alerts, and it syncs into existing care documentation systems. A study conducted with the Charité in Berlin reported roughly 30 percent time savings on documentation.
Capability Axes
Proprietary domain specific speech recognition and an on device large language model, both built in house by founders with systems engineering backgrounds. The technical choice to run inference locally rather than calling a hosted model is itself evidence that model work is the company rather than a wrapper around someone else's API.
Not assessed, and this is the most consequential gap in the record. Nothing was located describing the review gate between spoken input and a committed entry. That matters more here than for an office visit scribe because of what voize writes into: medication administration records and vital signs are legally significant clinical documents where an error is a patient safety event rather than a wording problem, and emergency notifications are an action rather than a record. Establish directly what a caregiver confirms, and at what point, before any of those categories are committed.
More architecturally specific than most in this category. voize states what the model is, an on device large language model, where it runs, locally on smartphones, and what it was built to handle, namely medical shorthand, regional accents and multilingual speech patterns. That is a description a buyer can test rather than a set of adjectives. Held at B because the headline accuracy claim of 99.2 percent is published without any methodology, denominator, reference standard or breakdown, and an accuracy figure that precise invites the question of what exactly was measured.
Above the vendor testimonial norm of this category because an academic institution was involved. A study conducted with the Charite in Berlin, one of Europe's largest university hospitals, reported roughly 30 percent time savings on documentation, and a separate reported figure puts the saving at an average of 39 minutes per shift. Deployment scale is genuine rather than aspirational at more than 75,000 nurses across over 1,100 facilities. Held at B rather than A because no peer reviewed publication was located, the study design and cohort were not retrieved, and this index does not assert details it has not seen. A published Charite paper would move this to A.
The strongest privacy architecture located in this category, because it is structural rather than contractual. The model runs on the caregiver's device and functions without a constant internet connection, so speech is processed where it is spoken rather than transmitted to a vendor for inference. That removes an entire class of exposure rather than promising to manage it, and unlike a retention policy it is verifiable by the buyer simply by testing the app offline. Read the boundary precisely: inference is local, but the resulting structured documentation still synchronises into the care record system, so this protects the audio and the processing rather than the finished record.
Not applicable as assessed. Deployment to date is Germany and Austria under GDPR rather than HIPAA. The company has stated intent to enter the United States market and partner with skilled nursing providers, so a United States buyer should establish business associate agreement posture directly rather than inferring it from the European position.
Not assessed. No named or dated attestation and no trust centre located in this pass, which is the obvious gap alongside an otherwise excellent privacy architecture.
Not a regulated medical device and none claimed. Worth flagging for the United States expansion: documentation of medication administration sits closer to regulated territory than narrative note generation, and the classification question should be asked rather than assumed.
Treats the category's central failure mode as a design requirement rather than a disclaimer, which is rare and worth crediting. voize states its model was built to understand regional accents and multilingual speech patterns alongside medical shorthand. That matters unusually much for this specific user population: care work in Germany and Austria is disproportionately performed by multilingual and migrant staff, so a speech model that degrades on non native accents would fail hardest on exactly the workforce it is sold to support. Held at B because no performance breakdown by accent, language or speaker group has been published, so the design intent is stated rather than demonstrated. Note the pattern across this index: the two vendors engineering for accent variation rather than disclaiming it, voize and Corti, are both European and both build their own models.
Integrates into existing care documentation systems through APIs and interfaces with data synchronisation of documentation and client information, with Vivendi PD named as a supported system. Note the segment difference: these are long term care documentation platforms rather than hospital electronic health records, so integration breadth is measured against a different and largely German speaking market than the rest of this category. Coverage outside that market is not yet evidenced.
The clearest answer to the where does the data go question available anywhere in this index, because the answer is that it does not go. Inference runs on the device in the caregiver's hand and continues working without a constant internet connection, which also solves a practical problem specific to the setting: care homes and hospital wards have poor connectivity in exactly the rooms where documentation happens. Compare the two other strong answers in this category, Corti offering sovereign cloud or on premise deployment and Lyrebird confining everything to one national jurisdiction. voize is the only one that removes the transmission of speech entirely.
No published rate card located. Sold to care facility and hospital operators rather than to individual clinicians, so pricing is negotiated at the organisation level. One market signal rather than a price: some care providers now cite voize in job listings as a recruitment advantage, which suggests operators are valuing it partly as a retention instrument rather than purely as a documentation cost line.
Covers a workforce this index otherwise barely reaches. Where nearly every competitor documents a physician office visit, voize covers the nursing and caregiving day across care homes and hospitals: documentation, shift handovers, wound documentation with imaging, vital signs, movement logs, medication administration, scheduling and emergency alerts. Shift handover in particular is a high risk communication event with no equivalent in outpatient documentation. The only comparable nursing capability in this index is the Dragon Copilot nursing edition, which is a module of a physician product rather than a product designed for the role. Geographic reach is currently Germany and Austria.
Pricing
Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.
| Entry Price | Pricing Basis | BAA Tier | Implementation | Source |
|---|---|---|---|---|
|
Not published. Sold to care facility and hospital operators
|
Organisation level, negotiated with care providers and hospitals rather than licensed per clinician self serve. | Not applicable as assessed. GDPR frame, Germany and Austria. Establish separately for United States deployment. | Not published. Runs on standard smartphones with on device inference, so there is no server infrastructure to provision, though integration with the existing care documentation system is required. | Vendor Published |
No published pricing and no self serve path, which is consistent with a product sold to care home and hospital operators rather than to individual clinicians. The buying case is also structurally different from the rest of this category: the reported benefit is roughly 30 percent less documentation time across an entire nursing workforce rather than minutes returned to a physician, and some operators are treating it as a recruitment and retention instrument by naming it in job listings. That reframes the business case from labour cost saved to staff turnover avoided, which is the more expensive problem in long term care.