Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Pending DHIT TOS Input

...

Table of Contents

Acceptance of Terms

This NeoMed FHIR API NeoDeck Holdings, Corp. Standardized API for Patient and Population Services Terms of Service document (the “API TOS”) is an agreement you must accept in order to use the PatientVault API (as described below). This document describes both your rights and your obligations as part of using the PatientVault API. It is important that you read it carefully because you will be legally bound to these terms. NeoDeck Holdings Corp. (“NeoDeck” “we” “us”) only provides the PatientVault API (“PatientVault”, “our API”, “this API”) to you subject to this API TOS. By accepting this API TOS or by accessing or using the PatientVault API(“Developer Terms” or “Terms”) are a legal agreement between you (“Developer”, “you,” “your”) and NeoDeck Holdings, Corp.(“NeoDeck,” “we,” “our” or “us”) governing your use of certified FHIR application programming interfaces (“Certified FHIR APIs”) and access to data. By creating a software application or other product or service that interacts or is associated with the Certified FHIR APIs (“Developer App”), you agree to be bound by this API TOS (including the Privacy Policy, Brand Guidelines, and general Terms of Service, which are incorporated here by reference)these Developer Terms and any documentation and guidelines.

If you are entering into this API TOS on behalf of a company or other legal entity, you represent that you have the authority to bind such entity to this API TOS. In that case, the terms “you” or “your” shall also refer to such entity. If you do not have such authority, or if you do not agree with this API TOS, you may not use the PatientVault API services. You acknowledge that this API TOS is a contract between you and NeoDeck, even though it is electronic and is not physically signed by you and NeoDeck, and it governs your use of the PatientVault Standardized API for Patient and Population Services.

API Key Definitions

  1.  Application – Any software application, website, or product you create or service you offer using the

    PatientVault

    FHIR API service (defined below).

  2.  API Documentation – The documentation, data and information

    that NeoDeck provides

    regarding the use of the

    PatientVault

    FHIR API through the Developer Site.

  3.  Data – means any data and content uploaded, posted, transmitted or otherwise made available by users via the Services, including messages, files, comments, profile information and anything else entered or uploaded into the Service by a user of the Service.

  4.  Developer Site –

    PatientVault

    FHIR API’s Developer site is found at 

    http

    https://

    www

    fhir-presentationdev.

    neodeckholdings

    patientvault.com/

  5.  NeoDeck / PatientVault Brand – The NeoDeck and PatientVault brand and

     

    PatientVault API or “our API” – The publicly available PatientVault’s Application Programming Interface (“API”) as well as the related API Documentation.

    NeoDeck / NeoMed Brand – The NeoDeck and NeoMed brand and brand assets, including names, logos, trade names and trademarks.

  6.  NeoDeck Service(s) /

    PatientVault

    NeoMed Service(s) – NeoDeck’s real-time communication, messaging, archiving and search services and related systems and technologies, as well as the website http://www.neodeckholdings.com/ (the “Site”), and all software, applications, data, reports, text, images, and other content made available by or on behalf of NeoDeck through any of the foregoing. The “Service” does not include Data or any software application or service that is provided by you or a third party (including Applications), whether or not NeoDeck designates them as “official integrations”.

  7. API License

As long as you follow this API TOS, NeoDeck grants you a limited, non-exclusive, non-assignable, non-transferable license to use the APIs to develop, test, and support any software application, website, or product, and to integrate the PatientVault APIs with your Application. Your license is subject to the limitations set forth in Section 4.2 through 4.11 and Section 9 below, and you agree that violation of Section 4 will automatically terminate your license to use the PatientVault APIs.

  1. Use of APIs and PatientVault’s Data

The following identifies limitations on use related to the PatientVault API:

...

 Reliance on API. PatientVault is still evolving, and we need the flexibility to occasionally make changes to our APIs, including backwards incompatible ones. We will try to give notice of these changes. Also, parts of our API are undocumented, including certain methods, events, and properties. Given that these undocumented aspects of our API may change at any time, you should not rely on these behaviors.

