Healthcare · Moraph software

Surgical Block Scheduling Optimizer

See which operating room time will go unused, release it in time, and schedule cases closer to how long they really take

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

The Surgical Block Scheduling Optimizer measures how each surgeon and service uses its allocated block time, predicts which blocks are likely to go unused, and suggests release in time for other surgeons to book. It estimates case durations from your own historical cases, so schedulers can compare the booked time with a data-based estimate. People decide every release, allocation and schedule change; the Optimizer proposes and records the reasoning.

The problem it solves

Block allocations are often set once and reviewed rarely, unused time is released late or not at all, and surgeons waiting for time cannot see what might open up. Case durations are booked from surgeon preference cards or habit, so some days run late and others finish early. When the perioperative committee reviews allocations, utilization figures are assembled from EHR reports and argued over, because each service measures them differently.

  • Unused block time is found too late for anyone else to use it
  • Booked case durations often differ from how long similar cases actually took
  • Utilization is calculated differently by each service and disputed at committee
  • Release requests and open-time requests travel by phone and email without a record

Who uses it

  • Perioperative services directors and operating room managers
  • OR schedulers and surgeon office schedulers
  • Surgical department chairs and service line leaders
  • Anesthesia leadership who plan staffing against the schedule
  • Perioperative governance committees who set block policy

Requirements it supports

HIPAA Privacy Rule (45 CFR Part 164, Subpart E)HIPAA Security Rule (45 CFR Part 164, Subpart C)CMS Conditions of Participation for hospitals, surgical services (42 CFR 482.51)CMS Conditions for Coverage for ambulatory surgical centers (42 CFR Part 416, Subpart C)CMS Conditions of Participation for hospitals, quality assessment and performance improvement (42 CFR 482.21)

The product supports these requirements; meeting them remains your organization’s responsibility.

See how it works

A short walkthrough

Illustrative screens with fictional sample data. They show the workflow, not any client’s data or configuration, and the layout of the product itself differs. A live demonstration uses the product with sample data.

  1. Step 1

    Blocks at risk of going unused

    Schedulers and the perioperative director see upcoming blocks with low bookings and how likely each is to go unused.

    DateRoomBlock ownerBookedLikely unusedStatus
    Day +6OR 4Orthopedics, Surgeon 112 (fictional)3 of 10 hoursHighSuggestion sent
    Day +7OR 2General Surgery6 of 10 hoursMediumMonitoring
    Day +8OR 7Urology, Surgeon 204 (fictional)0 of 8 hoursHighRelease due today
    Day +9OR 1Cardiac Surgery9 of 10 hoursLowOn track
    Day +10OR 5ENT, Surgeon 87 (fictional)4 of 8 hoursMediumPartly released
    Schedulers and the perioperative director see upcoming blocks with low bookings and how likely each is to go unused.

  2. Step 2

    Why a release is suggested

    Each suggestion shows the booking pattern behind it, and the block owner decides.

    OR 7 · Urology · Surgeon 204 (fictional)

    Block date
    Day +8
    Allocated
    8 hours
    Booked so far
    0 hours
    Release deadline
    Today, per service policy
    Waitlist requests that fit
    2

    Factors behind the suggestion

    • Bookings for this block usually arrive more than 10 days ahead
    • Last 4 equivalent blocks released or under half used
    • Surgeon calendar shows a conflict entered by the office
    Each suggestion shows the booking pattern behind it, and the block owner decides.

  3. Step 3

    Booking with a duration estimate

    When a case is booked, the scheduler sees the requested time beside an estimate from similar past cases.

    Case request · Patient 70214 (fictional) · Surgeon 112 (fictional)

    Procedure
    Total knee arthroplasty
    Requested duration
    150 minutes
    Estimated duration
    118 minutes
    Typical range
    104 to 135 minutes
    Past cases behind estimate
    64

    Room fit for Day +6, OR 4

    • 2 cases already booked
    • Room fits a third case if the estimate is used
    When a case is booked, the scheduler sees the requested time beside an estimate from similar past cases.

  4. Step 4

    What happened to released time

    Releases, offers and rebookings are recorded, so the committee can see whether released time was used.

    Block BK-5521 · OR 7 · Day +8

    1. Release suggestedSystem
    2. Block released in fullSurgeon 204 office (fictional)
    3. Time offered to 2 waitlist requestsOR scheduler
    4. General Surgery request accepted for 6 hoursService chief, General Surgery
    5. Remaining 2 hours added to open timeOR scheduler
    Releases, offers and rebookings are recorded, so the committee can see whether released time was used.

  5. Step 5

    Utilization by service

    Every service's utilization is calculated the same way and shown with releases and rebooked time.

    ServiceAllocated hoursUtilizationReleased on timeReleased time rebookedEstimate vs actual
    Orthopedics64081%72 hours58 hoursWithin range
    General Surgery72086%40 hours36 hoursWithin range
    Urology32058%24 hours18 hoursWithin range
    ENT24074%30 hours12 hoursOverruns above range
    Every service's utilization is calculated the same way and shown with releases and rebooked time.

  6. Step 6

    Modeling an allocation change

    Before the committee decides, a proposed allocation change is tested against past schedules and demand.

    ServiceCurrent blocks per weekProposedPast cases that would not fitWaitlist demand met
    Urology432No change
    General Surgery9100More met
    Orthopedics880No change
    Before the committee decides, a proposed allocation change is tested against past schedules and demand.

