Skip to page content
PreOpSure
Platform / Epic integration

Bring Epic into your
pre-procedural workflow.

With an authorized Epic connection, your team can select patients, review their demographics, add procedure details, and queue them for screening in PreOpSure.

PreOpSureDashboardEpic ImportInteractive example

Epic Patient Import

Review patient information. Prepare the screening queue.

Fictional patient data

Example patient results

3 patients
Jamie ParkerDOB 04/12/1972(555) 010-0124DEMO-001
Alex MorganDOB 09/23/1968(555) 010-0136DEMO-002
Taylor ReedDOB 02/07/1980(555) 010-0148DEMO-003

Add patients, then review the screening queue.

Review queue

Screening Queue

1 selected

Procedure and scheduling details are added by your team.

Jamie Parker
Procedure
Knee arthroscopy
Surgery date
Nov 12, 2026
Arrival
07:30 AM
Surgeon
Dr. Rivera

Review the details before sending patients for screening.

Explore a simplified view of Epic Import with fictional patients. Nothing is sent to Epic or the clinical application.

Patient information comes in.
Your team stays in control.

Patient import brings the demographics into place. Your team adds the case details and manages outreach, review, and follow-up in PreOpSure.

  1. 01

    Connect with your facility’s authorization.

    A facility administrator establishes the Epic connection through SMART on FHIR. The patients and actions available depend on the access approved for your Epic environment.

  2. 02

    Review the patient. Add the case.

    Select an available patient and review their name, date of birth, and contact details. Add the procedure, surgery date, arrival time, and surgeon before sending the record for screening.

  3. 03

    Move into parallel screening.

    Selected patients enter the screening queue. Your team starts outreach from there, then reviews completed calls, clinical findings, and any preparation still needed.

    Explore parallel screening

Plan the path back
to the chart.

PreOpSure includes a document writeback workflow for verified screening documentation using FHIR DocumentReference.

Document return depends on your facility’s permissions and configuration. We’ll review the document format, delivery workflow, and validation with your Epic team before go-live.

Patient import and document return are separate capabilities. Neither replaces your team’s clinical verification.

Start with the workflow.
Scope the connection together.

A CSV roster gives your team another way to start preparing cases while you evaluate the Epic connection.

See the CSV workflow

What we’ll work through with your IT team

Access and permissions
App registration, authorized users, patient access, and the permissions your Epic environment allows.
Information and documents
Patient demographics to import, procedure details entered in PreOpSure, and any approved document-return workflow.
Validation before go-live
Confirm the connection, test the agreed workflow, and align on responsibilities before using it with patients.
Review security and trust

Common integration questions.

Do we need Epic to use PreOpSure?

No. Your team can start with a CSV roster. An Epic connection is a separate setup path for facilities that want to import patient demographics.

Does importing a patient automatically start a call?

No. Import adds the patient to the screening queue. Your team reviews the case details and starts outreach from PreOpSure.

Does this sync our surgery schedule or the entire chart?

The import workflow described here brings in patient demographics. Procedure and scheduling details are added in PreOpSure. Any additional data exchange needs to be scoped and validated with your facility.

Epic is a trademark of Epic Systems Corporation. This page does not imply endorsement or certification by Epic.