Portal, billing and business requirements
Regulatory, compliance and certification support
Compliance evidence.
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
C0829Does AuroraMed maintain a compliance calendar of licenses, accreditations, certificates, drills and filings with expiry alerts?
Designed, not built: there is no code for this in the pilot. For reference, REQ-2551 (a high-priority requirement, all three tiers) says the system must maintain a compliance calendar of licenses, accreditations, certificates, drills and filings with expiry alerts. Check: alert 90/60/30 days [Open lead times]. Parts of it are explicitly marked as open in the specification.
C0830Does AuroraMed support information-blocking exception documentation and Cures Act tooling?
The system must support information-blocking exception documentation and Cures Act tooling. That is REQ-2552, a top-priority requirement for the medium and large tiers. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: exception record exists per denial.
C0831Does AuroraMed support ONC certification test data and real-world testing evidence?
No. The specification describes it, but the pilot does not include it. REQ-2553 says the system must support ONC certification test data and real-world testing evidence. Its acceptance check: evidence pack generated.