Workflows

The principal workflows

  1. Measure

    Scheduled and completed cases flow in from your EHR's surgical module, and block utilization is calculated the same way for every service, using the definitions your committee agrees.

    • Block allocations, booked cases and case times arrive by interface or scheduled extract
    • Data quality checks flag missing in-room and out-of-room times
    • Utilization calculated by block, surgeon, service and period using your agreed definition
    • Turnover time, late starts and overruns measured alongside
    • Results published to the surgeons and services they concern

  2. Predict and release

    For each upcoming block, the Optimizer estimates how likely the time is to go unused, based on booking patterns, and suggests release to the block owner in time for the time to be rebooked.

    • Upcoming blocks scored on likelihood of going unused, with the factors shown
    • Suggestions sent to the block owner or their office before your release deadline
    • Block owner releases, keeps or partly releases the time, with a reason
    • Automatic release at your policy deadline applied and recorded
    • Released time offered to the waitlist and open-time requests

  3. Schedule

    When a case is booked, the scheduler sees an estimated duration from your historical data for that surgeon and procedure alongside the requested time, and decides what to book.

    • Case request received with procedure, surgeon and requested duration
    • Estimated duration shown with the range and the number of past cases behind it
    • Scheduler books the requested time or adjusts it after discussion with the surgeon's office
    • Room fit checked against block time, turnover and staffed hours
    • Booked duration and estimate both kept for later comparison

  4. Review allocations

    Before each allocation review, the Optimizer prepares utilization, release behavior and demand for open time by service, and models proposed allocation changes for the committee to decide.

    • Utilization and release history summarized for each block owner
    • Unmet demand from waitlists and declined open-time requests shown
    • Proposed allocation changes modeled against past schedules
    • Committee decides changes and records the rationale
    • New allocations published with an effective date

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

OR scheduler

OR scheduler, surgical scheduling coordinator, perioperative scheduling lead

Books cases, offers released time and keeps the schedule full and realistic.

Sees

  • Upcoming blocks across the rooms they schedule, with bookings and release status
  • Case requests with requested durations and estimates
  • Waitlist and open-time requests
  • Room fit by day

Does

  • Books or adjusts case durations after reviewing the estimate
  • Offers released time to waitlist and open-time requests
  • Applies releases and booking changes in the EHR where they are not written back automatically
  • Records reasons for overruns and late starts where your procedures require

Cannot

  • Change block allocations or release policy
  • Release a block on the owner's behalf without the owner's instruction, except at the automatic release deadline
  • Change utilization definitions
Approvals
Exceptions to release policy go to the perioperative director.
Notified about
Released time to offer, new open-time requests, and bookings well above or below the estimate.

Perioperative director

Director of perioperative services, OR director, surgical services administrator

Owns the schedule and block policy, and brings utilization evidence to the committee.

