FHIR API Documentation for PacEHR

FHIR Server 1.0.0 for Cures Act Update

This server accepts requests in format(s): application/fhir+json

Terms of Service

Endpoints for this server are documented at the links below, which can also be reached from the web at https://thesnfist.com/cures-update/

• FHIR Resource: AllergyIntolerance
• USCD Data elements (USCDV1)
  • Substance (Drug Class)
  • Substance (Medication)
  • Reaction

  Endpoint: AllergyIntolerance

/id: id

Retrieve an AllergyIntolerance resource by its id.

Parameters:

Example

/AllergyIntolerance/1010Retrieve the AllergyIntolerance resource with id 1010.

search: patient, date

Search AllergyIntolerance resources using query string parameters.

Parameters:

Example

/AllergyIntolerance/?patient=722&date=lt2012–01–04Retrieve list of AllergyIntolerance resources added before January 4th, 2012 for the specified patient.

HL7 Documentation

• FHIR Resource: CarePlan
• USCD Data elements (USCDV1)
  • Assessment and Plan of Treatment in Encounters

Endpoint: CarePlan

/id: id

Retrieve a CarePlan by its id.

Parameters:

Example

/CarePlan/1001Retrieve the Care Plan with id 1001.

search: patient , date , Status

Search CarePlans using query string parameters.

Parameters:

Example

/CarePlan/?patient=722Retrieve Care Plan list for the specified patient

HL7 Documentation

• FHIR Resource: CareTeam
• USCD Data elements (USCDV1)
  • Care Team
  • (USCDI v2) Care Team Member Name
  • (USCDI v2) Care Team Member Identifier
  • (USCDI v2) Care Team Member Role
  • (USCDI v2) Care Team Member Location
  • (USCDI v2) Care Team Member Telecom

Endpoint: CareTeam

/id: id

Retrieve a CareTeam resource by its id.

Parameters:

Example

/CareTeam/101Retrieve the Care Team resource with id 101.

search: patient, date, Status

Search CareTeam resources using query string parameters.

Parameters:

Example

/CareTeam/?patient=722&date=gt2012–01–06Retrieve list of Care Teams in effect after January 6th, 2012 for the specified patient.

HL7 Documentation

• FHIR Resource: Condition
• USCD Data elements (USCDV1)
  • Health Concern
  • Problems

Endpoint: Condition

/id: id

Retrieve an Condition resource by its id.

Parameters:

Examples

/Condition/I505Retrieve the Condition resource with id I505./Condition/N5000Retrieve the Condition resource with id N5000.

search: patient

Search Condition resources using query string parameters.

Parameters:

Example

/Condition/?patient=722&asserted–date=lt2012–01–13Retrieve list of Condition resources documented before January 13th, 2012 for the specified patient.

HL7 Documentation

• FHIR Resource: Device
• USCD Data elements (USCDV1)
  • Unique Device Identifier(s) for Patients’ Implantable Device(s)

Endpoint: Device

/id: id

Retrieve a Device resource by its id.

Parameters:

Example

/Device/11Retrieve the device with id 11.

search: patient

Search Devices query string parameters.

Parameters:

Example

/Device/?patient=722Retrieve Device list for the specified patient

HL7 Documentation

• FHIR Resource: DocumentReference, DiagnosticReport
• USCD Data elements (USCDV1)
  • Consultation Note
  • Discharge Summary Note
  • History & Physical
  • Procedure Note
  • Progress Note
  • Imaging Narrative
  • Laboratory Report Narrative
  • Pathology Report Narrative

Endpoint: DocumentReference

/id: id

Retrieve a DocumentReference (CCDA) resource by its id. The resource includes the encoded CCDA in the content.attachment field if it is ready.

Parameters:

Examples

/DocumentReference/N10999Retrieve the CCDA resource with id N10999./DocumentReference/L20010Retrieve the CCDA resource with id L20010./DocumentReference/S11Retrieve the CCDA resource with id S11.

search: patient, period, status

Search DocumentReference (CCDA) resources using query string parameters.

Parameters:

Examples

