Moving the Profession Forward. Again.

I'm writing this from a folding chair behind our booth in Las Vegas, shoes off, voice mostly gone. If you were at the Assembly this week, you know the feeling. Mandalay Bay is a long walk from anywhere to anywhere. 

We came here to unveil OPIE 2.0 under a theme we've earned the right to say: Moving the Profession Forward. Again. Thirty-some years ago, a practicing clinician named Paul Prusakowski, CPO, FAAOP, decided O&P deserved software built for O&P instead of a general medical system with a few fields renamed. He was treating patients when he started building it, which is why it worked. It was not a marketing idea. It was a conviction that this profession was distinct enough, and serious enough, to be worth building for. 

This week showed me that the conviction still holds. 

What happened at the booth 

We expected people to come by, and we expected some skepticism. The aisle in front of us jammed up for most of the week. The skepticism showed up too — and it turned into the most useful conversations we had. 

We ran demos back-to-back. We ran out of chairs. Several of you stood around. One practice owner brought her whole team over on their way to lunch, pointed at the screen, and said, "Show them the billing part again." 

The questions were the best part, and they were not softballs: 

• "How much retraining does my staff need?" 

• "What happens to my WIP the day we switch?" 

• "Do I have to convert all of my old data?" 

• "Will my documentation still hold up in an audit?" 

Every one of those questions came from someone who will personally live with the answer. That is the toughest audience there is, and they liked what they saw. 

The theme is not about software 

I want to be careful here, because a booth is a terrible place to be humble and I've been standing in ours for two days. The theme isn't really about a release. It's about a habit this profession has of pushing itself forward when it could be easier to coast. 

Look at what else happened this week. Practitioners filled an 8:00 a.m. workshop on CMS updates and year-round accreditation compliance, by choice. "From the Payer's Perspective" and "Reimbursement and Documentation" drew crowds for the least glamorous, most consequential work we do. Sessions like "Measure. Monitor. Justify." and "Stop Guessing, Start Scoring" were full of people who have decided that proving outcomes is part of the job now. Students and residents stood by their posters defending methodology to anyone who asked. That's a profession moving, not an industry drifting. 

The forward motion is not automatic. It happens because a few thousand people decide to be inconvenienced on purpose — travel, time away from patients, a week of missed schedule — for the sake of getting better. 

What I heard between the demos 

A pattern showed up in almost every conversation, and it had nothing to do with features. 

Most practices are not held back by a lack of good ideas. They're held back by good ideas that never become repeatable. Somebody comes home from a meeting like this fired up, tries a new intake process for nine days, gets slammed with three unexpected deliveries and a staff illness, and the new process quietly dies. Nobody decided to abandon it. It just never got built into how the week runs. 

The part that changes this 

For most of the history of software — ours and everybody else's — making the system match your process meant calling somebody. You described what you wanted, it went on a list, and if enough other practices wanted it too, maybe it showed up in a release two or three quarters later. So practices did the rational thing and built their process outside the software. Sticky notes. A shared spreadsheet. A Word doc that only one person knows how to update. A training conversation that has to be repeated with every new hire and drifts a little every time. 

In OPIE 2.0, the process lives in the software, and you control it. 

Want a new step in the fabrication process for a KAFO? Create it, publish it to your team, and require it. The job does not advance until that step is done. Have hard-won knowledge about how authorization actually gets approved at your top three payers? Build those steps into the workflow and save them. The next time anyone on your staff starts an auth, your steps are sitting right there in front of them. Author a form layout once and publish it to every branch. Set your procedures, justifications, fee schedules, and chart templates once, in one place, and use them everywhere. 

No support ticket. No waiting for a release. Ten minutes, and the way you want it done becomes the way it gets done. 

That is the whole difference between a good idea and a process. The idea you carried home from Las Vegas has about a nine-day life expectancy as a conversation. As a required step inside the system your team already works in every day, it has an indefinite one. Log into OPIE Anywhere (2.0).  If you do not have it, reach out to your CSM. 

The one-week follow-through checklist 

This is what I'd do Monday morning:  

Pick one. Look at your notes and choose a single change. Not five. The rest go on a "later" list you'll actually revisit next quarter. 

1. Name the owner. A change with no named person is a wish, and it should not automatically be you. 

2. Define what "done" looks like in numbers. "Better documentation" is not a goal. "Every initial eval note complete before the clinician leaves for the day, measured weekly" is a goal. 

3. Put it on the calendar as a recurring check. Fifteen minutes, same day each week, for six weeks. If it survives six weeks, it's a process. 

4. Tell your team what you're not doing. Protecting the one change from the other four is the actual leadership act. 

5. Build it into the system, not a spreadsheet. If the change only exists in a document, it depends on memory. If it exists as a step your team has to complete, it depends on nothing. You can configure that yourself now, this week, without asking us for permission. 

Thank you 

To everyone who stood in that aisle, waited for a chair, pushed back on our assumptions, and told us what you need: thank you. That feedback shapes what comes next more than any internal roadmap meeting ever has.