Sees

  • Every block, booking, release and request across their facilities
  • All utilization, release and estimate reporting
  • Release rules and their change history
  • The audit trail

Does

  • Sets release deadlines and automatic release rules within committee policy
  • Approves exceptions to release policy
  • Prepares allocation reviews and runs allocation models
  • Publishes new allocations once the committee decides

Cannot

  • Change allocations without a recorded committee decision, where your policy requires one
  • Edit or delete entries in the audit trail
Approvals
Approves policy exceptions and release rule changes; allocation changes follow the committee's decision.
Notified about
High-likelihood unused blocks near the deadline, exception requests, and allocation reviews coming due.

Surgeon or surgeon office

Surgeon, surgical practice manager, surgeon office scheduler

Manages the surgeon's own block time and requests more time when it is needed.

Sees

  • Their own blocks, bookings and release suggestions
  • Their own scorecard: utilization, releases and booking accuracy
  • Open and released time available to request

Does

  • Releases, partly releases or keeps blocks, with a reason
  • Requests open or released time
  • Submits case requests where your organization uses the Optimizer for requests

Cannot

  • See other surgeons' patients or case details
  • Change allocations or policy
  • See another surgeon's scorecard unless your organization shares them
Approvals
Open-time requests are approved by the scheduler or the service chief, as your policy sets.
Notified about
Release suggestions for their blocks, upcoming release deadlines, and open time matching their requests.

Service chief

Department chair, division chief, service line director

Manages the service's block time among its surgeons and answers for the service's utilization.

Sees

  • The service's blocks, bookings and releases
  • Scorecards for surgeons in the service
  • Service utilization and demand for more time

Does

  • Reassigns the service's block time among its surgeons
  • Approves or declines open-time requests within the service
  • Comments on allocation proposals affecting the service

Cannot

  • Change other services' blocks
  • Change release policy or utilization definitions
Approvals
Reassignments within the service are recorded; changes to the service's total allocation go to the committee.
Notified about
Service blocks likely to go unused and requests for the service's time.

Perioperative committee member

Perioperative governance committee member, OR executive committee member

Decides allocations and block policy on evidence everyone can see.

Sees

  • Utilization, releases and demand for every service
  • Allocation models and their assumptions
  • Past allocation decisions and their rationale

Does

  • Reviews allocation models before meetings
  • Records allocation and policy decisions with the rationale
  • Requests further analysis from the analyst

Cannot

  • Book or release individual cases and blocks
  • Change utilization definitions outside a recorded committee decision
Approvals
Decisions are recorded as committee decisions, with the members present as your governance requires.
Notified about
Allocation review packs ready before each meeting.

Analyst

Perioperative data analyst, decision support analyst, OR business analyst

Maintains the definitions and models and prepares the analysis the committee relies on.

Sees

  • Case data, utilization calculations and definitions
  • Model accuracy reports comparing estimates with actual times
  • Data quality results from incoming feeds

Does

  • Proposes changes to utilization definitions
  • Reviews model accuracy and requests retraining
  • Builds allocation models for the committee
  • Works data quality issues with the EHR team

Cannot

  • Apply a definition change without the perioperative director's approval
  • Book, release or change cases and blocks
Approvals
Definition changes and model retraining are approved by the perioperative director before they take effect.
Notified about
Data quality failures, accuracy falling outside the range you set, and committee analysis requests.

Administrator

Application administrator, clinical systems or IT administrator

Manages users, roles, interfaces and notification settings.

Sees

  • Users, roles and their services and facilities
  • Interface status and mapping errors
  • The record of permission changes

Does

  • Adds and removes users, or maps them from single sign-on groups
  • Assigns roles, services and facilities
  • Maintains rooms, services and notification settings
  • Runs access review reports

Cannot

  • Book, release or change cases and blocks
  • Change release policy or utilization definitions
  • Grant themselves another role without a second administrator
Approvals
Role changes that grant access to case details follow your organization's access approval process.
Notified about
Interface failures, access reviews coming due and accounts not used for a period your policy sets.

Permissions at a glance

