AuroraMed v0.2.0 is a synthetic-data pilot. See exactly what's built →

Portal, billing and business requirements

Public health reporting

Registries and surveillance.

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

C0826Does AuroraMed support eCR (eICR/RR), ELR, syndromic surveillance, IIS, cancer, trauma, stroke, cardiac, PDMP, NHSN, vital records and NEMSIS reporting as configured by jurisdiction?

The public health reporting part of the specification (REQ-2501) says the system must support eCR (eICR/RR), ELR, syndromic surveillance, IIS, cancer, trauma, stroke, cardiac, PDMP, NHSN, vital records and NEMSIS reporting as configured by jurisdiction. No. The specification describes it, but the pilot does not include it. Acceptance check: each report validates against its authority's schema.

Designed, not yet builtPermalink

C0827Does AuroraMed receive HAN/public-health alerts?

How would it be tested? The specification says alert routes to infection prevention. That is the check for REQ-2502: the system must receive HAN/public-health alerts. Not yet. It is designed in the specification and not built in the pilot.

Designed, not yet builtPermalink

C0828Does AuroraMed support DHIS2 aggregate export (ADX/DXF2) and OpenMRS/Bahmni/FHIR exchange for low-resource deployments?

Designed, not built: there is no code for this in the pilot. For reference, REQ-2503 (a lower-priority requirement, all three tiers) says the system must support DHIS2 aggregate export (ADX/DXF2) and OpenMRS/Bahmni/FHIR exchange for low-resource deployments. Check: aggregate export validates.

Designed, not yet builtPermalink
See the synthetic-data demo first.Request a demo