This page manages HCOR scheduling configuration and is restricted to administrators.
Scheduling Configuration
Build the reusable rules and catalogs that future scheduling cycles will use.
One input, one responsibility. Activities define what the work is and who is qualified; Workload Groups define which burden is balanced; Coverage Requirements define how many assignments are needed and when. A cycle may temporarily replace the configured calendar, and its displayed Optimizer uses value is authoritative for that cycle.
Active configuration
Loading…
Draft configuration
Loading…
Runtime schema
—
Your scheduling role
—
Revision workflow
Active revisions are immutable. Creating a draft copies Activities, Credentials, provider profiles, targets, and rules unchanged into a new editable revision. Existing cycles remain pinned to their current revision unless a Configuration-stage cycle is explicitly switched to a newer active revision.
Loading…
Locations
The physical or logical places where schedulable work occurs.
Use this for “where.” An Activity may allow one or several Locations. Do not use Locations for specialties or job roles.Examples: MCR, PVH, GH, FTC, LVLD, Cheyenne, Scottsbluff.
Create a draft configuration before adding or editing locations.
Location
Aliases
Effective dates
Status
Loading…
Credentials & Capabilities
Extra capabilities that determine whether a provider can perform particular work.
Use this for “what this provider is qualified to do” beyond specialty. GEN/INT/EP stays in People and should never be recreated here.Examples: CT, MRI, TAVR Imager, LAAO, MitraClip, CTO, TEE, Vascular Reads.
Create a draft configuration before adding or editing credentials.
Credential
Aliases
Effective dates
Status
Loading…
Workload Groups
The independent buckets the future optimizer will balance against provider targets.
Use this only for “what burden should be fair on its own.” A Workload Group does not create dates, assignments, or provider qualifications. Activities and Roles feed completed-work credit into it; Coverage Requirements create the work.Examples: GEN Weeknight Call, GEN Weekend Call, INT Inpatient, INT Outpatient, CT Reads, MRI Reads.
Create a draft configuration before editing workload groups.
Workload Group
Domain / unit
Baseline responsibility
Preference mode
Status
Loading…
Activities
The actual pieces of work that can appear on a schedule.
Use this for “what assignment is the provider doing, and who can do it.” Activities own allowed segments/locations and specialty or credential requirements. Their weekdays are reusable defaults; a cycle Work Calendar may replace those dates for that cycle.Examples: MCR INT Inpatient, FTC Clinic, Cheyenne Outreach, GEN Weekend Call, MRI Reads.
Create a draft configuration before adding or editing activities.
Activity
Domain / time
Location
Requirements
Preference
Status
Loading…
Assignment Roles
A special responsibility layered on top of one or more host Activities.
Use a Role when someone has a special job within an Activity, not a separate unrelated assignment. Roles can have their own eligibility and Workload Group.Examples: FTC Early Start (FTC(7)), LVLD Triage, CoAg hosted at FTC/LVLD, TAVR INT Operator, TAVR Imager.
Create a draft configuration before editing assignment roles.
Role
Host activities
Requirements
Workload group
Status
Loading…
Coverage Requirements
Defines how many Activity or Role slots are needed and the normal calendar pattern. Each scheduling cycle can add dates, remove dates, or temporarily override the configured pattern without rewriting Configuration.
Use this only for “how many assignments do we need, and when.” Coverage points to an Activity or Role and creates slot inventory. It does not define qualifications, fairness, or the provider who will fill the slot.Examples: 1 FTC provider every weekday; 1 FTC Early Start each weekday; 1 CoAg at FTC or LVLD; 1 TAVR Imager on TAVR dates.
Create a draft configuration before editing coverage.
Requirement
Target
Count
Recurrence
Status
Loading…
Rules & Dependencies
Defines relationships, recovery requirements, spacing, and continuity between assignments.
Use this for “if this assignment happens, what should or must happen around it.” Initial-generation behavior can differ from later operational edits, and override policy is explicit.Examples: Friday hospital must match GEN weekend call; Thursday match preferred; Monday recovery after weekend call; no outreach after overnight call; keep Shock with one provider when possible.
Create a draft configuration before editing rules.
Rule
Type
Source → target
Initial / operational
Exception / priority
Loading…
Generation Scopes
Defines which configured demand and rules are executable in a draft-generation run.
Use this to define solver scope without hard-coded specialty or pool branches. A scope selects Coverage Requirements, provider-specific fixed Activities, and Rules. Provider candidates still come from activity/role eligibility.Example: the initial NORTH GEN + INT scope can include NORTH demand while eligible LPH physicians remain candidates for selected NORTH work.
Create a draft configuration before editing generation scopes.
Scope
Coverage
Fixed activities
Rules
Status
Loading…
Save & Reuse Your Scheduling Setup
Software updates do not require starting over. Save edits first, then export your current configuration as a reusable seed. For an existing cycle, also export its cycle inputs. Original configurations and cycles are never overwritten by a restore.
Includes activities, credentials, provider eligibility, baseline targets, workload participation, coverage, rules, scopes, and (when selected) cycle calendars, imported dates, preferences and capacity adjustments. Generated targets and schedules stay in the original cycle and are not included in this input backup. People/accounts and Holiday/Vacation/Restorative data use the separate Settings backup.
Restore a backup as a separate draft
Nothing is activated automatically. The previous draft remains saved; unfinished configurations can be restored and validated before activation. Provider IDs must already exist in People—names are not used to guess identities.
Carry cycle inputs into the active configuration
After reviewing and activating your configuration, copy the existing cycle or a cycle from your backup. Dates and saved inputs are retained. People status/FTE are refreshed with a preview; preferences become drafts for review. Targets and schedules must be recalculated. The original cycle and its results remain unchanged.
Exporting reads saved data only. Unsaved editor changes are not included.
Imports & Historical Seed
Use historical QGenda data to create a realistic starting configuration without making QGenda the source of truth.
This is a one-time, reviewable seed—not synchronization. The bundled seed was derived from the 2025–2026 QGenda Calendar By Task export plus the scheduling decisions already confirmed for HCOR. QGenda surnames are resolved to canonical providerId values at apply time; specialty/FTE/NORTH-LPH data are never imported from QGenda.Examples: create MCR/PVH/GH, outreach sites, CT/MRI capabilities, call workload groups, FTC(7)/CoAg/TAVR roles, historical provider eligibility, Shock/Scottsbluff rules, and Estes 3-days/week beginning 2027.
Create a draft configuration before previewing or applying the historical seed.
QGenda 2025–2026 historical seed
Historical seeding is for an empty configuration only. It is not an upgrade tool for a customized setup. Use the preservation workflow above to keep your work and review schema changes.
Preview the seed to see provider matching, proposed records, and items intentionally left for review.
Provider Scheduling Profiles
Connect canonical HCOR providers to scheduling capabilities and eligible work.
Core identity stays in People. Specialty, NORTH/LPH home group, FTE, active status, and contract status are read-only here. Scheduling stores only credentials and Activity/Role eligibility.Example: Hatch remains INT + LPH in People, while Scheduling can separately make him eligible for selected NORTH call work. The cycle/configuration snapshot determines whether a provider is schedulable; contract status remains factual roster metadata.
Profiles are view-only while the active configuration is selected. Create a draft to edit them.
Provider
Specialty / home
FTE / status
Credentials
Eligible activities
Eligible roles
Loading…
Master Scheduler Permissions
Controls who may operate schedules; it is separate from general Admin access.
Admin configures the system; Master Scheduler operates schedules. A user may have either or both roles. Later, sensitive actions such as reopening a finalized pre-start schedule can require both.Examples: generating/finalizing a schedule and operational reassignment are Master Scheduler duties; editing Activities and Rules is Admin work.
User
Account role
Scheduling role
Open this section to load users.
Entity
Preferred in compact scheduling views.
Check every active provider who has this capability. This updates the same credentials shown in each provider’s Scheduling Profile. Inactive assignments may be viewed but cannot be changed here.
Select every segment in which this activity may be assigned. The optimizer chooses one allowed segment for each placement.
For flexible target activities, these weekdays define the normal calendar on which HCOR may place the work. The cycle Work Calendar can remove dates, add extra dates, or temporarily override this pattern. Leave blank to allow every day.
Select every location where this activity may occur. Leave all unchecked when location is not fixed. If several are selected, the optimizer chooses one location for each placement.
Optional. Assigns this activity to a distinct fairness/target bucket.
Use automatic for work available to every schedulable provider who meets the specialty/credential requirements. Use explicit for restricted pools, outreach, hospital rotations, and similar jobs.
Leave all unchecked if the activity is not specialty-restricted.
Set the assignment eligibility and linked workload participation together. A provider must satisfy the selected specialty and credential requirements.
GEN:
INT:
EP:
Equal share divides aggregate workload equally among Native providers regardless of FTE; capacity adjustments still apply. FTE weighted scales the baseline by provider FTE and capacity. Provider-specific targets does not distribute aggregate activity Coverage Requirements; baseline responsibility must be entered explicitly for eligible Activities or Assignment Roles.
A host is the actual scheduled event (for example, CardioMEMS or TAVR). This role is a seat staffed within that event; it does not require a separate activity with the role's name. Set the Coverage Requirement count to 2 when two providers fill this role at each event.
An existing assignment counts only when it occurs on the same date, overlaps the required segment, and its assigned provider is legally eligible for the primary target. Use this for conditional coverage such as “MRI PM unless an MRI reader is assigned Image.”
Minimum staffing. Missing required positions are scheduling gaps.
Ideal staffing. Positions above the required count are best-effort and do not count as unfilled work.
Use Flexible quota for “X times per week/month/cycle” when the optimizer may choose the dates.
This controls where the optimizer may place the quota; it does not change how many occurrences are required.
weeks
Example: 3 active weeks out of every 4 repeats three weeks on, one week off.
Identifies week 1 of the repeating block.
For recurring work, a confirmed imported feed may add extra dates to the configured default. For “Imported dates only,” this key is required. Multiple role requirements may share one work calendar/feed.
A paired companion rule creates this target assignment for each matching source occurrence. Use Required initial generation when the same provider must cover both.
Used by Relative Availability Gate rules, such as requiring Friday PM or following Monday AM availability for a weekend assignment.
Used only by a Preferred generation rule or Preferred operational warning.
Generation required
Preferred priority does not apply because neither enforcement setting is Preferred.
Used later for imports such as QGenda labels. Aliases must be unique within this entity type.
Provider
Core roster fields below are read-only and remain sourced from People. Credentials and activity eligibility belong only to this scheduling configuration revision.
Credentials & Capabilities
Factual scheduling capabilities. These are separate from activity eligibility.
Activity Eligibility
A provider must satisfy the activity's specialty and credential requirements before eligibility can be enabled. Providers excluded from scheduling by the current snapshot cannot be made activity-eligible.
Baseline Activity Targets
Quantity only for provider-specific responsibilities such as outreach days/year. Activity settings define segments and locations; the cycle Work Calendar is the single source of placement dates. Annual targets are prorated to the cycle length in the generation preview.
Assignment Role Eligibility
Roles are seats inside a scheduled host Activity. A provider must satisfy the role requirements and be eligible for at least one host. A CardioMEMS Operator role hosted by CardioMEMS does not require an “Operator” Activity.
Baseline Assignment Role Targets
Assign this provider a specific share of an existing role's required seats. These targets distribute coverage; they do not create additional procedures or role positions.
Advanced: Workload Participation Overrides
Ordinary participation is automatic from eligible Activities. Use this section only to exclude the provider from a fairness bucket or to add buy-only cross-pool participation.
Advanced: Provider Rule Adjustments
Use only for a persistent provider-specific exception to a general Rule. Rules without an adjustment are not repeated here, and never-schedule rules cannot be weakened.