Skip to content

A more connected surgical journey

Same Page.
Seamless Care.

From the first office update to the conversation after anesthesia. Bring the right information to the right team, before the patient reaches the operating room.

Office communication available today.
Connected clinical workflows are in development.

THE PREOPCONNECT VISIONOne connected care team
Clinical SummaryDevelopment preview
Fictional PreOpConnect clinical summary showing a provider-reviewed assessment and pending follow-up items
Less fragmented information.A clearer view of the patient and the plan.

Actual development screen. Fictional patient data. Not an activated clinical service.

CONNECTED AROUND THE PATIENT

Medical & specialty offices

Surgical teams

Surgery centers

Anesthesia departments

THE PLATFORM

Different systems.
A shared direction.

You don’t need the same EHR to start communicating better. Choose your setting to see the office-policy tools and the clinical workflow being built around it.

No EHR connection required for policy communication.

Clinical charting is a separate, planned capability.
Office workspace available

Keep every office up to date.

Connect medical and surgical offices with anesthesia departments and facilities. Share policy updates, medication considerations, fasting guidance and other patient-free preparation information.

  • Publish consistent guidance to connected offices.
  • Request an explicit acknowledgment from the recipient.
  • See what still needs follow-up.
See how office communication works
Planned clinical workspace

A paperless pre-op record.

A planned workspace for surgery centers to bring clearances, labs, ECGs, chest imaging reports and specialist information into one patient-centered record, without requiring Epic or Oracle.

  • Create medical and cardiac clearances in one workspace.
  • Prepare an anesthesia plan in advance or at the bedside.
  • Route concerns to the responsible team before surgery day.
  • Document the anesthesia provider’s review and readiness decision.
Explore advance review

THE CONNECTION THAT STARTS IT ALL

An update sent.
A message acknowledged.

One consistent place for facility policies and pre-op guidance, instead of relying on each office to hear about a change somewhere along the way.

Create an office-policy account

OFFICE-POLICY COMMUNICATION

  1. 01

    Publish the update

    The designated facility team prepares and reviews the guidance.

  2. 02

    Notify connected offices

    Share policy information through the configured email workflow.

  3. 03

    Confirm it was seen

    The recipient explicitly acknowledges the update. Delivery or opening alone does not count.

  4. 04

    Follow up where needed

    Keep unconfirmed updates visible to the responsible team.

Policy updates never contain patient information. Sending and facility access depend on configuration and authorization.

BEFORE, DURING & AFTER

One patient.
A connected care journey.

The clinical vision follows the work teams already do, with fewer disconnected documents and a clearer path for review. Clinical steps below are in development or planned.

  1. 01

    Prepare together

    Give referring offices consistent facility guidance.

    Office communication
  2. 02

    Review earlier

    Bring clearances, records and concerns into view before surgery day.

    Advance chart review
  3. 03

    Make the plan clear

    Give patients reviewed, individualized preparation instructions.

    Patient instructions
  4. 04

    See the full context

    Review the important events in a complex patient’s history.

    Patient Journey Timeline
  5. 05

    Close the conversation

    Explain what happened during anesthesia and what matters next.

    After-anesthesia report

REVIEW BEFORE THE DAY OF SURGERY

Find the concern.
Before the disruption.

Before someone takes time off work, fasts, arranges a ride and arrives for surgery, the team should have a chance to address the issues already visible in the chart.

The planned surgery-center workflow gives anesthesia providers a place to review in advance, flag a concern, identify who needs to act and document the reassessment. At the bedside, the same record supports preparation and discussion.

Planned standalone clinical workspace. Not an automatic clearance system.

THE INTENDED REVIEW LOOP

Review the record

Clearances, labs, ECGs, imaging reports and relevant history.

Route the concern

The responsible office or surgery-center team coordinates the needed follow-up.

Reassess and document

The anesthesia provider records the review and readiness decision. The clinical team retains the final decision.

A SHARED CLEARANCE, NOT ANOTHER COPY

Different expertise.
One evolving assessment.

The cardiologist shouldn’t need to start the entire clearance again. Neither should the medical office.

The planned shared document lets either office begin, then brings each specialist’s contribution into the same assessment. Core information stays visible, while each clinician owns their own clinical input.

Shared collaboration & EHR write-back planned
Either office can start +

A cardiology visit can come first, or the primary medical clearance can. The workflow is designed to follow the patient, not a fixed order of offices.

Keep common information together +

Weight, allergies, medications and other shared facts remain available so a specialist can focus on their assessment instead of copying the entire form.

Resolve differences, don’t overwrite them +

If offices have different medication lists, allergies or other details, the intended workflow brings the discrepancy to their attention for confirmation and reconciliation.

Finalize with the right review +

Clinical flags require a documented response or plan. The goal is one reviewed clearance with specialist contributions and, once separately implemented and approved, filing back into the EHR.

Patient pre-op instructions
Fictional patient instruction sheet from the existing development build, with reviewed medication and preparation sections

Development preview · Fictional example · Click to inspect

BEFORE SURGERY

Instructions patients
can take with them.

Turn the reviewed plan into a clear printout: what to do, what to bring and who to contact when something changes.

  • Individualized food and drink restrictions.
  • Arrival time, location and transportation details.
  • Medication hold or continue directions.
  • Additional provider instructions and contact information.

