Case study

Implementing clinical decision systems adopted across 100+ hospital go-lives

Implemented the clinical decision rules — Best Practice Advisories, order sets, and quality-measurement workflows — that fired during live clinical workflows across 100+ hospital go-lives. Proposed a company-wide escalation process for regulatory updates and critical bugs that was adopted across the organization.

2012–2013

Implementation Engineer / Technical Services. Configured clinical decision-support rules, quality-measurement workflows, and proposed the escalation process adopted company-wide. Coached 100+ hospitals through go-lives as subject-matter expert.

Public MyChart app screenshot
MyChart — the EHR surface where the decision rules fire, and where institutional workflow architecture has to work.

Implemented the clinical decision rules — Best Practice Advisories, order sets, and quality-measurement workflows — that fired during live clinical workflows across 100+ hospital go-lives. Proposed a company-wide escalation process for regulatory updates and critical bugs that was adopted across the organization.

Each hospital go-live required hundreds of clinical decision rules, but there was no systematic escalation path when regulatory updates or critical bugs landed mid-deployment. During go-lives, I saw how close a misrouted alert could come to burying a critical lab result — not as a hypothetical, but as a real risk that clinicians and implementation teams managed in real time. Diverse hospital policies made per-organization customization the default, creating maintenance debt that would compound across 100+ implementations.

Each hospital go-live required hundreds of clinical decision rules, but there was no systematic escalation path when regulatory updates or critical bugs landed mid-deployment. During go-lives, I saw how close a misrouted alert could come to burying a critical lab result — not as a hypothetical, but as a real risk that clinicians and implementation teams managed in real time. Diverse hospital policies made per-organization customization the default, creating maintenance debt that would compound across 100+ implementations.

Proposed building reusable rule configurations rather than per-hospital customization. Automated Best Practice Advisories that triaged alerts between binding and advisory based on policy constraints, and a company-wide escalation process that gave regulatory updates and critical bugs a defined owner and response time.

Configured clinical decision-support rules in Epic's rule engine that mapped hospital policy constraints into automated triage logic — reducing alert fatigue without losing safety checks. Proposed the escalation process for regulatory updates and critical bugs and advocated for its adoption across Epic's internal teams. Supported named go-lives at Owensboro Health (hospital relocation) and UAMS, and coached 100+ hospitals as subject-matter expert.

100+ hospital go-lives supported with configured clinical decision rules. The escalation process was adopted company-wide — the origin of the escalation-design philosophy I still practice.

1 Epic's MyChart is the EHR surface clinicians navigate daily.

Public product context for the EHR workflow environment.

Epic Systems
1 Regulatory update or critical bug detected 2 Escalation process triggered — owner and response time defined 3 Clinical decision-support rules updated in Epic's rule engine 4 Rules deployed across affected hospitals 5 Quality-measurement workflows verified against federal standards
  • High-stakes clinical workflows where a misrouted alert could bury a critical lab result.
  • Regulatory deadlines tied to federal incentive programs (Meaningful Use).
  • Diverse hospital policies creating pressure for per-organization customization — resisted in favor of reusable configurations.
  • Best Practice Advisories, order sets, and documentation flows in Epic's rule engine.
  • Company-wide escalation process for regulatory updates and critical bugs.
  • Policy-constraint mapping that triaged alerts between binding and advisory.
  • Meaningful Use and quality-measurement workflow implementation.
  • 100+ hospital go-lives supported with configured clinical decision rules.
  • Company-wide escalation process adopted for regulatory updates and critical bugs.
  • Alert fatigue reduced without losing safety checks through policy-constraint mapping.
  • Meaningful Use and quality-measurement workflows implemented at production scale.
  • Clinical decision-support rule configurations across 100+ hospitals.
  • Escalation process documentation adopted company-wide.
  • Quality-measurement workflows tied to federal incentive programs.

← Back to portfolio