NIST Normative Test Process Document: e-prescribing (erx) Test Tool

Size: px
Start display at page:

Download "NIST Normative Test Process Document: e-prescribing (erx) Test Tool"

Transcription

1 NIST Normative Test Process Document: e-prescribing (erx) Test Tool Test Tool and Test Descriptions to Conduct ONC 2015 Edition Certification Version 1.7 Date: December 3, 2015 Developed by the National Institute of Standards and Technology (NIST) in collaboration with the National Council for Prescription Drug Programs (NCPDP) and the Office of the National Coordinator (ONC) for Health IT

2 Explanation of Terms List of Contents A table containing a key of equivalents for names and terms used frequently in this document Informative Test Description Key background information for conducting the certification testing; includes information about Definition of Tester for this document Care settings and profiles that are in-scope for the testing Capabilities the Health IT Module must be able to demonstrate during the certification testing Normative Test Description Detailed description of the testing process, including Derived Test Requirement(s), Testing Workflow Diagram(s), Required Vendor Information, Required Testing Actions, and Inspection Test Guide Test Data Detailed description of the purpose and use of the provided test data, including allowed exceptions Navigating a Test Case Detailed description of the information and instructions available in the NIST Test Tool related to the Test Cases How to Interpret the Message Content Data Sheet Detailed description of the purpose of and information available in the Message Content Data Sheet, including the meaning of the NIST Test Data Categories and Qualifiers Conformance Test Tools Links to the web-based NIST Test Tool and Support sites, as well as information to assist the Tester in interpreting the Validation Reports generated by the Tool Document History Listing of Version Numbers and Publication Dates for the final published versions of the NIST Normative Testing Process document 2

3 NIST Normative Test Process Document for (b)(3) Electronic Prescribing This document explains the testing process for which a National Institute of Standards and Technology (NIST) validation test tool is used in evaluating conformance of a health information technology module (Health IT Module) to the certification criterion (b)(3) Electronic Prescribing defined in 45 CFR Part 170 of the Office of the National Coordinator for Health Information Technology (ONC), Department of Health and Human Services (HHS) 2015 Edition Health Information Technology (Health IT) Certification Criteria, 2015 Edition Base Electronic Health Record (EHR) Definition, and ONC Health IT Certification Program Modifications Final Rule. For the ONC Approved (b)(3) Electronic Prescribing test procedure visit For detailed certification criterion verbiage, please consult ONC s 2015 Edition Certification Companion Guide for Electronic Prescribing EXPLANATION OF TERMS Key for Names and Terms Used Frequently in this Document Referenced Names and Terms NCPDP SCRIPT Standard, Implementation Guide, Version 10.6 RxNorm, a standardized nomenclature for clinical drugs produced by the United States National Library of Medicine, September 8, 2015 Release International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM) Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT ) Health IT Module Context-based capability of the NIST eprescribing Test Tool Equivalent Used in Document SCRIPT Implementation Guide Named RxNorm Standard or RxNorm ICD-10-CM or ICD-10 SNOMED CT or SNOMED HIT Module or Module Tool 3

4 INFORMATIVE TEST DESCRIPTION This section provides key background information for conducting the certification testing. This document has been developed to be used by the ONC-Accredited Testing Laboratories (ATLs) in certification of Health IT Modules for the ONC. The term Tester, when used in this document, refers to a person (such as an ATL employee) acting on behalf of an ATL for certification testing of a Vendor s HIT Module. In addition, a Vendor may use this document to test their own HIT Modules in preparation for certification testing by an ATL. The test evaluates the capability for a Health IT Module to Support prescription-related electronic transactions that o Are conformant to the NCPDP SCRIPT Standard, Implementation Guide, Version 10.6; and use, at minimum, the RxNorm, a standardized nomenclature for clinical drugs produced by the United States National Library of Medicine, September 8, 2015 Release, including a) Creating messages for new prescriptions and receiving/processing new prescription status messages b) Receiving/processing request messages for changing a prescription and creating messages for change prescription responses c) Creating messages for cancel prescription requests and receiving/processing response messages for cancelling prescriptions d) Receiving/processing request messages for refilling a prescription and creating messages for refill prescription responses e) Receiving/processing fill status notification messages f) Creating request messages for medication history information and receiving/processing medication history information response messages Receive/process and transmit the reason for each of the prescription-related electronic transactions named in a) f) above, using ICD-10-CM coded data in the diagnosis elements in DRU Segment Limit prescription-related electronic transaction to use of only metric standard units of ml (i.e., not cc) for all oral liquid medications Enforce insertion of leading zeroes before the decimal point for [dosage] amounts less than one (1) Enforce never allowing use of trailing zeroes after a decimal point for [dosage amounts in] prescription-related electronic transactions Optionally. Receive/process and transmit each of the prescription-related electronic transactions named in a) f) above (except for the Cancel Prescription Response and Medication History Request), with the SNOMED CT coded reason for the prescription in the indication elements and ICD-10 codes for diagnosis elements in the SIG Segment The ONC 2015 Edition Final Rule specifies the NCPDP SCRIPT Standard, Implementation Guide, Version 10.6, as the messaging standard. This standard defines 12 Profiles; the Profiles shown in Table 1 are in-scope for the certification testing process. 4

5 Transaction Change Prescription (RXCHG, CHGRES) Cancel Prescription (CANRX, CANRES) Refill Prescription (REFREQ, REFRES) Fill Status (RXFILL) Medication History (RXHREQ, RXHRES) STATUS ERROR VERIFY Table 1 In-Scope eprescribing Profiles and Description Description Allows a pharmacist to request a change of a new prescription or a fillable prescription. Allows a prescriber to respond to pharmacy requests to change a prescription. Notifies the pharmacist that a previously sent prescription should be canceled and not filled. Sends the prescriber the results of a prescription cancellation request. Allows the pharmacist to request approval for additional refills of a prescription beyond those originally prescribed. Allows the prescriber to grant the pharmacist permission to provide a patient with additional refills or decline to do so. Allows the pharmacist to notify the prescriber about the status of a prescription in three cases: 1) to notify the prescriber of a dispensed prescription, 2) to notify the prescriber of a partially dispensed prescription, and 3) to notify a prescriber of a prescription not dispensed. Allows a requesting entity to generate a patient-specific medication history request. The responding entity can respond, as information is available, with a patient s medication history, including source, fill number, follow-up contact, date range. Is used to relay acceptance of a transaction back to the sender. A STATUS in response to REFREQ, REFRES, NEWRX, VERIFY, RXCHG, CHGRES, CANRX, CANRES, or RXFILL indicates acceptance and responsibility for a request. This indicates an error has occurred indicating the request was terminated. (An ERROR can be generated when there is a communication problem or when the transaction actually had an error.) If the sender asked for verification that the recipient did in fact receive the message, this is the message type that is sent back to the sender. The National Council for Prescription Drug Programs (NCPDP) supports a task group, the Meaningful Use and NIST Test Methods for eprescribing Task Group, which, in collaboration with NIST, provided the Test Cases and Test Data for this testing process. The testing process also follows the implementation recommendations of NCPDP in the NCPSP SCRIPT Implementation Recommendations, Version Listed in the Test Data section of this document are the Test Scenarios that have been developed for the NIST testing process. Test Data PDF Documents, which are accessible from the NIST eprescribing Test Tool identified in the Conformance Test Tools section of this testing process document, contain the test data that are specific to each Test Scenario. Instructions for use of the provided test data are listed in the Normative Test Description and Test Data sections of this testing process document. The testing process entails four groups of Scenarios that cover the prescription-related electronic transactions required in the certification criterion. Diagrams 1 5 illustrate the key transactions that comprise the Test Steps in the Scenarios. (The numbers in these diagrams indicate transaction flow within each diagram and do not correlate with the numbers of the Derived Test Requirements listed in the Normative Test Description section.) 1 5

6 Each of the Scenario groups includes several Test Scenarios consisting of multiple Test Steps; the Test Steps are provided for both edi and xml. For ONC certification testing, the Tester shall select all of the Test Scenarios and all of the Test Steps (either edi or xml) and shall use the Test Steps together in the sequence in which they are listed in the Test Tool (see Table 2 in the Test Data section of this document for a detailed list of the Scenarios and their Test Steps). Diagram 1 Overview of erx Use Cases and Test Steps Included in Testing Process 6

