Skip to content
Integrations Epic

Epic + Finn.

Epic integration with Finn. Epic brings patient records, appointments, and administrative information together for hospitals and healthcare organizations.

What you can do with Epic.

Epic brings patient records, appointments, and administrative information together for hospitals and healthcare organizations.

Run patient scheduling conversations

Finn handles routine appointment requests from the first question to a recorded booking.

Typically handled byPatient access center

Starts when

A patient asks to schedule or change a routine visit.

What Finn handles

  1. Match the patient and collect the request using the health system’s scheduling instructions.
  2. Find suitable appointments through the health system’s connected Epic scheduling services.
  3. Book the selected visit and record the patient’s confirmation.
  4. Send the correct location, arrival, and preparation instructions through the connected patient communication service.

The result

The patient has a recorded appointment and clear next steps.

Complete registration and visit preparation

Finn gathers administrative details and follows up on missing forms before an appointment.

Typically handled byPatient registration team

Starts when

An appointment requires new or updated registration information.

What Finn handles

  1. Read the patient’s administrative record and visit requirements.
  2. Collect the missing contact, insurance, and responsible-party information.
  3. Update the registration workflow and send forms through the health system’s secure intake service.
  4. Track completion and notify the patient of the final arrival requirements.

The result

The visit’s administrative record and patient instructions are complete.

Coordinate referral scheduling

Finn closes the administrative loop between a clinician’s referral, the receiving office, and the patient.

Typically handled byReferral coordination team

Starts when

A clinician records a referral needing an appointment.

What Finn handles

  1. Read the referral destination and scheduling instructions.
  2. Collect the required existing documents and send them through the connected referral workflow.
  3. Follow up with the receiving office and patient and complete the selected scheduling step.
  4. Record the receiving office’s response and appointment outcome for the referring team.

The result

The referral has a documented receiving-office and patient scheduling result.

Complete prior authorization follow-up

Finn manages the document and status work surrounding an authorization request.

Typically handled byPrior authorization team or outsourced revenue cycle service

Starts when

A clinician’s ordered service enters the authorization workflow.

What Finn handles

  1. Read the order and the coverage requirements returned by the payer-connected workflow.
  2. Collect the required existing records and request missing clinical information from the clinician.
  3. Submit the administrative packet through the authorization service and track its status.
  4. Record the payer’s determination and notify the appropriate scheduling or billing owner.

The result

The authorization request has a completed submission and recorded payer response.

Run clinician-directed patient outreach

Finn handles the contact and scheduling work behind a care team’s outreach list.

Typically handled byPatient engagement or care coordination support team

Starts when

The care team selects patients for a follow-up campaign.

What Finn handles

  1. Read the selected roster, outreach instructions, and contact preferences.
  2. Send the care team’s message through the connected patient communication channel.
  3. Complete routine scheduling or document requests and direct clinical questions to the care team.
  4. Record each patient’s response, booking, or decline.

The result

The campaign has completed administrative actions and a recorded patient response for each contact.

Resolve patient account and payment inquiries

Finn manages the billing conversation using the health system’s recorded account information.

Typically handled byPatient financial services center

Starts when

A patient asks about a statement, payment, or receipt.

What Finn handles

  1. Read the relevant billing information through the connected revenue-cycle workflow.
  2. Explain the recorded charges and payments and collect any dispute evidence.
  3. Send the health system’s payment flow, with processing handled by its connected processor, or track a billing correction.
  4. Confirm the recorded account result and provide the final receipt or explanation.

The result

The patient receives a clear billing outcome tied to the account record.

Coordinate medical record requests

Finn completes the administrative follow-up around a patient’s authorized record request.

Typically handled byHealth information management team

Starts when

A patient or authorized recipient requests records.

What Finn handles

  1. Collect the requested record scope and complete the health system’s identity and release process.
  2. Retrieve or request the selected records through the connected record-sharing workflow.
  3. Deliver the released material through the health system’s secure channel.
  4. Confirm delivery and retain the request and release record.

The result

The authorized recipient receives the released records with a documented delivery outcome.

Prepare patients for telehealth visits

Finn handles the setup and administrative questions that often occupy virtual-care support teams.

Typically handled byTelehealth support coordinator

Starts when

A patient books an eligible video visit.

What Finn handles

  1. Read the appointment and the health system’s telehealth instructions.
  2. Send the access link and required preparation or intake steps through the connected telehealth service.
  3. Resolve routine joining questions and coordinate technical help when needed.
  4. Record the patient’s readiness or scheduling change and notify the visit team.

The result

The patient has the access information and completed administrative preparation for the visit.

Complete patient contact-center follow-up

Finn carries routine service calls through action, documentation, and patient confirmation.

Typically handled byPatient service call center

Starts when

A patient calls about an administrative request.

What Finn handles

  1. Identify the patient and the relevant appointment, document, or service request.
  2. Complete the connected scheduling or administrative workflow needed to resolve it.
  3. Record the call outcome and transcript through the health system’s Epic telephony integration.
  4. Send the patient confirmation and track any remaining owner-assigned task.

The result

The call produces a recorded service result and a complete contact history.

Coordinate post-discharge administrative tasks

Finn handles the scheduling and practical follow-up specified by the discharge team.

Typically handled byCare transition support coordinator

Starts when

A clinician completes the discharge instructions.

What Finn handles

  1. Read the care team’s follow-up appointments, document needs, and contact instructions.
  2. Arrange the specified visits and coordinate administrative requests with the connected providers.
  3. Send the patient the clinician-issued instructions and practical appointment details.
  4. Record completed arrangements and return clinical questions or unresolved care decisions to the care team.

The result

The discharge team’s administrative follow-up has a documented completion record.

Set up the connection around your work.

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from Epic.

Each healthcare organization approves connections to its own Epic system and decides which information can be shared.

Visit Epic

Part of the work in your industry.

Put your Epic integration to work.

Tell us which records, actions, and teams the connection needs to support.