/DocumentReference/?patient=722Retrieve list of DocumentReference resources for visit 123456 for the specified patient./DocumentReference/?patient=722&period=gt2012–01–31&status=currentCreate a CCDA for the period after January 31st, 2012 (to present) for the specified patient.  This endpoint returns an ID which can be

HL7 Documentation

• FHIR Resource: Encounter, Condition Encounter Diagnosis
• USCD Data elements (USCDV2)
• Encounter Type
• Encounter Diagnosis
• Encounter Time
• Encounter Location
• Encounter Disposition

Endpoint: Encounter

/ search: patient, Id

Retrieve an Encounter by its id.

Parameters:

Example

/Encounter/100001Retrieve the Encounter resource with id 100001.

HL7 Documentation

• FHIR Resource: Goal
• USCD Data elements (USCDV1)
• Goals

Endpoint: Goal

/id: id

Retrieve a Goal resource by its id.

Parameters:

Example

/Goal/10123Retrieve the Goal resource with id 10123.

search: patient, Id

Search Goals using query string parameters.

Parameters:

Example

/Goal/?patient=722&target–date=ge2012–01–07Retrieve list of Care Teams in effect for the specified patient with target date on or after January 7th, 2012.

HL7 Documentation

• FHIR Resource: Immunization
• USCD Data elements (USCDV1)
• Immunization

Endpoint: Immunization

/id: id

Retrieve an Immunization resource by its id.

Parameters:

Example

/Immunization/500Retrieve the Immunization resource with id 500.

search: patient, date

Search Immunization resources using query string parameters.

Parameters:

Example

/Immunization/?patient=722&date=lt2012–01–11Retrieve list of Immunization resources added before January 11th, 2012 for the specified patient.

HL7 Documentation

• FHIR Resource: Location
• USCD Data elements (USCDV1)
• Facility
• NPI
• Status
• Address
• Telecom

Endpoint: Location ?

/id: id

Retrieve a Location by its id.

Parameters:

Example

/Location/20Retrieve the Location resource with id 20.

HL7 Documentation

• FHIR Resource: Medication, MedicationRequest
• USCD Data elements (USCDV1)
  • Medications
• FHIR Resource: AllergyIntolerance
• USCD Data elements (USCDV1)
  • Medications Allergies

Endpoint: MedicationRequest

/id: id

Retrieve a MedicationRequest resource by patient

Parameters:

Example

/MedicationRequest?Patient=722Retrieve the MedicationRequest resource with Patient=722

HL7 Documentation

Endpoint: Medication

/id: id

Retrieve a Medication resource by its id.

Parameters:

Example

/Medication/3003Retrieve the Medication resource with id 3003.

HL7 Documentation

• FHIR Resource: Observation, DiagnosticReport
• USCD Data elements (USCDV1)
  • Laboratory Tests
  • Laboratory Values/Results
  • Smoking Status
  • Diastolic Blood Pressure
  • Systolic Blood Pressure
  • Body Height
  • Body Weight
  • Heart Rate
  • Respiratory Rate
  • Body Temperature
  • Pulse Oximetry
  • Inhaled Oxygen Concentration
  • BMI Percentile (2-20 years old)
  • Weight-for-Length Percentile (Birth-36 months)
  • Occipital-frontal Head Circumference Percentile (Birth-36 months)

Endpoint: Observation

/id: id

Retrieve a Observation resource by its id.

Parameters:

Examples

/Observation/N102Retrieve the Observation resource with id N102./Observation/L20002Retrieve the Observation resource with id L20002.

search: patient, date

Search Observation resources using query string parameters.

Parameters:

Example

/Observation/?patient=722&date=2012–01–05Retrieve list of observations from January 5th, 2012 for the specified patient.

HL7 Documentation

• FHIR Resource:name.given
• USCD Data elements (USCDV1)
  • First Name
  • Middle Name

• FHIR Resource:name.family
• USCD Data elements (USCDV1)
  • Last Name

• FHIR Resource:name
• USCD Data elements (USCDV1)
  • Previous Name