7 Diagram 2 erx Use Case and Test Steps: Change Prescription Scenarios Diagram 3 erx Use Case and Test Steps: Cancel Prescription Scenarios 7

8 Diagram 4 erx Use Case and Test Steps: Refill Prescription Scenarios Diagram 5 erx Use Case and Test Steps: Medication History Scenarios 8

9 NORMATIVE TEST DESCRIPTION Derived Test Requirements The following four Scenario groups cover the prescription-related electronic transactions identified in the ONC erx criterion. Each Scenario group is composed of two or more Test Steps (which equate to Derived Test Requirements (DTR)) that are to be tested together in the indicated sequence. Each DTR listed below corresponds to a Test Step found in the Test Scenarios provided in the ONC Certification Test Plan of the eprescribing Test Tool. Change Prescription and Receive Fill Status Notifications Scenario Test Steps (NEWRX, RXCHG, CHGRES, RXFILL) erx_dtr - 1: Create Electronic Transaction for New Prescription erx_dtr - 2: Receive and Process Electronic Status Transaction for New Prescription erx_dtr - 3: Receive and Process Electronic Transaction for Change Prescription Request erx_dtr - 4: Create Electronic Status Transaction for Change Prescription Request erx_dtr - 5: Create Electronic Change Response Transaction for Change Prescription Request erx_dtr - 6: Receive and Process Electronic Status Transaction for Change Prescription Response erx_dtr - 7: Receive and Process Electronic Transaction for Fill Status Notification erx_dtr - 8: Create Electronic Status Transaction for Fill Status Notification Cancel Prescription Scenario Test Steps (NEWRX, CANRX, CANRES) erx_dtr - 9: Create Electronic Transaction for New Prescription erx_dtr - 10: Receive and Process Electronic Status Transaction for New Prescription erx_dtr - 11: Create Electronic Transaction for Cancel Prescription Request erx_dtr - 12: Receive and Process Electronic Status Transaction for Cancel Prescription Request erx_dtr - 13: Receive and Process Electronic Transaction for Cancel Prescription Response erx_dtr - 14: Create Electronic Status Transaction for Cancel Prescription Response Refill Prescription Scenario Test Steps (NEWRX, REFREQ, REFRES). erx_dtr - 15: Create Electronic Transaction for New Prescription erx_dtr - 16: Receive and Process Electronic Status Transaction for New Prescription erx_dtr - 17: Receive and Process Electronic Transaction for Refill for Prescription Request erx_dtr - 18: Create Electronic Status Transaction for Refill for Prescription Request erx_dtr - 19: Create Electronic Refill Response Transaction for Refill for Prescription Request erx_dtr - 20: Receive and Process Electronic Status Transaction for Refill Response Transaction Medication History Request Scenario Test Steps (RXHREQ, RXHRES) erx_dtr - 21: Create Electronic Transaction for Medication History Information Request erx_dtr - 22: Receive and Process Electronic Transaction for Medication History Response 9

10 Change Prescription and Receive Fill Status Notifications Scenario Test Steps (NEWRX, RXCHG, CHGRES, RXFILL) erx_dtr - 1: Create Electronic Transaction for New Prescription Figure 1 Create New Prescription Message The instructions in the testing process listed below reference the numbered test steps in Figure 1. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) create patient records in the Module and input the test data for the test patients, 2) create prescription-related electronic transaction messages using the test data according to the Referenced Standards, and 3) import 2 the prescription-related electronic transaction messages into the Tool 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction messages into the Tool 2 During certification testing, the mechanism by which the eprescibing test message is imported (sent) from or to the Health IT Module being tested is not specified. The ATL may have their own utility, they may allow the Module vendor to use a utility created by that vendor, or the message can be cut from the Module and pasted into the NIST Test Tool or cut from the NIST Test Tool and pasted into the Module. For certification testing, the key requirement is for the Module to demonstrate real time/dynamic import. 10

11 Required Testing Actions 1. Using the Context-based capability provided in the Tool identified in the Conformance Test Tools section of this testing process document, the Tester shall access the ONC Certification Test Plan and the Change Prescription Tests, and shall a) Select a Change Scenario and either edi or xml [Figure 1, Step 1] b) Select a Create New Prescription Test Step [Figure 1, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall a) Input the provided new prescription test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 1, Step 3] i. For Change Prescription Tests/Scenario 3, using the capabilities of the HIT Module the Tester shall attempt to enter the test data for the New Prescription for an oral liquid medication first using a unit of measure other than ml (e.g., cc or teaspoon ) for the dosage in the medication order, and the Tester shall inspect the HIT Module to verify its ability to prevent use of any unit of measure other than ml b) Cause the Module to generate the indicated new prescription message [Figure 1, Step 4] 3. In the Tool, the Tester shall load the selected Create New Prescription Test Step and import the new prescription message generated by the HIT Module [Figure 1, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the new prescription message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 1, Step 7, 8, & 9], and that a) The HIT Module limits prescription-related electronic transaction to use of only metric standard units of ml (i.e., not cc) for all oral liquid medications b) The HIT Module enforces insertion of leading zeroes before the decimal point for [dosage] amounts less than one (1) c) The HIT Module enforces never allowing use of trailing zeroes after a decimal point for [dosage amounts in] prescription-related electronic transactions 2. ICD-10 codes in the messages are acceptable with or without decimals 3. If the Tester determines that the ICD-10 code in a message created by the Module is a valid code for a data item (e.g., diagnosis) even though it is different from the ICD-10 code provided for that data item in the test data for that message, the Tester shall allow an exception 4. Once during the certification testing for this criterion, the Tester shall inspect the HIT Module to verify its ability to support the ICD-10 and SNOMED CT coding systems as specified in the SCRIPT Implementation Guide and in the Preamble of the ONC 2015 Final Rule regarding the erx criterion a) Using the functions of the HIT Module and the Tool, the Vendor shall demonstrate to the Tester that their Module supports o The ICD-10 coding system for the diagnosis elements in the DRU Segment 11

12 o o Optionally, the SNOMED CT coding system for the reason for prescription in the indication elements in the SIG Segment Optionally, the ICD-10 coding system for the diagnosis element in the SIG Segment. erx_dtr - 2: Receive and Process Electronic Status Transaction for New Prescription Figure 2 Receive New Prescription Status Message The instructions in the testing process listed below reference the numbered test steps in Figure 2. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) import the Status messages into the Module, and 2) verify that the Status messages are processed according to the Referenced Standards 2. Vendor shall provide the mechanism necessary to import the Status messages into the Module Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 1: Create Electronic Transaction for New Prescription [Figure 2, Step 1] and shall a) Select the New Prescription Status Test Step [Figure 2, Step 2] b) Load the test message [Figure 2, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Status message into the Module, and the Module will consume the message [Figure 2, Steps 3 & 4] 12

13 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected New Prescription Status Test Step [Figure 2, Step 5] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module processed the Status message correctly Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Status message according to the conformance requirements in the Referenced Standards [Figure 2, Step 6] a) No notification need be made visible in the Health IT Module unless the Module is unable to process the Status message b) If the Module is unable to process the Status message, the processing issue(s) must be made visible to the user in some manner in the Module erx_dtr - 3: Receive and Process Electronic Transaction for Change Prescription Request Figure 3 Receive Change Prescription Request Message The instructions in the testing process listed below reference the numbered test steps in Figure 3. 13

14 Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) import the prescription-related electronic transaction messages into the Tool, and 2) verify that the Change Prescription Request messages are processed according to the Referenced Standards 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction messages into the Tool Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 1: Create Electronic Transaction for New Prescription [Figure 3, Step 1] and shall a) Select the Receive Change Prescription Request Test Step [Figure 3, Step 2] b) Load the test message [Figure 3, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Change Prescription Request message into the Module, and the Module will consume the message [Figure 3, Steps 3 & 4] 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected Receive Change Prescription Request Test Step [Figure 3, Step 5] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module processed the change prescription request message correctly Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Change Prescription Request message according to the conformance requirements in the Referenced Standards [Figure 3, Step 6] 14

15 erx_dtr - 4: Create Electronic Status Transaction for Change Prescription Request Figure 4 Create Change Prescription Request Status Message The instructions in the testing process listed below reference the numbered test steps in Figure 4. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) input the test data for the test patients, 2) create prescription-related electronic transaction status messages using the test data according to the Referenced Standards, 3) and import the prescription-related electronic transaction status messages into the Tool 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction status messages into the Tool Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 1: Create Electronic Transaction for New Prescription [Figure 4, Step 1] and shall select the Create Change Prescription Request Status Test Step [Figure 4, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall a) Input the provided change prescription request status test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 4, Step 3] 15

