by ar7hur on 3/14/23, 2:16 PM with 137 comments
We're Alex, Martin and Laurent. We previously founded Wit.ai (W14), which we sold to Facebook in 2015. Since 2019, we've been working on Nabla (https://nabla.com), an intelligent assistant for health practitioners.
When GPT-3 was released in 2020, we investigated it's usage in a medical context[0], to mixed results.
Since then we’ve kept exploring opportunities at the intersection of healthcare and AI, and noticed that doctors spend am awful lot of time on medical documentation (writing clinical notes, updating their EHR, etc.).
Today, we're releasing Nabla Copilot, a Chrome extension generating clinical notes from video consultations, to address this problem.
You can try it out, without installation nor sign up, on our demo page: https://nabla.com/copilot-demo/
Here’s how it works under the hood:
- When a doctor starts a video consultation, our Chrome extension auto-starts itself and listens to the active tab as well as the doctor’s microphone.
- We then transcribe the consultation using a fine-tuned version of Whisper. We've trained Whisper with tens of thousands of hours of medical consultation and medical terms recordings, and we have now reached an error rate which is 3× lower than Google's Speech-To-Text.
- Once we have the transcript, we feed it to a heavily trained GPT-3, which generates a clinical note.
- We finally return the clinical note to the doctor through our Chrome extension, the doctor can copy it to their EHR, and send a version to the patient.
This allows doctors to be fully focused on their consultation, and saves them a lot time.
Next, we want to make this work for in-person consultation.
We also want to extract structured data (in the FHIR standard) from the clinical note, and feed it to the doctor’s EHR so that it is automatically added to the patient's record.
Happy to further discuss technical details in comments!
---
by swatcoder on 3/14/23, 3:18 PM
This is a task that perhaps can be supported with AI some day, but there are fields that deserve the application of a mature technology, not the gold rush rush game of integrating today's hottest thing.
by JohnFen on 3/14/23, 6:43 PM
My doctor could vet it for accuracy, I suppose, but why? He's already putting his notes in my records anyway.
by v4dok on 3/14/23, 2:56 PM
Obviously the business model is harder with on-prem, but cloud-first for doctor notes is in the long run much harder.
by priyanmuthu on 3/14/23, 3:01 PM
by avgDev on 3/14/23, 3:04 PM
How are 2 party consent states handled?
Is this HIPPA compliant?
by NorthOf33rd on 3/14/23, 3:08 PM
Nothing like “subtly wrong” clinical notes to affect positive medical outcomes. And time pressed medical professionals are certainly well suited to vigilance tasks like correcting machine generated errors. /s.
I sincerely hope this never sees the light of day.
by urduntupu on 3/14/23, 3:03 PM
Doctor's already today spent too little time with their patients to understand diseases holistically enough.
Adding technically between these 2 will make treatments in most of the cases worse, not better.
by orcajerk on 3/14/23, 2:58 PM
by D13Fd on 3/14/23, 4:35 PM
That way you still get the benefit of summaries, without polluting the medical records with hallucinated AI nonsense.
by Terretta on 3/15/23, 1:51 AM
This is spectacular for telemedicine in the post-covid regulation environment.
The new model is an onsite medical assistant taking patient vitals and setting up the Zoom, the patient then talks to an APRN (Advanced Practice Registered Nurse) in the patient's field (e.g. subacute care, gerontology, etc.).
The APRNs spend 30 minutes reading the file, tele-consult with a patient for a half hour. Medicare pays for the half hour. Then the APRN has to spend ~60 minutes turning that session into the EHR notes. Many just don't, they make an ultra short note, and hope Medicare doesn't challenge it. Patient loses. If too strapped for time, they also may not pre-read, because they only get paid for the video conf time. Patient loses.
Downside I see with this is the APRNs doing telemedicine are making about 1/4 of the rate they should be, and can't afford an expensive tool. The telehealth provider is not going to pay for it, they get paid for the 1/2 hour, the wasted time is not out of their pocket, so they won't spend to make it up. This is going to be on the nurse, who likely can't afford it.
On the plus side: time saved with this tool would go directly to ability to pre-read, or ability to see a patient an hour instead of one per two or three hours. It would also permit a higher caliber of expertise nurse to do tele-medicine visits in off days, because the time saved could bring comp back more in line with the expertise.
Go for it!
by 908B64B197 on 3/14/23, 2:58 PM
Here's the thing: rigorous medical documentation is not a burden on the practitioner, but rather an integral part of treating someone. You need detailed historical data to diagnose some tricky conditions and treat them correctly.
What's the tool doing to prevent a practitioner from simply blindly copy-pasting the output without verifying it?
> and saves them a lot time.
Which means more billable. Have you considered charging per medical act performed?
by norgie on 3/14/23, 6:23 PM
I'd be pretty concerned if my doctor relied on this to be honest.
by ysavir on 3/14/23, 3:07 PM
by rubatuga on 3/14/23, 9:02 PM
On-prem stuff is more tricky, but useful for privacy. Nvidia is supporting the space with their health AGX series.
by hartleybrody on 3/14/23, 3:19 PM
by lukah on 3/14/23, 3:08 PM
by cinntaile on 3/14/23, 3:57 PM
I think the general idea is interesting but this is the wrong benchmark to convince people imo. What is the actual error rate of Google's Speech-to-Text on this your data? How convinced are you that it's properly labeled? That it's 3x lower isn't necessarily impressive. Then a follow up question... What I as a patient would want to know is something else, how does it compare against medical secretaries that usually transcribe documents like these?
by CiceroCiceronis on 3/16/23, 10:02 AM
by tomasyany on 3/14/23, 2:52 PM
by retox on 3/14/23, 9:16 PM
by gigel82 on 3/14/23, 8:11 PM
I'd recommend looking at a fully self-hosted LLM alternative or ensuring the GPT-3 endpoint you're using is compliant (I've heard Azure has a GPT-3 API that is supposedly more "compliant").
by ar9av on 3/14/23, 3:17 PM
This could elevate a lot of problems we have with our public healthcare(Canada).
by tzm on 3/14/23, 4:30 PM
by stopachka on 3/14/23, 2:53 PM
by phren0logy on 3/14/23, 2:59 PM
by mitchellpkt on 3/14/23, 3:28 PM
by Banjor on 3/16/23, 9:37 AM
by SkyPuncher on 3/15/23, 12:15 AM
This is actually a solved problem in medicine, already. Maybe not solved, but absolutely "good enough". M-Modal, Dragon, and Telephone services (yes, call someone and have them translate) all exist. They all translate notes well enough. For most doctors, it's a huge improvement over typing.
The problem is primarily access. Most institutions simply do not want to pay for this. They don't view it as necessary. Further complicating the issue. Unless a physician is in private practice, they have little to no control over their ability to use a tool like this. HIPAA is far too high of a barrier.
You're trying to implement a technical solution to what's ultimately a politics/human problem.
----
I've spent a bunch of time in the space, both as a MedSpouse and the CTO of a HealthTech company. I wish you the best of luck as I'd love to see life be easier for my wife, but this is _extremely_ far from being MVP viable.
* HIPAA - You absolutely, 100%, without a doubt need to be HIPAA compliant. You likely want to be HITRUST compliant as well. You're very, very clearly a Business Associate (HIPAA term) and processing PHI. Without that, you're dead in the water.
* Chrome extension - This is not going to cut it. At baseline, it requires copy and pasting between Chrome and the EHR system. Bad UX.
* More tactically, most EHR access occurs via remote access, like Citrix. Often from a thin-terminal on the hospital floor or at a med station. These are locked down environments that have a high likely hood of not having Chrome installed _and_ not being allow to install _any_ software (including Chrome extensions).
* Doctors need real-time feedback and the ability to correct. Real-time feedback is critical because carrying a patient takes mental load. Part of the purpose of notes is to create a written record that "closes" a patient for the time being. An async service isn't really helpful since it generates an interrupt after the physician has already moved on.* Accuracy is important. Accuracy is even more important with _extremely_ similar and _extremely_ uncommon words. For example, can this system differential between prednisone and prednilisone? In fact, can it even identify those words? Can it do it with an accent?
* FHIR is only as much of a standard as tables are to relational databases. The hard part is the thousands of custom fields that are different between health systems.
* Structured data really isn't used or useful in medicine. You might have a medication list that can be structured as data, but actual notes include a lot of prose. I believe part of this is necessary to capture the nuance/minutiae of some healthcare. Part of it stems from the lack of any standard.
* Again, this is all possible already. Tele-notes have been done since the introduction of EHR systems.
* Nobody is going to use a Chrome extension.
by ouid on 3/14/23, 2:58 PM
by BCM43 on 3/14/23, 2:59 PM
by rubenstern on 3/14/23, 5:58 PM
by kgiddens1 on 3/14/23, 6:55 PM
by mjdowney on 3/14/23, 3:15 PM
by futureisvintage on 3/14/23, 9:06 PM
by avipars on 3/14/23, 8:27 PM
by ismosoft on 3/14/23, 8:35 PM
by ismosoft on 3/14/23, 8:34 PM