MsJaneHH

A few months back I was filling up at a gas station and two women in scrubs were on their break, venting about work. OASIS documentation. Missing fields kicking assessments back. Stuff QA didn't catch for days. I had no clue what OASIS even was.

I do now.

Quick rundown for anyone else who doesn't know: home health agencies have to complete OASIS assessments for basically every Medicare patient. Detailed clinical documentation, tied to specific points in the patient's care. Mess it up and it delays billing, can trigger an audit, or just eats hours of a QA nurse's day tracking down what's wrong.

I got curious and dug into what software these agencies actually use. Pretty much two options. Big all in one EHR platforms that do everything, scheduling, billing, documentation, all of it, but buying one means basically re-platforming your whole agency just to fix a documentation problem. Or the newer AI scribe tools, some of them genuinely solid, but they all mean sending real patient data through an AI model somewhere, and getting the HIPAA side of that actually right end to end is a lot harder than the marketing pages make it sound. I read through a bunch of legal breakdowns on this and it's pretty clear a lot of vendors get at least one piece of it wrong.

Neither one felt like what those two nurses wanted. They didn't want a bigger, more complicated system. They wanted the one they already had to stop being wrong.

So that's what I'm building. MsJaneHH. Private, rules based OASIS QA software. No AI in the default path. Every flag it gives you points to a real CMS citation, an actual chapter and section you can go check yourself instead of just trusting a black box.

The thing I'm actually most proud of so far: I ran a full audit of my own rules against CMS's live OASIS data. All 90 items I track, checked one by one. Found a bunch that had gone stale during the recent E1 to E2 transition. Fixed the ones I could verify cleanly. Flagged the rest for an actual credentialed OASIS nurse to look at instead of guessing myself. That's basically the whole point of how I want this to work. It should know the difference between what it can safely fix on its own and what actually needs a person, and it should never just guess when it doesn't know.

This isn't the first time I've built something like this either. Done compliance software for craft distilleries and for cannabis cultivators too. I keep landing in the same spot. An industry with real regulatory weight on it, nobody enjoys the paperwork, and being trustworthy matters a lot more than being flashy.

Right now I'm pre pilot. Site's up, demo works, and I'm looking for the first few home health agencies or OASIS/QA consultants willing to actually try it and tell me what's wrong with it.

If that's you, or you know someone, I'd genuinely love to talk: www.msjanehh.com