For health systems and surgical centers

Perioperative Health, built into every surgical episode.

PERIOME partners with health systems and surgical centers to co-design, pilot and study connected perioperative programs: understanding patients earlier, supporting preparation, carrying context into surgery and following recovery after discharge. It starts with one service line.

The problem, in practice

Excellent operations, a fragmented episode.

Surgery, anesthesia and ERAS pathways are among medicine's real accomplishments. The episode around them is still assembled by hand, and the patient often carries the pieces.

  • Fragmented informationHistory, instructions, test results and what the patient reports live in different places. No single view follows the patient from scheduling to recovery.
  • Readiness that goes unseenClearance is documented. Whether the patient is ready, and what changed after the visit, usually is not.
  • Preparation nobody confirmsInstructions vary by surgeon, site and visit. Whether a medication was held or a carbohydrate drink was taken is often learned on the morning of surgery.
  • Issues that surface lateThe clearance that slipped or the instruction that never reached the patient tends to appear on the day of surgery, when it is hardest to fix.
  • Teams carrying it by handPre-admission and nursing teams chase calls, reminders and questions one patient at a time.
  • Recovery and measurement that stop at dischargeRecovery at home is rarely followed against the patient's starting point, so programs have little longitudinal data to improve on as accountability for the whole episode grows.

Accountability now reaches past the operating room.

The clinical case for preparing patients is decades old, and ERAS already reaches the days before an operation. What has changed is accountability: Medicare's Transforming Episode Accountability Model became mandatory in January 2026, and value-based contracts are moving the same way.

When a program is accountable for the whole episode, the weeks before surgery and the weeks after discharge become part of the program.

CMS TEAM

  • 188 Markets where participation is mandatory, January 2026 through December 2030.
  • 30 days After hospital discharge, counted in each surgical episode.

Source · Centers for Medicare & Medicaid Services

Where the episode is felt

Discharged is not the same as recovered.

Outcomes have many causes; the patient's condition around the operation is one of them. ERAS established the evidence for structured pathways. What remains is operational: delivering preparation before the patient arrives, knowing what they actually did, and following recovery after discharge.

Cognitive recovery

Roughly one in four

Patients aged 60 and over with measurable cognitive decline in the first week after major non-cardiac surgery. About one in ten at three months.

Throughput

PACU time and discharge

Recovery variability extends PACU time, delays discharge and adds nursing load where throughput drives program economics.

After discharge

The weeks at home

Recovery continues at home, where it is hardest to follow against the patient's own starting point.

Perioperative neurocognitive disorder figures (studied at the time as postoperative cognitive dysfunction): ISPOCD and Monk et al.

Operate the episode

See every journey, not only the case.

Coordinate active episodes, surface unresolved work, follow recovery, and understand how the program is performing across the full surgical window.

PERIOME OS · Perioperative Health Infrastructure
Illustrative product environment Northstar Health System

Perioperative command center

Active surgical episodes across the health system

Active episodes
186Across 4 facilities
Surgery within 7 days
4712 with open work
Open actions
298 due today
Recovery follow-up
516 flagged for review
Connected sources
94%Of active episodes

Episode workqueue

Ordered by surgery date and unresolved work
Episode workqueue
PatientProcedureSurgeryJourneyCurrent attentionOwnerAction
Eleanor ReedMRN 482910Total knee · Right18 Nov · 14 daysPrepareHematologic follow-upPeriop RN
Marcus HillMRN 550217Colectomy21 Nov · 17 daysPrepareHome support incompleteNavigator
Linda EvansMRN 601144Lumbar fusion24 Nov · 20 daysUnderstandFunctional trend changedPhysical therapy
Daniel ParkMRN 332817Total hip25 Nov · 21 daysPrepareMedication reconciliationPharmacy
Sofia RamirezMRN 702449Hysterectomy09 Nov · 5 daysCareReadiness review dueAnesthesia

Program watch

