Clinical care requirements
Care management, care coordination and referral
Referral loops, care plans, community resources.
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
C0747Does AuroraMed manage referrals with loop closure and status tracking across internal and external recipients?
The care management, care coordination and referral part of the specification (REQ-1601) says the system must manage referrals with loop closure and status tracking across internal and external recipients. No. The specification describes it, but the pilot does not include it. Acceptance check: closed loop dashboard.
C0748Does AuroraMed support care plans, care teams and shared goals with patient view?
How would it be tested? The specification says patient sees goals. That is the check for REQ-1602: the system must support care plans, care teams and shared goals with patient view. Not yet. It is designed in the specification and not built in the pilot.
C0749Does AuroraMed support SDOH screening, community resource referral and Gravity value sets?
Designed, not built: there is no code for this in the pilot. For reference, REQ-1603 (a medium-priority requirement, the medium and large tiers) says the system must support SDOH screening, community resource referral and Gravity value sets. Check: referral status tracked.
C0750Does AuroraMed support transitions of care (C-CDA/Direct/HIE) with reconciliation?
The system must support transitions of care (C-CDA/Direct/HIE) with reconciliation. That is REQ-1604, 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: received C-CDA goes to reconciliation.