Capability
Application Access – All Data Request
Description of Capability
- This functionality enables a patient to connect with 3rd party applications using APIs to request data from their provider’s EHR application.
Cost and Fees
Types of costs or fees that a user may be required to pay to purchase, license, implement, maintain, upgrade, use, or otherwise enable and support the use of the implementation or use of the capability -OR- in connection with the data generated in the course using the capability.
Cost and Fees:
Clients are required to subscribe to a Monthly Provider License of Freedom | PM | EHR | ERX in order to possess the 2015 certified EHR technology capabilities. Provider licenses are charged on a per provider basis for (Full-Time / Part-Time) providers. Use of the following relied upon 3rd Party services is included in the monthly provider license subscription:
- DrFirst Rcopia
- EBSCO Patient Education Reference Center (PERC)
- EBSCO Dynamed
- IMO Procedure, Problem
- Medline Plus
- EMR Direct
Monthly Fee:
- Monthly Provider License Fee (Full-Time / Part-Time)
One-Time Implementation & Setup Fee:
- API Setup & Configuration Fee
Annual Maintenance Fee:
- Included with Monthly Provider License Fee
Additional Third-Party Application(s) Cost:
- Fees associated with the use or implementation of the Interoperability Engine 2017 Open API applications with 3rd party applications whether patient or provider related is outside the scope of the CCC’s Software License Agreement.
- Use of CCC’s programming services related to the integration or support of any third-party developer(s) or user(s) may result in additional hourly or one-time fees.
- In the event, third-party developer(s) or user(s) cause excessive use of system resources, additional hardware, network, or communication fees may apply, in order to support third-party developer(s) or user(s).
- If third-party developer(s) or user(s) require additional data capture or extended data storage, additional hardware may be required to accommodate the needs of third-party developer(s) or user(s).
Contractual Limitations
Limitations of a contractual nature (including developer policies and other business practices) that a user may encounter in the implementation or use of the capability -OR- in the connection with the data generated in the course of using the capability.
Contractual Limitations:
Developer(s) and/or User(s) who would like access to patient health information through the Interoperability Engine 2017 Open API need to agree to the Terms of Use and License Agreement associated with establishing Open API access.
Technical or Practical Limitations
Limitations of a technical or practical nature that a user may encounter that could prevent or impair the successful implementation, configuration, maintenance, support, or use of the capability -OR- prevent or limit the use, exchange, or portability of any data generated in the course of using the capability.
Technical Limitations:
- None
Practical Limitations:
This certified EHR interacts with EMR Direct’s Interoperability Engine 2017 Open API which was used during certification as relied-upon software.