Get the data right before the EHR conversation starts.
Epic and Oracle Health implementations rarely fail in the software. They fail in the operational layer underneath it: the data fields, reports, and clinical and revenue cycle workflows that no one documented before the vendor conversation started. We are operators who became consultants, and we do not stop at naming the problem.
The Situation
The vendor assumes you know your own operation.
You have decided to move to Epic or Oracle Health. Maybe the legacy system is being sunset, maybe an acquired clinic or physician group forced the question, maybe clinical and revenue cycle leadership finally lost patience with what you have. Whatever the trigger, the next step is a conversation with the vendor.
That conversation assumes you can answer questions about your own operation that, in almost every health system, no one has ever written down. Which data fields actually drive the work, and where they originate. Which of your reports are load bearing and which are duplicates nobody has retired. How the process really runs, including the workarounds, not how the policy says it runs. What has to keep working the day after go-live. The gap between what the vendor assumes and what you can answer is where design and configuration decisions get made without you.
The budget does not blow in the software. It blows in the operational layer, in the fields, reports, and workflows that were never documented before somebody had to configure them.
The Diagnosis
The same foundation gap, in a domain that punishes it.
This is the same problem the rest of the NoBullStrategy practice addresses: an organization acting on data and processes no one has audited, owned, or made trustworthy. Healthcare simply raises the stakes. PHI, interoperability standards including HL7 v2, FHIR, C-CDA and USCDI, and the distance between how your operation actually runs and how the target EHR expects it to run make this far more expensive to get wrong, and decisions made in the design phase without operational input surface as overruns mid-implementation and as clinical and revenue risk at go-live.
So the sequence is not negotiable. Document the operation first: what the data is, which reports matter, how the work is really performed, what must survive the transition. Then have the vendor conversation. And because a recommendation is not a result, we stay through implementation and adoption to confirm the finished configuration actually works in the environment your teams operate in every day.
The Work
Three engagements, laddered.
Each engagement is fixed-scope and stands on its own. Each one qualifies you for the next, and none of them commits you to the one after it. Document the operation first. Then implement.
Operational Data, Reporting & Process Mapping
We document how your data, reports, workflows, teams, and operational processes actually connect, working with individual contributors and leadership, not just the process owners. End-to-end process with handoffs, owners, dependencies, and decision points. Data field inventory with origin and lineage. Report inventory with frequency, audience, and purpose, including the overlaps and duplicates. A current-state read of what is working, what is not, and what needs investigating before you transition.
What you keep: a vendor-ready account of your operational needs, in language your team and your implementation partner can both use.
Implementation Translation & Vendor Facilitation
We translate your operational needs into vendor-facing requirements and sit in the discovery, design, workflow review, and specification meetings as a translation layer. We help your team ask the right questions, clarify where you and the vendor use different words for the same function, and surface where proposed functionality does not meet an operational requirement. Where a direct one-to-one replacement does not exist, we facilitate the alternatives and document what each one costs you downstream.
What you keep: documented requirements, specification requests, named gaps, agreed alternatives, and a record of every decision with its owner.
Full Implementation, Adoption & Validation Support
We stay through the implementation to protect operational continuity and confirm the result works. Tracking whether documented requirements are actually being built. Safeguards and interim workflows so critical operations, reporting, and decision-making keep running during the transition. Rebuilding workflows in the new environment with roles and handoffs intact. Validating reports and data against the agreed requirements. Then testing whether the new process is genuinely being used, investigating why where it is not, and closing the gap.
What you keep: validated workflows and reports, documented decisions and exceptions, adoption findings with corrective actions, and a closeout record of remaining risks.
The mapping engagement is best completed four to six months before the vendor transition process begins, while there is still time to consolidate reports, retire duplicates, and fix inefficiencies rather than carrying them into a new system. Most organizations start there, because that is where the expensive surprises hide, and decide on the later engagements with the facts in hand rather than at the vendor's table.
Capabilities
What the work actually touches.
The Outcome You Keep
You walk in knowing your own operation, not hoping.
The fee is fixed and scoped to a named outcome before work begins. It is what you keep when the engagement ends, whether or not you continue up the ladder.
How We Work
The boundaries are the point.
How a consultant sits between you and your vendor determines whether you keep control of your own implementation. Ours is deliberate.
We do not decide for you
We translate, facilitate, and document. Final decisions, write-ups, and approvals stay with the client. That separation is not a formality, it is what keeps the implementation yours and keeps your operational teams accountable for the outcome.
We never meet your vendor without you
Every vendor conversation is a three-way call. No side channels, no decisions relayed secondhand, no version of events that only one party heard. If it matters to your implementation, you were in the room.
Operators, not analysts
The foundation of the practice is operational professionals who became consultants. We do not stop at naming the issue or recommending an idea. We help you make the change, support you through it, and confirm the result works.
No software to sell
We do not resell Epic or Oracle Health and take no vendor incentive. The recommendation is an honest read of your operation, not a push toward a contract or a license.
Compliance discipline. This work follows the same HIPAA-aware, BAA-ready discipline as the rest of the NoBullStrategy practice, with PHI handled on a minimum-necessary basis and de-identified data used wherever the work allows. A Business Associate Agreement is executed before any protected health information is accessed. NoBullStrategy does not practice medicine and does not provide legal advice; compliance and legal terms are confirmed with your counsel.
Start a Conversation
Before the vendor conversation starts, that's the conversation.
One direct conversation. We'll tell you honestly which engagement fits where you are, and what the work looks like. No deck, no retainer pitch, no software to sell you.