16 b) Cause the Module to generate the indicated change prescription request status message [Figure 4, Step 4] 3. In the Tool, the Tester shall load the selected Create Change Prescription Request Status Test Step and import the change prescription request status message generated by the HIT Module [Figure 4, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the change prescription request status message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 4, Step 7, 8, & 9] 16

17 erx_dtr - 5: Create Electronic Response Transaction for Change Prescription Request Figure 5 Create Change Prescription Response Message The instructions in the testing process listed below reference the numbered test steps in Figure 5. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) input the test data for the test patients, 2) create prescription-related electronic transaction messages using the test data according to the Referenced Standards, 3) and import the prescription-related electronic transaction messages into the Tool 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction messages into the Tool Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 1: Create Electronic Transaction for New Prescription [Figure 5, Step 1] and shall select the Create Change Prescription Response Test Step [Figure 5, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall 17

18 a) Input the provided change prescription response test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 5, Step 3] b) Cause the Module to generate the indicated change prescription response message [Figure 5, Step 4] 3. In the Tool, the Tester shall load the selected Create Change Prescription Response Test Step and import the change prescription response message generated by the HIT Module [Figure 5, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the change prescription response message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 5, Step 7, 8, & 9] erx_dtr - 6: Receive and Process Electronic Status Transaction for Change Prescription Response Figure 6 Receive Change Prescription Response Status Message The instructions in the testing process listed below reference the numbered test steps in Figure 6. 18

19 Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) import the Change Prescription Response Status messages into the Module, and 2) verify that the Change Prescription Response Status messages are processed according to the Referenced Standards 2. Vendor shall provide the mechanism necessary to import the Change Prescription Response Status messages into the Module Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 1: Create Electronic Transaction for New Prescription [Figure 6, Step 1] and shall a) Select the Receive Change Prescription Response Status Test Step [Figure 6, Step 2] b) Load the test message [Figure 6, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Change Prescription Response Status message into the Module, and the Module will consume the message [Figure 6, Steps 3 & 4] 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected Receive Change Prescription Response Status Test Step [Figure 6, Step 5] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module processed the Change Prescription Response Status message correctly Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Change Prescription Response Status message according to the conformance requirements in the Referenced Standards [Figure 6, Step 6] 19

20 erx_dtr - 7: Receive and Process Electronic Transaction for Fill Status Notification Figure 7 Receive Fill Status Notification The instructions in the testing process listed below reference the numbered test steps in Figure 7. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) import the Fill Status Notification messages into the Module, and 2) verify that the Fill Status Notification messages are processed according to the Referenced Standards 2. Vendor shall provide the mechanism necessary to import the Fill Status Notification messages into the Module Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 1: Create Electronic Transaction for New Prescription [Figure 7, Step 1] and shall a) Select the Receive Fill Status Notification Test Step [Figure 7, Step 2] b) Load the test message [Figure 7, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Fill Status Notification message into the Module, and the Module will consume the message [Figure 7, Steps 3 & 4] 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected Fill Status Notification Test Step [Figure 7, Step 5] 20

21 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module processed the Fill Status Notification message correctly Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Fill Status Notification message according to the conformance requirements in the Referenced Standards [Figure 7, Step 6] erx_dtr - 8: Create Electronic Status Transaction for Fill Status Notification Figure 8 Create Fill Status Notification Status Message The instructions in the testing process listed below reference the numbered test steps in Figure 8. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) input the test data for the test patients, 2) create prescription-related electronic transaction status messages using the test data according to the Referenced Standards, 3) and import the prescription-related electronic transaction status messages into the Tool 21

22 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction status messages into the Tool Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 1: Create Electronic Transaction for New Prescription [Figure 8, Step 1] and shall select the Create Fill Status Notification Status Test Step [Figure 8, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall a) Input the provided fill status notification status test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 8, Step 3] b) Cause the Module to generate the indicated fill status notification status message [Figure 8, Step 4] 3. In the Tool, the Tester shall load the selected Create Fill Status Notification Status Test Step and import the fill status notification status message generated by the HIT Module [Figure 8, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the fill status notification status message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 8, Step 7, 8, & 9] 22

23 Cancel Prescription Scenario Test Steps (NEWRX, CANRX, CANRES) erx_dtr - 9: Create Electronic Transaction for New Prescription Figure 9 Create New Prescription Message The instructions in the testing process listed below reference the numbered test steps in Figure 9. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) create patient records in the Module and input the test data for the test patients, 2) create prescription-related electronic transaction messages using the test data according to the Referenced Standards, 3) import the prescription-related electronic transaction messages into the Tool, and 4) demonstrate support for the named standard coding systems 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction messages into the Tool 23

24 Required Testing Actions 1. In the Tool, the Tester shall access the ONC Certification Test Plan and the Cancel Prescription Tests, and shall a) Select a Cancel Scenario and either edi or xml [Figure 9, Step 1] b) Select a Create New Prescription Test Step [Figure 9, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall a) Input the provided new prescription test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 9, Step 3] b) Cause the Module to generate the indicated new prescription message [Figure 9, Step 4] 3. In the Tool, the Tester shall load the selected Create New Prescription Test Step and import the new prescription message generated by the HIT Module [Figure 9, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the new prescription message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 9, Step 7, 8, & 9] 2. ICD-10 codes in the messages are acceptable with or without decimals 3. If the Tester determines that the ICD-10 code in a message created by the Module is a valid code for a data item (e.g., diagnosis) even though it is different from the ICD-10 code provided for that data item in the test data for that message, the Tester shall allow an exception; 24

25 erx_dtr - 10: Receive and Process Electronic Status Transaction for New Prescription Figure 10 Receive and Process New Prescription Status Message The instructions in the testing process listed below reference the numbered test steps in Figure 10. Required Vendor Information Same as for erx_dtr 2 Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 9: Create Electronic Transaction for New Prescription [Figure 10, Step 1] and shall a) Select the New Prescription Status Test Step [Figure 10, Step 2] b) Load the test message [Figure 10, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Status message into the Module, and the Module will consume the message [Figure 10, Steps 3 & 4] 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected New Prescription Status Test Step [Figure 10, Step 5] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module consumed the Status message correctly 25

26 Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Status message according to the conformance requirements in the Referenced Standards [Figure 10, Step 6] a) All Status messages provided in the Test Tool are positive acknowledgements, and no notification need be made visible in the Health IT Module unless the Module is unable to process the message b) If the Module is unable to process the Status message, the processing issue(s) must be made visible to the user in some manner in the Module erx_dtr - 11: Create Electronic Transaction for Cancel Prescription Request Figure 11 Create Cancel Prescription Request Message The instructions in the testing process listed below reference the numbered test steps in Figure

27 Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) create patient records in the Module and input the test data for the test patients, 2) create prescription-related electronic transaction messages using the test data according to the Referenced Standards, 3) and import the prescription-related electronic transaction messages into the Tool 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction messages into the Tool Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 9: Create Electronic Transaction for New Prescription [Figure 11, Step 1] and shall select the Create Cancel Prescription Request Test Step [Figure 11, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall a) Input the provided cancel prescription test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 11, Step 3] b) Cause the Module to generate the indicated cancel prescription request message [Figure 11, Step 4] 3. In the Tool, the Tester shall load the selected Create Cancel Prescription Request Test Step and import the cancel prescription request message generated by the HIT Module [Figure 11, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the cancel prescription request message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 11, Step 7, 8, & 9] 27

28 erx_dtr - 12: Receive and Process Electronic Status Transaction for Cancel Prescription Request Figure 12 Receive and Process Cancel Prescription Request Status Message The instructions in the testing process listed below reference the numbered test steps in Figure 12. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) import the Cancel Prescription Request Status messages into the Module, and 2) verify that the Cancel Prescription Request Status messages are processed according to the Referenced Standards 2. Vendor shall provide the mechanism necessary to import the Cancel Prescription Request Status messages into the Module Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 9: Create Electronic Transaction for New Prescription [Figure 12, Step 1] and shall a) Select the Receive Cancel Prescription Request Status Test Step [Figure 12, Step 2] b) Load the test message [Figure 12, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Cancel Prescription Request Status message into the Module, and the Module will consume the message [Figure 12, Steps 3 & 4] 28

29 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected Receive Cancel Prescription Request Status Test Step [Figure 12, Step 5] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module processed the Cancel Prescription Request Status message correctly Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Cancel Prescription Request Status message according to the conformance requirements in the Referenced Standards [Figure 12, Step 6] erx_dtr - 13: Receive and Process Electronic Transaction for Cancel Prescription Response Figure 13 Receive Cancel Prescription Response Message The instructions in the testing process listed below reference the numbered test steps in Figure 13. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) import the prescription-related electronic transaction messages into the Tool, and 2) verify that the Cancel Prescription Response messages are processed according to the Referenced Standards 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction messages into the Tool 29