ActionSchedulerOR directorSurgeon officeService chiefCommitteeAnalystAdmin
View case detailsFullFullOwn work onlyOwn work onlyNo accessView onlyNo access
Book or adjust case durationsFullFullNo accessNo accessNo accessNo accessNo access
Release block timeNo accessFullOwn work onlyOwn work onlyNo accessNo accessNo access
Request open timeFullFullOwn work onlyOwn work onlyNo accessNo accessNo access
Approve open-time requestsApprovesApprovesNo accessApprovesNo accessNo accessNo access
Change release rulesNo accessApprovesNo accessNo accessView onlyView onlyNo access
Change utilization definitionsNo accessApprovesNo accessNo accessView onlyOwn work onlyNo access
Run allocation modelsNo accessFullNo accessNo accessView onlyFullNo access
Record allocation decisionsNo accessView onlyNo accessView onlyFullView onlyNo access
View surgeon scorecardsView onlyView onlyOwn work onlyOwn work onlyView onlyView onlyNo access
View audit trailNo accessView onlyNo accessNo accessNo accessView onlyView only
Manage users and rolesNo accessApprovesNo accessNo accessNo accessNo accessFull
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Block owners control their own time: suggestions go to the surgeon or office, and only the owner, their service chief or the perioperative director releases a block before the automatic deadline.
  • Roles are configured with you during implementation. You can rename them, create custom roles, and limit them by facility, service or room, so each person sees only the schedules they are responsible for.
  • Every permission change is recorded in the audit trail with who made it and when, and access review reports list each person's roles for periodic certification.
  • Staff sign in through your identity provider, and roles can follow its groups. Surgeon offices see their own surgeons' patients only, and committee members see utilization without patient detail.

Features

What it does

Consistent utilization

Block utilization calculated with one definition your committee agrees, including how turnover, releases and add-on cases are counted, and shown with the calculation.

Unused-time prediction

Each upcoming block scored on how likely it is to go unused, with the booking patterns behind the score shown to the block owner.

Release suggestions

Suggestions to release time sent to block owners before your release deadline, with one-step release, keep or partial release.

Automatic release rules

Unbooked time released at the deadline your policy sets for each service, with exceptions recorded.

Case duration estimates

Estimated durations for each surgeon and procedure from your own completed cases, with a range and the number of cases behind each estimate.

Open-time requests and waitlist

Surgeons request open or released time in one place, and requests are matched to time as it becomes available.

Room fit view

See how booked cases, estimated durations and turnover fit into each room's staffed hours before the day arrives.

Allocation modeling

Model a proposed change to block allocations against past schedules and demand before the committee decides.

Late start and overrun tracking

First-case start times, turnover and overruns measured by room, service and surgeon, with reasons recorded where staff enter them.

Model monitoring

Estimates compared with actual durations over time, so you can see whether the predictions remain reliable and when they need retraining.

Surgeon scorecards

Each surgeon and office sees their own utilization, releases and booking accuracy, using the same definitions as the committee.

Audit trail

Every release, allocation change, booking adjustment and policy change is logged with the person, time and reason.

Integrations

How it connects to your systems

Connects toHowWhat flows
EHR surgical schedulingBlock templates, booked cases, case requests and case times from your EHR's surgical module, through HL7 SIU messages, FHIR or scheduled extracts mapped during implementation.In: block templates, bookings, case events and times.
Release and booking updatesReleases and booking adjustments decided in the Optimizer are sent back to the EHR scheduling module where your EHR supports it, or worked there by schedulers from a task list.Out: release and booking updates, or scheduler tasks.
Staffing and anesthesia schedulingStaffed room hours and anesthesia coverage from your staffing system, so room fit reflects the rooms you can actually run.In: staffed rooms and hours by day.
Integration engineFeeds can be routed through the integration engine you already use, including a Moraph-managed integration engine.In: HL7 and FHIR messages routed by your engine.
Email and messagingRelease suggestions and open-time notices reach surgeon offices by email or your secure messaging platform.Out: notifications without clinical detail beyond what your policy allows.
Single sign-onStaff sign in through your identity provider (SAML or OpenID Connect).In: user identity and group membership for role assignment.
Work APIUtilization, release and booking data available to your data warehouse and reporting tools through the Moraph Work API.Out: utilization, releases, estimates and outcomes.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Single sign-on

