API Platform Policy
Terms of Service
MacPractice provides application program interfaces (APIs) for
its customers and partners to allow them to create their own tools to
access MacPractice's PHI Patient Portal information. By using
MacPractice APIs you agree to this policy.
In this policy, the term 'user' is anyone or any organization and its
employees or representatives that access our APIs, including sole
proprietors. This policy along with any documentation MacPractice has
published for specific APIs are referred to as the 'terms' herein. The
word 'they' may be used as the singular gender neutral term in place
of 'he or she'. The words 'application', 'app', or 'program' are
interchangeable and refer to any software designed to perform a group
of coordinated functions, tasks, or activities on a computational
device, such as on a computer, phone, etc.
We reserve the right to change or rescind this policy at any time
without notice or obligation to the user other than updating this
website, so please check it regularly. Your continued use of an API
after a policy change constitutes the user is accepting the changes.
A. General Terms
Don't confuse deceive, defraud, mislead, or harass anyone.
Be transparent about your identity and your program's identity.
B. User Identity
During MacPractice's API Beta period, users must apply for and be
granted approval to use the APIs via the MacPractice API Request
Application process before beginning development on an application
that makes use of the APIs.
The user shall not bypass any authentication process documented for
The individual accepting these terms affirms that they are
authorized to act on behalf of their organization.
C. API Limitations
MacPractice may set and enforce limits on use of its APIs. The user
shall follow, and shall not try to circumvent, any limits documented
within an API.
D. Legal Compliance
The user shall comply with all applicable privacy laws and
regulations, laws regarding import or export of data, and all other
The user shall require its end users to comply with, and shall not
knowingly allow them to violate, the terms and any applicable law or
If the user will use the API to create a service for other
organizations, it shall first provide to the other organizations a
information the user will collect and how it will use and share that
F. Unauthorized Use
When using an API, the user shall not:
Sublicense the API for use by a third party or create an application
that functions substantially the same as the API for use by a third
Introduce to MacPractice's products and services any viruses, worms,
defects, Trojan horses, malware or other destructive items;
Reverse engineer or attempt to extract any source code from the API
or related software;
Defame, abuse, harass, stalk, or threaten any person;
Use the API contrary to any applicable documentation; or
Use the API in a way that violates another's intellectual property
MacPractice may monitor use of the APIs to ensure quality and
security, to improve MacPractice products and services, and to
verify the user's compliance with the terms. This monitoring may
include MacPractice accessing and using any application the user has
created to access the APIs. The user shall not interfere with this
monitoring, and MacPractice may use any technical means to overcome
MacPractice may suspend a user's access to the APIs if it reasonably
believes the user is in violation of the terms.
MacPractice does not acquire ownership in any applications the user
creates to use the APIs, and the user does not acquire any ownership
rights to the APIs or any content accessed through them.
If the user provides feedback or suggestions about the APIs,
MacPractice may use that information without obligation to the user.
I. Brand Features
The terms do not grant either party any right, title, or interest in
or to the other party's trade names, trademarks, service marks,
logos, or domain names (collectively "brand features"), except as
stated in section I(2).
The user shall display any attributions required by MacPractice as
stated in the API documentation.
MacPractice provides the APIs "as is," without any guarantee as to
their reliability, availability, or ability to meet the user's
K. Limit of Liability
MacPractice will not be liable for any damages arising from any
failure of the APIs.
The user shall indemnify MacPractice against any claims (1) arising
from the user's negligence or violation of these terms or (2)
arising out of the user's use of, or inability to use, an API.
MacPractice shall send notices under this agreement to the email
address the user provides during registration. The user shall keep
this email address current.
The user shall send notices under this agreement to MacPractice at
N. Entire Agreement
These terms of service constitute the entire agreement between
MacPractice and the Customer as to their subject matter.
O. Binding Arbitration
If the parties are unable to resolve any disputes arising from this
agreement by direct negotiation, they shall resolve the dispute
through binding arbitration in Lincoln, NE before a single
arbitrator from the American Arbitration Association in accordance
with its Commercial Arbitration Rules. The parties hereby waive any
right to a jury trial in connection with any claim arising from this
P. Attorneys' Fees
If any arbitration or legal proceeding is validly instituted to
enforce the terms of this agreement, the prevailing party may
recover its attorneys' fees and other costs.
Q. Governing Law; Personal Jurisdiction; Venue
This agreement is governed by the laws of the State of Nebraska. If
any litigation is validly instituted in connection with this
agreement, the parties hereby consent to the exclusive personal
jurisdiction of the courts in Nebraska and waive any objection as to
venue or inconvenient forum.
R. Waiver of Rights
Failure to enforce a right or provision under this agreement does
not constitute a waiver of that right or provision.
If any part of this agreement is declared unenforceable by a court,
all other parts will remain enforceable. By submitting a request to
access or by accessing the APIs, the user agrees to these terms.