Today
  • 8
    Actions due today

    Orthopedics, colorectal and gynecology.

  • 6
    Recovery paths to review

    Function or symptoms outside the planned path.

  • 3
    Source gaps

    External laboratory results awaiting reconciliation.

  • 1
    Implementation note

    West Campus begins total-joint enrollment Monday.

What PERIOME is building

One connected model for the whole episode.

PERIOME is building the infrastructure to connect each step of the surgical episode around the patient. Some of it runs in a founding implementation today; the rest is being built. Each line says which.

  • Understand patients earlierA structured baseline from the day surgery is scheduled, captured through Morton. In pilot.
  • Identify preparation opportunitiesWhat is still modifiable in the time that remains, surfaced while there is time to act. Readiness measurement is in development.
  • Support preparationDay-by-day guidance timed to the operation, with the PERIOME Protocol as the first structured intervention. Morton in pilot; the Protocol opens with its first production run.
  • Carry context into surgeryWhat changed, what was completed and what is still open, summarized for the team. Being built in PERIOME OS.
  • Follow recovery after dischargeCheck-ins and patient-reported recovery after the patient goes home. In pilot through Morton.
  • Structured information for improvementCohort reporting on preparation, patient experience and recovery against measures agreed in advance. Part of every founding implementation.
See the system

Founding implementation

A clear path from first conversation to a decision on the evidence.

A founding PERIOME implementation is run like any clinical program evaluation. Scope and commercial terms are set with each institution; there is no fixed package.

  1. Sponsor and champion

    An executive sponsor and a clinical champion own the program inside the institution.

  2. Service line and cohort

    Choose one surgical service line and a defined patient population to start.

  3. Scope and governance

    Agree the intervention scope, clinical governance and how it fits existing workflow.

  4. Permissions and data

    Set data permissions and handling, through the institution's legal and compliance review.

  5. Implement

    Patients are introduced at visits they already attend: the surgeon's office, primary care clearance, pre-admission clinic or pre-anesthesia evaluation. No EHR build to begin.

  6. Measure

    Track the patient, workflow and recovery indicators agreed in advance.

  7. Review

    Leadership reviews a cohort report and decides, on the evidence, whether expansion is justified.

Measures, reporting, data permissions and any data sharing are agreed in advance and go through each institution's legal and compliance review. A founding implementation evaluates delivery and patient experience; PERIOME makes no claim that it will change clinical or financial outcomes.

Operational lift

PERIOME carries the operational load.

An implementation should not compete for IT roadmap, capital or clinical staff. PERIOME runs the patient-facing work; the institution provides sponsorship, clinical leadership and access to the visits patients already attend.

PERIOME handles

  • Patient enrollment and onboarding
  • Protocol fulfillment timed to each operation
  • Day-by-day guidance through the surgical window
  • Post-discharge recovery follow-up
  • Data capture across the cohort
  • Patient experience measurement
  • Cohort reporting to program leadership
  • A direct-purchase option for patients, where appropriate

The institution provides

  • An executive sponsor and a clinical champion
  • Access to the preoperative visits patients already attend
  • Legal, compliance and data review before launch
  • Agreed data access, where permitted
Discuss a founding implementation

The Council

Building the standard with the field.

PERIOME is convening the Perioperative Health Council: clinicians from across the surgical journey, scientists, health system leaders and operators who have built clinical infrastructure at scale. Its work is to define the measurement, evidence and implementation standards the discipline will need.

A program that adopts Perioperative Health early helps shape it. The Council is independent of PERIOME's products and does not endorse them.

About the Council

Start here

Discuss a founding implementation.

Tell us about your program: the service line you have in mind, your surgical volume and what matters most to your leadership. We will come back with a scoped next step.

  • Routed to the team that scopes implementations.
  • An answer either way: a scoped next step, or an honest no.
  • Handled under our privacy policy. Please do not include patient information.

Message received.

Our team reviews every request personally and follows up to schedule a time to talk.

Start the conversation

No patient enters surgery unknown.

A founding implementation begins with one service line and a conversation with your leadership team.

Discuss a founding implementation

A new standard for the oldest promise in medicine: that the patient comes first.