Staff sign in through your identity provider, so your password and multi-factor policies apply.

Role-based access

What each person can see and do follows their role; a surgeon office sees its own blocks and cases, not other surgeons' patients.

Business associate agreement

Case schedules contain protected health information, and Moraph signs a business associate agreement with you.

Encryption and keys

Client data is encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Complete audit trail

Every view, release, booking change, allocation decision and export is logged with the person and time, and cannot be edited.

AI proposes, people decide

Predictions and suggestions are shown with their basis; releases, bookings and allocations are made by people, and the models are monitored for accuracy.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Blocks at risk

For oR schedulers and the perioperative director

Upcoming blocks with their bookings, the likelihood of going unused, release suggestions sent and the owner's response.

Break down by
Date, Room, Service, Block owner, Status
Delivered as
Live dashboard; scheduled email
Used for
Following up release decisions before the deadline.

Open time and waitlist

For oR schedulers and service chiefs

Open and released time available, open-time requests and waitlist cases, and which requests were filled.

Break down by
Date, Service, Request status, Room
Delivered as
Live dashboard; CSV export
Used for
Matching released time with the surgeons who need it.

Day-of-surgery performance

For perioperative director and OR managers

First-case starts, turnover times and overruns by room and service, with the reasons recorded.

Break down by
Room, Service, Surgeon, Reason, Period
Delivered as
Live dashboard; CSV export
Used for
Finding the causes of late starts and long days.

Utilization and governance

Block utilization

For perioperative committee, service chiefs, perioperative director

Utilization by block owner, service and room on the committee's agreed definition, with the calculation shown.

Break down by
Service, Surgeon, Room, Facility, Period
Delivered as
Live dashboard; PDF for committee packs; CSV export
Used for
Reviewing allocations on figures every service accepts.

Release behavior

For perioperative committee and service chiefs

Time released by each owner, how far ahead it was released, automatic releases, and how much released time was rebooked.

Break down by
Service, Block owner, Lead time, Release type, Period
Delivered as
Live dashboard; PDF; CSV export
Used for
Encouraging earlier releases and informing allocation decisions.

Allocation review pack

For perioperative committee

For each service, utilization, releases, unmet demand and modeled allocation changes, prepared before each review.

Break down by
Service, Period, Scenario modeled
Delivered as
PDF; scheduled email
Used for
Preparing committee members to decide allocations.

Allocation decision history

For perioperative director and committee

Every allocation and policy change with the committee decision, rationale and effective date.

Break down by
Service, Decision date, Change type
Delivered as
Live view; PDF and CSV export
Used for
Showing how and why allocations changed.

Scheduling accuracy

Booked versus actual duration

For schedulers, surgeon offices, perioperative director

Booked durations, estimates and actual case times compared by surgeon and procedure.

Break down by
Surgeon, Procedure, Service, Period
Delivered as
Live dashboard; CSV export
Used for
Improving booking accuracy and discussing it with surgeon offices.

Surgeon scorecard

For surgeons, surgeon offices, service chiefs

A surgeon's utilization, releases, booking accuracy and day-of-surgery performance on the committee's definitions.

Break down by
Period, Room, Procedure
Delivered as
PDF; scheduled email; live view
Used for
Giving each surgeon the same figures the committee sees.

Model oversight

Prediction accuracy

For analysts and the perioperative director

How estimated durations and unused-time predictions compared with what happened, over time and by service.

Break down by
Model, Service, Procedure, Period
Delivered as
Live view; PDF and CSV export
Used for
Deciding when the models need retraining and evidencing that they are monitored.

Definition and rule change history

For analysts, perioperative director, committee

Every change to utilization definitions, release rules and model versions, with who proposed and approved it.

Break down by
Item changed, Change date, Approver
Delivered as
Live view; PDF and CSV export
Used for
Showing that the figures and rules in use were approved.

