Learn About Our FHIR Terminologies
Explore concise guidelines for FHIR API usage and compliance.
1. Accepting the Terms
These Terms of Use (“Terms”) govern your access to and use of the eMedPractice FHIR APIs, documentation, software, services, etc. By accessing or using the eMedPractice FHIR APIs, you agree to be bound by these Terms. The API provided by eMedPractice is allow to development of health care consumer-facing (i.e., patient or a patient’s authorized representative) applications only. Any application developed by the developer also must compliance with ONC Certification Criteria. Developer represent and warrant that you are at least 18 years of age and that you possess the legal right and ability to agree to these Terms and to use the eMedPractice FHIR APIs in accordance with these Terms.
2. Modification of Terms
eMedPractice reserves the right to modify these terms at any time in its sole discretion and without notice. Any changes made to this agreement will considered as effective from the time of publish to public. These updated terms will be applicable to the developer who are continued to use eMedPractice FHIR API.
3. Developer Account
In order to establish a Developer Account, you may be required to provide contact information, organizational details, developers purpose of accessing API, billing details, and other information, and you agree to keep the information updated at all times.
4. Transparency
Developer must provide the license terms and conditions to use the application. Also, developers must keep the pricing and documents clear and reliable.
5. Safety and Security
Your application must be designed and developed by adopting any of Federal equivalent standard QMS, usability and Safety enhanced design stands. If your app storing the data on end-user device data must be fully encrypted. If your app is transmitting to any of patient information other third party, data must be shared on a secure encrypted transportation channel. Your app must maintain all user activity and share the info with eMedPractice on Demand. You should not share secure client ID.
6. Privacy
Your application must not hide or share any of PHI information without patient knowledge. Your app must comply with all HIPPA standards. Your app must be sharing or storing any PHI you must clearly describe the usage off that data to patient as well as eMedPractice . You CAN NOT use any of patient personal information obtained by using eMedPractice FHIR API for any other purposes until unless the patient approval.
7. Responsibilities
Developer is solely responsible for Developer’s use of and access to the API. eMedPractice has no responsibility or control over any development performed by Developer in conjunction with the API, including all acts or omissions of anyone permitted by Developer to use and access the API. Developer acknowledges and agrees that it accepts all risks associated with the use of and access to the API, including any reliance on the accuracy, completeness, or usefulness of the API. Developer app must need to be reviewed by eMedPractice Tech review team before publishing it to consumers.
8. Patient Access
Developers are exclusively accountable for determining and safeguarding patient independent access to their App for the purposes of Meaningful Use (MU) and Merit-based Incentive Payment System (MIPS) reporting.
9. Termination, Suspension, and Limitation of Use
Developer is not allowed to over load the sever, if any of such activities found eMedPractice reserve the rights to disable your account right away. eMedPractice reserves the right in its sole decision at any time to terminate or suspend Developer access to the API or to disable Developer credentials. Upon such termination or suspension, Developer will no longer have access to the API, and all of Developer’s use rights therein will terminate. Any rights and obligations under the Agreement which by their nature should continue and will remain in full effect after termination or expiration of the Agreement. eMedPractice may also limit the use of the access to or use of API, including but not limited to the number of transactions or data flow permitted, in its discretion.
10. Open Source
Developer warrant that their Apps do not contain any open source software licensed under terms that require the user to make the user’s modifications to the open source freely available in source code form, or any software that the user “combines” with the open source software freely available in source code form.
11. Warranties and Liability
Developers using the eMedPractice FHIR API use at their own risk. API will be provided to developers AS IS without any warranties, eMedPractice is not responsible for any Faults. To the extent permissible by law, neither eMedPractice nor its affiliates nor their respective suppliers or licensors shall be liable under any contract, negligence, strict liability, or other legal or equitable theory for any direct, indirect, exemplary, special, incidental, or consequential damages, including but not limited to loss of profits or other economic loss of developer or any third party, even if informed of the possibility of such damages. To the extent governing law does not permit such limitations to be applied in full, eMedPractice liability shall be limited in all respects to the greatest extent permissible by law.