30 Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 9: Create Electronic Transaction for New Prescription [Figure 13, Step 1] and shall a) Select the Receive Cancel Prescription Response Test Step [Figure 13, Step 2] b) Load the test message [Figure 13, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Cancel Prescription Response message into the Module, and the Module will consume the message [Figure 13, Steps 3 & 4] 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected Receive Cancel Prescription Response Test Step [Figure 13, Step 5] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module processed the cancel prescription response message correctly and that the message includes the specified information Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Cancel Prescription Response message according to the conformance requirements in the Referenced Standards [Figure 13, Step 6] 30

31 erx_dtr - 14: Create Electronic Status Transaction for Cancel Prescription Response Figure 14 Create Cancel Prescription Response Status Message The instructions in the testing process listed below reference the numbered test steps in Figure 14. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) input the test data for the test patients, 2) create prescription-related electronic transaction messages using the test data according to the Referenced Standards, 3) and import the prescription-related electronic transaction messages into the Tool 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction messages into the Tool Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 9: Create Electronic Transaction for New Prescription [Figure 14, Step 1] and shall select the Create Cancel Prescription Response Status Test Step [Figure 14, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall a) Input the provided cancel prescription response status test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 14, Step 3] 31

32 b) Cause the Module to generate the indicated cancel prescription response status message [Figure 14, Step 4] 3. In the Tool, the Tester shall load the selected Create Cancel Prescription Response Status Test Step and import the cancel prescription response status message generated by the HIT Module [Figure 14, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the cancel prescription response status message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 14, Step 7, 8, & 9] 32

33 Refill Prescription Scenario Test Steps (NEWRX, REFREQ, REFRES). erx_dtr - 15: Create Electronic Transaction for New Prescription Figure 15 Create New Prescription Message The instructions in the testing process listed below reference the numbered test steps in Figure 15. Required Vendor Information Same as for erx_dtr 1 Required Testing Actions 1. In the Tool, the Tester shall access the ONC Certification Test Plan and the Refill Prescription Tests, and shall a) Select a Refill Scenario and either edi or xml [Figure 15, Step 1] b) Select a Create New Prescription Test Step [Figure 15, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall 33

34 a) Input the provided new prescription test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 15, Step 3] b) Cause the Module to generate the indicated new prescription message [Figure 15, Step 4] 3. In the Tool, the Tester shall load the selected Create New Prescription Test Step and import the new prescription message generated by the HIT Module [Figure 15, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the new prescription message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 15, Step 7, 8, & 9] 2. ICD-10 codes in the messages are acceptable with or without decimals 3. If the Tester determines that the ICD-10 code in a message created by the Module is a valid code for a data item (e.g., diagnosis) even though it is different from the ICD-10 code provided for that data item in the test data for that message, the Tester shall allow an exception erx_dtr - 16: Receive and Process Electronic Status Transaction for New Prescription Figure 16 Receive New Prescription Status Message The instructions in the testing process listed below reference the numbered test steps in Figure

35 Required Vendor Information Same as for erx_dtr 2 Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 15: Create Electronic Transaction for New Prescription [Figure 16, Step 1] and shall a) Select the New Prescription Status Test Step [Figure 16, Step 2] b) Load the test message [Figure 16, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Status message into the Module, and the Module will consume the message [Figure 16, Steps 3 & 4] 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected New Prescription Status Test Step [Figure 16, Step 5] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module processed the Status message correctly Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Status message according to the conformance requirements in the Referenced Standards [Figure 16, Step 6] a) No notification need be made visible in the Health IT Module unless the Module is unable to process the Status message b) If the Module is unable to process the Status message, the processing issue(s) must be made visible to the user in some manner in the Module 35

36 erx_dtr - 17: Receive and Process Electronic Transaction for Refills for Prescription Request Figure 17 Receive Prescription Refills Request Message The instructions in the testing process listed below reference the numbered test steps in Figure 17. Required Vendor Information Same as for erx_dtr 3 Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 15: Create Electronic Transaction for New Prescription [Figure 17, Step 1] and shall a) Select the Receive Refill Prescription Request Test Step [Figure 17, Step 2] b) Load the test message [Figure 17, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Refill Prescription Request message into the Module, and the Module will consume the message [Figure 17, Steps 3 & 4] 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected Receive Refill Prescription Request Test Step [Figure 17, Step 5] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module processed the Refill Prescription Request message correctly 36

37 Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Refill Prescription Request message according to the conformance requirements in the Referenced Standards [Figure 17, Step 6] erx_dtr - 18: Create Electronic Status Transaction for Refills for Prescription Request Figure 18 Create Refills for Prescription Request Status Message The instructions in the testing process listed below reference the numbered test steps in Figure 18. Required Vendor Information Same as for erx_dtr 4 Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 15: Create Electronic Transaction for New Prescription [Figure 18, Step 1] and shall select the Create Refill Prescription Request Status Test Step [Figure 18, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall 37

38 a) Input the provided refill prescription request status test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 18, Step 3] b) Cause the Module to generate the indicated refill prescription request status message [Figure 18, Step 4] 3. In the Tool, the Tester shall load the selected Create Refill Prescription Request Status Test Step and import the refill prescription request status message generated by the HIT Module [Figure 18, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the refill prescription request status message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 18, Step 7, 8, & 9] 38

39 erx_dtr - 19: Create Electronic Response Transaction for Refill for Prescription Request Figure 19 Create Response for Prescription Refills Request Message The instructions in the testing process listed below reference the numbered test steps in Figure 19. Required Vendor Information Same as for erx_dtr 5 Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 15: Create Electronic Transaction for New Prescription [Figure 19, Step 1] and shall select the Create Refill Prescription Response Test Step [Figure 19, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall a) Input the provided refill prescription response test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 19, Step 3] b) Cause the Module to generate the indicated refill prescription response message [Figure 19, Step 4] 39

40 3. In the Tool, the Tester shall load the selected Create Refill Prescription Response Test Step and import the refill prescription response message generated by the HIT Module [Figure 19, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the refill prescription response message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 19, Step 7, 8, & 9] erx_dtr - 20: Receive and Process Electronic Status Transaction for Refills for Prescription Response Figure 20 Receive Refills for Prescription Response Status Message The instructions in the testing process listed below reference the numbered test steps in Figure 20. Required Vendor Information Same as for erx_dtr 6 Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 15: Create Electronic Transaction for New Prescription [Figure 20, Step 1] and shall a) Select the Receive Refill Prescription Response Status Test Step [Figure 20, Step 2] 40

41 b) Load the test message [Figure 20, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Refill Prescription Response Status message into the Module, and the Module will consume the message [Figure 20, Steps 3 & 4] 3. In the Tool, the Tester shall retrieve the test step-specific Juror Document for the selected Receive Refill Prescription Response Status Test Step [Figure 20, Step 5] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module processed the Refill Prescription Response Status message correctly Inspection Test Guide 1. Using the test step-specific Juror Document retrieved from the Tool, the Tester shall inspect the Health IT Module and verify that the Module processed the Refill Prescription Response Status message according to the conformance requirements in the Referenced Standards [Figure 20, Step 6] Medication History Request Scenario Test Steps (RXHREQ, RXHRES) erx_dtr - 21: Create Electronic Transaction for Medication History Request Figure 21 Create Medication History Request The instructions in the testing process listed below reference the numbered test steps in Figure

42 Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) create patient records in the Module and input the test data for the test patients, 2) create prescription-related electronic transaction messages using the test data according to the Referenced Standards, 3) and import the prescription-related electronic transaction messages into the Tool 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction messages into the Tool Required Testing Actions 1. In the Tool, Tester shall access the ONC Certification Test Plan and the Medication History Tests [Figure 21, Step 1] and shall select the Create Medication History Request Test Step [Figure 21, Step 2] 2. Using the capabilities in the Health IT Module, the Tester shall a) Input the provided request medication history test data using the Test Data Specification in the Tool for the Test Step (input can be performed using a manual or automated process) [Figure 21, Step 3] b) Cause the Module to generate the indicated medication history request message [Figure 21, Step 4] 3. In the Tool, the Tester shall load the selected Create Medication History Request Test Step and import the medication history request message generated by the HIT Module [Figure 21, Steps 5 & 6] 4. Using the Inspection Test Guide, the Tester shall verify that the HIT Module created the medication history request message correctly and that the message includes the specified information Inspection Test Guide 1. Using the Validation Report produced by the Tool, the Tester shall analyze the Report and verify that the message created by the Health IT Module meets the conformance requirements in the Referenced Standards [Figure 21, Step 7, 8, & 9] 42