...

 Applicable laws or agreements. You may not use the PatientVault API in violation of any law or regulation, or rights of any person, including but not limited to intellectual property rights, rights of privacy, or rights of personality, or in any manner inconsistent with this API TOS or other NeoDeck’s agreements to which you are subject.

...

 Scope of acceptable use. You may not use the PatientVault API or any other technology in a manner that accesses or uses any information beyond what NeoDeck allows under this API TOS or the Documentation; that changes the NeoDeck / PatientVault Service; that breaks or circumvents any of NeoDeck’s or PatientVault’s technical, administrative, process or security measures; that disrupts or degrades the performance of the NeoDeck / PatientVault Service or the PatientVault API; or that tests the vulnerability of NeoDeck / PatientVault systems or networks.

...

 Malware. You may not transmit any viruses or other computer programming that may damage, detrimentally interfere with, surreptitiously intercept, or expropriate any system or data.

...

 Reverse engineering. You may not attempt to reverse engineer or otherwise derive source code, trade secrets, or know-how in the PatientVault API or portion thereof;

...

 Functionality. You may not use the PatientVault API to replicate or compete with core products or services offered by NeoDeck. You acknowledge and agree that NeoDeck has or may in the future offer products or services that are similar to your Application, and nothing will prevent NeoDekc from doing so;

...

 Commercial Use. You may charge for your Application. However, you may not sell, rent, lease, sublicense, redistribute, or syndicate access to the PatientVault API.

...

 Advertising. You may place advertisements on and around your Application. However, you may not:

  1. Place any advertisements within NeoDeck / PatientVault Service channels, and your advertisements may not resemble or be reasonably likely to confuse users as being a NeoDeck / PatientVault Service message;

  2. Use Data or any content from NeoDeck / PatientVault in any advertisements or for purposes of targeting advertisements, in your Application or elsewhere; or

  3. Use contact information obtained from NeoDeck / PatientVault (including email addresses) to contact NeoDeck users outside of NeoDeck without their express permission.

...

 Distribution of your application. You may not distribute or allow access to the PatientVault APIs to anyone other than, if applicable, the company on whose behalf you entered into this API TOS. Anyone who wants to access our APIs must agree to be bound by this API TOS.

...

Use of NeoDeck Brands or Marks. You must not use NeoDeck Brands in a way that suggests your service is endorsed by, sponsored by, or associated with NeoDeck.

...

Security Measures

  1.  Protections. The network, operating system and software of your web servers, databases, and computer systems (collectively, “Your Systems”) must be properly configured to securely operate your Application and store Data. Your Application must use reasonable security measures to protect your users’ information. You must not architect or select Your Systems in a manner to avoid the foregoing obligation.

  2.  Reporting. You must promptly report any security deficiencies in, or intrusions to, your Systems to NeoDeck in writing via email to cs@nd-soft.com or subsequent contact information posted on the Developer Site. This includes any unauthorized access, use, disclosure or destruction of Data. You will work with NeoDeck to immediately correct any security deficiency, and will immediately disconnect any intrusions or intruder. In the event of any security deficiency or intrusion involving the Application, PatientVault APIs or Data, you will make no public statements regarding such deficiencies or intrusions (e.g., press, blogs, social media, bulletin boards, etc.) without prior written and express permission from NeoDeck in each instance.

...

