|Costs and Limitations|
|Description of Capability||HIEBus includes support for provider and patient portals which are populated via inbound interfaces for lab results as well as other clinical data from a variety of upstream systems, and can include Direct messaging functionality for transitions of care and secure messaging; outbound interfaces supported include transmission of lab results to ambulatory providers as well as transmission to public health agencies for immunization registries or syndromic surveillance.|
|Types of Costs or Fees||Fees include a one-time software license fee, an annual maintenance fee (which includes support and upgrades), and integration fees.
The base license and annual maintenance fees are based upon the scope of the organization’s implementation (for example, provider portal only vs provider portal plus patient portal). If an organization chooses to expand their HIEBus implementation to add additional functionality at a future point (such as adding a patient portal), additional license fee will apply. As an organization’s volume grows, the annual maintenance fee will increase accordingly.
Integration fees are a one-time fee for each distinct integration. An integration can include an inbound HL7 interface, an inbound direct polling driver, an outbound interface to an ambulatory provider, an outbound interface to a public health agency, a PIX/XDS connection for transitions of care, or a connection to an external HISP for Direct messaging. The integration fees are based upon the complexity of the integration and are quoted in advance.
|Contractual Limitations||A signed contract is required. Software is licensed from CareEvolution. CE staff provide installation and ongoing support services. Software is hosted at the healthcare organization’s data center or at a third-party hosting facility. Typically the customer is responsible for managing the core server infrastructure of the software: servers, network, storage,and backups.|
|Technical or Practical Limitations||Integration with a third-party HISP is dependent upon that HISP being compliant with the Direct standards. The customer organization is responsible for establishing all required contractual agreements with the third- party organization for establishing the necessary trust relationship.|
Real World Testing
Under the ONC Health IT Certification Program, health IT developers are required to conduct “Real World Testing” of their certified health IT systems. See CareEvolution’s Real World Testing Plan for details.