• FHIR Resource: Patient.name.suffix
• USCD Data elements (USCDV1)
  • Suffix

• FHIR Resource: US Core Birth Sex Extension
• USCD Data elements (USCDV1)
  • Sex (Assigned at Birth)

• FHIR Resource: US Core Observation Sexual Orientation Profile
• USCD Data elements (USCDV2)
  • Sexual Orientation

• FHIR Resource: US Core Gender Identity Extension
• USCD Data elements (USCDV2)
  • Gender Identity

• FHIR Resource: Patient.birthDate
• USCD Data elements (USCDV1)
  • Date of Birth

• FHIR Resource: US Core Race Extension
• USCD Data elements (USCDV1)
  • Race

• FHIR Resource: US Core Ethnicity Extension
• USCD Data elements (USCDV1)
  • Ethnicity

• FHIR Resource: Patient.communication
• USCD Data elements (USCDV1)
  • Preferred Language

• FHIR Resource: Patient.address
• USCD Data elements (USCDV1)
  • Address

• FHIR Resource: Patient.telecom
• USCD Data elements (USCDV1)
  • Phone Number

Endpoint: Patient

/id: id

Retrieve a Patient resource by its id.

Parameters:

Example

/Patient/722Retrieve the Patient resource with id 722.

/id?versionId: id, versionId

Retrieve a historical version of a Patient resource by its version id.

Parameters:

Example

/Patient/722?versionId=2018–01–02T17:35:19.360Retrieve the Patient resource version id 2018–01–02T17:35:19.360 for the specified patient.

count:

Count Patient resources (internal method).

search: id, identifier, name, family, given, gender, birthdate, deceased, death-date, email, phone, address-city, address-state, address-postalcode, address-country

Search Patient resources using query string parameters.

Parameters:

Example

/Patient/?birthdate=eq2012–01–14&sex=femaleRetrieve list of female patients born on January 14th, 2012

HL7 Documentation

• FHIR Resource: Practitioner
• USCD Data elements (USCDV1)
  • Role
  • Name
  • First Name
  • Last Name
  • DOB
  • NPI
  • Status
  • Address
  • Telecom

Endpoint: Practitioner

/id: id

Retrieve a Practitioner resource by its id.

Parameters:

Examples

/Practitoner/L2562Retrieve the Practitioner resource with id L2562./Practitoner/P40506Retrieve the Practitioner resource with id P40506.

count:

Count Practitioner resources (internal method).

HL7 Documentation

• FHIR Resource: Procedure
• USCD Data elements (USCDV1)
  • Procedures

Endpoint: Procedure

/id: id

Retrieve a Procedure resource by its id.

Parameters:

Example

/Procedure/1010Retrieve the Procedure resource with id 1010.

search: patient

Search Procedure resources using query string parameters.

Parameters:

Example

/Procedure/?patient=722&date=le2012–01–03Retrieve list of Procedures performed on or before January 3rd, 2012 for the specified patient.

HL7 Documentation

API Terms of Service

Last modified: December 23, 2022

Thank you for using Saisystems’ APIs, other developer services, and associated software (collectively, “APIs”). By accessing or using our APIs, you are agreeing to the terms below. If there is a conflict between these terms and additional terms applicable to a given API, the additional terms will control for that conflict. Collectively, we refer to the terms below, any additional terms, terms within the accompanying API documentation, and any applicable policies and guidelines as the “Terms.” You agree to comply with the Terms and that the Terms control your relationship with us. So please read all the Terms carefully. If you use the APIs as an interface to, or in conjunction with other Saisystems’ products or services, then the terms for those other products or services also apply.

Under the Terms, “SSD” means Saisystems Digital LLC, with offices at 5 Research Drive,  Shelton CT.   Unless set forth otherwise in additional terms applicable for a given API. We may refer to “SSD” as “we”, “our”, or “us” in the Terms.

Section 1: Account and Registration

a. Accepting the Terms

You may not use the APIs and may not accept the Terms if (a) you are not of legal age to form a binding contract with SSD, or (b) you are a person barred from using or receiving the APIs under the applicable laws of the United States or other countries including the country in which you are resident or from which you use the APIs.