Government Access. You will not knowingly:

  1.  Allow or assist any government entities, law enforcement, or other organizations to conduct surveillance or obtain data using your access to the PatientVault API in order to avoid serving legal process directly on NeoDeck. Any such use by you for law enforcement purposes is a breach of this API TOS.

  2.  Display, distribute or otherwise make available Data or any Application to any person or entity that you reasonably believe will use Data to violate the Universal Declaration of Human Rights (located at http://www.un.org/en/documents/udhr/), including without limitation Articles 12, 18, or 19. You will not conduct and your Application will not provide analyses or research that isolates a small group of individuals or any single individual for any unlawful or discriminatory purposes. Exemptions to these restrictions may be requested for exigent circumstances and are subject to prior written approval from NeoDeck.

...

Government Use.

The PatientVault APIs are “commercial items” as that term is defined at 48 C.F.R. 2.101, consisting of “commercial computer software” and “commercial computer software documentation” as such terms are used in 48 C.F.R. 12.212. Any use, modification, derivative, reproduction, release, performance, display, disclosure or distribution of the PatientVault API by any government entity is prohibited, except as expressly permitted by the terms of this API TOS. Additionally, any use by U.S. government entities must be in accordance with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4. The contractor/manufacturer is NeoDeck Holdings Cop., 2053 Ponce by Pass, Suite 209

  1. Ownership.

...

  1. Documentation, Access, and Fees. In order to connect your Developer App to the Certified FHIR APIs, you will be required to register as an API Developer and register your Developer App. Upon registering your Developer App, NeoDeck will provide an API key that may be passed with each API request. In addition, we will provide credentials to a sandbox database that you may use for testing. Certified FHIR API access is provided to Developer free of charge. NeoDeck may, at its sole discretion, introduce reasonable fees to continue using the Certified FHIR API, provided, however, that such fees would be subject to applicable law. Consequently, no additional support services are provided to Developer as part of these Terms. If additional support services are required, Developer can contact NeoDeck.

  1. Trademark Use. NeoDeck grants Developer the right to use the NeoDeck name (not including any other NeoDeck trademarks or logos), for the sole purpose of identifying the Developer App as interoperable with NeoDeck’s hosted applications. Under no circumstances may Developer represent or imply that the Developer App or any integration solutions between the Developer App and NeoDeck’s hosted applications are certified, approved, endorsed, or in any way recommended or reviewed by NeoDeck. Such certification (and accompanying additional trademark and/or logo usage rights) may be made available to Developer under a separate agreement at NeoDeck’s sole discretion.

  1. Relationship. Neither Developer nor NeoDeck will represent that it has any authority to assume or create any obligation, express or implied, on behalf of the other party, nor to represent the other party as agent, employee, franchisee, or in any other capacity. Nothing in these Terms shall be construed to limit either party's right to independently develop or distribute software that is functionally similar to the other party's products, so long as proprietary information of the other party is not included in such software (except to the extent it is included to enable access, exchange or use of electronic health information through the Certified FHIR API).

Use of APIs and NeoMed’s Data

The following identifies limitations on use related to NeoMeds' data and API Service usage:

  1. API Service Usage and System Performance. While these Terms do not place any pre-set restrictions on frequency or nature of application calls via the Certified FHIR API Service, NeoDeck may, in consideration of overall system performance, limit the frequency or nature of application calls by Developer for a period of time no longer than necessary to resolve any negative impacts caused by excessive application calls.

  1.  Applicable laws or agreements. You may not use the API in violation of any law or regulation, or rights of any person, including but not limited to intellectual property rights, rights of privacy, or rights of personality, or in any manner inconsistent with this API TOS or other NeoDeck’s agreements to which you are subject.

  2.  Scope of acceptable use. You may not use the API or any other technology in a manner that accesses or uses any information beyond what NeoDeck allows under this API TOS; that changes NeoDeck Service; that breaks or circumvents any of NeoDeck’s technical, administrative, process or security measures; that disrupts or degrades the performance of the NeoDeck Service; or that tests the vulnerability of NeoDeck systems or networks.

  3.  Malware. You may not transmit any viruses or other computer programming that may damage, detrimentally interfere with, surreptitiously intercept, or expropriate any system or data.

  4.  Reverse engineering. You may not attempt to reverse engineer or otherwise derive source code, trade secrets, or know-how in the API or portion thereof.

  5.  Functionality. You may not use the API to replicate or compete with core products or services offered by NeoDeck. You acknowledge and agree that NeoDeck has or may in the future offer products or services that are similar to your Application and nothing will prevent NeoDeck from doing so;

  6.  Commercial Use. You may charge for your Application. However, you may not sell, rent, lease, sublicense, redistribute, or syndicate access to the API.

  7.  Advertising. You may place advertisements on and around your Application. However, you may not:

    1. Place any advertisements within NeoDeck Service channels, and your advertisements may not resemble or be reasonably likely to confuse users as being a NeoDeck Service message.

    2. Use Data or any content from NeoDeck in any advertisements or for purposes of targeting advertisements, in your Application or elsewhere; or

    3. Use contact information obtained from NeoDeck (including email addresses) to contact NeoDeck users outside of NeoDeck without their express permission.

  8.  Distribution of your application. You may not distribute or allow access to the APIs to anyone other than, if applicable, the company on whose behalf you entered into this API TOS. Anyone who wants to access our APIs must agree to be bound by this API TOS.

  9. Use of NeoDeck Brands or Marks. You must not use NeoDeck Brands in a way that suggests your service is endorsed by, sponsored by, or associated with NeoDeck.

Security Measures

  1.  Protections. The network, operating system and software of your web servers, databases, and computer systems (collectively, “Your Systems”) must be properly configured to securely operate your Application and store Data. Your Application must use reasonable security measures to protect your users’ information. You must not architect or select Your Systems in a manner to avoid the foregoing obligation.

  2.  Reporting. You must promptly report any security deficiencies in, or intrusions to, your Systems to NeoDeck in writing via email to cs@nd-soft.com or subsequent contact information posted on the Developer Site. This includes any unauthorized access, use, disclosure or destruction of Data. You will work with NeoDeck to immediately correct any security deficiency and will immediately disconnect any intrusions or intruder. In the event of any security deficiency or intrusion involving the Application, NeoMed’s API Service or Data, you will make no public statements regarding such deficiencies or intrusions (e.g., press, blogs, social media, bulletin boards, etc.) without prior written and express permission from NeoDeck in each instance.

  3. HIPAA. Developer understands and agrees that these Terms prohibit the access to and use of NeoMed end-users’ hosted application data including all Protected Health Information (“PHI”) as defined by the Health Insurance Portability and Accountability Act (“HIPAA”), unless such access is arranged directly between the Developer and the NeoMed end-user, whose relationship with the Developer may require a separate Business Associate Agreement between those two parties and otherwise comply with all applicable laws.

  4. Confidentiality. Developer acknowledges and agrees that the Access Credentials comprise highly sensitive and confidential information of NeoMed (“NeoMed Confidential Information”). Developer agrees to treat the Access Credentials, together with any other information or documentation provided by NeoMed in connection with the Access Credentials, whether in tangible, electronic, oral or other format, as highly confidential information and retain it in confidence using the same degree of care it uses with respect to its own highly confidential information, but in no event less than reasonable care for such information. Developer specifically agrees that the NeoMed Confidential Information will be accessible only by those employees and third-party consultants who (i) are directly involved with the Developer Programs; (ii) have a definite need to access the NeoMed Confidential Information and other information; and (iii) have entered into appropriate agreements with Developer binding them, as individuals or business entities, to the terms of agreements, including without limitation these Terms, entered into between Developer and third parties. NeoMed shall treat confidential information received from Developer on the same basis as set forth above (“Developer Confidential Information”).

    Confidential Information of either party hereunder shall not include information that: (a) is or becomes a part of the public domain through no act or omission of the other party; (b) was in the other party's lawful possession prior to the disclosure and had not been obtained by the other party either directly or indirectly from the disclosing party; (c) is lawfully disclosed to the other party by a third party without restriction on disclosure; or (d) is independently developed by the other party. For the avoidance of doubt, nothing in these Terms shall be construed to prohibit or restrict any communication in a manner that violates the Condition of Certification at 45 C.F.R. § 170.403(a). Further, Developer shall not impose any prohibition or restriction on any third party that prohibits or restricts any communication in a manner that violates the Condition of Certification.

    The confidentiality obligations under this Section of these Terms shall survive termination of Developer’s access to the Access Credentials for any reason. The parties acknowledge that money damages will not be an adequate remedy if the Confidentiality provisions of these Terms are breached and, therefore, either party may, in addition to any other legal or equitable remedies, seek injunctive or other equitable relief against such breach or threatened breach without the necessity of posting any bond or surety. In the event that either party is requested or required for the purposes of legal, administrative, or arbitration to disclose any Confidential Information, the party receiving such disclosure request will provide the other party with immediate written notice of any such request or requirement so that such party may seek an appropriate protective order or other relief.

Government Access 

You will not knowingly:

  1.  Allow or assist any government entities, law enforcement, or other organizations to conduct surveillance or obtain data using your access to the API in order to avoid serving legal process directly on NeoDeck. Any such use by you for law enforcement purposes is a breach of this API TOS.

  2.  Display, distribute or otherwise make available Data or any Application to any person or entity that you reasonably believe will use Data to violate the Universal Declaration of Human Rights (located at http://www.un.org/en/documents/udhr/), including without limitation Articles 12, 18, or 19. You will not conduct and your Application will not provide analyses or research that isolates a small group of individuals or any single individual for any unlawful or discriminatory purposes. Exemptions to these restrictions may be requested for exigent circumstances and are subject to prior written approval from NeoDeck.

Term and Termination

  1.  Duration of Terms. This API TOS will go into effect on the date upon which you agree to them, by accessing or using the

    PatientVault

    API, and will continue until terminated as set forth herein.

  2.  Your Right to Terminate. You may terminate this API TOS by discontinuing use of our APIs.

  3.  Suspension; Termination. We may change, suspend or discontinue the access to the

    PatientVault

    API Service and suspend or terminate your use of the

    PatientVault

    API Services, the NeoDeck Services, and/or NeoDeck /

    PatientVault

    NeoMed Brand at any time and for any reason, without notice. Without limiting the foregoing, we may limit your Application's access to the

    PatientVault

    API Service if it, in our sole discretion, may negatively affect our Service or our ability to provide our Service.

  4.  Effect of Termination. Upon

    termination of this API TOS:
  5. All rights and licenses granted to you will terminate immediately;

  6. You will promptly destroy Documentation and any other NeoDeck’s information in your possession or control that was received under

    termination of this API TOS

    ;

    :

    1.  Legal Representations. You represent and warrant to NeoDeck that, excluding NeoDeck products, you have the right to use, reproduce, transmit, copy, publicly display, publicly perform, and distribute your Application, and that use of your Application by NeoDeck and its users will not violate the rights of any third party (e.g., copyright, patent, trademark, privacy, publicity or other proprietary right of any person or entity), or any applicable regulation or law, including the Digital Millennium Copyright Act, the laws of any country in which your Application is made available and any applicable export laws.

    2. Unless we agree otherwise in writing or as stated in this API TOS, you must permanently delete all Data and other information

      that you stored pursuant to your use of the PatientVault APIs. NeoDeck may request that you certify in writing your compliance with this section; and
    3. NeoDeck will make commercially reasonable efforts to remove all references and links to your Application from its Services (NeoDeck has no other obligation to delete copies of, references to, or links to your Application).

    4.  The following sections of this API TOS shall survive any termination, Sections 5 (“Use of NeoDeck Brands or Marks”), 6 (“Security Measures”), 9 (“Ownership”), 10 (“Term and Termination”), 11 (“Other Important Terms”), 12 (“Disclaimer of Warranties; Limitation of Liability; Indemnity”), 13 (“Dispute Resolution”) and 14 (“General Legal Terms”).

  7. Other Important Terms.

    1.  Modification of the API TOS. We may change, add to or delete this API TOS or any portion thereof from time to time in our sole discretion. If we make a material change to this API TOs, we will provide you with reasonable notice prior to the changes either by emailing the email address associated with your account or by posting a notice on the Developer Site. You acknowledge that these updates and modifications may adversely impact how you access, use, and communicate with the PatientVault API. If any change in unacceptable to you, then your only recourse is to cease all use of the PatientVault API. Your continued access or use of the PatientVault API will mean that you agree to the updates and modificationsthat you stored pursuant to your use of the APIs. NeoDeck may request that you certify in writing your compliance with this section; and

    2. NeoDeck will make commercially reasonable efforts to remove all references and links to your Application from its Services (NeoDeck has no other obligation to delete copies of, references to, or links to your Application).

  8. Other Important Terms.

    1.  Legal Representations. You represent and warrant to NeoDeck that, excluding NeoDeck products, you have the right to use, reproduce, transmit, copy, publicly display, publicly perform, and distribute your Application, and that use of your Application by NeoDeck and its users will not violate the rights of any third party (e.g., copyright, patent, trademark, privacy, publicity or other proprietary right of any person or entity), or any applicable regulation or law, including the Digital Millennium Copyright Act, the laws of any country in which your Application is made available and any applicable export laws.

    2.  Modification of the API TOS. We may change, add to or delete this API TOS or any portion thereof from time to time in our sole discretion. If we make a material change to this API TOs, we will provide you with reasonable notice prior to the changes either by emailing to the email address associated with your account or by posting a notice on the Developer Site. You acknowledge that these updates and modifications may adversely impact how you access, use, and communicate with the API. If any change in unacceptable to you, then your only recourse is to cease all use of the API Service. Your continued access or use of the API Service will mean that you agree to the updates and modifications.

    3. Responsibility for Modification of Data. Developer acknowledges that, where permitted by NeoMed end-users, use of the Certified FHIR APIs can result in changes to NeoMed end-users’ hosted application data. Developer accepts full and complete responsibility for changes to such data made by means of access to the Certified FHIR APIs by or on behalf of Developer and/or Developer App, or by means of access by any third party to the extent such third party obtained access to the Certified FHIR APIs as a result of intentional disclosure by Developer or any breach of these Terms or any negligence by Developer, its personnel, agents or third-party contractors. NeoDeck has no liability under these Terms for any such changes, or for any consequences that may arise from such changes, including, but not limited to, incorrectly modified or lost data.

    4. Audit
      Developer agrees that if NeoDeck has reason to suspect that Developer may be in violation of the Developer Terms, NeoDeck may conduct an audit of Developer’s use of the License granted hereunder upon reasonable notice to Developer, but not less than three (3) business days.

Disclaimer of Warranties; Limitation of Liability; Indemnity

  1.  NO WARRANTIES. THE

    PatientVault

    API AND ALL RELATED COMPONENTS AND INFORMATION ARE PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS WITHOUT ANY WARRANTIES OF ANY KIND, AND NEODECK EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. YOU ACKNOWLEDGE THAT NEODECK DOES NOT WARRANT THAT THE

    PatientVault

    API WILL BE UNINTERRUPTED, TIMELY, SECURE, ERROR-FREE OR VIRUS-FREE, NOR DOES IT MAKE ANY WARRANTY AS TO THE RESULTS THAT MAY BE OBTAINED FROM USE OF THE

    PatientVault

    API, AND NO INFORMATION, ADVICE OR SERVICES OBTAINED BY YOU FROM NEODECK OR THROUGH THE DEVELOPER SITE SHALL CREATE ANY WARRANTY NOT EXPRESSLY STATED IN THIS API TOS.

  2.  LIMITATION ON LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY (WHETHER IN CONTRACT, TORT, OR OTHERWISE) SHALL NEODECK BE LIABLE TO YOU OR ANY THIRD PARTY FOR (A) ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING LOST PROFITS, LOST SALES OR BUSINESS, LOST DATA, OR (B) FOR ANY AMOUNT IN THE AGGREGATE IN EXCESS OF THE FEES ACTUALLY PAID BY YOU IN THE SIX (6) MONTHS PRECEDING THE EVENT GIVING RISE TO YOUR CLAIM OR, IF NO FEES APPLY, FIVE HUNDRED ($500) U.S. DOLLARS, OR (C) ANY MATTER BEYOND OUR REASONABLE CONTROL. THE PROVISIONS OF THIS SECTION ALLOCATE THE RISKS UNDER THIS TOS BETWEEN THE PARTIES, AND THE PARTIES HAVE RELIED ON THESE LIMITATIONS IN DETERMINING WHETHER TO ENTER INTO THIS TOS. Some jurisdictions do not allow the exclusion of implied warranties or limitation of liability for incidental or consequential damages, which means that some of the above limitations may not apply to you. IN THESE JURISDICTIONS, NEODECK’S LIABILITY WILL BE LIMITED TO THE GREATEST EXTENT PERMITTED BY LAW.

  3.  Indemnity. You agree to defend, hold harmless and indemnify NeoDeck, and its subsidiaries, affiliates, officers, agents, employees, and suppliers, from and against any third party claim arising from or in any way related to your or your users’ use of the Application,

    PatientVault

    API or Data, use of NeoDeck Brands, or violation of this API TOS, including any liability or expense arising from all claims, losses, damages (actual and consequential), suits, judgments, litigation costs and attorneys’ fees, of every kind and nature. In such a case, we will provide you with written notice of such claim, suit, or action.

Dispute Resolution

This API TOS and any claim, cause of action or dispute (“Claim”) arising out of or related to this Agreement shall be governed by the laws of the commonwealth of Puerto Rico, United States, regardless of your country of origin or where you access the NeoDeck API Service, and notwithstanding any conflicts of law principles and the United Nations Convention for the International Sale of Goods. You and NeoDeck agree that all Claims arising out of or related to this Agreement must be resolved exclusively in the courts located in the commonwealth of Puerto Rico. You and NeoDeck agree to submit to the personal jurisdiction of the courts located within the Commonwealth of Puerto Rico and agree to waive any and all objections to the exercise of jurisdiction over the parties by such courts and to venue in such courts for the purpose of litigating all such Claims. Notwithstanding the above, you agree that NeoDeck shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction.

General Legal Terms

  1.  Severability. If any provision of this API TOS is found to be illegal, void, or unenforceable, the unenforceable provision will be modified so as to render it enforceable to the maximum extent possible in order to effect the intention of the provision; if a term cannot be so modified, it will be severed and the remaining provisions of this API TOS will not be affected in any way.

  2.  Language. Where NeoDeck has provided you with a translation of the English language version of this API TOS or any document referenced in this API TOS, you agree that the translation is provided for your convenience only and that the English language versions of any such document, will control.

  3.  Notice and Service of Process. We may notify you via postings on the Developer Site or via the email address associated with your Application or NeoDeck

    / PatientVault

    Service account. NeoDeck accepts service of process by mail or courier at the physical address set forth in Section 16.9 below. Any notices that you provide without compliance with this section shall have no legal effect.

  4.  Entire Agreement. This API TOS and any documents incorporated into this API TOS by reference, constitute the entire agreement between you and NeoDeck regarding the

    PatientVault

    APIs and supersedes all prior agreements and understandings, whether written or oral, or whether established by custom, practice, policy or precedent, with respect to the subject matter of this API TOS.

  5.  No Informal Waivers, Agreements, or Representations. Our failure to act with respect to a breach of this API TOs by you or others does not waive our right to act with respect to that breach or subsequent similar or other breaches. No representations, statements, consents, waivers or other acts or omissions by any NeoDeck affiliate shall be deemed legally binding on any NeoDeck affiliate, unless documented in a physical writing hand signed by a duly appointed officer of NeoDeck.

  6.  Injunctive Relief. In no event shall you seek or be entitled to rescission, injunctive or other equitable relief, or to enjoin or restrain the operation of the Developer Site or NeoDeck Service or any

    PatientVault

    APIs, or other material used or displayed through the NeoDeck Developer Site or NeoDeck Service.

  7.  Assignment and Delegation. You may not assign or delegate any rights or obligations under this API TOS, including in connection with a change of control. Any purported assignment and delegation shall be ineffective. We may freely assign or delegate all rights and obligations under this API TOs, fully or partially without notice to you. We may also substitute, by way of unilateral novation, effective upon notice to you, NeoDeck Holdings Corp. for any third party that assumes our rights and obligations under this API TOs.

  8.  Potential Other Rights and Obligations. You may have rights or obligations under local law other than those enumerated here if you are located outside the United States.

  9.  How to Contact Us. If you have questions or comments about this API TOS, or wish to make use of our

    PatientVault

    API Service in any way not permitted by this API TOS, please contact us via email at cs@nd-soft.com, phone, or by physical mail at:

  • 2053 Ponce by Pass

...

  • , Suite 209
    Ponce, PR 00717-1308

  • Support: (787) 651-4444

  • Administration: (787) 651-6154

  • Sales: (787) 651-6154

FHIR® is the registered trademark of Health Level Seven International and is used with the permission of HL7.