43 erx_dtr - 22: Receive and Process Electronic Transaction for Medication History Response Figure 22 Receive Medication History The instructions in the testing process listed below reference the numbered test steps in Figure 22. Required Vendor Information 1. Vendor shall identify the Health IT Module function(s) that are available to 1) import the prescription-related electronic transaction messages into the Tool, and 2) verify that the Response messages are processed according to the Referenced Standards 2. Vendor shall provide the mechanism necessary to import the prescription-related electronic transaction messages into the Tool Required Testing Actions 1. In the Tool, Tester shall select the same Test Scenario (and edi or xml) selected for erx-dtr - 21: Create Electronic Transaction for Medication History Request [Figure 22, Step 1] and shall a) Select the Receive Medication History Response Test Step [Figure 22, Step 2] b) Load the test message [Figure 22, Step 3] 2. Using the capabilities in the Health IT Module, the Tester shall import the Medication History Response message into the Module, and the Module will consume the message [Figure 22, Steps 3 & 4] 43

NCPDP SCRIPT Standard v10.6 Exam Study Guide

NCPDP SCRIPT Standard v10.6 Exam Study Guide NCPDP SCRIPT Standard v10.6 Exam Study Guide Last updated 10/17/2017 Table of Contents Introduction... 3 Benefits... 3 Preparing for the Exam... 3 Transaction Types... 4 Important! Study Methods... 4 Taking

More information

Robert Snelick, NIST Sheryl Taylor, BAH. October 11th, 2012

Robert Snelick, NIST Sheryl Taylor, BAH. October 11th, 2012 Test Tool Orientation for International Society for Disease Surveillance (ISDS): 2014 Edition 170.314(f)(3) Transmission to Public Health Agencies - Syndromic Surveillance Robert Snelick, NIST Sheryl Taylor,

More information

Test Procedure for (c) Record Demographics

Test Procedure for (c) Record Demographics Test Procedure for 170.304 (c) Record Demographics This document describes the test procedure for evaluating conformance of complete EHRs or EHR modules 1 to the certification criteria defined in 45 CFR

More information

Test Procedure for (a) Computerized Provider Order Entry

Test Procedure for (a) Computerized Provider Order Entry Test Procedure for 170.304 (a) Computerized Provider Order Entry This document describes the draft test procedure for evaluating conformance of complete EHRs or EHR modules 1 to the certification criteria

More information

Test Procedure for (s) Integrity

Test Procedure for (s) Integrity Test Procedure for 170.302 (s) Integrity This document describes the draft test procedure for evaluating conformance of complete EHRs or EHR modules 1 to the certification criteria defined in 45 CFR Part

More information

SLI Compliance ONC-ATL Testing Program Guide

SLI Compliance ONC-ATL Testing Program Guide SLI Compliance A Division of Gaming Laboratories International, LLC 4720 Independence St. Wheat Ridge, CO 80033 303-422-1566 www.slicompliance.com SLI Compliance ONC-ATL Testing Program Guide Document

More information

eprescribing for EC, Inpatient, and HOD

eprescribing for EC, Inpatient, and HOD Overview This reference guide provides the steps on how a Provider eprescribes medications and medication refills for patients at Discharge and how successful receipt and processing by the pharmacy is

More information

Quality Data Model (QDM)

Quality Data Model (QDM) Quality Data Model (QDM) Overview Document National Quality Forum 4/20/2011 QUALITY DATA MODEL (QDM): OVERVIEW TABLE OF CONTENTS Quality Data Model (QDM): Overview... 2 National Quality Forum: Overview

More information

PrescribeIT 2.0. User Guide

PrescribeIT 2.0. User Guide PrescribeIT 2.0 User Guide Revisions and Approvals Document Version Date Approved By Description Page# 1.0 Aug 21 2017 Diana Cius First Draft 2.0 March 9 2018 Diana Cius Updated Sections: - Retrieving

More information

Electronic Signature Guidance

Electronic Signature Guidance National Council for Prescription Drug Programs White Paper Electronic Signature Guidance Version 1.0 February 2014 This document provides clarification and guidance to the industry for the use of electronic

More information

PRESCRIPTION MONITORING PROGRAM (PMP)

PRESCRIPTION MONITORING PROGRAM (PMP) PRESCRIPTION MONITORING PROGRAM (PMP) DATA REPORTING MANUAL Effective Date: April 1, 2012 Contact Information: (505) 222-9830 larry.loring@state.nm.us 1 P a g e Table of Contents Reporting requirements

More information

Medical Transcription Billing Corporation (MTBC) Address: 7 Clyde Road, Somerset, NJ (732) x243

Medical Transcription Billing Corporation (MTBC) Address: 7 Clyde Road, Somerset, NJ (732) x243 2015 Edition Health IT Module Test Report Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: TalkEHR Product /Release: 1.0 1.2 Developer Information Developer Name:

More information

Existing Healthcare Standards

Existing Healthcare Standards Existing Healthcare Standards Category Context (Information Model) Information Interchange Standard & Specific Elements ASN.1 Abstract Syntax Notation.1 ASTM E2369-05 Standard Specification for Continuity

More information

Copyright 2012 Pulse Systems, Inc. Page 1 of 28

Copyright 2012 Pulse Systems, Inc. Page 1 of 28 Welcome to the e-learning lesson for erx Administration. In this demonstration, you will learn how to configure the User Options function in the erx module. At the end of the lesson, you may take a practice

More information

Send and Receive Exchange Use Case Test Methods

Send and Receive Exchange Use Case Test Methods Send and Receive Exchange Use Case Test Methods Release 1 Version 1.0 October 1, 2017 Send and Receive Exchange Test Methods Release 1 Version 1.0 Technology Sponsor [Name] [Email] [Telephone] Signature

More information

Care360 Mobile Frequently Asked Questions

Care360 Mobile Frequently Asked Questions Care360 Mobile Frequently Asked Questions Table of Contents Care360 for Mobile Devices... 3 What mobile devices can run Care360?... 3 How do I upgrade one of the supported devices to ios 9.x?... 3 How

More information

Test Procedure for (b) Electronic Prescribing

Test Procedure for (b) Electronic Prescribing Test Procedure for 170.304 (b) Electronic Prescribing This document describes the draft test procedure for evaluating conformance of complete EHRs or EHR modules 1 to the certification criteria defined

More information

Abstract. RevolutionEHR RxNT User s Guide. RevolutionEHR

Abstract. RevolutionEHR RxNT User s Guide. RevolutionEHR RevolutionEHR 6 Boulder Creek Circle Madison, WI 53717 Phone: 866-260-5196 www.revolutionehr.com jschneider@revolutionehr.com RevolutionEHR RxNT User s Guide Abstract This document provides detailed descriptions

More information

Interface. Installation. ScriptSure erx

Interface. Installation. ScriptSure erx ScriptSure erx Interface 1 About ScriptSure ScriptSure is a SureScripts GOLD certified product and rated #1 eprescribing software for its breadth of technology and ease of use. Print, fax or electronically

More information

Chapter 6 Data Entry. Tasks in Data Entry. Window Elements in Data Entry

Chapter 6 Data Entry. Tasks in Data Entry. Window Elements in Data Entry Chapter 6 Data Entry Tasks in Data Entry Starting Data Entry Searching for a Prescriber in Data Entry Searching for a Product in Data Entry Using the Generic Substitution Window Entering Data Entry Detail

More information

Pharmacist Resource Center User Guide

