Clinical care requirements
Population health, registries and quality measurement
Cohorts, registries, quality reports.
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
C0751Does AuroraMed build cohorts and registries from structured data without exporting identifiers unless authorized?
No. The specification describes it, but the pilot does not include it. For reference, REQ-1501 (a high-priority requirement, the medium and large tiers) says the system must build cohorts and registries from structured data without exporting identifiers unless authorized. Check: cohort list requires purpose and quota.
C0752Does AuroraMed compute eCQMs with CQL and value sets and produce QRDA I/III?
The system must compute eCQMs with CQL and value sets and produce QRDA I/III. That is REQ-1502, a medium-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: sample measure passes CMS test deck.
C0753Does AuroraMed provide risk stratification and gaps-in-care lists?
Designed, not built: there is no code for this in the pilot. REQ-1503 says the system must provide risk stratification and gaps-in-care lists. Its acceptance check: model version shown.
C0754Does AuroraMed support immunization registry reporting and query?
REQ-1504 is a high-priority requirement for the medium and large tiers: the system must support immunization registry reporting and query. This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says vXU accepted by test IIS.
C0755Does AuroraMed produce the reports in the reference catalogs through the report engine using registry-defined report definitions?
The population health, registries and quality measurement part of the specification (REQ-1505) says the system must produce the reports in the reference catalogs through the report engine using registry-defined report definitions. No. The specification describes it, but the pilot does not include it. Acceptance check: report definition can be created without code release.