Identity, registration and scheduling
Scheduling and access management
Appointments, resources, waitlists, reminders.
How to read status labels: In the pilot (v0.2.0, synthetic data) Simulated in the pilot Coming (Wave 2, rolling out) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0595Does AuroraMed provide provider templates, visit types, durations and overbooking rules with effective dating?
Designed, not built: there is no code for this in the pilot. REQ-0351 says the system must provide provider templates, visit types, durations and overbooking rules with effective dating. Its acceptance check: slots generated from a template match its rules.
C0596Does AuroraMed schedule multi-resource appointments (provider, room, equipment)?
REQ-0352 is a high-priority requirement for the medium and large tiers: the system must schedule multi-resource appointments (provider, room, equipment). This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says booking fails if any resource is unavailable.
C0597Does AuroraMed support recurring series, group appointments and block scheduling with release rules?
The scheduling and access management part of the specification (REQ-0353) says the system must support recurring series, group appointments and block scheduling with release rules. No. The specification describes it, but the pilot does not include it. Acceptance check: series exceptions tracked.
C0598Does AuroraMed provide waitlist management with automatic fill?
How would it be tested? The specification says cancelled slot is offered to eligible waitlisted patients in priority order. That is the check for REQ-0354: the system must provide waitlist management with automatic fill. Not yet. It is designed in the specification and not built in the pilot.
C0599Does AuroraMed provide online self-scheduling through the patient portal/wallet with rules per visit type?
Designed, not built: there is no code for this in the pilot. For reference, REQ-0355 (a high-priority requirement, all three tiers) says the system must provide online self-scheduling through the patient portal/wallet with rules per visit type. Check: ineligible visit type is not offered.
C0600Does AuroraMed send reminders by SMS, email, voice, push and WhatsApp where allowed, honoring per-channel contact consent?
The system must send reminders by SMS, email, voice, push and WhatsApp where allowed, honoring per-channel contact consent. That is REQ-0356, a top-priority requirement for all three tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: a patient who declined SMS receives none.
C0601Does AuroraMed check referral and authorization requirements before scheduling?
No. The specification describes it, but the pilot does not include it. REQ-0357 says the system must check referral and authorization requirements before scheduling. Its acceptance check: missing authorization blocks or warns per rule.
C0602Does AuroraMed detect double booking and require override permission with reason?
REQ-0358 is a top-priority requirement for all three tiers: the system must detect double booking and require override permission with reason. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says override is audited.
C0603Does AuroraMed enforce no-show and late-cancel policies with configurable rules?
The scheduling and access management part of the specification (REQ-0359) says the system must enforce no-show and late-cancel policies with configurable rules. Designed, not built: there is no code for this in the pilot. Acceptance check: policy triggers task or fee flag.
C0604Does AuroraMed publish and consume HL7 SIU S12-S26 and FHIR Appointment/Schedule/Slot?
How would it be tested? The specification says interface tests pass. That is the check for REQ-0360: the system must publish and consume HL7 SIU S12-S26 and FHIR Appointment/Schedule/Slot. This is on the design side of the line. Nothing in v0.2.0 does it.
C0605Does AuroraMed provide schedule utilization and access analytics (third-next-available, fill rate)?
No. The specification describes it, but the pilot does not include it. For reference, REQ-0361 (a medium-priority requirement, the medium and large tiers) says the system must provide schedule utilization and access analytics (third-next-available, fill rate). Check: values match test data.
C0606Does AuroraMed support recall and preventive-care outreach lists?
The system must support recall and preventive-care outreach lists. That is REQ-0362, a high-priority requirement for all three tiers. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: list generation honors suppression rules.
C0607Does AuroraMed support telehealth visit scheduling and link generation?
Designed, not built: there is no code for this in the pilot. REQ-0363 says the system must support telehealth visit scheduling and link generation. Its acceptance check: link is single-use and expires.
C0608Does AuroraMed support provider absence management with automatic rebooking suggestions?
REQ-0364 is a medium-priority requirement for the medium and large tiers: the system must support provider absence management with automatic rebooking suggestions. This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says absence produces a rebooking worklist.
C0609Does AuroraMed provide a regulation-queue adapter for national referral systems such as SISREG?
The scheduling and access management part of the specification (REQ-0365) says the system must provide a regulation-queue adapter for national referral systems such as SISREG. No. The specification describes it, but the pilot does not include it. Acceptance check: referral status round-trips in test.