Healthcare · Moraph software

Physician On-Call Scheduling

Build fair on-call rotations from your own rules, and keep the call list right

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Physician On-Call Scheduling builds call schedules from the rules each department actually uses: rotations, coverage requirements, time-off, work-hour limits and how holidays and weekends are shared out. It shows how evenly call has been distributed over time, handles swaps with the right approvals, and publishes one current call list to the switchboard, the emergency department and clinicians. Every schedule change keeps who made it and why.

The problem it solves

On-call schedules are often built by one person per department in spreadsheets, with rules held in their head: who covers which holidays, who cannot work back-to-back weekends, who has privileges at which site. Swaps are agreed by text message and the call list the operators use is updated by hand, so it drifts from what physicians believe. When a physician says holiday call has not been fair, or a surveyor asks how the hospital keeps its on-call list current, there is no single record to point to.

  • Rotation and fairness rules live in spreadsheets and one scheduler's memory
  • Holiday and weekend call is hard to share evenly across years
  • Swaps happen informally and the operator's call list falls out of date
  • Questions about past coverage and who was on call are hard to answer

Who uses it

  • Medical staff offices and department schedulers at hospitals and health systems
  • Department chairs and section chiefs who own call coverage
  • Physicians and advanced practice providers who take call
  • Switchboard operators and emergency department staff who need the current call list
  • Graduate medical education offices that schedule residents alongside attendings

Requirements it supports

EMTALA (42 U.S.C. 1395dd) and its on-call list requirement (42 CFR 489.20(r)(2) and 489.24(j))CMS Conditions of Participation for hospitals, medical staff (42 CFR 482.22)The Joint Commission Medical Staff (MS) standardsACGME Common Program Requirements on clinical and educational work hoursHIPAA Security Rule (45 CFR Part 164, Subpart C)

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

    The department's rules

    Each department's rules are listed in plain words, with which ones are protected and who approved them.

    RuleTypeApplies toProtectedApproved by
    Two physicians on call each night, one at each campusCoverageAll nightsYesDepartment chief
    No more than one weekend in threeRestAll attendingsYesDepartment chief
    No call the night before a scheduled procedure dayRestInterventionalNoDepartment chief
    Holiday weight 3, weekend day weight 1.5FairnessAll attendingsYesDepartment chief
    Only physicians with cath lab privileges on interventional callEligibilityInterventional callYesMedical staff office
    Each department's rules are listed in plain words, with which ones are protected and who approved them.

  2. Step 2

    The proposed schedule

    The engine proposes a schedule and lists every shift it could not fill without breaking a rule, with the reason.

    DateShiftPrimaryBackupIssue
    Day 1Night, North campusDr. Sample A (fictional)Dr. Sample C (fictional)
    Day 1Night, South campusDr. Sample B (fictional)Dr. Sample D (fictional)
    Day 6Weekend, North campusDr. Sample E (fictional)Dr. Sample A (fictional)
    Day 7Weekend, South campusUnfilledDr. Sample B (fictional)Weekend rule: all eligible physicians at limit
    Day 12Interventional callDr. Sample C (fictional)Dr. Sample F (fictional)Procedure day rule overridden, reason recorded
    The engine proposes a schedule and lists every shift it could not fill without breaking a rule, with the reason.

  3. Step 3

    A swap request

    A swap is checked against the rules and privileges before it reaches the scheduler for approval.

    Swap · Dr. Sample A (fictional) with Dr. Sample E (fictional)

    Giving
    Night, North campus, Day 14
    Taking
    Night, North campus, Day 21
    Privileges
    Both current for the service
    Weekend rule
    Within limit for both
    Approval needed
    Scheduler

    Checks

    • Coverage requirement still met on both nights
    • No rest rule broken for either physician
    • Holiday totals unchanged
    A swap is checked against the rules and privileges before it reaches the scheduler for approval.

  4. Step 4

    Holiday fairness

    Weighted call totals carry across years, so the department can see who is owed the next holiday.

    PhysicianNightsWeekend daysHolidaysWeighted totalAgainst target
    Dr. Sample A (fictional)4112265On target
    Dr. Sample B (fictional)3914369+4
    Dr. Sample C (fictional)4410162-3
    Dr. Sample D (fictional)4012470+5, skip next holiday
    Dr. Sample E (fictional)3813263.5-1.5
    Weighted call totals carry across years, so the department can see who is owed the next holiday.

  5. Step 5

    The published call list

    Operators and the emergency department see one current list of who to call, with backups and escalation order.

    ServiceSitePrimaryBackupUntil
    CardiologyNorth campusDr. Sample A (fictional)Dr. Sample C (fictional)07:00
    CardiologySouth campusDr. Sample B (fictional)Dr. Sample D (fictional)07:00
    General surgeryNorth campusDr. Sample G (fictional)Dr. Sample H (fictional)07:00
    NeurologyBoth campusesDr. Sample J (fictional)Backup not assigned08:00
    OrthopedicsNorth campusDr. Sample K (fictional)Dr. Sample L (fictional)07:00
    Operators and the emergency department see one current list of who to call, with backups and escalation order.

  6. Step 6

    Who was on call

    For any past date and time, the record shows who was on call as published then, and every change made around it.

    Neurology · Sample date, evening

    1. Schedule published with Dr. Sample J (fictional) as primaryDepartment chief
    2. Swap requested to Dr. Sample M (fictional)Physician
    3. Swap checked against rules and privilegesRules engine
    4. Swap approvedScheduler
    5. Call list updated and switchboard feed sentSystem
    For any past date and time, the record shows who was on call as published then, and every change made around it.

