Corepoint Integration Engine in a large health system using Epic

UnityPoint Health technical team lead, Joe Hamilton, discusses the role Corepoint Health plays in their Epic environment, ensuring needed data gets from one point to another while adhering to HIPPA regulations.



Customer Perspectives


Corepoint Integration Engine in a large health system using Epic

Joe Hamilton – UnityPoint Health


Solving vendor issues and saving money

Ted Perryman – Oak Bend Medical Center


Integration with Vocera Communication Badges

Ryan Ellerton – Halifax Health


Connecting with clients efficiently

Sung Pyo – Cleveland HeartLab

Meaningful Use Achievement

Jeremy Goslin – East Alabama Medical Center

Connecting with cloud applications

Michael Lucas – Sonic Healthcare

The role of an interface Engine in Epic migration

Paul Labonte – Southcoast Health

Innovative Approaches to Handling DICOM SR data

Scott Adair – North State Radiology

CIRA Interoperability Success – DICOM and Web Services Features

Nate Anderson and Steve McHenry – Central Illinois Radiological Associates

The Corepoint Health Development Philosophy

Dave Shaver, CTO/Founder

Customer Support is Key at Corepoint Health

Sonal Patel, VP of Client Service and David Li, Director of Customer Support

Auditability, Logging, & Protecting PHI

Scott McManis, Senior Sales Engineer

The Importance of a Reliable Engine

Scott McManis, Senior Sales Engineer

Interfacing Standards


HL7 ADT Messages: The Basics


Best Practices When Connecting to EMRs


How does an interface engine simplify your environment?


Fundamentals of an HL7 Engine


What do I Need from a Vendor to Create an Interface?


HL7 ORU Messages: The Basics


Testing Interfaces in the Real World


HL7 FHIR: The Future of Health Data Exchange

 Print Friendly