Exports, access and evidence

  • Every report can be exported to CSV, and summary and committee reports to PDF. Reports can be scheduled to arrive by email for the people entitled to see them.
  • Each report can be filtered and the filters saved, so schedulers, service chiefs and committee members can keep their own views. Reports that need a different shape can be built in your own tools from the data described below.
  • Utilization, release, booking and estimate data is available through the Moraph Work API, and can be delivered to your data warehouse or business intelligence tool alongside other operational data.
  • Reports respect each viewer's role: a surgeon office sees its own surgeons, a service chief sees the service, and committee reports show utilization without patient detail.
  • Committee reports can be run as of a past date and give the same result each time. Running and exporting a report is itself recorded in the audit trail.

Deployment

Where and how it runs

Moraph cloud

Hosted and operated by Moraph in the United States region. United Kingdom and Australia regions are available for organizations outside the US.

Dedicated environment

A single-tenant environment for health systems whose policies require isolation, scoped in the proposal.

With a managed service

Optionally run alongside Moraph's managed integration engine for interface monitoring and support.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Data mapping

We map your EHR's block templates, bookings and case events and agree the interface or extract schedule. We need data extracts and a contact from your EHR and integration teams.

Definitions and policy

Utilization definitions, release deadlines and automatic release rules are configured with your perioperative director and documented for the committee.

Model training and validation

Duration and unused-time models are trained on your historical cases, and their accuracy is reviewed with your team on a held-back period before they are shown to schedulers.

Workflow and roles

Release routes, open-time requests, notifications and roles are configured to match how your services and surgeon offices work.

Pilot

The Optimizer can start with a few services or one facility, with results reviewed before it is extended.

Training and go-live

Schedulers, surgeon offices, service chiefs and committee members are trained on their own workflows.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • The Optimizer does not replace your EHR's surgical scheduling module. Cases remain booked in the EHR, and the Optimizer works alongside it.
  • Predictions and duration estimates are suggestions. Releases, bookings and allocations are decided by your staff and committee.
  • Estimates depend on the completeness and accuracy of recorded case times. Surgeons and procedures with few past cases get wider ranges or no estimate.
  • Whether released time is rebooked depends on demand and on your staff acting on suggestions; the Optimizer cannot guarantee that time will be used.
  • Writing releases and booking changes back to the EHR depends on what your EHR's interfaces support; otherwise schedulers apply them from a task list.
  • It does not schedule staff, anesthesia or equipment, although it uses staffed room hours where you provide them.
  • It is not a clinical decision tool and does not assess patients' fitness for surgery.
  • Block policy, allocation decisions and release deadlines are your organization's decisions; the Optimizer records and models them.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Load a period of your own historical schedules and compare the Optimizer's utilization figures with those your committee uses
  2. Check the duration estimates against actual times on a held-back period of your cases
  3. Ask a surgeon office to review a release suggestion and decide on it
  4. Ask a scheduler to book a case using the estimate and the room fit view
  5. Model an allocation change your committee has recently discussed
  6. Confirm role separation: what surgeon offices, service chiefs and schedulers can each see and change

Questions

Frequently asked questions

Does the Optimizer release block time automatically?

Only where your policy sets an automatic release deadline. Otherwise it suggests releases, and the block owner or scheduler decides.

Where do the duration estimates come from?

From your own completed cases, by surgeon and procedure. Each estimate shows its range and how many past cases it is based on, and accuracy is monitored over time.

Do we have to change our EHR scheduling?

No. Cases stay booked in your EHR. The Optimizer reads from it, and writes changes back where your EHR's interfaces allow.

How is it priced?

As a subscription, usually measured by the number of operating rooms or facilities covered, with implementation charged separately. See Working with Moraph for what drives a quotation.

Do you sign a business associate agreement?

Yes. Case schedules contain protected health information, and Moraph signs a business associate agreement before any patient data is loaded.

Is there an accessibility conformance report?

Ask for one through the procurement request form at /how-to-buy/request, naming the version you are evaluating.

Next steps

Evaluate Surgical Block Scheduling Optimizer

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Surgical Block Scheduling Optimizer guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Surgical Block Scheduling Optimizer support guide.

Related products