Workflows

The principal workflows

  1. Set the rules

    Each department records its coverage requirements and scheduling rules once: which services need call, how many people per shift, rotation patterns, rest rules, and how holidays and weekends are weighted.

    • Services, sites and shift types defined for the department
    • Coverage requirements set per shift, including backup call
    • Rotation patterns and rest rules entered as named rules
    • Holidays and weekends given weights for fairness counting
    • Rule set reviewed and approved by the department chief

  2. Build the schedule

    The rules engine proposes a schedule for the period, honoring approved time-off and privileges, and shows where it could not satisfy a rule so the scheduler decides how to resolve it.

    • Time-off requests and preferences collected for the period
    • Engine proposes a schedule against the department's rules
    • Unfilled shifts and rule conflicts listed with the reason
    • Scheduler adjusts assignments and records why a rule was overridden
    • Draft shared with physicians for review before publishing

  3. Publish and maintain

    The approved schedule becomes the call list used by operators, the emergency department and clinicians. Swaps and last-minute changes go through the app so the list stays current.

    • Schedule approved and published to the call list
    • Physicians request swaps or giveaways in the app
    • Engine checks the change against rules and privileges
    • Scheduler or chief approves where the rules require it
    • Call list updated and the people affected notified

  4. Review fairness

    Call taken by each physician is counted over the periods you choose, with holidays and weekends weighted, so imbalances are visible and can be corrected in the next schedule.

    • Call counted per physician by shift type and weight
    • Running totals carried across schedule periods and years
    • Imbalances flagged against the department's fairness rule
    • Next period's holiday assignments seeded from the totals
    • Fairness report shared with the department

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.

Physician

Attending physician, advanced practice provider, fellow, resident

Takes call, tells the department when they are unavailable, and arranges swaps through the app so the call list stays right.

Sees

  • The published schedule for their departments and services
  • Their own call shifts, time-off and pending requests
  • Their own call totals, including weighted holidays and weekends
  • Who is on call for other services, as the hospital call list shows it

Does

  • Submits time-off requests and shift preferences in the request window
  • Offers, requests and accepts swaps and giveaways
  • Subscribes to their call shifts in a personal calendar
  • Comments on a draft schedule before it is published
  • Updates their contact numbers for the call list

Cannot

  • Change the published schedule directly
  • See other physicians' time-off reasons
  • Change rules or fairness weights
Approvals
Their time-off requests and any swap the department marks as needing approval go to the scheduler or department chief.
Notified about
Schedule published, a swap offered to them or accepted, a request approved or declined, and changes to their own shifts.

