Skip to content

Clinical Workflow Assessment

Almost every failed healthcare automation project failed at the same point: the organization automated the workflow it could describe rather than the workflow that was actually running. The described workflow lives in a policy document. The real one lives in the workarounds staff invented to make the policy survivable.

$24,997

Fixed fee. 3 to 5 weeks.

The assessment finds the real one. We shadow the people doing the work, trace where protected health information genuinely moves, audit what your systems can and cannot support, and hand you a prioritized roadmap with cost, effort, and expected return attached to each item.

It is deliberately a fixed fee and a fixed scope. You get a document you can take to a board, use to brief another vendor, or act on yourself. There is no obligation to build with us afterward, and a meaningful share of assessments conclude that some items should not be built at all.

What you receive

PHI flow map

Every point where protected health information enters, moves through, rests in, or leaves the workflows in scope, including the paths that exist only because a staff member built them.

Technical infrastructure audit

What your EHR, practice management system, clearinghouse, and interface engine can actually support, verified rather than assumed from vendor documentation.

Time and cost baseline

Measured staff time per workflow step, converted into annual cost, so the return on any proposed automation has a denominator.

Prioritized automation roadmap

Each candidate initiative sized for effort, cost, risk, and expected return, sequenced so early work makes later work cheaper.

Compliance gap register

Where current practice diverges from your own policies and from HIPAA requirements, with severity and remediation effort noted.

Board-ready summary

A short document written for people who will not read the technical appendix, with the financial case stated plainly.

How the engagement runs

In order, with what happens at each point stated plainly.

  1. Execute the BAA and scope

    A business associate agreement is signed before we look at anything. Scope, access, and named contacts are agreed in writing in the first week.

  2. Observe the work

    We sit with the people performing the workflows in scope. Not interviews about the process, observation of the process.

  3. Trace the data

    We follow PHI through every system, interface, export, and manual step, including the spreadsheets and shared drives nobody mentions in interviews.

  4. Audit the systems

    We verify what integration capability actually exists in your specific environment and version, rather than what the vendor’s documentation claims.

  5. Model the return

    Measured time and cost data feeds a return model per candidate initiative, with the assumptions written down so you can argue with them.

  6. Present and hand over

    A working session with your leadership, then the full document delivered. Yours to use with or without us.

This is a good fit when

  • Organizations that have tried automation before and it did not stick
  • Groups planning a multi-year automation program that needs a defensible sequence
  • Leadership that needs a costed case before releasing budget
  • Teams choosing between building internally, buying a platform, or hiring a partner

This is the wrong engagement when

  • Single narrow workflows where the problem is already well understood
  • Practices below roughly ten providers, where the assessment usually costs more than it can return
  • Organizations looking for a vendor selection report rather than an operational one

If any of these describe you, say so on the call. We would rather scope a smaller engagement correctly than a larger one badly. (307) 454-0600

Common Questions

Do we have to build with you afterward?

No, and the assessment is priced on the assumption that you might not. The deliverable is written to be usable by your internal team or another vendor. We would rather produce work that stands on its own than a document that only makes sense as a sales pitch.

How much of our staff’s time does this consume?

Typically four to eight hours per workflow owner across the engagement, most of it observation while they do their normal work rather than meetings. We plan around clinic schedules, not the other way around.

What if the assessment concludes we should not automate?

Then that is what it says. Several assessments have concluded that the highest-return action was fixing a configuration or a staffing model rather than building software. You still get the map, the baseline, and the compliance register.

Request this engagement.

Tell us about the organization and the workflow. We will come back with a scope, a timeline, and an honest read on whether this is the right starting point.

Or browse the workflows we automate first.

Do not include protected health information in this form. We execute a business associate agreement before any PHI or workflow detail is shared.

Start with a conversation, not a proposal.

A 45-minute call with a senior engineer. We will tell you honestly whether automation is the right answer for the workflow you have in mind.