Pharmacist Resource Center User Guide Pharmacist Resource Center User Guide Purpose: This document is a step-by-step instruction guide for accessing the Pharmacist Resource Center functions. The Pharmacist Resource Center is an online tool

More information

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: National Jewish Health Patient

More information

Test Results Summary for 2014 Edition EHR Certification R-0041-PRA V1.0, September 11, (f)(5) Amb. only. (d)(3)

Test Results Summary for 2014 Edition EHR Certification R-0041-PRA V1.0, September 11, (f)(5) Amb. only. (d)(3) 2.2 Gap Certification The following identifies criterion or criteria certified via gap certification 170.314 (a)(1) (a)(19) (d)(6) (h)(1) (a)(6) (a)(20) (d)(8) (h)(2) (a)(7) (b)(5)* (d)(9) (h)(3) (a)(17)

More information

ONC HIT Certification Program

ONC HIT Certification Program ONC HIT Certification Program Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: Clicktate Product Version: 5.0 Domain: Ambulatory Test Type: Complete 1.2 Developer/Vendor

More information

CPRD Aurum Frequently asked questions (FAQs)

CPRD Aurum Frequently asked questions (FAQs) CPRD Aurum Frequently asked questions (FAQs) Version 1.0 Date: 6 December 2017 Author: Helen Booth and Daniel Dedman, CPRD, UK Documentation Control Sheet During the course of the project it may be necessary

More information

Wescom Solutions, Inc. Practitioner Engagement Android Version CFR EPCS Certification Report

Wescom Solutions, Inc. Practitioner Engagement Android Version CFR EPCS Certification Report Wescom Solutions, Inc. Practitioner Engagement Android Version 1.0 21 CFR EPCS Certification Report April 27, 2017 Prepared by Drummond Group drummondgroup.com Page 1 of 5 Certification Summary Overview

More information

Thank you for using our clinical software Medinet. Together with Practice 2000, Medinet offers a complete solution for Medical Practitioners.

Thank you for using our clinical software Medinet. Together with Practice 2000, Medinet offers a complete solution for Medical Practitioners. Brief Guide Forewords Thank you for using our clinical software Medinet. Together with Practice 2000, Medinet offers a complete solution for Medical Practitioners. Medinet helps GPs to streamline clinical

More information

Guide to Meaningful Use Stage 2

Guide to Meaningful Use Stage 2 February, 2014 Introduction This document describes the following Core Measure requirements that are needed to comply with Meaningful Use Stage 2. Meaningful Use Clinical Quality Measures for 2014 and

More information

ELECTRONIC SITE DELEGATION LOG (esdl) USER MANUAL

ELECTRONIC SITE DELEGATION LOG (esdl) USER MANUAL Version 1.0 24May16 ELECTRONIC SITE DELEGATION LOG (esdl) USER MANUAL - Table of Contents - 1. INTRODUCTION... 3 Background... 3 Purpose of the Site Delegation Log... 3 TNCC Contacts... 3 2. SYSTEM REQUIREMENTS...

More information

Prepared by. On behalf of The California HealthCare Foundation. Nov. 24, Sujansky & Associates, LLC 1

Prepared by. On behalf of The California HealthCare Foundation. Nov. 24, Sujansky & Associates, LLC 1 Guidelines for the Electronic Prescribing of Controlled Substances: Identity Proofing, Issuing Authentication Credentials, and Configuring Logical Access Controls Prepared by Sujansky & Associates, LLC

More information

SigmaCare Care Management

SigmaCare Care Management This document will walk a physician or nurse through the process of creating a physician order in SigmaCare. Creating a Physician Order Do this Step 1. From the Resident Summary page, click the Orders

More information

Medtech Evolution electronic Prescribing User Guide

Medtech Evolution electronic Prescribing User Guide Medtech Evolution electronic Prescribing User Guide New Zealand electronic Prescription Service (NZePS) Setup Medtech Global 48 Market Place, Viaduct Harbour, Auckland, New Zealand P: 0800 2 MEDTECH E:

More information

The following identifies criterion or criteria certified via gap certification

The following identifies criterion or criteria certified via gap certification 2.2 Gap Certification The following identifies criterion or criteria certified via gap certification 170.314 (a)(1) (a)(17) (d)(5) (d)(9) (a)(6) (b)(5)* (d)(6) (f)(1) (a)(7) (d)(1) (d)(8) *Gap certification

More information

Certification Commission for Healthcare Information Technology. CCHIT A Catalyst for EHR Adoption

Certification Commission for Healthcare Information Technology. CCHIT A Catalyst for EHR Adoption Certification Commission for Healthcare Information Technology CCHIT A Catalyst for EHR Adoption Alisa Ray, Executive Director, CCHIT Sarah Corley, MD, Chief Medical Officer, NextGen Healthcare Systems;

More information

ChARM EPCS. User Guide for Washington

ChARM EPCS. User Guide for Washington ChARM EPCS User Guide for Washington Table of Contents 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Abbreviations Symbols & Definitions ChARM EPCS Users and Roles Top Level Task Flow - How it works?

More information

Test Results Summary for 2014 Edition EHR Certification R 0033 PRA V1.0, June 26, (f)(5) Amb. only. (d)(3)

Test Results Summary for 2014 Edition EHR Certification R 0033 PRA V1.0, June 26, (f)(5) Amb. only. (d)(3) 2.2 Gap Certification The following identifies criterion or criteria certified via gap certification 170.314 (a)(1) (a)(19) (d)(6) (h)(1) (a)(6) (a)(20) (d)(8) (h)(2) (a)(7) (b)(5)* (d)(9) (h)(3) (a)(17)

More information

ONC HIT Certification Program. Test Results Summary for 2014 Edition EHR Certification

ONC HIT Certification Program. Test Results Summary for 2014 Edition EHR Certification ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: Centricity Perinatal Product

More information

NAVINET USER GUIDE CO N F I D E N T I A L 2017 CoverMyMeds LLC. All Rights Reserved.

NAVINET USER GUIDE CO N F I D E N T I A L 2017 CoverMyMeds LLC. All Rights Reserved. NAVINET USER GUIDE CO NFIDENTIAL 2017 CoverMyMeds LLC. All Rights Reserved. TABLE OF CONTENTS Overview 3 Account Setup 4 Drug Authorizations Homepage 5 Starting a Request 6 Completing the Request Fields

More information

ONC HIT Certification Program

ONC HIT Certification Program ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: Centricity Perinatal (CPN)

More information

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification 15-3251-R-0014-PRA Vl.O, March 12, 2015 ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification lnfoigard Part 1: Product and Developer Information 1.1 Certified Product Information

More information

ONC HIT Certification Program

ONC HIT Certification Program ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: IGNITE Product Version: 1.0.0

More information

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: Soteria Product Version:

More information

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification. Inpatient Modular EHR. www. healthmedx.com

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification. Inpatient Modular EHR. www. healthmedx.com ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Note: Originally tested by CCHIT, inherited certification from CHPL Product ID: CC-2014-510940-1 Part 1: Product and

More information

ONC Health IT Certification Program

ONC Health IT Certification Program ONC Health IT Certification Program Certification Requirements Update March 17, 2016 ICSA Labs Health IT Program Agenda Introduction Mandatory Product Disclosures and Transparency Requirements Certified

More information

Meaningful Use Setup Guide

Meaningful Use Setup Guide Meaningful Use Setup Guide Table of Contents ChiroWrite Certified Settings... 3 Exports... 3 Dr. First... 4 Imports... 4 Microsoft HealthVault... 5 Additional Settings... 7 CPOE... 7 Orders... 8 Order

More information

Training Guide for Alabama Practitioners and Pharmacists. Alabama Department of Public Health Prescription Drug Monitoring Program

Training Guide for Alabama Practitioners and Pharmacists. Alabama Department of Public Health Prescription Drug Monitoring Program Training Guide for Alabama Practitioners and Pharmacists Alabama Department of Public Health Prescription Drug Monitoring Program August 2015 Contents Contents 1 Document Overview... 3 Purpose and Contents...

More information

ONC HIT Certification Program

ONC HIT Certification Program ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: DataMotion Direct Product

More information

Training Guide for Alabama Practitioners and Pharmacists. Alabama Department of Public Health Prescription Drug Monitoring Program

Training Guide for Alabama Practitioners and Pharmacists. Alabama Department of Public Health Prescription Drug Monitoring Program Training Guide for Alabama Practitioners and Pharmacists Alabama Department of Public Health Prescription Drug Monitoring Program March 2015 Contents Contents 1 Document Overview... 2 Purpose and Contents...