Department scheduler

Department scheduler, practice manager, division administrator, chief resident (for resident schedules)

Turns the department's rules, requests and coverage needs into a schedule, and keeps it current after it is published.

Sees

  • The department's rules, coverage requirements and fairness weights
  • Time-off requests, preferences and swap requests
  • Proposed schedules with unfilled shifts and rule conflicts
  • Call totals for every physician in the department

Does

  • Opens request windows and runs the engine for a schedule period
  • Resolves rule conflicts and records the reason for any override
  • Approves time-off and swaps within the authority the department grants
  • Fills last-minute gaps and updates the call list
  • Sends the draft schedule for chief approval
  • Proposes changes to the department's rules

Cannot

  • Approve rule set changes or their own overrides of rules marked as protected
  • Assign a physician to a service they are not privileged for
  • Edit the change history
Approvals
Published schedules, rule changes and overrides of protected rules are approved by the department chief.
Notified about
New requests and swaps, unfilled shifts, conflicts introduced by a change, and approvals or returns from the chief.

Department chief

Department chair, section chief, medical director, program director

Owns the department's coverage: approves the rules, the schedules built from them and the exceptions to them.

Sees

  • The department's schedules, rules and change history
  • Fairness totals and imbalances across the department
  • Overrides and the reasons recorded for them
  • Open gaps and coverage at risk

Does

  • Approves or returns rule sets and fairness weights
  • Approves schedules for publication
  • Approves overrides of protected rules and escalated swaps
  • Decides how imbalances are corrected in the next period
  • Shares fairness reports with the department

Cannot

  • Approve an override they requested themselves where your policy requires a second approver
  • Change another department's schedule or rules
  • Edit the change history
Approvals
Approves the department's rules, schedules and exceptions; changes to coverage requirements that affect the hospital call list may also need the medical staff office.
Notified about
Schedules and rule changes awaiting approval, overrides of protected rules, and shifts still unfilled close to their start.

Medical staff office

Medical staff services manager, director of medical staff services, chief medical officer's office

Makes sure every service the hospital must cover has call coverage, and that the hospital's call list is complete and current.

Sees

  • Coverage across all departments and sites
  • Services without coverage for any period
  • Privileges data used to check eligibility
  • The hospital-wide call list and its history

Does

  • Defines which services must appear on the hospital call list
  • Reviews coverage gaps across departments and follows up with chiefs
  • Records cross-coverage and coverage agreements between groups
  • Answers questions about who was on call at a past date and time
  • Prepares coverage reporting for medical staff committees

Cannot

  • Change a department's schedule without the department's approval, except where your policy grants emergency authority
  • Change privileges, which come from the credentialing system
  • Edit the change history
Approvals
Changes to the list of services that must be covered are approved through your medical staff process and recorded here.
Notified about
Services with no coverage for an upcoming period, published schedules with gaps, and privileges that expire during a scheduled period.

Operator or ED staff

Switchboard operator, telecommunications staff, ED charge nurse, unit clerk

Finds the right physician to call, quickly, from one current list.

Sees

  • Who is on call now and next, by service and site
  • Primary and backup contacts and escalation order
  • Notes the department has added for operators

Does

  • Searches the call list by service, site or physician
  • Looks up who is on call at a past time when asked
  • Reports a problem with the call list to the department scheduler

Cannot

  • Change schedules, rules or contacts
  • See time-off reasons or fairness totals
Approvals
None; access is read-only.
Notified about
Changes to the call list for the current and next shift, where your hospital turns this on.

Auditor (read-only)

Internal auditor, compliance officer, surveyor (under temporary access)

Reviews call coverage and the history of schedule changes without being able to change anything.

Sees

  • Published schedules and the call list as of any past date
  • Change history, overrides and approvals
  • Coverage reports within the scope granted

Does

  • Searches and reads schedules and call history within their scope
  • Exports reports and records, with each export logged

Cannot

  • Change, approve or delete anything
  • See records outside the scope and dates granted
  • Keep access after it expires
Approvals
Their access is approved by the medical staff office or an administrator, with a scope and an end date.
Notified about
Nothing by default.