b. Entity Level Acceptance

If you are using the APIs on behalf of an entity, you represent and warrant that you have authority to bind that entity to the Terms and by accepting the Terms, you are doing so on behalf of that entity (and all references to “you” in the Terms refer to that entity).

c. Registration

In order to access certain APIs you may be required to provide certain information (such as identification or contact details) as part of the registration process for the APIs, or as part of your continued use of the APIs. Any registration information you give to SSD will always be accurate and up to date and you’ll inform us promptly of any updates.

d. Subsidiaries and Affiliates

SSD has subsidiaries and affiliated legal entities around the world. These companies may provide the APIs to you on behalf of SSD and the Terms will also govern your relationship with these companies.

Section 2: Using Our APIs

a. Your End Users

You will require your end users to comply with (and not knowingly enable them to violate) applicable law, regulation, and the Terms.

b. Compliance with Law, Third Party Rights, and Other SSD Terms of Service

You will comply with all applicable law, regulation, and third party rights (including without limitation laws regarding the import or export of data or software, privacy, and local laws). You will not use the APIs to encourage or promote illegal activity or violation of third party rights. You will not violate any other terms of service with SSD (or its affiliates).

c. Permitted Access

You will only access (or attempt to access) an API by the means described in the documentation of that API. If SSD assigns you developer credentials (e.g. client IDs), you must use them with the applicable APIs. You will not misrepresent or mask either your identity or your API Client’s identity when using the APIs or developer accounts.

d. API Limitations

SSD sets and enforces limits on your use of the APIs (e.g. limiting the number of API requests that you may make or the number of users you may serve), in our sole discretion. You agree to, and will not attempt to circumvent, such limitations documented with each API. If you would like to use any API beyond these limits, you must obtain SSD’s express consent (and SSD may decline such request or condition acceptance on your agreement to additional terms and/or charges for that use). To seek such approval, contact the relevant SSD API team for information (e.g. by using the SSD developers console).

e. Open Source Software

Some of the software required by or included in our APIs may be offered under an open source license. Open source software licenses constitute separate written agreements. For certain APIs, open source software is listed in the documentation. To the limited extent the open source software license expressly supersedes the Terms, the open source license instead sets forth your agreement with SSD for the applicable open source software.

f. Communication with SSD

We may send you certain communications in connection with your use of the APIs. Please review the applicable API documentation for information about opting out of certain types of communication.

g. Feedback

If you provide feedback or suggestions about our APIs, then we (and those we allow) may use such information without obligation to you.

h. Non-Exclusivity

The Terms are non-exclusive. You acknowledge that SSD may develop products or services that may compete with the API Clients or any other products or services.

Section 3: Your API Clients

a. API Clients and Monitoring

The APIs are designed to help you enhance your websites and applications (“API Client(s)”). YOU AGREE THAT SSD MAY MONITOR USE OF THE APIS TO ENSURE QUALITY, IMPROVE SSD PRODUCTS AND SERVICES, AND VERIFY YOUR COMPLIANCE WITH THE TERMS. This monitoring may include SSD accessing and using your API Client, for example to identify security issues that could affect SSD or its users. You will not interfere with this monitoring. SSD may use any technical means to overcome such interference. SSD may suspend access to the APIs by you or your API Client without notice if we reasonably believe that you are in violation of the Terms.

b. Security

You will use commercially reasonable efforts to protect user information collected by your API Client, including personally identifiable information (“PII”), from unauthorized access or use and will promptly report to your users any unauthorized access or use of such information to the extent required by applicable law.

c. Ownership

SSD does not acquire ownership in your API Clients, and by using our APIs, you do not acquire ownership of any rights in our APIs or the content that is accessed through our APIs.

d. User Privacy and API Clients

You will comply with all applicable privacy laws and regulations including those applying to PII. You will provide and adhere to a privacy policy for your API Client that clearly and accurately describes to users of your API Client what user information you collect and how you use and share such information (including for advertising) with SSD and third parties.