Provider-reviewed printing is in clinical development. Instructions are not issued automatically.

Patient Journey Timeline
Actual Patient Journey Timeline development screen showing fictional chronological events and source review

Epic development preview · Fictional example · Click to inspect

FOR THE MEDICALLY COMPLEX PATIENT

See the story.
Not just the latest note.

A chronological view brings diagnoses, procedures, treatments and hospitalizations into context, with filters and source details for closer review.

  • Preserve event dates, documentation dates and missing information.
  • Review surgery-related events and outstanding concerns.
  • Let the clinician determine significance, not the software.

Currently in Epic development. Original narrative/PDF viewing, saved cross-office approval and Oracle timeline support are not enabled.

After-anesthesia communication
Fictional patient-facing anesthesia communication report from the development build

Epic development preview · Fictional example · Click to inspect

AFTER ANESTHESIA

Their care.
Their information.

Patients deserve to hear directly about their anesthesia care, not depend on information being relayed through someone else.

  • Reviewed medications given, doses and provider-checked explanations.
  • Difficult-airway information to share with future care teams.
  • What helped prevent or treat postoperative nausea and vomiting.
  • Other anesthesia observations and follow-up to discuss.

Currently in Epic development. Source completeness and provider review matter; this is not an automatically complete anesthesia record.

EVERY TEAM HAS A PART

Built around the people
who prepare the patient.

Clearer communication for offices. Earlier visibility for anesthesia. A more understandable plan for patients.

01 / MEDICAL & SPECIALTY OFFICES

Contribute your expertise.

Receive facility guidance today. The clinical vision adds medication and condition review, shared clearance contributions and reconciliation with the other offices involved.

02 / SURGICAL OFFICES & CENTERS

Coordinate before arrival.

Keep policy communication organized. The planned clinical record brings supporting documents and unresolved concerns into view before the day of surgery.

03 / ANESTHESIA TEAMS

Review, prepare, communicate.

Publish preparation guidance, review the developing clinical picture and give patients a clear account of the important details after anesthesia.

A CLEAR VIEW OF WHAT’S READY

Built in stages.
Communicated honestly.

Explore the full vision without confusing a development preview with an activated clinical service.

Available workspace

Office-policy communication

Account access, facility/office connections, guidance and explicit acknowledgment tracking. Live sending depends on configuration and authorization.

Clinical development

Provider-reviewed clinical tools

Chart flags, clearance/instruction workflows and Epic timeline/anesthesia-report development. Authorized integration and clinical activation remain separate.

Planned capabilities

A shared, longitudinal patient record

Standalone clinical storage, cross-specialist collaboration, saved team handoff and EHR write-back. These are not currently offered as active clinical services.

A FEW IMPORTANT DETAILS

Your questions.
Clear answers.

Already have an account?
Sign in to your workspace

Do we need Epic or Oracle to use PreOpConnect?+

No. The office-policy workspace is separate from EHR integration and connects participating facilities with medical and surgical offices. A standalone, patient-centered clinical workspace for ambulatory surgery centers is planned; it is not currently an activated replacement for your clinical record.

What can an account user access today?+

Existing users can sign in to the office-policy workspace. Facilities can prepare and manage updates, connect with participating offices and track explicit acknowledgments. Facility access and live email delivery depend on configuration and authorization. The clinical workflows shown on this page are development previews or planned capabilities.

Can we replace paper charts with PreOpConnect today?+

Not yet. The planned standalone clinical workspace would bring clearances, labs, ECGs, imaging reports and specialist information together for advance and bedside review. Patient-record storage, approved clinical deployment and team access must be established before a facility uses it for patient care.

Can specialists share a clearance and send it back into Epic?+

That is part of the planned workflow, not a currently activated capability. The goal is for either the medical office or a specialist to begin one assessment, with other clinicians adding their own input and resolving discrepancies. Shared editing and EHR write-back require separate implementation and approval.

How would the Patient Journey Timeline populate?+

The current Epic development build organizes supported structured records from an authorized SMART on FHIR launch. It preserves source dates and missing information; it does not invent events or infer why one event caused another. A clinician reviews the evidence and confirms significance. Saved cross-office approval and Oracle timeline support remain planned.

Who decides whether a patient is ready for surgery?+

The responsible clinical team. PreOpConnect is designed to organize evidence, surface items for review and document decisions; it does not automatically clear a patient. A flag needs a documented clinical response or plan, and the anesthesia team retains responsibility for its assessment and readiness decision.

What would patients receive before and after surgery?+

The clinical development workflows include provider-reviewed preoperative instructions and an after-anesthesia communication report. The latter can explain reviewed medication administrations, airway considerations, nausea/vomiting management and follow-up. These are professional review-and-print workflows, not an activated public patient portal or an automatic complete medical record.

Does the policy email system contain patient information?+

No. Policy communication is for facility guidance and updates, not patient-specific information. Planned clinical charting is a separate workflow that requires its own approved deployment and access controls. Never place patient information in an office-policy update.

START WITH BETTER COMMUNICATION

Every update. Every office.
Connected.

Explore the vision. Connect your office. Keep the patient at the center.

Create an account Account login