applaud
← Check another system

Epic Systems Corporation

Can applaud connect to EpicCare Ambulatory Base?

YesReady: automatic connection

How it connects

Best way

Connects automatically

EpicCare Ambulatory Base sends each visit to applaud as it happens. Nothing for your team to do day to day.

Outgoing HL7v2 feed (Outgoing ADT or Appointment Scheduling) pushed to applaud over HTTPS, built by the customer's interface team

Connects automatically: EpicCare Ambulatory Base

  1. The Epic customer (the practice, or the health system that hosts its Epic) signs applaud's BAA and agrees to send a feed; nothing here can be switched on by a single clinic user.
  2. applaud stands up an HTTPS endpoint that accepts HL7v2 over HTTP (HAPI) with authentication applaud specifies, or receives MLLP through a VPN if the customer requires it.
  3. applaud gives the customer's interface team: the interface wanted (Outgoing Patient Administration/ADT, or Outgoing Appointment Scheduling), the endpoint and auth, and the filter: only the agreed clinic departments, and only the event that marks a finished visit (check-out/discharge or appointment status change; ask which event the customer's build sends, as the open.epic spec needs a login).
  4. The customer's interface engine filters and forwards the messages; applaud parses PID (name, phone, email) and the visit date and posts each completed visit to POST https://applaud.you/api/v1/contacts.
  5. Confirm which PID-13 entry is the mobile number in this customer's configuration before go-live.

Resources

Other ways, in order

Option 2

Connects by export

Recent patients are exported from EpicCare Ambulatory Base and uploaded to applaud. A couple of minutes, and we can set it up with you.

Customer-built report extract (Reporting Workbench / Clarity) of completed visits; applaud's own Epic seat not documented

Connects by export: EpicCare Ambulatory Base

  1. The customer's BI or reporting team builds a report of yesterday's completed visits in the agreed departments with first name, last name, mobile, email and visit date, and nothing clinical.
  2. The report is scheduled (Epic's guide says daily to a couple of times an hour) and delivered to applaud by the customer's chosen secure channel, or a staff member exports it and uploads it to applaud.
  3. Alternative from Epic's guide: applaud licenses Kit or Clarity through Epic Vendor Services and writes the query itself (cost not public).

Resources

Option 3

Connects through a partner tool

A connector tool links EpicCare Ambulatory Base to applaud.

Keragon: Epic Systems connector (actions only, no trigger)

Connects through a partner tool: EpicCare Ambulatory Base

  1. Listed, not recommended: Keragon's Epic connector has no trigger, and its 'Get appointments' action needs a patient, so it cannot find completed visits by itself.
  2. Any Keragon-to-Epic connection would still need the Epic customer's FHIR setup (client-ID download, subscription agreement) described in the FHIR route.

Resources

Questions about connecting EpicCare Ambulatory Base? We set it up with every new practice.

Ask us about your system

Tell us where to reach you and we'll come back with how applaud connects.

Book a demo