Administrator

Application administrator, IT systems analyst

Manages users, departments, sites and integrations, without deciding who takes call.

Sees

  • Users, roles, departments and sites
  • Integration status for credentialing, directory and calendar feeds
  • The record of permission changes

Does

  • Adds and removes users, or maps them from single sign-on groups
  • Assigns roles and department membership
  • Maintains sites, services and integration settings
  • Runs access review reports

Cannot

  • Build, approve or change schedules
  • Change rules or fairness weights
  • Grant themselves a scheduling role without a second administrator
Approvals
Role changes that grant scheduling or approval rights are confirmed by the department chief or medical staff office.
Notified about
Integration failures, access reviews coming due and accounts not used for a period your policy sets.

Permissions at a glance

ActionPhysicianSchedulerDept chiefMed staffOperator/EDAuditorAdmin
View published scheduleView onlyFullFullView onlyView onlyView onlyNo access
Request time-off and swapsOwn work onlyFullFullNo accessNo accessNo accessNo access
Approve time-off and swapsNo accessFullApprovesNo accessNo accessNo accessNo access
Run the engine and edit draftsNo accessFullFullNo accessNo accessNo accessNo access
Publish a scheduleNo accessNo accessApprovesNo accessNo accessNo accessNo access
Override a protected ruleNo accessNo accessApprovesNo accessNo accessNo accessNo access
Change rules and fairness weightsNo accessFullApprovesView onlyNo accessView onlyNo access
View call totalsOwn work onlyFullFullView onlyNo accessView onlyNo access
Search the call listView onlyView onlyView onlyFullView onlyView onlyNo access
Define services that need coverageNo accessNo accessView onlyFullNo accessView onlyNo access
View change historyOwn work onlyView onlyView onlyView onlyNo accessView onlyView only
Manage users and rolesNo accessNo accessApprovesApprovesNo accessNo accessFull
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Schedulers build and maintain schedules, but publishing a schedule and overriding a rule the department marks as protected need the department chief, and nobody approves an override they requested themselves where your policy requires a second approver.
  • Roles are configured with you during implementation. You can rename them, add custom roles, and limit each role to its departments, sites or programs, so a scheduler sees only the schedules they are responsible for.
  • Every permission change is recorded 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. Operators get a read-only call list view, and auditors get temporary read-only access with a defined scope and an end date.

Features

What it does

Rules engine

Coverage, rotation, rest and eligibility rules written as named rules per department, with each rule's effect visible in the proposed schedule.

Holiday and weekend fairness

Holidays and weekends weighted the way your department agrees, with running totals carried across years so the next holiday goes to whoever is owed it.

Rule conflict explanations

When the engine cannot fill a shift without breaking a rule, it says which rule and why, and the scheduler decides.

Time-off and preferences

Physicians submit time-off and shift preferences in one place, with request windows and approval by the department.

Swaps and giveaways

Swaps checked against rules and privileges before they take effect, with approval where the department requires it.

Privileges awareness

Assignments limited to physicians with current privileges for the service and site, using data from your credentialing system.

Current call list

One published call list by service and time for operators, the emergency department and clinicians, with primary and backup contacts.

Work-hour checks

Residents and fellows checked against the work-hour rules your program configures, with warnings before a schedule is published.

Multi-site and cross-coverage

Schedules across campuses, with cross-coverage between departments or groups recorded so the call list shows who actually covers.

Calendar sync

Each physician's call shifts available as a personal calendar feed, updated when the schedule changes.

Point-in-time call history

Who was on call for any service at any past date and time, as published then, with every later change recorded.

Change history

Every assignment, swap, override and approval kept with the person, time and reason.

Integrations

How it connects to your systems

