Capability
Authentication, Access Control, Authorization
Description of Capability
- EHR verifies against a unique identifier(s) (e.g., username and password) that a user seeking access to electronic health information is the one claimed; and
- EHR establishes the type of security access to electronic health information a user is permitted based on the unique identifier(s) provided above, and the actions the user is permitted to perform within the technology.
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:
- None
Annual Maintenance Fee:
- Included with Monthly Provider License Fee
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:
Client Security Administrators are required complete and submit the following forms in order to assign appropriate end user security access privileges:
- New User Request Form
- Modify Existing User Change Form
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:
- None