Difference between revisions of "DirectTrust Activation"
(→Testing) |
(→Testing) |
||
| Line 10: | Line 10: | ||
== Testing == | == Testing == | ||
In order to support testing and development, we have enabled access to two QA-only features. The first feature is a set of test data that will allow you to step through the DirectTrust activation process and obtain realistic results. The second feature is an API call that will allow you to directly toggle the Vetted value for any of your practices/sites. By combining these two features, you should be able to test your workflow end-to-end in a production-similar manner. | In order to support testing and development, we have enabled access to two QA-only features. The first feature is a set of test data that will allow you to step through the DirectTrust activation process and obtain realistic results. The second feature is an API call that will allow you to directly toggle the Vetted value for any of your practices/sites. By combining these two features, you should be able to test your workflow end-to-end in a production-similar manner. | ||
| + | |||
| + | |||
[[DirectTrust Activation Test Cases]] | [[DirectTrust Activation Test Cases]] | ||
| − | [[API_Method_PracticeVettedToggle|PracticeVettedToggle]] | + | [[https://updoxqa.com/iodox/updox-iodox#PracticeVettedToggle|Interactive API page for the PracticeUpdate API method]] |
| + | |||
| + | [[API_Method_PracticeVettedToggle|Samples and examples using the PracticeVettedToggle API method]] | ||
Revision as of 11:24, 19 December 2013
Description
In order for a practice/site to become part of the DirectTrust trust bundle, at least one user per practice/site must successfully go through vetting process as defined by DirectTrust.org. This involves three steps: 1) a computerized telephone call that provides an validation code to be entered into a webpage, 2) validation of supplied demographic information, and 3) validation of supplied credit card information.
Your DirectTrust activation page can be found in QA at:
https://updoxqa.com/activate/vendorId?accountId=accountId&userId=userId
where vendorId is your the vendorId provided as your vendor credentials, accountId is the id you assigned to the relevant practice/site, and userId is the userId you wish to be vetted from within that practice/site.
Testing
In order to support testing and development, we have enabled access to two QA-only features. The first feature is a set of test data that will allow you to step through the DirectTrust activation process and obtain realistic results. The second feature is an API call that will allow you to directly toggle the Vetted value for any of your practices/sites. By combining these two features, you should be able to test your workflow end-to-end in a production-similar manner.
DirectTrust Activation Test Cases
[API page for the PracticeUpdate API method]
Samples and examples using the PracticeVettedToggle API method