Section 4: Prohibitions and Confidentiality

a. API Prohibitions

When using the APIs, you may not (or allow those acting on your behalf to):

1. Sublicense an API for use by a third party. Consequently, you will not create an API Client that functions substantially the same as the APIs and offer it for use by third parties.
2. Perform an action with the intent of introducing to SSD products and services any viruses, worms, defects, Trojan horses, malware, or any items of a destructive nature.
3. Defame, abuse, harass, stalk, or threaten others.
4. Interfere with or disrupt the APIs or the servers or networks providing the APIs.
5. Promote or facilitate unlawful online gambling or disruptive commercial messages or advertisements.
6. Reverse engineer or attempt to extract the source code from any API or any related software, except to the extent that this restriction is expressly prohibited by applicable law.
7. Use the APIs for any activities where the use or failure of the APIs could lead to death, personal injury, or environmental damage (such as the operation of nuclear facilities, air traffic control, or life support systems).
8. Use the APIs to process or store any data that is subject to the International Traffic in Arms Regulations maintained by the U.S. Department of State.
9. Remove, obscure, or alter any SSD terms of service or any links to or notices of those terms.

SSD has obligations under the Health Insurance Portability and Accountability Act, as amended (“HIPAA”), and makes every effort to ensure that the APIs satisfy HIPAA requirements. If you are (or become) a “covered entity” or “business associate” as defined in HIPAA, you will not use the APIs for any purpose or in any manner involving transmitting protected health information to SSD unless you have received prior written consent to such use from SSD.

b. Confidential Matters

10. Developer credentials (such as passwords, keys, and client IDs) are intended to be used by you and identify your API Client. You will keep your credentials confidential and make reasonable efforts to prevent and discourage other API Clients from using your credentials. Developer credentials may not be embedded in open source projects.
11. Our communications to you and our APIs may contain SSD confidential information. SSD confidential information includes any materials, communications, and information that are marked confidential or that would normally be considered confidential under the circumstances. If you receive any such information, then you will not disclose it to any third party without SSD’s prior written consent. SSD confidential information does not include information that you independently developed, that was rightfully given to you by a third party without confidentiality obligation, or that becomes public through no fault of your own. You may disclose SSD confidential information when compelled to do so by law if you provide us reasonable prior notice, unless a court orders that we not receive notice.

Section 5: Content

a. Content Accessible Through our APIs

Our APIs contain some third party content (such as text, images, videos, audio, or software). This content is the sole responsibility of the person that makes it available. We may sometimes review content to determine whether it is illegal or violates our policies or the Terms, and we may remove or refuse to display content. Finally, content accessible through our APIs may be subject to intellectual property rights, and, if so, you may not use it unless you are licensed to do so by the owner of that content or are otherwise permitted by law. Your access to the content provided by the API may be restricted, limited, or filtered in accordance with applicable law, regulation, and policy.

b. Submission of Content

Some of our APIs allow the submission of content. SSD does not acquire any ownership of any intellectual property rights in the content that you submit to our APIs through your API Client, except as expressly provided in the Terms. For the sole purpose of enabling SSD to provide, secure, and improve the APIs (and the related service(s)) and only in accordance with the applicable SSD privacy policies, you give SSD a perpetual, irrevocable, worldwide, sublicensable, royalty-free, and non-exclusive license to Use content submitted, posted, or displayed to or from the APIs through your API Client. “Use” means use, host, store, modify, communicate, and publish. Before you submit content to our APIs through your API Client, you will ensure that you have the necessary rights (including the necessary rights from your end users) to grant us the license.

c. Retrieval of content

When a user’s non-public content is obtained through the APIs, you may not expose that content to other users or to third parties without explicit opt-in consent from that user.

d. Prohibitions on Content

Unless expressly permitted by the content owner or by applicable law, you will not, and will not permit your end users or others acting on your behalf to, do the following with content returned from the APIs:

12. Scrape, build databases, or otherwise create permanent copies of such content, or keep cached copies longer than permitted by the cache header;
13. Copy, translate, modify, create a derivative work of, sell, lease, lend, convey, distribute, publicly display, or sublicense to any third party;
14. Misrepresent the source or ownership; or
15. Remove, obscure, or alter any copyright, trademark, or other proprietary rights notices; or falsify or delete any author attributions, legal notices, or other labels of the origin or source of material.

Section 6: Brand Features; Attribution

a. Brand Features

“Brand Features” is defined as the trade names, trademarks, service marks, logos, domain names, and other distinctive brand features of each party. Except where expressly stated, the Terms do not grant either party any right, title, or interest in or to the other party’s Brand Features. All use by you of SSD’s Brand Features (including any goodwill associated therewith) will inure to the benefit of SSD.

b. Attribution

You agree to display any attribution(s) required by SSD as described in the documentation for the API. SSD hereby grants to you a nontransferable, nonsublicenseable, nonexclusive license while the Terms are in effect to display SSD’s Brand Features for the purpose of promoting or advertising that you use the APIs. You must only use the SSD Brand Features in accordance with the Terms and for the purpose of fulfilling your obligations under this Section. In using SSD’s Brand Features, you must follow the SSD Brand Features Use Guidelines. You understand and agree that SSD has the sole discretion to determine whether your attribution(s) and use of SSD’s Brand Features are in accordance with the above requirements and guidelines.

c. Publicity

You will not make any statement regarding your use of an API which suggests partnership with, sponsorship by, or endorsement by SSD without SSD’s prior written approval.

d. Promotional and Marketing Use

In the course of promoting, marketing, or demonstrating the APIs you are using and the associated SSD products, SSD may produce and distribute incidental depictions, including screenshots, video, or other content from your API Client, and may use your company or product name. You grant us all necessary rights for the above purposes.

Section 7: Privacy and Copyright Protection

a. SSD Privacy Policies

By using our APIs, SSD may use submitted information in accordance with our privacy policies.

b. SSD DMCA Policy

We provide information to help copyright holders manage their intellectual property online, but we can’t determine whether something is being used legally or not without their input. We respond to notices of alleged copyright infringement and terminate accounts of repeat infringers according to the process set out in the U.S. Digital Millennium Copyright Act. If you think somebody is violating your copyrights and want to notify us, you can find information about submitting notices and SSD’s policy about responding to notices in our Help Center.

Section 8: Termination

a. Termination

You may stop using our APIs at any time with or without notice. Further, if you want to terminate the Terms, you must provide SSD with prior written notice and upon termination, cease your use of the applicable APIs. SSD reserves the right to terminate the Terms with you or discontinue the APIs or any portion or feature or your access thereto for any reason and at any time without liability or other obligation to you.

b. Your Obligations Post-Termination

Upon any termination of the Terms or discontinuation of your access to an API, you will immediately stop using the API, cease all use of the SSD Brand Features, and delete any cached or stored content that was permitted by the cache header under Section 5. SSD may independently communicate with any account owner whose account(s) are associated with your API Client and developer credentials to provide notice of the termination of your right to use an API.

c. Surviving Provisions

When the Terms come to an end, those terms that by their nature are intended to continue indefinitely will continue to apply, including but not limited to: Sections 4b, 5, 8, 9, and 10.

Section 9: Liability for our APIs

a. WARRANTIES

EXCEPT AS EXPRESSLY SET OUT IN THE TERMS, NEITHER SSD NOR ITS SUPPLIERS OR DISTRIBUTORS MAKE ANY SPECIFIC PROMISES ABOUT THE APIS. FOR EXAMPLE, WE DON’T MAKE ANY COMMITMENTS ABOUT THE CONTENT ACCESSED THROUGH THE APIS, THE SPECIFIC FUNCTIONS OF THE APIS, OR THEIR RELIABILITY, AVAILABILITY, OR ABILITY TO MEET YOUR NEEDS. WE PROVIDE THE APIS “AS IS”.

