Epic Cupid is Epic’s cardiovascular information system (CVIS). It connects cardiology orders, scheduling, procedure documentation, structured reporting, results, communication, charging, and analytics.

Epic’s current specialty-product overview says Cupid supports invasive and noninvasive cardiology procedures. It is designed to work with PACS, ECG, imaging, and other connected systems. Exact capabilities depend on the licensed products, configuration, specialties, devices, and operating model.

What Does Epic Cupid Do?

Cupid follows a cardiology procedure or diagnostic study from the initial order through scheduling, performance, interpretation, results, follow-up, and reporting.

Common Cupid workflows may include:

• Cardiology orders
• Procedure and resource scheduling
• Patient preparation
• Echocardiography
• Vascular ultrasound
• Cardiac catheterization
• Electrophysiology procedures
• Stress testing
• ECG-related workflows
• Structured procedure documentation
• Image and measurement integration
• Supplies and implants
• Results and communication
• Charges and reporting
• Registry-data capture

Cupid provides workflow and documentation tools, but clinical decisions remain the responsibility of qualified professionals following organizational policy.

Invasive and Noninvasive Cardiology Workflows

Cardiology spans many settings, specialties, and procedures. A health system may use Cupid for echocardiography, stress testing, cardiac catheterization, and electrophysiology workflows.

Each area brings its own requirements for scheduling, preparation, devices, documentation, measurements, supplies, implants, medications, results, and follow-up. Treating all of cardiology as one uniform workflow misses those differences.

Structured Cardiology Reporting

Structured reporting captures defined findings and measurements in a consistent format. Epic describes Cupid’s structured reporting as a way to standardize cardiology reports and support reporting and continuity of care.

Structured data can support:

• Consistent procedure documentation
• Reuse of measurements and findings
• More complete reports
• Operational and clinical analytics
• Quality review
• Registry workflows
• Communication across the care team

A useful template captures the right information without forcing clinicians through irrelevant fields or extra clicks. Governance needs to cover ownership, required elements, change control, and review after upgrades or policy changes.

Cupid, PACS, ECG, and Device Integrations

Cardiology workflows depend on information from imaging, ECG, hemodynamic, device, supply, reporting, and other specialized systems. Epic’s public interoperability documentation describes exchanging cardiology orders and results with PACS and other external systems.

Integration areas may include:

• Patient demographics and visit information
• Orders and scheduling
• Modality or procedure worklists
• Images and image availability
• Discrete measurements
• ECG results
• Procedure reports
• Supplies and implant use
• Charges
• Status updates
• Corrections and cancellations

Testing should include routine cases, corrections, duplicates, updates, patient merges, unavailable systems, delayed messages, downtime, and recovery.

Scheduling and Patient Preparation

Cardiology scheduling may depend on procedure type, location, room, equipment, staff, provider, duration, patient characteristics, preparation, authorization, and other requirements.

Before a procedure moves forward, staff should know what information is required. They also need clear ownership and an escalation path.

Accurate rules and well-maintained data make it easier for schedulers to find the right resources and avoid rework. Rules that are outdated or unnecessarily complex have the opposite effect.

Supplies, Implants, and Charges

Invasive cardiology procedures may involve high-cost supplies and implants. Cupid can support documentation of supply or implant use. That information may connect with inventory, charging, and clinical records.

Important design areas include:

• Item and implant data
• Barcode workflows
• Lot, serial, and expiration information
• Procedure documentation
• Charge rules
• Integration with supply-chain systems
• Reconciliation
• Exceptions and substitutions

Clinical, supply-chain, finance, and technical teams should test these processes together.

Cardiology Results and Follow-Up

Cupid can place cardiology results in the broader patient record. The organization still needs clear rules for routing and communicating preliminary, final, amended, urgent, and critical results.

Follow-up workflows may also need to address recommendations, referrals, additional testing, device surveillance, or other cardiology-specific needs. Responsibility and escalation should be explicit.

Epic Cupid Reporting and Analytics

Potential measures include:

• Order-to-schedule time
• Patient wait time
• Procedure turnaround time
• Report completion time
• Cancellation and delay reasons
• Room or laboratory utilization
• Documentation completion
• Supply and implant variance
• Registry-data completeness
• Charge reconciliation
• Result communication
• Interface errors

Before publishing a dashboard, teams should agree on definitions, source data, exclusions, refresh timing, and operational ownership.

Epic Cupid Implementation Considerations

Implementation or optimization planning should address:

• Cardiology governance
• Procedure and order dictionaries
• Scheduling and readiness
• Structured documentation
• PACS, ECG, imaging, and device integrations
• Supplies, implants, and charging
• Result communication
• Registry and quality reporting
• Security and access
• End-to-end testing
• Role-based training
• Activation and support
• Downtime and recovery

The team should represent every part of the cardiology workflow. Include clinical, scheduling, imaging, supply chain, revenue cycle, registry, technical, training, testing, and project leaders.

Epic Cupid Jobs and Skills

Common roles include:

• Epic Cupid analyst
• Cardiology informaticist
• Imaging or PACS specialist
• Interface analyst
• Application architect
• Reporting or registry specialist
• Testing lead
• Project manager
• Trainer
• Go-live and support specialist

Employers may seek cardiology workflow experience, relevant Epic certification, structured reporting, and imaging or device integration. Implementation, testing, reporting, and communication skills also matter.

Frequently Asked Questions About Epic Cupid

Is Epic Cupid a cardiovascular information system?

Yes. Cupid is Epic’s cardiovascular information system for invasive and noninvasive cardiology workflows.

What cardiology procedures can Cupid support?

Depending on configuration, Cupid can support echocardiography, vascular ultrasound, stress testing, cardiac catheterization, electrophysiology, and related cardiology workflows.

Is Cupid a PACS?

No. Cupid is designed to work with PACS, ECG, imaging, and other systems that manage images, measurements, and specialized device data.

What is the difference between Epic Cupid and Epic Radiant?

Cupid focuses on cardiovascular workflows, while Epic Radiant focuses on radiology workflows. Both applications may connect with imaging and reporting systems.

How can an organization optimize Cupid?

Optimization may address scheduling, templates, reporting, integrations, supplies, implants, results, registries, analytics, and training. It should also reduce manual workarounds.

Explore Epic consulting services or search healthcare IT opportunities.