Mockup 3: iFrame Embedded

Summary

Notes

Orders

Results

Pharmacogenomics

Medications

Allergies

John Doe

MRN-12345 | DOB: 01/15/1965 | Age: 61

High Risk

Medications

Moderate Risk

Interaction

Genes Tested

Results Available

⚠️ High-Risk Medications

Clopidogrel 75mg

CYP2C19 Poor Metabolizer (*2/*2) - Reduced efficacy

Codeine 30mg

CYP2D6 Poor Metabolizer - Ineffective pain relief

⚡ Moderate-Risk Interactions

Warfarin 5mg

CYP2C9 *1/*2 + VKORC1 - Consider dose adjustment

When to Use This Approach

This approach is appropriate when:

Fast launch required: Minimal Epic IT configuration for quick deployment
Passive lookup preferred: Clinician initiates check when needed, no automatic alerts
Minimal Epic integration: iFrame embed requires less Epic IT effort than BPA rules or CDS Hooks
Starting point: Quick pilot before committing to more complex integration approaches

Tradeoff: Lower clinical impact than proactive alert approaches (Approaches 1-2) because relies on clinician remembering to check.

✅ Advantages

Zero Epic IT maintenance
Low Epic IT effort (just iFrame config)
All logic in Helix - update anytime
Full-featured portal experience
No Epic BPAs to configure
Clinician stays in Epic UI

⚠️ Tradeoffs

No proactive alerts - passive only
Clinician must remember to click tab
High-risk patients could be missed
No Epic data storage (external DB)
Requires deliberate workflow step

🟢 Epic IT Burden: LOW

Configuration: Add iFrame web component to chart, pass patient context via URL parameter
Authentication: Epic SSO (MyChart) - already implemented
Maintenance: ZERO - all logic lives in Helix, not Epic
Updates: Deploy Helix changes instantly, Epic unaffected
No BPAs: No Epic alerts to configure or maintain
All data managed by Helix

💬 Discussion Questions for CMO

Passive vs Proactive: Is it acceptable that providers must click the "Pharmacogenomics" tab to see risk? Or do you need alerts that interrupt workflow?
Alert Fatigue: Would this passive approach reduce alert fatigue by avoiding interruptions?
Missed Cases: Would you worry about providers missing high-risk patients because there's no alert firing at order time?
Data Governance: Is it acceptable that genetic data lives in Helix database? Or do you need Epic-native data storage?
Epic Integration: Does having a dedicated Epic tab feel "integrated enough" for your clinicians?
Training: Would you need to train providers to check the tab for every high-risk medication order?

Key Insight

This approach minimizes Epic IT burden but sacrifices proactive safety alerts. It's ideal for organizations with limited Epic resources or high alert fatigue. However, the passive nature means clinicians must remember to check the tab - high-risk cases could be missed. Best suited for "pull" workflows (provider initiates review) rather than "push" workflows (system alerts provider).

Approach 3: iFrame Embedded