Schedule Profile¶
| Canonical | ../StructureDefinition/nexus-emr-core-schedule |
|---|---|
| Status | draft · 1.26.0 |
| Base | Schedule (constraint) |
| CQL primary code path | serviceType — what this means |
| Source | FSH · JSON |
Minimal Nexus EMR profile for Schedule resources, representing a clinic or provider's bookable calendar. Slots reference back to a Schedule via Slot.schedule. Phase 1 sources OscarPro provider templates (one Schedule per provider) but the profile supports room/equipment (Location) and service-line (HealthcareService) schedules as well.
Elements / Key elements
The working view: must-support, required, modifier and sliced elements from the effective (snapshot) definition.
| Element | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Schedule | 0..* | Nexus EMR Schedule Core Invariants: dom-2, dom-3, dom-4, dom-5, dom-6, schedule-actor-required, schedule-actor-provider-max, schedule-actor-location-max, schedule-actor-healthcareservice-max |
||
| meta | 0..1 | Meta | Metadata about the resource Invariants: ele-1 |
|
| source | S | 0..1 | uri | Identifies EMR instance & pipeline version the resource came from i Invariants: ele-1 |
| implicitRules | ?! | 0..1 | uri | A set of rules under which this content was created i Invariants: ele-1 |
| text | S | 0..1 | Narrative | Narrative i Invariants: ele-1 |
| identifier | S | 0..* | Identifier | Business identifier(s) for schedule i Invariants: ele-1 |
| use | ?! | 0..1 | code | usual | official | temp | secondary | old (If known) i Binding: identifier-use ( required)Invariants: ele-1 |
| system | 1..1 | uri | The namespace for the identifier value i Invariants: ele-1 |
|
| value | 1..1 | string | The value that is unique i Invariants: ele-1 |
|
| active | S ?! | 0..1 | boolean | Whether the schedule is in active use i Invariants: ele-1 |
| serviceCategory | S | 0..* | CodeableConcept | Service category with raw code support i Binding: service-category ( example)Invariants: ele-1 |
| serviceType | S | 0..* | CodeableConcept | Service type with raw code support i Binding: service-type ( example)Invariants: ele-1 |
| actor | S | 1..* | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Device | HealthcareService | Location) | Who/what the schedule belongs to i Invariants: ele-1 |
| planningHorizon | S | 0..1 | Period | Rolling booking window this schedule supports Invariants: ele-1 |
| comment | S | 0..1 | string | Free-text scheduling notes Invariants: ele-1 |