Electronic prescribing

Complete the following steps using the NCPDP SCRIPT Standard Version 2017071.

1. The health IT developer creates new prescriptions (NewRx) in accordance with (b)(3)(ii)(A)(3)(i) and (b)(3)(ii)(A)(3)(ii) request and respond to change prescriptions (RxChangeRequest, RxChangeResponse), and (b)(3)(ii)(A)(3)(v) fill status notifications (RxFill).
2. The health IT developer creates new prescriptions (NewRx) in accordance with (b)(3)(ii)(A)(3)(i) and (b)(3)(ii)(A)(3)(iii) request and respond to cancel prescriptions (CancelRx, CancelRxResponse).
3. The health IT developer creates new prescriptions (NewRx) in accordance with (b)(3)(ii)(A)(3)(i) and (b)(3)(ii)(A)(3)(iv) request and respond to renew prescriptions (RxRenewalRequest, RxRenewalResponse).
4. The health IT developer relays acceptance of a transaction back to the sender (Status) in accordance with (b)(3)(ii)(A)(3)(vii).
5. The health IT developer responds that there was a problem with the transaction (Error) in accordance with (b)(3)(ii)(A)(3)(viii).
6. The health IT developer responds that a transaction requesting a return receipt has been received (Verify) in accordance with (b)(3)(ii)(A)(3)(ix).

Complete the following steps using the NCPDP SCRIPT Standard Version 2023011.

1. The health IT developer creates new prescriptions (NewRx) in accordance with (b)(3)(ii)(A)(3)(i) and (b)(3)(ii)(A)(3)(ii) request and respond to change prescriptions (RxChangeRequest, RxChangeResponse), and (b)(3)(ii)(A)(3)(v) fill status notifications (RxFill).
2. The health IT developer creates new prescriptions (NewRx) in accordance with (b)(3)(ii)(A)(3)(i) and (b)(3)(ii)(A)(3)(iii) request and respond to cancel prescriptions (CancelRx, CancelRxResponse).
3. The health IT developer creates new prescriptions (NewRx) in accordance with (b)(3)(ii)(A)(3)(i) and (b)(3)(ii)(A)(3)(iv) request and respond to renew prescriptions (RxRenewalRequest, RxRenewalResponse).
4. The health IT developer relays acceptance of a transaction back to the sender (Status) in accordance with (b)(3)(ii)(A)(3)(vii).
5. The health IT developer responds that there was a problem with the transaction (Error) in accordance with (b)(3)(ii)(A)(3)(vii).
6. The health IT developer responds that a transaction requesting a return receipt has been received (Verify) in accordance with (b)(3)(ii)(A)(3)(ix).

The test lab verifies the following steps in accordance with the NCPDP SCRIPT Standard Version 2017071.

1. The tester verifies the Health IT Module sends and receives the following transactions and completes all required test tool interaction steps and verifies the validation report for the following required transactions:
   1. Create and send new prescription (NewRx);
   2. Receive prescription change request (RxChangeRequest);
   3. Create and send prescription change response (RxChangeResponse); and
   4. Receive fill status notification (RxFill).
2. The tester verifies the Health IT Module sends and receives the following transactions and completes all required test tool interaction steps and verifies the validation report for the following required transactions:
   1. Create and send new prescription (NewRx);
   2. Send request to cancel prescription (CancelRx); and
   3. Receive response to request to cancel prescription (CancelRxResponse).
3. The tester verifies the Health IT Module sends and receives the following transactions and completes all required test tool interaction steps and verifies the validation reports for the following required transactions:
   1. Create and send new prescription (NewRx);
   2. Receive request to renew prescription (RxRenewalRequest); and
   3. Create and send response to renew prescription (RxRenewalResponse).
4. The tester verifies the Health IT Module supports Status, Error and Verify transactions.

Complete the following steps using the NCPDP SCRIPT Standard Version 2023011.

1. The tester verifies the Health IT Module sends and receives the following transactions and completes all required test tool interaction steps and verifies the validation report for the following required transactions:
   1. Create and send new prescription (NewRx);
   2. Receive prescription change request (RxChangeRequest);
   3. Create and send prescription change response (RxChangeResponse); and
   4. Receive fill status notification (RxFill).
