Anything that second guesses my clinical judgment, and/or requires extra paperwork to do so, had better be able to show its justification in an intelligent manner. There is a lot involved in evaluating a patient that is not encoded in machine-readable form, so some percentage of things software reports is going to be wrong or pointless. (Trivial example: The K is 3.4. Is the patient hypokalemic?) The time spent ignoring nuisance notices may render the whole thing useless, even if there is useful information somewhere.
Have practicing physicians intimately involved in the UI design process, so the resulting product is usable to physicians and actually saves time. Billing software in disguise such as Epic has a terrible user experience and could be so much better.
There's more, but I have to head to work...
Eef: I've seen the horror that is Epic's 1980's terminal SQL nightmare backend. Lipstick on a dead, rotting windows-only pig running on citrix.
Does the software parse free text, depend on someone taking the time to curate a list of "problems" or "diagnoses", or just look at lab values? What is the explanation given by the software when it makes a recommendation, other than deference to a statistical model?
Why would I, a physician, want to spend time or money on this rather than depend on my own sensibilities and training? (I am not going to watch the demo video on your website because I will not agree to an NDA.)