Cost and Limitations Disclosure for ONC Heath IT Certification Program
|Developer||E-Z BIS, Inc.|
|Date product certified||May 28, 2019|
|Product version||E-Z BIS Office version 12.0
[Other 2015-Edition certified versions]
[2014-Edition certified versions]
|Unique certification number||15.04.04.1386.EZBi.12.01.1.190528
|Certification criteria to which the product has been certified||170.315(a)(1-14)
170.315(b)(1, 2, 6)
|CQMs to which the product has been certified||CMS68v7
|Additional software certified product relied upon to demonstrate its compliance with certification criteria||phiMail Server|
This certified EHR is 2015-Edition 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.
Cost and Limitations
This certified product-version requires additional costs, contractual obligations and technical and practical limitations as described below:
EZBIS offers both a standard Electronic Health Records system that does not offer the capabilities needed to meet the Promoting Interoperability (PI) objectives of the Merit-based Incentive Program (MIPS), and an add-on “Meaningful Use Option” (MUO) that supplements the standard EHR with capabilities for needed to meet the PI objectives of MIPS. The EZBIS Electronic Health Records system with the added MUO is the electronic health record technology that has been tested and certified by the ONC-ACB. EZBIS charges a one-time fee for the MUO and a recurring monthly fee per provider who is participating in MIPS. EZBIS licensees are required to sign an agreement when purchasing the MUO, which specifies these fees. The term of the agreement is for the duration of the providers’ participation in the Merit-based Incentive Program. EZBIS also requires that licensees participating in MIPS purchase and maintain an annual service agreement subscription so as to receive necessary updates and assistance.
The one-time and recurring fees cover all features and capabilities which are not included in the standard EZBIS EHR for the specific purpose of meeting the objectives of MIPS including, but not limited to; Provide Patient Access, Send a Summary of Care, Request/Accept Summary of Care, Patient Specific Education, View, Download or Transmit (VDT), Secure Messaging, Patient-Generated Health Data, and Clinical Information Reconciliation.
The Promoting Interoperability (PI) objectives of MIPS cannot be met with the standard EZBIS EHR. PI objectives of MIPS can only be achieved with the add-on purchase of the EZBIS Meaningful Use Option. EZBIS licensees are required to maintain annual service agreements and upon expiration, many functionalities required for achieving Meaningful Use are disabled. The certified EZBIS EHR product requires an internet connection to perform many required tasks and for licensing verification.
The certified EZBIS EHR utilizes EMR Direct phiMail for the facilitation of Direct messaging. By relying on EMR Direct phiMail for Direct messaging, providers using the certified EZBIS EHR are limited to exchanging Direct messages with Direct addresses that are associated with the trust communities with which EMR Direct participates. 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. The certified EZBIS EHR also relies upon EMR Direct’s Interoperability Engine to facilitate Application Access Patient Selection, Data Category Request and All Data Request for the 2015 Edition certification criteria.
The certified EZBIS product is dependent upon a third party for some capabilities. This third party is EMR Direct and is utilized to facilitate Direct Messaging and Application Access. EZBIS licensees may not choose alternatives to this third party and are not required to enter into separate agreements with the third party.