Clinical care requirements
Pharmacy, medication management and e-prescribing
Medication orders, verification, dispensing, eMAR, prescribing, controlled substances.
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
C0676Does AuroraMed provide medication ordering with RxNorm coding, dose/route/frequency/indication and duration?
The pharmacy, medication management and e-prescribing part of the specification (REQ-0701) says the system must provide medication ordering with RxNorm coding, dose/route/frequency/indication and duration. No. The specification describes it, but the pilot does not include it. Acceptance check: free-text-only medication order is refused unless policy allows and flags it.
C0677Does AuroraMed check drug-drug, drug-allergy, duplicate therapy, dose range, renal/hepatic and age/weight rules using a licensed knowledge base?
How would it be tested? The specification says seeded test cases fire alerts; override needs coded reason. That is the check for REQ-0702: the system must check drug-drug, drug-allergy, duplicate therapy, dose range, renal/hepatic and age/weight rules using a licensed knowledge base. Not yet. It is designed in the specification and not built in the pilot.
C0678Does AuroraMed support weight/BSA and pediatric dosing calculators with recency checks on weight?
Designed, not built: there is no code for this in the pilot. For reference, REQ-0703 (a top-priority requirement, all three tiers) says the system must support weight/BSA and pediatric dosing calculators with recency checks on weight. Check: stale weight blocks weight-based order.
C0679Does AuroraMed provide pharmacist verification queues?
The system must provide pharmacist verification queues. That is REQ-0704, 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: order cannot be administered before verification unless override policy.
C0680Does AuroraMed provide eMAR with barcode medication administration?
Not built. What the pilot has is a stand-in, not the feature. Pilot detail: MAR entries are free-text (drug, dose, route, status); no barcode scan or five-rights check. REQ-0705 says the system must provide eMAR with barcode medication administration. Its acceptance check: wrong-patient scan blocks administration.
C0681Does AuroraMed integrate IV pumps and dispensing cabinets via standards?
REQ-0706 is a medium-priority requirement for the large tier only: the system must integrate IV pumps and dispensing cabinets via standards. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says pump rate mismatch alerts.
C0682Does AuroraMed maintain medication lists with reconciliation at transitions?
The pharmacy, medication management and e-prescribing part of the specification (REQ-0707) says the system must maintain medication lists with reconciliation at transitions. The pilot covers part of this. The rest is designed, not built. In the pilot: Coded medication list (RxNorm subset) with reconciliation that must decide every active medication; no transition-of-care triggers. Acceptance check: discharge cannot complete until reconciliation done (per site policy).
C0683Does AuroraMed retrieve external medication history (NCPDP RxHistory / Surescripts)?
How would it be tested? The specification says history marked external. That is the check for REQ-0708: the system must retrieve external medication history (NCPDP RxHistory / Surescripts). This is on the design side of the line. Nothing in v0.2.0 does it.
C0684Can AuroraMed send prescriptions electronically using NCPDP SCRIPT?
No. The specification describes it, but the pilot does not include it. For reference, REQ-0709 (a top-priority requirement, all three tiers) says the system must e-prescribe via NCPDP SCRIPT with version negotiation between 2017071 and 2023011 and must use 2023011 exclusively for Part D by 2028-01-01. Check: test with both partner versions passes.
C0685Does AuroraMed support EPCS with DEA-required identity proofing, two-factor signing and audit?
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. Not yet. It is designed in the specification and not built in the pilot. Test in the specification: ePCS audit report matches DEA requirements checklist (to be verified).
C0686Does AuroraMed query PDMP as required and record purpose?
Designed, not built: there is no code for this in the pilot. REQ-0711 says the system must query PDMP as required and record purpose. Its acceptance check: query result not stored beyond policy.
C0687Does AuroraMed check formulary/benefit (NCPDP F&B v60) and real-time benefit (RTPB v13)?
REQ-0712 is a medium-priority requirement for the medium and large tiers: the system must check formulary/benefit (NCPDP F&B v60) and real-time benefit (RTPB v13). This is on the design side of the line. Nothing in v0.2.0 does it. To verify it, the specification says response time budget file 07.
C0688Does AuroraMed support controlled-substance inventory, witness waste and diversion analytics?
The pharmacy, medication management and e-prescribing part of the specification (REQ-0713) says the system must support controlled-substance inventory, witness waste and diversion analytics. No. The specification describes it, but the pilot does not include it. Acceptance check: variance opens case.
C0689Does AuroraMed support IV compounding, hazardous drug and non-sterile records?
How would it be tested? The specification says bUD computed by category. That is the check for REQ-0714: the system must support IV compounding, hazardous drug and non-sterile records. Not yet. It is designed in the specification and not built in the pilot.
C0690Does AuroraMed support pharmacy inventory with par levels and recalls?
Designed, not built: there is no code for this in the pilot. For reference, REQ-0715 (a medium-priority requirement, the medium and large tiers) says the system must support pharmacy inventory with par levels and recalls. Check: recall lot search returns dispensed units.
C0691Does AuroraMed support antimicrobial stewardship, MTM and ADE reporting?
The system must support antimicrobial stewardship, MTM and ADE reporting. That is REQ-0716, a medium-priority requirement for the large tier only. This is on the design side of the line. Nothing in v0.2.0 does it. Test in the specification: aDE report exports MedWatch fields.
C0692Does AuroraMed support specialty and discharge pharmacy workflows and refill requests?
No. The specification describes it, but the pilot does not include it. REQ-0717 says the system must support specialty and discharge pharmacy workflows and refill requests. Its acceptance check: refill queue ownership enforced.
C0693Does AuroraMed support Brazil controlled prescriptions and digital prescribing rules?
REQ-0718 is a medium-priority requirement for all three tiers: the system must support Brazil controlled prescriptions and digital prescribing rules. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says notificação de Receita series validated.
C0694Does AuroraMed support chemotherapy regimens with dose banding and independent double check?
The pharmacy, medication management and e-prescribing part of the specification (REQ-0719) says the system must support chemotherapy regimens with dose banding and independent double check. Designed, not built: there is no code for this in the pilot. Acceptance check: missing second check blocks release.
C0695Does AuroraMed support anticoagulation, insulin and TPN protocols?
How would it be tested? The specification says protocol version stored. That is the check for REQ-0720: the system must support anticoagulation, insulin and TPN protocols. This is on the design side of the line. Nothing in v0.2.0 does it.
C0696Does AuroraMed support 340B tracking and split billing where applicable?
No. The specification describes it, but the pilot does not include it. For reference, REQ-0721 (a lower-priority requirement, the large tier only) says the system must support 340B tracking and split billing where applicable. Check: accumulator report reconciles.
C0697Does AuroraMed support drug shortage substitutions?
The system must support drug shortage substitutions. That is REQ-0722, a lower-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: substitution requires pharmacist approval.