Connects toHowWhat flows
Credentialing and privilegingCurrent privileges by service and site from your credentialing system, including Moraph's Credentialing & Privileging Portal, so only eligible physicians are scheduled.In: privileges, sites and expiry dates.
Staff directory and HRPhysician records, departments and contact details from your directory or HR system, on a schedule agreed in implementation.In: people, departments, roles and contact details.
Switchboard and call list systemsThe published call list sent to your operator console, paging or clinical communication system by file or API.Out: on-call assignments by service, time and contact order.
Residency managementResident rotations and work-hour logs from your residency system, including Moraph's Residency Program Manager, for combined attending and resident schedules.In: rotations and assignments. Out: call shifts for work-hour logging.
CalendarsPersonal calendar feeds for each physician's call shifts, readable by common calendar applications.Out: the physician's own shifts, updated when the schedule changes.
Payroll and call payShifts worked exported for call pay or stipend calculation in your payroll or physician compensation system.Out: shifts worked by physician, shift type and date.
Single sign-onStaff sign in through your identity provider (SAML or OpenID Connect).In: user identity and group membership for role assignment.
Work APISchedules, call lists and fairness totals available to your data warehouse and other systems through the Moraph Work API.Out: schedules, assignments, changes and totals.

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 and department; building a schedule is separate from approving it.

Minimal personal data

Schedules hold staff data, not patient records. If your use brings protected health information into the app, Moraph signs a business associate agreement.

Encryption and keys

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

Complete audit trail

Every assignment, swap, override, approval and export is logged with the person and time, and cannot be edited.

Data residency

Data stays in the hosting region you choose: the United States, the United Kingdom or Australia.

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

Coverage gaps

For department schedulers, chiefs and the medical staff office

Every shift in an upcoming period that is unfilled, filled below its coverage requirement, or filled by someone whose privileges expire before it.

Break down by
Department, Service, Site, Shift type, Date range
Delivered as
Live dashboard; scheduled email; CSV export
Used for
Closing gaps before a shift starts rather than on the day.

Requests and swaps

For department schedulers and chiefs

Open and decided time-off requests, swaps and giveaways, with who requested, who approved and when.

Break down by
Department, Request type, Status, Physician, Period
Delivered as
Live dashboard; CSV export
Used for
Keeping the request queue moving and seeing where swaps cluster.

Call list changes

For medical staff office and operators' supervisors

Changes made to the published call list after publication, with the shift, the old and new physician, and who made the change.

Break down by
Department, Service, Change type, Time before shift
Delivered as
Live view; CSV export
Used for
Spotting late changes that operators and the ED need to know about.

Fairness and workload

Call distribution

For department chiefs and physicians (own totals)

Call taken by each physician by shift type, with holidays and weekends weighted the way the department agreed, for the period and running across years.

Break down by
Physician, Shift type, Holiday, Period, FTE
Delivered as
Live dashboard; PDF for department meetings; CSV export
Used for
Showing the department that call is shared as agreed, and correcting imbalances.

Holiday history

For department chiefs and schedulers

Which physician covered each named holiday in past years, and who is next in line under the department's rule.

Break down by
Holiday, Year, Physician, Service
Delivered as
Live view; CSV export
Used for
Assigning upcoming holidays fairly and answering questions about past ones.

Rule overrides

For department chiefs and the medical staff office

Each time a rule was overridden in a schedule, with the rule, the reason recorded and who approved it.

Break down by
Rule, Department, Approver, Period
Delivered as
Live view; CSV export
Used for
Seeing which rules are routinely broken and whether they need to change.

Work-hour warnings

For program directors and chief residents

Residents and fellows whose scheduled call would exceed the work-hour rules configured for the program, before and after publication.

Break down by
Program, Trainee, Rule, Period
Delivered as
Live dashboard; scheduled email
Used for
Fixing schedules before they create work-hour violations.

Compliance and audit

Call coverage by service

For medical staff office and compliance

For each service the hospital lists as requiring coverage, whether coverage was in place for every hour of the period, and by whom.

Break down by
Service, Site, Period, Department
Delivered as
Live view; PDF and CSV export
Used for
Evidencing that the hospital maintained its on-call list for the services it offers.

Point-in-time call list

For medical staff office, compliance and risk management

Who was on call for a service at a chosen past date and time, as published then, and any changes made around that time.

Break down by
Service, Date and time, Site
Delivered as
On request in the product; PDF export
Used for
Answering incident reviews, complaints and survey questions about who was on call.

Change history extract

