Security, data and compliance in Physician On-Call Scheduling

How Physician On-Call Scheduling protects data and supports your compliance obligations.

Security controls

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.

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) standards
• ACGME Common Program Requirements on clinical and educational work hours
• HIPAA Security Rule (45 CFR Part 164, Subpart C)

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

Where 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.

Limitations

• 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.