Portal, billing and business requirements
Patient portal, wallet and telehealth
Patient-facing surfaces (app, portal, wallet).
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
C0802Does AuroraMed provide a patient portal and wallet app for records view, messages, scheduling, forms, payments, proxy access and consent?
No. The specification describes it, but the pilot does not include it. REQ-1701 says the system must provide a patient portal and wallet app for records view, messages, scheduling, forms, payments, proxy access and consent. Its acceptance check: patient can view results per release rules.
C0803Does AuroraMed present a patient-visible access history derived from ledger audit batches?
REQ-1702 is a top-priority requirement for all three tiers: the system must present a patient-visible access history derived from ledger audit batches. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says access list matches audit for that patient.
C0804Does AuroraMed support patient-initiated records requests with identity verification and automatic fulfilment through the consent flow?
The patient portal, wallet and telehealth part of the specification (REQ-1703) says the system must support patient-initiated records requests with identity verification and automatic fulfilment through the consent flow. Designed, not built: there is no code for this in the pilot. Acceptance check: request completes within profile SLA.
C0805Does AuroraMed support proxy/guardian access with scoped views and age-based transitions (adolescent)?
How would it be tested? The specification says proxy loses adolescent-confidential items. That is the check for REQ-1704: the system must support proxy/guardian access with scoped views and age-based transitions (adolescent). This is on the design side of the line. Nothing in v0.2.0 does it.
C0806Does AuroraMed support secure telehealth video visits (WebRTC) with recording off by default and consent capture?
No. The specification describes it, but the pilot does not include it. For reference, REQ-1705 (a high-priority requirement, the medium and large tiers) says the system must support secure telehealth video visits (WebRTC) with recording off by default and consent capture. Check: no recording without consent.
C0807Does AuroraMed support remote patient monitoring and wearable data intake flagged as patient-reported?
The system must support remote patient monitoring and wearable data intake flagged as patient-reported. That is REQ-1706, a lower-priority requirement for the large tier only. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: values tagged.
C0808Does AuroraMed provide SMART Health Cards / Links for vaccination and summary data?
Designed, not built: there is no code for this in the pilot. REQ-1707 says the system must provide SMART Health Cards / Links for vaccination and summary data. Its acceptance check: card verifies with public key.
C0809Does AuroraMed support patient payment (card, PIX, local methods) via certified processors that never store card data in the record?
REQ-1708 is a medium-priority requirement for all three tiers: the system must support patient payment (card, PIX, local methods) via certified processors that never store card data in the record. This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says no PAN in database.