Marty KoepkeUseful · Trustworthy · HumanAbout Marty
I am an informatics leader, founder, writer, and applied AI builder. For more than fifteen years, my work has centered on translating between the people doing the work, the leaders accountable for it, and the technical teams building the systems around it.
The throughline
My career has been spent where operations, clinical expertise, and technology meet. I listen to the people doing the work, help a group define what actually needs to change, translate that need into decisions a technical team can act on, and stay with the work through design, implementation, adoption, and refinement.
At CommonSpirit Health, that has meant helping guide informatics strategy and governance across more than 2,500 ambulatory sites and 25,000 clinicians using multiple EHR platforms. The scale is large, but the central question remains practical: did we build the right thing, and did it make the work meaningfully better?
Start with how the work actually happens, including the handoffs, exceptions, constraints, and decisions that are easy to miss from a distance.
Create enough shared clarity that operational leaders, subject-matter experts, vendors, and technical teams can move forward together.
Make ownership, evidence, boundaries, review, and accountability part of the system rather than an afterthought.
A launch is not the outcome. Follow the work far enough to learn whether the workflow improved and where refinement is still needed.
Measured work
The enterprise initiatives I have helped lead include front- and back-office automation across 350 clinics associated with more than $26 million in annual labor savings; ambient documentation work across 222 providers associated with a 14.7% reduction in documentation time and 12% wRVU growth; and quality-improvement work that increased Medicare Annual Wellness Visit completion by 42% and screening compliance by 17%.
These were collaborative enterprise outcomes. My role included informatics leadership, workflow integration, standards, governance, quality assurance, and adoption—not sole authorship of the underlying vendor products.
The founder-builder chapter
Over the last eighteen months, I moved from helping organizations implement technology to building applications of my own. That meant learning why a working screen is only the beginning: useful products also require architecture, data design, integrations, migrations, testing, deployment, observability, security, and governance.
This work is an extension of my informatics career, not a departure from it. The same disciplines still matter: understand the problem, preserve human judgment, define the decision boundaries, test the whole workflow, and be honest about what the technology can and cannot do.
Founder-built product
An AI visibility and business-accuracy product that measures what major AI systems say about a business, separates observation from evidence, and gives an owner a practical next move.
Visit Daizie.ai ↗Application prototype
A connected operating environment for moving ideas through prioritization, assignment, delivery, resource balancing, and portfolio oversight.
Explore the workflow tools →Education and credentials
I distinguish carefully between products I designed and built, enterprise vendor products I helped implement and govern, and ideas I am still testing. Credibility depends on making those boundaries visible.