2. The tester verifies the Health IT Module sends and receives the following transactions and completes all required test tool interaction steps and verifies the validation report for the following required transactions:
   1. Create and send new prescription (NewRx);
   2. Send request to cancel prescription (CancelRx); and
   3. Receive response to request to cancel prescription (CancelRxResponse).
3. The tester verifies the Health IT Module sends and receives the following transactions and completes all required test tool interaction steps and verifies the validation reports for the following required transactions:
   1. Create and send new prescription (NewRx);
   2. Receive request to renew prescription (RxRenewalRequest); and
   3. Create and send response to renew prescription (RxRenewalResponse).
4. The tester verifies the Health IT Module supports Status, Error and Verify transactions.

Complete the following steps using the NCPDP SCRIPT Standard Version 2017071.

1. The health IT developer requests and receives a patient’s medication history (RxHistoryRequest, RxHistoryResponse) in accordance with (b)(3)(ii)(A)(3)(vi).

Complete the following steps using the NCPDP SCRIPT Standard Version 2023011.

1. The health IT developer requests and receives a patient’s medication history (RxHistoryRequest, RxHistoryResponse) in accordance with (b)(3)(ii)(A)(3)(vi).

Complete the following steps using the NCPDP SCRIPT Standard Version 2017071.

1. The tester verifies the Health IT Module sends and receives the following transactions and completes all required test tool interaction steps and verifies the validation report for the following required transactions:
   1. Send a request for a medication history (RxHistoryRequest); and
   2. Receive a response to a request for a medication history (RxHistoryResponse); or
   3. Receive a Status message (Status) in response to a request for a medication history (RxHistoryRequest) and receive a response to a request for a medication history (RxHistoryResponse).

Complete the following steps using the NCPDP SCRIPT Standard Version 2023011.

1. The tester verifies the Health IT Module sends and receives the following transactions and completes all required test tool interaction steps and verifies the validation report for the following required transactions:
   1. Send a request for a medication history (RxHistoryRequest); and
   2. Receive a response to a request for a medication history (RxHistoryResponse); or
   3. Receive a Status message (Status) in response to a request for a medication history (RxHistoryRequest) and receive a response to a request for a medication history (RxHistoryResponse).

Complete the following steps using the NCPDP SCRIPT Standard Version 2023011.

1. The health IT developer completes the electronic prior authorization transactions (PAInitiationRequest, PAInitiationResponse, PARequest, PAResponse, PAAppealRequest, PAAppealResponse, PACancelRequest, PACancelResponse, PANotification) in accordance with (b)(3)(ii)(A)(3)(x).

1. The health IT developer enables a user to exchange race and ethnicity information when performing the following prescription-related electronic transactions, if using the standard in § 170.205(b)(2):
   1. Receive fill status notifications (RxFill).
   2. Request and respond to change prescriptions (RxChangeRequest, RxChangeResponse).
   3. Request to cancel prescriptions (CancelRx).
   4. Request and respond to renew prescriptions (RxRenewalRequest, RxRenewalResponse). 

1. The tester verifies the Health IT Module enables a user to exchange race and ethnicity information when performing the following transactions:
   1. Receive fill status notifications (RxFill).
   2. Request and respond to change prescriptions (RxChangeRequest, RxChangeResponse).
   3. Request to cancel prescriptions (CancelRx).
   4. Request and respond to renew prescriptions (RxRenewalRequest, RxRenewalResponse). 

Complete the following steps using the NCPDP SCRIPT Standard Version 2017071.

1. The Health IT Module is able to transmit and receive the reason for the prescription using the <Diagnosis><Primary> or <Secondary> diagnosis elements  for the following transactions in accordance with (b)(3)(ii)(C)(1):
   1. Create new prescriptions (NewRx);
   2. Request and respond to change prescriptions (RxChangeRequest, RxChangeResponse);
   3. Request to cancel prescriptions (CancelRx);
   4. Request and respond to renew prescriptions (RxRenewalRequest, RxRenewalResponse); and
   5. Receive fill status notifications (RxFill); 

Complete the following steps using the NCPDP SCRIPT Standard Version 2023011.

1. The Health IT Module is able to transmit and receive the diagnosis or diagnoses that are the reason for the prescription for the following transactions in accordance with (b)(3)(ii)(C)(1):
   1. Create new prescriptions (NewRx);
   2. Request and respond to change prescriptions (RxChangeRequest, RxChangeResponse);
   3. Request to cancel prescriptions (CancelRx);
   4. Request and respond to renew prescriptions (RxRenewalRequest, RxRenewalResponse); and
   5. Receive fill status notifications (RxFill)

