Difference between revisions of "TEST DELETE ME"
Peterbodtke (talk | contribs) |
Peterbodtke (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | + | '''SECTION # ''': Section 170.302(a)—Drug-Drug, Drug- Allergy, Drug-Formulary Checks | |
| − | 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. | ||
| + | |||
| + | '''TEST CRITERIA #''' | ||
| + | §170.302 (a) | ||
| + | http://healthcare.nist.gov/docs/170.302.a_DrugDrugDrugAllergy_v1.0.pdf | ||
| + | |||
| + | '''STANDARDS''' | ||
| + | N/A | ||
{| class="grey" border="1" cellpadding="2" | {| class="grey" border="1" cellpadding="2" | ||
| − | |||
| − | |||
! USERS | ! USERS | ||
! CORE / MENU | ! CORE / MENU | ||
! DEVELOPMENT OWNER | ! DEVELOPMENT OWNER | ||
| + | ! STATUS | ||
|- | |- | ||
| − | |||
| All | | All | ||
| core | | core | ||
| Oroville | | Oroville | ||
| + | | In development | ||
|} | |} | ||
| − | |||
| − | |||
| − | + | '''SOLUTION DESIGN / TECHNOLOGY''' | |
| − | |||
| − | + | (Add details here) | |
| − | |||
| − | |||
| − | |||
| − | + | '''DELIVERABLE''' | |
| − | |||
| − | |||
| − | + | (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''' | |
Note: VistA currently doesn't maintain formularies. This will need to be done with an interface to a 3rd party application, such as the NewCrop ePrescibing service. Drug interactions are handled in VistA but because of the additional requirements, the current approach is that ePrescribing is used to check for allergies and interactions as part of that service using the drug database of the ePrescribing service. The first service being interfaced with it the NewCrop service which uses the First Databank Database that is the same one the VA was slated to use. The VA was slated to release the source code for that project but the project was stopped as it was running over budget and is under review, so we can't expect any help from the VA code anytime soon. The work being done and funded by Oroville hospital as an extension of the CCR-CCD project to provide ePrescribing is vital to this effort. It will be released as open source when it is completed. | Note: VistA currently doesn't maintain formularies. This will need to be done with an interface to a 3rd party application, such as the NewCrop ePrescibing service. Drug interactions are handled in VistA but because of the additional requirements, the current approach is that ePrescribing is used to check for allergies and interactions as part of that service using the drug database of the ePrescribing service. The first service being interfaced with it the NewCrop service which uses the First Databank Database that is the same one the VA was slated to use. The VA was slated to release the source code for that project but the project was stopped as it was running over budget and is under review, so we can't expect any help from the VA code anytime soon. The work being done and funded by Oroville hospital as an extension of the CCR-CCD project to provide ePrescribing is vital to this effort. It will be released as open source when it is completed. | ||
| Line 45: | Line 53: | ||
The third item may be difficult to provide in the setting of using the ePrescribing service. | The third item may be difficult to provide in the setting of using the ePrescribing service. | ||
| − | + | '''ACTION ITEMS / NEXT STEPS''' | |
| + | |||
| + | (Add details here) | ||
Revision as of 20:24, 17 August 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.
TEST CRITERIA # §170.302 (a) http://healthcare.nist.gov/docs/170.302.a_DrugDrugDrugAllergy_v1.0.pdf
STANDARDS
N/A
| USERS | CORE / MENU | DEVELOPMENT OWNER | STATUS |
|---|---|---|---|
| All | core | Oroville | In development |
SOLUTION DESIGN / TECHNOLOGY
(Add details here)
DELIVERABLE
(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 Note: VistA currently doesn't maintain formularies. This will need to be done with an interface to a 3rd party application, such as the NewCrop ePrescibing service. Drug interactions are handled in VistA but because of the additional requirements, the current approach is that ePrescribing is used to check for allergies and interactions as part of that service using the drug database of the ePrescribing service. The first service being interfaced with it the NewCrop service which uses the First Databank Database that is the same one the VA was slated to use. The VA was slated to release the source code for that project but the project was stopped as it was running over budget and is under review, so we can't expect any help from the VA code anytime soon. The work being done and funded by Oroville hospital as an extension of the CCR-CCD project to provide ePrescribing is vital to this effort. It will be released as open source when it is completed.
Eventually the code for ePrescibing can potentially come "in house" so that VistA instances can become their own ePrescribing service with interfaces to the insurance eligibility and formulary databases (proprietary), Sure Scripts and the commercial drug databases, but Phase one of this effort is to use the ePrescibing service software provided by the ePrescribing service and to send demographics, allergies and medication lists to the service and to return lists augmented by additional information brought back from the service, i.e., additional allergies and medications provided by other providers, etc. The third item may be difficult to provide in the setting of using the ePrescribing service.
ACTION ITEMS / NEXT STEPS
(Add details here)
