This bothers me. ALL enterprise SaaS prohibits reverse-engineering in its TOS and CSA and most prohibit bots and automation. So, the buyer will need the vendor's explicit permission to use something like 100x; and when the vendor has something on the roadmap, even if it's delayed, there's little chance that the vendor will give this permission. Anybody else bothered by this? Anybody who has a successful workaround?
Yes, the biggest problem with Healthcare AI assistants right now is that there is no way to "prompt" the AI on what a physician needs in a given scenario - eg. "only include medically relevant information in HPI", "don't give me a layman explanation of radiographic reports", "include direct patient quotes when a neurological symptom is being described" etc.
And the prompt landscape in the field is vast. And fascinating. Every specialist has their own preference for what is important to include in a note vs what should be excluded; and this preference changes by disease - what a neurologist want in an epilepsy note is very different from what they need in a dementia note for eg.
Note preferences also change widely between physicians, even in the same practice and same specialty! I'm the founder of Marvix AI (www.marvixapp.ai), an AI assistant for specialty care, we work with several small specialty care practices where every physician has their own preferences on which details they want to retain in their note.
But if you can get the prompts to really align with a physician's preferences, this tech is magical - physicians regularly confess to us that this tech saves them ~2 hours every day. We have now had half a dozen physicians tell us in their feedback calls that their wives asked them to communicate their 'thanks' to us for getting their husbands back home for dinner on an important occasion!
To answer your specific question about where to store data - use Cockroach DB. Where do you plan to host? I'd recommend Netlify - it has good support for Next and integrates well with Cockroach DB.