Complete the following steps using the NCPDP SCRIPT Standard Version 2017071.

1. The tester verifies the Health IT Module sends and receives the reason for the prescription using the <Diagnosis><Primary> or <Secondary> diagnosis elements for all transactions, using the test data specified with the selected test case via the test tool:
   1. Create new prescriptions (NewRx);
   2. Request and respond to change prescriptions (RxChangeRequest, RxChangeResponse);
   3. Request to cancel prescriptions (CancelRx);
   4. Request and respond to renew prescriptions (RxRenewalRequest, RxRenewalResponse); and
   5. Receive fill status notifications (RxFill)

Complete the following steps using the NCPDP SCRIPT Standard Version 2023011.

1. The tester verifies the Health IT Module sends and receives the diagnosis or diagnoses that are the reason for the prescription for all transactions, using the test data specified with the selected test case via the test tool:
   1. Create new prescriptions (NewRx);
   2. Request and respond to change prescriptions (RxChangeRequest, RxChangeResponse);
   3. Request to cancel prescriptions (CancelRx);
   4. Request and respond to renew prescriptions (RxRenewalRequest, RxRenewalResponse); and
   5. Receive fill status notifications (RxFill)

1. The Health IT Module is able to receive and transmit the diagnosis or diagnoses that are the reason for prescription for the electronic prior authorization transactions (PAInitiationRequest, PAInitiationResponse, PARequest, PAResponse, PAAppealRequest, PAAppealResponse, PACancelRequest, PACancelResponse, PANotification).

1. The tester verifies the Health IT Module receives and transmits the diagnosis or diagnoses that are the reason for prescription for the electronic prior authorization transactions (PAInitiationRequest, PAInitiationResponse, PARequest, PAResponse, PAAppealRequest, PAAppealResponse, PACancelRequest, PACancelResponse, PANotification).

1. The Health IT Module is able to prescribe all oral liquid medications in only the metric standard units of milliliter (mL) (i.e., not cubic centimeter (cc) or teaspoon) in accordance with (b)(3)(ii)(E).
2. Negative Testing: The health IT developer attempts to prescribe an oral liquid medication using non-metric standard units.

1. The Health IT Module is able to prescribe all oral liquid medications in only the metric standard units of milliliter (mL) (i.e., not cubic centimeter (cc) or teaspoon) in accordance with (b)(3)(ii)(E).
2. Negative Testing: The health IT developer attempts to prescribe an oral liquid medication using non-metric standard units.

1. The tester verifies the Health IT Module limits the ability to prescribe all oral liquid medications in metric standard units of milliliter (mL).
2. Negative Testing: The tester verifies through visual inspection of the System Under Test that the Health IT Module does not have the ability to prescribe oral liquid medications using non-metric standard units (i.e., cubic centimeter (cc), teaspoon).

1. The tester verifies the Health IT Module limits the ability to prescribe all oral liquid medications in metric standard units of milliliter (mL).
2. Negative Testing: The tester verifies through visual inspection of the System Under Test that the Health IT Module does not have the ability to prescribe oral liquid medications using non-metric standard units (i.e., cubic centimeter (cc), teaspoon).

1. The Health IT Module inserts leading zeroes before the decimal point for all amounts less than one when a prescriber prescribes medication in accordance with (b)(3)(ii)(F).
2. The Health IT Module does not allow trailing zeroes after a decimal point when a prescriber prescribes medication.

1. The Health IT Module inserts leading zeroes before the decimal point for all amounts less than one when a prescriber prescribes medication in accordance with (b)(3)(ii)(F).
2. The Health IT Module does not allow trailing zeroes after a decimal point when a prescriber prescribes medication.

1. The tester verifies through visual inspection of the System Under Test that leading zeroes are inserted before the decimal point for all amounts less than one when a prescriber prescribes medication.
2. The tester verifies through visual inspection of the System Under Test that there are no trailing zeroes after a decimal point when a prescriber prescribes medication.

1. The Health IT Module inserts leading zeroes before the decimal point for all amounts less than one when a prescriber prescribes medication in accordance with (b)(3)(ii)(F).
2. The Health IT Module does not allow trailing zeroes after a decimal point when a prescriber prescribes medication.