SOME JURISDICTIONS PROVIDE FOR CERTAIN WARRANTIES, LIKE THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. EXCEPT AS EXPRESSLY PROVIDED FOR IN THE TERMS, TO THE EXTENT PERMITTED BY LAW, WE EXCLUDE ALL WARRANTIES, GUARANTEES, CONDITIONS, REPRESENTATIONS, AND UNDERTAKINGS.

b. LIMITATION OF LIABILITY

TO THE FULLEST EXTENT PROVIDED BY LAW, IN NO EVENT WILL THE COMPANY, ITS AFFILIATES, OR THEIR LICENSORS, SERVICE PROVIDERS, EMPLOYEES, AGENTS, OFFICERS, OR DIRECTORS BE LIABLE FOR DAMAGES OF ANY KIND, UNDER ANY LEGAL THEORY, ARISING
OUT OF OR IN CONNECTION WITH YOUR USE, OR INABILITY TO USE, THE SERVICES, ANY WEBSITES LINKED TO IT, ANY CONTENT ON THE SERVICES OR SUCH OTHER WEBSITES, INCLUDING ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE
DAMAGES, INCLUDING BUT NOT LIMITED TO, PERSONAL INJURY, PAIN AND SUFFERING, EMOTIONAL DISTRESS, LOSS OF REVENUE, LOSS OF PROFITS, LOSS OF BUSINESS OR ANTICIPATED SAVINGS, LOSS OF USE, LOSS OF GOODWILL, LOSS OF DATA, AND WHETHER CAUSED BY TORT (INCLUDING NEGLIGENCE), BREACH OF CONTRACT, OR OTHERWISE, EVEN IF FORESEEABLE. THE FOREGOING DOES NOT AFFECT ANY LIABILITY THAT CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW.

c. Indemnification

You agree to defend, indemnify, and hold harmless the Company, its affiliates, licensors, and service providers, and its and their respective officers, directors, employees, contractors, agents, licensors, suppliers, successors, and
assigns from and against any claims, liabilities, damages, judgments, awards, losses, costs, expenses, or fees (including reasonable attorneys’ fees) arising out of or relating to your violation of these Terms of Use or your use
of the Services, including, but not limited to, your User Contributions, any use of the Service content, services, and products other than as expressly authorized in these Terms of Use or your use of any information obtained from the Services.

Section 10: General Provisions

a. Modification

We may revise and update these Terms of Use from time to time in our sole discretion. All changes are effective immediately when we post them, and apply to all access to and use of the Services thereafter.

Your continued use of the Services following the posting of revised Terms of Use means that you accept and agree to the changes. You are expected to check this page from time to time so you are aware of any changes, as they are binding
on you.

b. U.S. Federal Agency Entities

The APIs were developed solely at private expense and are commercial computer software and related documentation within the meaning of the applicable U.S. Federal Acquisition Regulation and agency supplements thereto.

c. General Legal Terms

We each agree to contract in the English language. If we provide a translation of the Terms, we do so for your convenience only and the English Terms will solely govern our relationship. The Terms do not create any third party beneficiary rights or any agency, partnership, or joint venture. Nothing in the Terms will limit either party’s ability to seek injunctive relief. We are not liable for failure or delay in performance to the extent caused by circumstances beyond our reasonable control. If you do not comply with the Terms, and SSD does not take action right away, this does not mean that SSD is giving up any rights that it may have (such as taking action in the future). If it turns out that a particular term is not enforceable, this will not affect any other terms. The Terms are the entire agreement between you and SSD relating to its subject and supersede any prior or contemporaneous agreements on that subject. For information about how to contact SSD, please visit our contact page.

If you are accepting the Terms on behalf of a United States city, county, or state government entity, then the following applies instead of the paragraph above: the parties agree to remain silent regarding governing law and venue.

Your Comments and Concerns

The Services are operated by Sai Systems Digital LLC, 5 Research Drive, Shelton, CT 06484.

All notices of copyright infringement claims should be sent to KPPB Law, One Lakeside Commons, Suite 800, 990 Hammond Drive NE, Atlanta, GA 30328, including a specific description of the claim, your name and your contact information.

All feedback, comments, requests for technical support, and other communications relating to the Services should be directed to: support@thesnfist.com.