For internal audit and compliance

Every change to schedules, rules, weights and permissions for a selected department or period, with the person, time and reason.

Break down by
Department, User, Action, Date range
Delivered as
On request in the product; CSV and PDF export
Used for
Answering audit requests without rebuilding the history by hand.

Shifts worked for call pay

For physician compensation and finance

Shifts worked by each physician by type and date, reflecting swaps, ready for call pay or stipend calculation.

Break down by
Physician, Shift type, Department, Pay period
Delivered as
Scheduled file; CSV export
Used for
Paying call on what was actually worked, not what was first scheduled.

Exports, access and evidence

  • Every report can be exported to CSV, and summary and evidence 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 a scheduler or chief can keep their own views. Reports that need a different shape can be built in your own tools from the Work API.
  • Schedules, assignments, changes and fairness totals are available through the Moraph Work API for your data warehouse or business intelligence tool.
  • Reports respect each viewer's role: physicians see their own totals, chiefs see their department, and the medical staff office sees coverage across the hospital.
  • Coverage and point-in-time 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 support for rule changes, new departments and schedule-period setup.

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.

Department discovery

We work with each department's scheduler and chief to write down the rules they use today, including the unwritten ones, and agree how holidays and weekends are weighted.

Rule configuration

Coverage requirements, rotation patterns, rest rules and fairness weights are configured per department and approved by the department chief.

Data and integrations

Physician records, privileges and contacts are loaded from your directory and credentialing system, and the call list feed to your switchboard or communication system is set up and tested.

History and parallel build

Past call history can be loaded so fairness totals start from where you are. A schedule period is built in both the old process and the app and the results compared.

Roles and approvals

Roles, department scopes, protected rules and approval steps are configured to match your medical staff policies.

Training and go-live

Schedulers, chiefs, physicians and operators are trained on their own tasks, and departments go live in an order you choose.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • The engine proposes schedules; schedulers and department chiefs decide. Where rules conflict and no schedule satisfies them all, it shows the conflict rather than choosing which rule to break.
  • Fairness is measured by the rules and weights your department agrees. The app does not decide what is fair.
  • It does not page or call physicians. It publishes the call list to the switchboard, paging or clinical communication system you already use.
  • It does not grant or verify privileges. It uses privileges data from your credentialing system and is only as current as that data.
  • It is not a time-and-attendance or payroll system. It exports shifts worked for your payroll or compensation process.
  • Work-hour checks follow the rules you configure; your graduate medical education office remains responsible for monitoring and reporting resident work hours.
  • It is designed for physician and advanced practice provider call. Nurse and general workforce staffing are not included.
  • Results depend on the rules being recorded accurately; unwritten department practices need to be captured during implementation to be applied.

Evaluation checklist

What to test in a demonstration or pilot

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

  1. Give us one department's current rules, including the unwritten ones, and compare the proposed schedule with the one you built
  2. Check that the conflict explanations would let your scheduler decide without reworking the whole schedule
  3. Run a holiday period and review whether the fairness totals match how your physicians see it
  4. Make a swap and confirm the call list your operators see updates and the change is recorded
  5. Ask for who was on call for a service at a past date and time and review the answer
  6. Confirm role separation: who can build, approve and publish a schedule, and who can override a protected rule

Questions

Frequently asked questions

Can each department keep its own rules?

Yes. Rules, coverage requirements and fairness weights are set per department, and a department chief approves their own department's rules.

What happens when the rules cannot all be met?

The engine shows which shifts it could not fill and which rule stood in the way. The scheduler decides how to resolve it, and any override of a protected rule goes to the department chief.

Does it replace our paging or clinical communication system?

No. It publishes the call list to the system your operators and clinicians already use.

Can we bring our past call history?

Yes, where you have it in a usable form. Loading history lets fairness totals start from where each physician stands today.

How is it priced?

As a subscription, usually measured by the number of physicians or departments scheduled, with implementation charged separately. See Working with Moraph for what drives a quotation.

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 Physician On-Call Scheduling

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: Physician On-Call Scheduling guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Physician On-Call Scheduling support guide.

Related products