More information

ONC HIT Certification Program

ONC HIT Certification Program ONC HIT Certification Program Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: Product Version: v4.3 Domain: Test Type: 1.2 Developer/Vendor Information Developer/Vendor

More information

RxAXIS EPCS Tutorial Quick Reference Guide

RxAXIS EPCS Tutorial Quick Reference Guide Lesson Title Introduction: RxAXIS EPCS The DEA s rule, Electronic Prescriptions for Controlled Substances revises the DEA s regulations to provide practitioners with the option of writing prescription

More information

User Manual/Guide for Direct Using encompass 3.0. Prepared By: Arête Healthcare Services, LLC

User Manual/Guide for Direct Using encompass 3.0. Prepared By: Arête Healthcare Services, LLC User Manual/Guide for Direct Using encompass 3.0 Prepared By: Arête Healthcare Services, LLC Document Version: V1.0 10/02/2015 Contents Direct Overview... 3 What is Direct?... 3 Who uses Direct?... 3 Why

More information

ONC HIT Certification Program

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification 15-3002-R-0007-PRA V1.14, February 28, 2016 ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Part 1: Product

More information

Ohio Automated Reporting System Handbook

Ohio Automated Reporting System Handbook Ohio Automated Reporting System Handbook Ohio State Board of Pharmacy Prescription Monitoring Program 77 South High St., Room 1702 Columbus, OH 43215-6126 Phone: 614-466-4143 (Option 1) OARRS Fax: 614-644-8556

More information

ONC HIT Certification Program

ONC HIT Certification Program ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: Access Profiler Enterprise

More information

ICD-10 Customer Testing Guidelines and Scenarios

ICD-10 Customer Testing Guidelines and Scenarios ICD-10 Customer Testing Guidelines and Scenarios Revision 2.0 Updated July 21, 2015 This document includes pre-release information and user interface designs that are in development for upcoming enhancements

More information

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification. OSEHRA pophealth for Eligible Providers 4.0.

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification. OSEHRA pophealth for Eligible Providers 4.0. 16-3687-R-0001-PRA Vl.O, January 15, 2016 ONC HIT Certification Program lnfoigard Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: Product Version: OSEHRA pophealth

More information

Maine Department of Health and Human Services

Maine Department of Health and Human Services Maine Department of Health and Human Services Minimum Data Set (MDS) Residential Care Assessment (RCA) Electronic Data Submission Requirements (Version 120103) Prepared For: Office of MaineCare Services

More information

Training Guide for Practitioners. Washington State Department of Health Washington State Prescription Monitoring Program

Training Guide for Practitioners. Washington State Department of Health Washington State Prescription Monitoring Program Training Guide for Practitioners Washington State Department of Health Washington State Prescription Monitoring Program April 2017 Training Guide for Practitioners Contents Contents 1 Document Overview...

More information

Using Additional Instructions

Using Additional Instructions ................................................................................................... Using Additional Instructions Pharmacy Technology Solutions May, 2013 Filling New Prescriptions: Using

More information

ONC HIT Certification Program

ONC HIT Certification Program ONC HIT Certification Program Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: ConnectEHR Product Version: 1 Domain: Ambulatory Test Type: Modular EHR Developer/Vendor

More information

NextGen UD2 Upgrade Enhancements

NextGen UD2 Upgrade Enhancements NextGen UD2 Upgrade Enhancements Summary NextGen EHR Enhancements May 23, 2016: Workflow Module Patient Information Bar Alerts Medication Module Allergy Module Encounter/Category View Filters NG Share

More information

Meaningful Use Webcast. Direct Messaging. Questions. November 7,2013

Meaningful Use Webcast. Direct Messaging. Questions. November 7,2013 November 7,2013 Meaningful Use Webcast Direct Messaging Questions Integration of Direct Messaging Review of Direct Messaging Review of CPSI Process Review of On-boarding Process for Direct Messaging Review

More information

Meaningful Use Webcast

Meaningful Use Webcast MU Security Objectives Direct Messaging Questions MU Security Objective Security s Importance to Meaningful Use The Security Objective Satisfying the Objective Security Mechanisms in the EHR Software MU

More information

Community Health Network of CT, Inc.

Community Health Network of CT, Inc. PRPRE0021-0612 Clear Coverage Online Authorizations DME, Medical Supplies Community Health Network of CT, Inc. A New Way to Request Authorizations Beginning on July 1, 2012, there will be three options

More information

Part 7: Medication data

Part 7: Medication data INTERNATIONAL STANDARD ISO 21549-7 Second edition 2016-12-01 Health informatics Patient healthcard data Part 7: Medication data Informatique de santé Données relatives aux cartes de santé des patients

More information

OptumRx quick reference guide

OptumRx quick reference guide OptumRx quick reference guide Our website, optumrx.com is a fast, safe and secure way to manage your prescription benefits online. This quick reference guide illustrates how to use the tools and features

More information

CNAS-RC02. Rules for Sanctions against the Accreditation of Certification Bodies

CNAS-RC02. Rules for Sanctions against the Accreditation of Certification Bodies CNAS-RC02 Rules for Sanctions against the Accreditation of Certification Bodies CNAS CNAS-RC02:2014 Page 1 of 7 Foreword This document is developed by CNAS. This document specifies rules for sanctions

More information

Alabama PDMP AWA E. User Support Manual

Alabama PDMP AWA E. User Support Manual Alabama PDMP AWA E User Support Manual 1 Contents 1 What Is a Requestor?... 4 2 Pre-Loaded User Access... 4 3 Registration... 5 3.1 Registration Process... 6 3.2 Registering as a Delegate... 10 3.3 Email

More information

ONC HIT Certification Program

ONC HIT Certification Program ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification Part 1: Product and Developer Information 1.1 Certified Product Information Product Name: Centricity Perinatal Product

More information

April 25, Dear Secretary Sebelius,

April 25, Dear Secretary Sebelius, April 25, 2014 Department of Health and Human Services Office of the National Coordinator for Health Information Technology Attention: 2015 Edition EHR Standards and Certification Criteria Proposed Rule

More information

ONC Health IT Certification Program: Enhanced Oversight and Accountability Proposed Rule

ONC Health IT Certification Program: Enhanced Oversight and Accountability Proposed Rule ONC Health IT Certification Program: Enhanced Oversight and Accountability Proposed Rule March 22, 2016 Michael L. Lipinski, J.D., Director, Division of Federal Policy and Regulatory Affairs Agenda ONC

More information

The General Equivalence Mappings. GEM Files Summary Sheet

The General Equivalence Mappings. GEM Files Summary Sheet The General Equivalence Mappings Files Summary Sheet Use the s When You are translating lists of codes, code tables, or other coded data You are converting a system or application containing ICD-9-CM codes

More information

Edition. MONTEREY COUNTY BEHAVIORAL HEALTH MD User Guide

Edition. MONTEREY COUNTY BEHAVIORAL HEALTH MD User Guide Edition 1 MONTEREY COUNTY BEHAVIORAL HEALTH MD User Guide i Table of Content OderConnect/InfoScriber Registration CH1 Pg.2 Sign In to MyAvatar CH2..Pg.10 Sync OrderConnect Password CH3.Pg.14 Client Look

More information

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification. Modular EHR

ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification. Modular EHR Test Results Summary for 2014 Edition EHR Certification 14-2552-R-0089-PRI Vl.O, December 24, 2014 ONC HIT Certification Program Test Results Summary for 2014 Edition EHR Certification lnfoigard Part 1:

More information

Section I: Best Available Vocabulary/Code Set/Terminology Standards and Implementation Specifications

Section I: Best Available Vocabulary/Code Set/Terminology Standards and Implementation Specifications Section I: Best Available Vocabulary/Code Set/Terminology s and s I-A: Allergies Interoperability Need: Representing patient allergic reactions / SNOMED-CT Final Production No Free N/A SNOMED-CT may not

More information

RELEASE NOTES. Client Notes. Practice Velocity Practice Management (PVM) PVM, 15.7 PRACTICE VELOCITY. Visit our website at:

RELEASE NOTES. Client Notes. Practice Velocity Practice Management (PVM) PVM, 15.7 PRACTICE VELOCITY. Visit our website at: Version: 15.7 Revision: Approved 1.5 Effective Date: Dec. 17, 2015 Practice Velocity Practice Management (PVM) Client Notes RELEASE NOTES PVM, 15.7 PRACTICE VELOCITY Copyright 2015. Practice Velocity,

