General Direct Messaging Certification Testing

EMR Direct provides additional support to customers preparing to certify their health IT using our software. We request that you let us know of an upcoming certification test and the name of your test lab so that we may stand by to assist you with any questions or concerns you might have. To prepare for your test, registered EMR Direct developers should go through the 2015 Edition Cures Update ETT and DCDT Testing with phiMail documentation at least once, completing the tests as documented and notifying us of any items you are unable to complete or have questions about. This guide was designed to prepare partners for testing and to help identify items that have changed since previous editions. On the day of proctored testing, simply follow the instructions from the proctor to go through the test procedure in the order they choose. The proctor may ask you for information you’ll find in the testing guide or in this FAQ, and will likely take screenshots of test results and ask you to forward email alerts we send to the developer or test tool report emails to them. For example, the proctor may ask for the version of the phiMail software you are using for Direct messaging services; the current version of the phiMail component of EMR Direct Interoperability Engine is version 2023. If you’re not sure on how to answer any of the proctor’s questions, please call or email us for assistance. Complimentary telephone-based support is available on the day of proctored certification testing.

EMR Direct developers will receive email alerts from EMR Direct that include exceptions from the phiMail API that are required to successfully certify when relying on EMR Direct for b.1, e.1, or h.1. Please remember to contact us at support@emrdirect.com to configure an alert email address of your choice, with your test address. The notifications you receive from EMR Direct at this email address are above and beyond the test tool validation reports which require separate registration at the test tool site.

Please note that the b.1-only address ending in “-edge2015@directtest.interopengine.com” must be configured into a profile at the test tool website according to the testing guide referenced above for much of the testing you will perform using that address. This is the ONLY address from EMR Direct that will work for b.1 testing and it cannot be used in h.1 testing.

When preparing to test the negative test cases in 2015 Edition Cures Update criteria, developers will want to confirm that your phiMail software integration displays the error messages returned by the phiMail API. For example, if no Direct certificate is found when composing a message to a regular email address, an appropriate error should be displayed in the health IT's user interface. Similarly, the implementer's user interface should give the end user an indication of any error returned by the phiMail API. Please see the 2015 Edition Cures Update ETT and DCDT Testing with phiMail document, available to EMR Direct Developers, for additional details.

Once you have established a test date with a lab, please confirm your test date(s) with us so that we may stand by to assist you on the day of your test, if needed, and configure your preferred incoming direct message notification email required to show server log snippets the proctor will need to review.


Did this article answer your question? If not, please contact us.