Difference between revisions of "MU Stage1 Final Rule - Drug-Drug Drug-Allergy Checks"
Peterbodtke (talk | contribs) |
Anthracite (talk | contribs) |
||
Line 46: | Line 46: | ||
(none) | (none) | ||
− | '''DEVELOPMENT STATUS''' | + | '''DEVELOPMENT STATUS'''Although VistA does this now, the need for other interaction checking will be coming and the ability of the purely open source VistA to do this will be leaving because the VA is implementing the use of FirstData and will not be maintaining the interactions in the National Drug File. ePrescribing that is being built by Oroville will need to pick up that function for both patients who have new prescriptions and those who don't. |
− | + | ||
'''ACTION ITEMS / NEXT STEPS''' | '''ACTION ITEMS / NEXT STEPS''' |
Revision as of 18:07, 3 September 2010
SECTION # Section 170.302(a)—Drug-Drug, Drug-Allergy, Drug-Formulary Checks
MU OBJECTIVE Implement drug-drug and drug-allergy interaction checks
MU STAGE 1 MEASURE The EP/eligible hospital/CAH has enabled this functionality for the entire EHR reporting period
CERTIFICATION CRITERION Final Rule Text: §170.302(a). (1) Notifications. Automatically and electronically generate and indicate in real-time, notifications at the point of care for drug- drug and drug-allergy contraindications based on medication list, medication allergy list, and computerized provider order entry (CPOE). (2) Adjustments. Provide certain users with the ability to adjust notifications provided for drug-drug and drug-allergy interaction checks.
STANDARDS N/A
TEST CRITERIA # §170.302 (a) http://healthcare.nist.gov/docs/170.302.a_DrugDrugDrugAllergy_v1.0.pdf
USERS | CORE / MENU | SOLUTION DEVELOPERS | STATUS |
---|---|---|---|
All | CORE | Oroville | In development |
SOLUTION DESIGN / TECHNOLOGY (Add details here)
SOLUTION COMPONENTS (Add details here - Ex. KIDS patch, Delphi code, User guide, Web resources, Manual test script, etc)
DEPENDENCIES (Add details here)
COMMENTS / NOTES (Add details here)
PREVIOUS NOTES (none)
DEVELOPMENT STATUSAlthough VistA does this now, the need for other interaction checking will be coming and the ability of the purely open source VistA to do this will be leaving because the VA is implementing the use of FirstData and will not be maintaining the interactions in the National Drug File. ePrescribing that is being built by Oroville will need to pick up that function for both patients who have new prescriptions and those who don't.
ACTION ITEMS / NEXT STEPS
(Add details here)
OPEN ISSUES / QUESTIONS (Add details here)