More information

Document No.: VCSATSP Restricted Data Protection Policy Revision: 4.0. VCSATS Policy Number: VCSATSP Restricted Data Protection Policy

Document No.: VCSATSP Restricted Data Protection Policy Revision: 4.0. VCSATS Policy Number: VCSATSP Restricted Data Protection Policy DOCUMENT INFORMATION VCSATS Policy Number: VCSATSP 100-070 Title: Restricted Data Protection Policy Policy Owner: Infrastructure Manager Effective Date: 5/1/2013 Revision: 4.0 TABLE OF CONTENTS DOCUMENT

More information

CliniSync Community Health Record. Version Release Notes Live 05/20/17

CliniSync Community Health Record. Version Release Notes Live 05/20/17 CliniSync Community Health Record Version 7.5.4.4 Release Notes Live 05/20/17 1 Contents Appearance and Performance... 3 Browser Support Validation... 3 Advanced Search Option... 4 Patient Age Display...

More information

Medicare Medicaid Encounter Data System

Medicare Medicaid Encounter Data System Medicare Medicaid Encounter Data System Standard Companion Guide for NCPDP Transaction Information Instructions related to National Council for Prescription Drug Programs (NCPDP) Transaction based on Post

More information

CPRD Aurum Frequently asked questions (FAQs)

CPRD Aurum Frequently asked questions (FAQs) CPRD Aurum Frequently asked questions (FAQs) Version 2.0 Date: 10 th April 2019 Authors: Helen Booth, Daniel Dedman, Achim Wolf (CPRD, UK) 1 Documentation Control Sheet During the course of the project

More information

Ascend. Release Notes. Software Version: 2018 Release Date: February 2018 ASPNR2018R1_01

Ascend. Release Notes. Software Version: 2018 Release Date: February 2018 ASPNR2018R1_01 Ascend Release Notes Software Version: 2018 Release Date: February 2018 ASPNR2018R1_01 Ascend 2018 This publication was written and produced by 2018 Copyright is not claimed in any material secured from

More information

Exchanging Patient Demographics Information using ANSI/HL7 v2.8.2

Exchanging Patient Demographics Information using ANSI/HL7 v2.8.2 Exchanging Patient Demographics Information using ANSI/HL7 v2.8.2 Created by: National Resource Centre for EHR Standards, Centre for Development of Advanced Computing (C-DAC), Pune, India Published: August

More information

Ordering New & Refill Prescriptions Online With Costco Mail Order

Ordering New & Refill Prescriptions Online With Costco Mail Order Ordering New & Refill Prescriptions Online With Costco Mail Order Last updated: 09/2018 Register an Account Visit: pharmacy.costco.com Click Sign In/Register and then Create Account to get started on your

More information

Training Guide for Arkansas Practitioners and Pharmacists. Arkansas Department of Health Prescription Monitoring Program

Training Guide for Arkansas Practitioners and Pharmacists. Arkansas Department of Health Prescription Monitoring Program Training Guide for Arkansas Practitioners and Pharmacists Arkansas Department of Health Prescription Monitoring Program May 2013 Contents Contents 1 Document Overview... 1 Purpose and Contents... 1 2 System

More information

YOUR GUIDE TO I-STOP COMPLIANCE AND EPCS

YOUR GUIDE TO I-STOP COMPLIANCE AND EPCS YOUR GUIDE TO I-STOP COMPLIANCE AND EPCS Q: I prescribe medication in New York. Why does EPCS matter to me? A: Beginning March 2015, paper prescriptions will no longer be accepted. Beginning March 27,

More information

OptumRx quick reference guide

OptumRx quick reference guide OptumRx quick reference guide Our website, optumrx.com is a fast, safe and secure way to manage your prescription benefits online. This quick reference guide illustrates how to use the tools and features

More information

Difference Between an EHR System Standard and Product Certification

Difference Between an EHR System Standard and Product Certification Difference Between an EHR System Standard and Product Certification Presented by: Donald T. Mon, PhD Vice President, Practice Leadership American Health Information Management Association HIMSS Annual

More information

Medicare Medicaid Encounter Data System

Medicare Medicaid Encounter Data System Medicare Medicaid Encounter Data System Standard Companion Guide for NCPDP Transaction Information Instructions related to National Council for Prescription Drug Programs (NCPDP) Transaction based on Post

More information

Terminology Harmonization

Terminology Harmonization Terminology Harmonization Rob McClure, MD; Lisa Anderson, MSN, RN-BC; Angie Glotstein, BSN, RN November 14-15, 2018 Washington, DC Table of contents OVERVIEW OF CODE SYSTEMS AND TERMINOLOGY TOOLS USING

More information

Controlled Substances

Controlled Substances 45.75.1 POLICY This policy addresses obtaining, using, storing, recordkeeping, dispensing, and disposing of controlled substances at WSU. This policy provides information and procedures to enable individuals

More information

Electronic Prescribing of Controlled Substances (EPCS)

Electronic Prescribing of Controlled Substances (EPCS) Electronic Prescribing of Controlled Substances (EPCS) This document, as well as the software described in it, is provided under a software license agreement with STI Computer Services, Inc. Use of this

More information

EPCS in the State of New York

EPCS in the State of New York EPCS in the State of New York Medical Society of the State of New York November 20, 2014 Ken Majkowski Vice President Partner Development EPCS Adoption Status as of October 19, 2014 Over 1.3 million New

More information

Denali v3.1b1/onc 2015 Edition Webinar EMR General Features

Denali v3.1b1/onc 2015 Edition Webinar EMR General Features Denali v3.1b1/onc 2015 Edition Webinar EMR General Features Bizmatics, Inc. 4010 Moorpark Avenue, Suite 222 San Jose, CA 95117 www.prognocis.com training@bizmaticsinc.com Copyright 2017 Bizmatics, Inc.

More information

Secure Messaging Meaningful Use Stage 3 Eligible Professionals

Secure Messaging Meaningful Use Stage 3 Eligible Professionals 2015 Certification Criterion: Secure Messaging Objective: Objective 6: Coordination of Care through Patient Engagement Measure 2: For more than 25% of all unique patients seen by the EP during the EHR

More information

California Clinical Data Project PHARMACY DATA STANDARD FORMAT SPECIFICATIONS Version 2.0 Last Revision Date: May 2, 2005

California Clinical Data Project PHARMACY DATA STANDARD FORMAT SPECIFICATIONS Version 2.0 Last Revision Date: May 2, 2005 PHAMACY DATA STANDAD FMAT SPECIFICATINS Last evision Date: May 2, 2005 Definition of Value/Comments # Name Format Length Location 1 Health Plan Name A/N 10 1-10 Name of Health Plan See endnote 1: Health

More information

The below Summary of Rule Changes and the Additional Guidance 2016 Reporting Period is informational for all clients.

The below Summary of Rule Changes and the Additional Guidance 2016 Reporting Period is informational for all clients. Meaningful Use Notice: Health Information Exchange February 10, 2016 Dear Centricity Practice Solution and Centricity EMR Customers: This is a Meaningful Use notice regarding the Health Information Exchange

More information

HL7 s Common Terminology Services Standard (CTS)

HL7 s Common Terminology Services Standard (CTS) HL7 s Common Terminology Services Standard (CTS) HIMSS06 Annual Conference and Exhibition February 15, 2006 San Diego, CA Russell Hamm Objectives Describe the HL7 Common Terminology Services Specification

More information

Kroll Version 10 Service Pack 12. Release notes

Kroll Version 10 Service Pack 12. Release notes Kroll Version 10 Service Pack 12 Release notes Table of Contents Kroll Version 10 Service Pack 12 Release notes...2 User Interface...2 [45638] Profile detail screen enhancement...2 [45650] Drop off screen

More information

Thank you, and enjoy the webinar.

Thank you, and enjoy the webinar. Disclaimer This webinar may be recorded. This webinar presents a sampling of best practices and overviews, generalities, and some laws. This should not be used as legal advice. Itentive recognizes that

More information

Training Guide for Practitioners

Training Guide for Practitioners Training Guide for Practitioners Washington State Department of Health Washington State Prescription Monitoring Program July 2014 RxSentry is a proprietary system for prescription monitoring provided by

More information