Table 3.

How‐to guide step 3 checklist and case study narrative

Case study narrative

Step 3 – Stakeholder Feedback Assemble the team Create an on‐going feedback forum Develop metrics

Assemble the team You create a synopsis of the project, with supporting literature, to present to the members of your stakeholder group. At your institution, the stakeholder group is required to include a department head, at least three clinicians, an HIT analyst, and a pharmacist. Your HIT analyst who has been assisting joins, and you serve as the pharmacist. The clinical champion reaches out to the department head, who is amenable, and provides five additional clinicians to reach out to for inclusion. Create an on‐going feedback forum After meeting with your stakeholder group, they recommend an expansion to the alert wording to “Due to reduced CYP2C19 activity, this patient is at increased risk of poor therapeutic response. Recommend use of alternative antiplatelet therapy such as ticagrelor.” One of the clinicians asks about integrating the PGx results into the PCI order set currently under development. As a next step, the team will develop a dynamic order set. Another clinician is concerned about non‐cardiovascular implications of PGx results. Luckily, your system already has an automatic consult request trigger every time a PGx panel has resulted. Develop metrics Finally, together you decide that you will track the number of times the alert fires, the number of overrides, and any comments or reasons submitted with the overrides. The plan is to re‐assess the alert functionality in 1 month initially and then again at 6 months.

HIT, Health Information Technology; PCI, percutaneous coronary intervention; PGx, pharmacogenomics.