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

Clinical care requirements · C0685

Does AuroraMed support EPCS with DEA-required identity proofing, two-factor signing and audit?

Simulated in the pilot (no real external system)

Short answer

The system must support EPCS with DEA-required identity proofing, two-factor signing and audit. That is REQ-0710, a top-priority requirement for all three tiers. Only as a simulation: real code runs against an in-hub stand-in, not against a real outside system. Where the code stands: Controlled substances: schedule derived from drug name, password step-up, Schedule II rules - NOT DEA EPCS (no identity proofing, no two-factor token). Test in the specification: ePCS audit report matches DEA requirements checklist (to be verified).

This is simulated in the pilot, not a real connection.

Specification item
REQ-0710
Specification priority
P0 (of P0 to P3)
Tiers
Small, Medium, Large

Status as of October 2, 2026. Version 0.5.0, synthetic data only. See what's built today. Not legal, medical or security advice.

Related answers

See it in context: Pharmacy, medication management and e-prescribing · Search the help center · Ask a question

See the synthetic-data demo first.Request a demo