Our phiMail® Server software has been certified as a 2014 Edition (h)(1) module for Direct Transport, so our HISP services can be used with any EHR System certified under the 2014 or 2014R2 criteria for Transitions of Care or Patient View, Download, Transmit for meaningful use.

Certification Details for phiMail Server:

This Health IT Module is 2014 Edition ONC HIT Certification compliant and has been certified by an ONC-ACB in accordance with the applicable certification criteria adopted by the Secretary of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services or guarantee the receipt of incentive payments.

Costs and Limitations: Use and support of this certified product version to send/receive Direct messages to/from other Direct enabled endpoints may require one-time setup costs, annual subscription fees based on number of providers, beds and/or number of Direct addresses, hourly technical support fees, and/or volume-based transaction or storage fees based on number and/or size of messages, as determined by the service plan type purchased. This certified product version includes bundled Health Information Service Provider (HISP), Certificate Authority (CA), and Registration Authority (RA) services. A license agreement is required to use this product. This product can be integrated with other ONC certified systems and the availability and implementation of specific product features will be at the discretion of the integrator. Support for integration with other systems may require additional one-time setup costs, hourly technical support fees, and/or ongoing maintenance fees. Maximum message and/or attachment size is based on the service plan type purchased. Our customers select their own trust networks for sending and/or receiving Direct messages by submitting a signed request. As of 4/7/16, we have trust relationships in place with numerous third party HISPs, including all DirectTrust Accredited Network participating HISPs, Microsoft HealthVault, and the Massachusetts Health Information HIway. Each trust network may impose its own restrictions and/or limitations upon participants, including eligibility requirements. To successfully send to and/or receive from a counter party endpoint, Direct exchange specifications may require the active cooperation of that counter party's HISP and/or Health IT vendor. Any limitations or restrictions imposed by the counter party and/or their vendor(s), such as implementation of trust policies that restrict inbound and/or outbound messages, non-conformance with relevant technical requirements, and/or payload constraints, may negatively impact the ability to successfully exchange Direct messages with that counter party. Establishing connectivity with a third party HISP with whom we do not have an existing trust relationship may require hourly technical support fees and/or other one time setup fees, and may not always be possible. Customers are responsible for any interconnection fees or other fees charged by third party HISPs and/or trust networks.