bing track

Technical API Documentation

GETTING STARTED

All RESTful web service endpoints require HTTP Basic Authentication with a valid username and password for either a Staff or a Patient for a Practice known on this server.
For all endpoints, please use the same server root portion of the url was used to access this FHIR Capability Statement.
Review the official HL7.org guidelines on FHIR implementation here:
http://hl7.org/fhir/index.html

ENDPOINT TO RETRIEVE FHIR CAPABILITY STATEMENT
The following endpoint may be used to retrieve the server’s FHIR Capability Statement:

TITLE: FHIR Capability Statement

DESCRIPTION: Retrieve the server’s FHIR Capability Statement.

URL: /fhir/metadata

METHOD: Get

OPTIONAL URL PARAMETERS:
_format [By default data will be returned as application/fhir+xml. Pass this optional parameter and set the value to json if you would like data returned as application/fhir+json.]

SUCCESSFUL HTTP RESPONSE CODE: 200 [The full server FHIR Capability Statement will be returned.]

ERROR HTTP RESPONSE CODES:
404 [Resource Not Found. This will occur if the Web Service Url was typed in error.]
500 [A general server error has occurred.]

EXAMPLE REQUEST: https://SERVER_ROOT/fhir/metadata&_format=json

ENDPOINTS FOR STAFF MEMBERS
The following endpoints are meant to be accessed with valid credentials for a Staff member:

TITLE: Lookup Patient Identifier

DESCRIPTION: Searches for a Unique Patient Identifier for the given demographics.

URL: /fhir/Patient

METHOD: Get

REQUIRED URL PARAMETERS:
given [An exact match for the Patient’s first name]
family [An exact match for the Patient’s last name]
gender [An exact match for the Patient’s gender. Valid values are male or female]
birthdate [An exact match for the Patient’s birthdate. Valid format is yyyy-MM-dd]

OPTIONAL URL PARAMETERS:
_format [By default data will be returned as application/fhir+xml. Pass this optional parameter and set the value to json if you would like data returned as application/fhir+json.]

SUCCESSFUL HTTP RESPONSE CODE: 200 [The matching Patient Resource will be returned. Only the id property of the Patient will be returned, and no additional data.]

ERROR HTTP RESPONSE CODES:
401 [Unauthenticated User detected. To remedy, ensure that you use HTTP Basic Authentication with a valid username and password for a Staff member known on this server.]
403 [Forbidden access. This will occur if the authenticated user is attempting to access Patient information that they do not have access to.]
404 [Resource Not Found. This will occur if no Patients exactly match the demographics or if the Web Service Url was typed in error.]
500 [A general server error has occurred.]

EXAMPLE REQUEST: https://SERVER_ROOT/fhir/Patient?given=Clayton&family=Abernathy&gender=male&birthdate=1982-06-02&_format=json

TITLE: Get All Data for Single Patient

DESCRIPTION: Retrieves All Data for a Patient.

URL: /fhir/Patient

METHOD: Get

REQUIRED URL PARAMETERS:
identifier [The unique Patient Identifier on the server. This identifier can be retrieved using the Lookup Patient Identifier Endpoint described earlier.]

OPTIONAL URL PARAMETERS:
_format [By default data will be returned as application/fhir+xml. Pass this optional parameter and set the value to json if you would like data returned as application/fhir+json.]

SUCCESSFUL HTTP RESPONSE CODE: 200 [The matching Patient Resource will be returned with all available data points.]

ERROR HTTP RESPONSE CODES:
401 [Unauthenticated User detected. To remedy, ensure that you use HTTP Basic Authentication with a valid username and password for a Staff member known on this server.]
403 [Forbidden access. This will occur if the authenticated user is attempting to access Patient information that they do not have access to.]
404 [Resource Not Found. This will occur if no Patient matches the requested Patient identifier or if the Web Service Url was typed in error.]
500 [A general server error has occurred.]

EXAMPLE REQUEST: https://SERVER_ROOT/fhir/Patient?identifier=1125&_format=json

TITLE: Get Specific Data for Single Patient

DESCRIPTION: Retrieves Specific Data for a Patient.

URL: /fhir/Patient

METHOD: Get

REQUIRED URL PARAMETERS:
identifier [The unique Patient Identifier on the server. This identifier can be retrieved using the Lookup Patient Identifier Endpoint described earlier.]

OPTIONAL URL PARAMETERS:
_include [Send a separate _include parameter for each desired section. See the NOTES below for a detail on each _include parameter]
date [Send a maximum of 2 date parameters to indicate a date range. Data for each included section for the Patient will be returned if it satisfies the date range. See the NOTES below for a further explanation of valid date parameter formats.]
_format [By default data will be returned as application/fhir+xml. Pass this optional parameter and set the value to json if you would like data returned as application/fhir+json.]

SUCCESSFUL HTTP RESPONSE CODE: 200 [The matching Patient Resource will be returned with the requested data points. Also included will be the Patient given name, family name, birthdate and gender.]

ERROR HTTP RESPONSE CODES:
401 [Unauthenticated User detected. To remedy, ensure that you use HTTP Basic Authentication with a valid username and password for a Staff member known on this server.]
403 [Forbidden access. This will occur if the authenticated user is attempting to access Patient information that they do not have access to.]
404 [Resource Not Found. This will occur if no Patient matches the requested Patient identifier or if the Web Service Url was typed in error.]
500 [A general server error has occurred.]

NOTES:
Valid date parameter values are as follows:
eqyyyy-MM-dd [date equals the yyyy-MM-dd formatted date]
ltyyyy-MM-dd [date is less than the yyyy-MM-dd formatted date]
leyyyy-MM-dd [date is less than or equal to the yyyy-MM-dd formatted date]
gtyyyy-MM-dd [date is greater than the yyyy-MM-dd formatted date]
geyyyy-MM-dd [date is greater than or equal to the yyyy-MM-dd formatted date]

Valid _include parameter values are as follows:
Patient:allergy [Patient allergy information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/allergyintolerance.html

Patient:assessment [Patient assessment information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/careplan.html

Patient:careTeam [Patient care team information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/careteam.html

Patient:device [Patient medical device information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/device.html

Patient:ethnicGroup [Patient ethnic group information will be returned if it is available]
Info on this data structure is available at http://hl7.org/fhir/us/core/2017Jan/ValueSet-detailed-ethnicity.html

Patient:goal [Patient goal information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/goal.html

Patient:healthConcern [Patient health concern information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/riskassessment.html

Patient:immunization [Patient immunization information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/immunization.html

Patient:medication [Patient medication information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/medicationstatement.html

Patient:preferredLanguage [Patient preferred language will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/valueset-languages.html

Patient:problem [Patient problem information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/problem.html

Patient:procedure [Patient procedure information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/procedure.html

Patient:race [Patient race information will be returned if it is available]
Info on this data structure is available at http://hl7.org/fhir/us/core/2017Jan/ValueSet-omb-race.html

Patient:result [Patient lab result information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/observation.html

Patient:smokingStatus [Patient smoking status will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/observation.html

Patient:treatmentPlan [Patient treatment plan information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/careplan.html

Patient:vitalSign [Patient vital sign information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/observation.html

EXAMPLE REQUEST: https://SERVER_ROOT/fhir/Patient?identifier=1125&_include=Patient:allergy&_include=Patient:medication&date=gt2015-12-31&date=le2016-03-31&_format=json

TITLE: Get All Data for All Patients in the Organization of the Staff member

DESCRIPTION: Retrieves all Data for all Patients in the Organization of the Staff member.

URL: /fhir/Patient

METHOD: Get

OPTIONAL URL PARAMETERS:
_format [By default data will be returned as application/fhir+xml. Pass this optional parameter and set the value to json if you would like data returned as application/fhir+json.]

SUCCESSFUL HTTP RESPONSE CODE: 200 [The matching Patient Resources will be returned with all available data points.]

ERROR HTTP RESPONSE CODES:
401 [Unauthenticated User detected. To remedy, ensure that you use HTTP Basic Authentication with a valid username and password for a Staff member known on this server.]
403 [Forbidden access. This will occur if the authenticated user is attempting to access Patient information that they do not have access to.]
404 [Resource Not Found. This will occur if no Patient Resources are found or if the Web Service Url was typed in error.]
500 [A general server error has occurred.]

EXAMPLE REQUEST: https://SERVER_ROOT/fhir/Patient?_format=json

TITLE: Get Specific Data for All Patients in the Organization of the Staff member

DESCRIPTION: Retrieves Specific Data for all Patients in the Organization of the Staff member.

URL: /fhir/Patient

METHOD: Get

OPTIONAL URL PARAMETERS:
_include [Send a separate _include parameter for each desired section. See the NOTES below for a detail on each _include parameter]
date [Send a maximum of 2 date parameters to indicate a date range. Data for each included section for Patients will be returned if it satisfies the date range. See the NOTES below for a further explanation of valid date parameter formats.]
_format [By default data will be returned as application/fhir+xml. Pass this optional parameter and set the value to json if you would like data returned as application/fhir+json.]

SUCCESSFUL HTTP RESPONSE CODE: 200 [The matching Patient Resources will be returned with the requested data points. Also included will be the Patient given name, family name, birthdate and gender.]

ERROR HTTP RESPONSE CODES:
401 [Unauthenticated User detected. To remedy, ensure that you use HTTP Basic Authentication with a valid username and password for a Staff member known on this server.]
403 [Forbidden access. This will occur if the authenticated user is attempting to access Patient information that they do not have access to.]
404 [Resource Not Found. This will occur if no Patient Resources are found or if the Web Service Url was typed in error.]
500 [A general server error has occurred.]

NOTES:
Valid date parameter values are as follows:
eqyyyy-MM-dd [date equals the yyyy-MM-dd formatted date]
ltyyyy-MM-dd [date is less than the yyyy-MM-dd formatted date]
leyyyy-MM-dd [date is less than or equal to the yyyy-MM-dd formatted date]
gtyyyy-MM-dd [date is greater than the yyyy-MM-dd formatted date]
geyyyy-MM-dd [date is greater than or equal to the yyyy-MM-dd formatted date]

Valid _include parameter values are as follows:
Patient:allergy [Patient allergy information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/allergyintolerance.html

Patient:assessment [Patient assessment information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/careplan.html

Patient:careTeam [Patient care team information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/careteam.html

Patient:device [Patient medical device information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/device.html

Patient:ethnicGroup [Patient ethnic group information will be returned if it is available]
Info on this data structure is available at http://hl7.org/fhir/us/core/2017Jan/ValueSet-detailed-ethnicity.html

Patient:goal [Patient goal information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/goal.html

Patient:healthConcern [Patient health concern information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/riskassessment.html

Patient:immunization [Patient immunization information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/immunization.html

Patient:medication [Patient medication information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/medicationstatement.html

Patient:preferredLanguage [Patient preferred language will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/valueset-languages.html

Patient:problem [Patient problem information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/problem.html

Patient:procedure [Patient procedure information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/procedure.html

Patient:race [Patient race information will be returned if it is available]
Info on this data structure is available at http://hl7.org/fhir/us/core/2017Jan/ValueSet-omb-race.html

Patient:result [Patient lab result information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/observation.html

Patient:smokingStatus [Patient smoking status will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/observation.html

Patient:treatmentPlan [Patient treatment plan information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/careplan.html

Patient:vitalSign [Patient vital sign information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/observation.html

EXAMPLE REQUEST: https://SERVER_ROOT/fhir/Patient?_include=Patient:allergy&_include=Patient:medication&date=gt2015-12-31&date=le2016-03-31&_format=json

ENDPOINTS FOR PATIENTS
The following endpoints are meant to be accessed with valid credentials for a Patient:

TITLE: Get All Data for Authenticated Patient

DESCRIPTION: Retrieves All Data for the Authenticated Patient.

URL: /fhir/Patient

METHOD: Get

OPTIONAL URL PARAMETERS:
_format [By default data will be returned as application/fhir+xml. Pass this optional parameter and set the value to json if you would like data returned as application/fhir+json.]

SUCCESSFUL HTTP RESPONSE CODE: 200 [The Patient Resource corresponding to the Authentication credentials will be returned with all available data points.]

ERROR HTTP RESPONSE CODES:
401 [Unauthenticated User detected. To remedy, ensure that you use HTTP Basic Authentication with a valid username and password for a Patient known on this server.]
403 [Forbidden access. This will occur if the authenticated user is attempting to access Patient information that they do not have access to.]
404 [Resource Not Found. This will occur if no Patient matches the requested Authentication credentials or if the Web Service Url was typed in error.]
500 [A general server error has occurred.]

EXAMPLE REQUEST: https://SERVER_ROOT/fhir/Patient?_format=json

TITLE: Get Specific Data for Authenticated Patient

DESCRIPTION: Retrieves Specific Data for the Authenticated Patient.

URL: /fhir/Patient

METHOD: Get

OPTIONAL URL PARAMETERS:
_include [Send a separate _include parameter for each desired section. See the NOTES below for a detail on each _include parameter]
date [Send a maximum of 2 date parameters to indicate a date range. Data for each included section for the Patient will be returned if it satisfies the date range. See the NOTES below for a further explanation of valid date parameter formats.]
_format [By default data will be returned as application/fhir+xml. Pass this optional parameter and set the value to json if you would like data returned as application/fhir+json.]

SUCCESSFUL HTTP RESPONSE CODE: 200 [The matching Patient Resource will be returned with the requested data points. Also included will be the Patient given name, family name, birthdate and gender.]

ERROR HTTP RESPONSE CODES:
401 [Unauthenticated User detected. To remedy, ensure that you use HTTP Basic Authentication with a valid username and password for a Patient known on this server.]
403 [Forbidden access. This will occur if the authenticated user is attempting to access Patient information that they do not have access to.]
404 [Resource Not Found. This will occur if no Patient matches the requested Authentication credentials or if the Web Service Url was typed in error.]
500 [A general server error has occurred.]

NOTES:
Valid date parameter values are as follows:
eqyyyy-MM-dd [date equals the yyyy-MM-dd formatted date]
ltyyyy-MM-dd [date is less than the yyyy-MM-dd formatted date]
leyyyy-MM-dd [date is less than or equal to the yyyy-MM-dd formatted date]
gtyyyy-MM-dd [date is greater than the yyyy-MM-dd formatted date]
geyyyy-MM-dd [date is greater than or equal to the yyyy-MM-dd formatted date]

Valid _include parameter values are as follows:
Patient:allergy [Patient allergy information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/allergyintolerance.html

Patient:assessment [Patient assessment information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/careplan.html

Patient:careTeam [Patient care team information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/careteam.html

Patient:device [Patient medical device information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/device.html

Patient:ethnicGroup [Patient ethnic group information will be returned if it is available]
Info on this data structure is available at http://hl7.org/fhir/us/core/2017Jan/ValueSet-detailed-ethnicity.html

Patient:goal [Patient goal information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/goal.html

Patient:healthConcern [Patient health concern information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/riskassessment.html

Patient:immunization [Patient immunization information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/immunization.html

Patient:medication [Patient medication information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/medicationstatement.html

Patient:preferredLanguage [Patient preferred language will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/valueset-languages.html

Patient:problem [Patient problem information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/problem.html

Patient:procedure [Patient procedure information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/procedure.html

Patient:race [Patient race information will be returned if it is available]
Info on this data structure is available at http://hl7.org/fhir/us/core/2017Jan/ValueSet-omb-race.html

Patient:result [Patient lab result information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/observation.html

Patient:smokingStatus [Patient smoking status will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/observation.html

Patient:treatmentPlan [Patient treatment plan information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/careplan.html

Patient:vitalSign [Patient vital sign information will be returned if it is available]
Info on this data structure is available at https://www.hl7.org/fhir/observation.html

EXAMPLE REQUEST: https://SERVER_ROOT/fhir/Patient?_include=Patient:allergy&_include=Patient:medication&date=gt2015-12-31&date=le2016-03-31&_format=json

Title: Retrieve Patient CCDA

Description: This Endpoint may be used to retrieve a full CCDA for the requested Patient

Method: Get

URL: https://SERVER_ROOT/ema/ws/v3/patient/ccd/{ID}

Required Parameter: ID [This is the identifier for the requested Patient]

SUCCESSFUL HTTP RESPONSE CODE: 200 [The requested Patient CCDA will be returned]

Example Request: https://SERVER_ROOT/ema/ws/v3/patient/ccd/12345

Title: Retrieve Patient CCDA for a Date Range
Description: This Endpoint may be used to retrieve a full CCDA for the requested Patient for a specific Date or a Date Range
Method: Get
URL: https://SERVER_ROOT/ema/ws/v3/patient/ccd/{ID}
Required Parameter: ID [This is the identifier for the requested Patient]
OPTIONAL URL PARAMETERS:
lowerBound [Indicates the lower bound of a date range. Data for each included section for the Patient will be returned if it satisfies the date range. See the NOTES below for a further explanation of valid date parameter formats.]
upperBound [Indicates the upper bound of a date range. Data for each included section for the Patient will be returned if it satisfies the date range. See the NOTES below for a further explanation of valid date parameter formats.]
exactDate [Use this parameter if data for a specific date is being requested. If using this parameter, do not pass any other parameters for a date range. Data for each included section for the Patient will be returned if it satisfies the date requested. See the NOTES below for a further explanation of valid date parameter formats.]
SUCCESSFUL HTTP RESPONSE CODE: 200 [The requested Patient CCDA will be returned]
NOTES:
Valid lowerBound date parameter values are as follows:
yyyy-MM-dd [date equals the yyyy-MM-dd formatted date]
eqyyyy-MM-dd [date equals the yyyy-MM-dd formatted date]
gtyyyy-MM-dd [date is greater than the yyyy-MM-dd formatted date]
geyyyy-MM-dd [date is greater than or equal to the yyyy-MM-dd formatted date]

Valid upperBound date parameter values are as follows:
yyyy-MM-dd [date equals the yyyy-MM-dd formatted date]
eqyyyy-MM-dd [date equals the yyyy-MM-dd formatted date]
ltyyyy-MM-dd [date is less than the yyyy-MM-dd formatted date]
leyyyy-MM-dd [date is less than or equal to the yyyy-MM-dd formatted date]

Valid exactDate date parameter value is as follows:
yyyy-MM-dd [date equals the yyyy-MM-dd formatted date]
Example Requests:
https://SERVER_ROOT/ema/ws/v3/patient/ccd/12345
https://SERVER_ROOT/ema/ws/v3/patient/ccd/12345?lowerBound=ge2017-01-01&upperBound=le2017-12-31
https://SERVER_ROOT/ema/ws/v3/patient/ccd/12345?exactDate=2017-10-01


MODERNIZING MEDICINE API TERMS OF USE – RELEASE VERSION 5.8.0

Modernizing Medicine, Inc. (“MMI”) makes available a hosted electronic health record system (“MMI System”) for use by medical practices, and an Application Programming Interface (“MMI API”) to permit third party websites and applications to access certain patient data stored in the MMI System (“EHR Data”).

By using or accessing the MMI API, you agree to these MMI API Terms of Use (the “API Terms”). If you are using the MMI API on behalf of your employer or other entity, you represent and warrant that you have the authority to bind that entity to the API Terms, and all references to “you” in the Terms refer to that entity.

  1. Your Products. You may configure your websites and applications developed by you (“Your Products”) to access EHR Data through the MMI API. You must configure Your Products so that access to EHR Data through Your Products requires users to input their MMI System credentials such that only (a) patients (“Patients”) with authorized access to the MMI System and (b) their healthcare providers (and their provider practice’s staff members) with authorized access to the MMI System and all permissions required by any statute, regulation or other law from the applicable Patient, will be able to access such Patient’s EHR Data (such Patients, providers, and staff, “Authorized Users”).
  2. Use of EHR Data. You will use EHR Data only to provide Your Products to the applicable Authorized User. You will not build any databases based on EHR Data obtained by you and will store EHR Data only for so long as needed and permitted by applicable laws. Without limiting the foregoing, you will not use EHR Data to create or commercialize de-identified data sets.
  3. Monitoring. MMI may monitor your use of the MMI APIs (including, without limitation, accessing and using Your Product) in order to verify your compliance with these Terms, improve the MMI System, and assess the quality and security of Your Products.
  4. Breach; Suspension; Termination. You must notify MMI immediately in the event that you become aware that you or Your Product is in violation of any provision of these Terms. MMI may suspend access to the MMI API by you or Your Products without notice if MMI believes in its sole discretion that you are in violation of these Terms or that your use of the MMI API is unauthorized, presents a security threat, is for obscene, offensive, harassing or fraudulent purposes or interferes with others’ appropriate use of the MMI API. Without limiting the foregoing suspension rights, MMI may terminate your access to the MMI API in the event that you fail to remedy any such issue within 30 days of notice.
  5. Privacy. You must notify Authorized Users that EHR Data will be available to Your Products, and you must provide legally adequate privacy notice and protection for Authorized Users. You must collect, process, use, store, disclose and transfer EHR Data only in compliance with all applicable laws, privacy policies and third-party contracts. You and Your Product may only use EHR Data for the limited purposes for which Authorized Users have given you permission. You will not submit or make available to MMI through the API any Protected Health Information (as defined under Health Insurance Portability and Accountability Act of 1996 (as amended)).
  6. Confidentiality and Security. You are responsible for maintaining the confidentiality and security of the EHR Data that you access through the API. You agree immediately to notify MMI of (a) any unauthorized access, use or disclosure of EHR Data of which you become aware and (b) any breach of security of the MMI System of which you become aware. You will protect the confidentiality and security of EHR Data and other user information collected by Your Product, including personally identifiable information (“PII”), from unauthorized access or use and will promptly notify Authorized Users of any unauthorized access or use of any such information to the extent required by applicable laws, rules or regulations.
  7. Use of API. You agree to engage in best efforts to ensure that your use of the MMI API will not generate excessive load on the MMI System or cause the MMI System to behave inaccurately or inconsistently. You will not corrupt or modify the EHR Data or use superseded or unauthorized versions of the MMI API, including (without limitation) for the purpose of obtaining unauthorized access to the MMI System or underlying software.
  8. Compliance with Law. You will, and will require all Authorized Users to, comply with all applicable laws and these Terms. You will not knowingly enable Authorized Users to violate any applicable law or these Terms.
  9. MMI API Availability. MMI may suspend access to or shut down the MMI API entirely at any time in order to fix problems with the MMI API, conduct routine maintenance, update the MMI API, or for any other reason. The MMI API may not always be available and should not be relied upon in an emergency.
  10. Restrictions. You will not and will not enable or allow Your Product or any other person or entity to: (a) reverse engineer, disassemble, decompile or otherwise attempt to derive the source code or the underlying ideas, algorithms, structure or organization of the MMI System; (b) sublicense, transfer, distribute or otherwise make available the EHR Data in any form to anyone other than the applicable Authorized User; (c) lease, loan or sell the MMI API; (d) create derivative works of or otherwise modify the MMI API; (e) attempt to defeat, avoid, bypass, remove, deactivate or otherwise circumvent any software protection mechanisms in the MMI API or MMI System, including (without limitation) any such mechanism used to restrict or control the functionality of any of the foregoing, or (f) disable, hack, disrupt, damage, interfere or otherwise access in an unauthorized manner the MMI System or any technology or service of MMI, or violate, tamper with, or circumvent the security of any computer network, software, passwords, encryption codes or technological protection measures.
  11. Attribution. You may make appropriate and truthful reference to MMI in the documentation for Your Product; provided that you must not, either directly or indirectly, promote or advertise Your Product as being sponsored, endorsed or recommended by MMI or its affiliates. You may not remove, obscure, or alter any MMI trademarks or trade names or MMI links to, or notices of, these Terms.
  12. No Solicitation. You agree to not solicit business from or otherwise market or contact any Authorized User due to such end user’s status as a customer of MMI. Your communications with Authorized Users and all use of Authorized User information shall be made solely within the context of and shall be exclusively related to Your Product, and all communications shall be made solely with information gathered through Your Product.
  13. No Implied Licenses. No license is granted, expressly, by implication or otherwise, under any patents, copyrights, trademarks, trade secrets or other intellectual property rights of MMI. MMI owns and retains ownership of the MMI and the MMI System and all intellectual property rights therein and thereto.
  14. Disclaimers. The MMI API is provided on an “as is” basis. MMI, on behalf of itself and its affiliates, to the fullest extent permitted by law, disclaims all warranties, express, implied, statutory or otherwise, including (without limitation) any implied warranties of merchantability, non-infringement of third parties’ rights, and fitness for a particular purpose.
  15. Limitations of Liability. MMI AND ITS AFFILIATES WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR RELATED TO THE MMI API, INCLUDING (WITHOUT LIMITATION): (a) YOUR USE OF OR INABILITY TO USE THE MMI API OR EHR DATA OR (b) ANY LACK OF AVAILABILITY OF OR INACCURACY OF ANY EHR DATA OBTAINED THROUGH YOUR USE OF THE MMI API.
  16. Indemnification. You agree, at your expense, to indemnify and hold MMI and its affiliates harmless from and against any and all losses, costs, damages, liabilities, and expenses (including, without limitation, attorneys’ fees) arising out of or relating to third party claims, actions, or allegations based on Your Product, your use of the MMI API, and any EHR Data accessed by you or Your Product through the MMI API.
  17. Governing Law; Jurisdiction. These Terms shall be governed by, and construed in accordance with, the laws of the State of Florida, without regard to its conflict of laws provisions. All disputes arising out of or related to these Terms will be settled by the state or federal courts in Palm Beach County, Florida, and you hereby consent to the jurisdiction thereof.
  18. Assignment. These Terms may not be delegated, assigned or transferred by you without prior written approval of MMI, and MMI may terminate these Terms in the event that you undergo a change of control. Any assignment in violation of the foregoing shall be null and void. MMI may assign or otherwise transfer these Terms in connection with a reorganization, consolidation, change of control, merger, acquisition or sale of substantially all of its assets that relate to these Terms.
  19. General. If you are a provider or staff member, you further agree that your use of the MMI System will be in compliance with the terms of the applicable contract governing your use of the MMI System. These Terms contain the entire agreement between you and MMI with respect to the MMI API. If any provision of these Terms is found by a court of competent jurisdiction to be invalid or unenforceable, then that provision will be deemed modified to the minimum extent necessary to render it valid and enforceable, and the remaining provisions of these Terms will continue to be valid and enforceable. No failure of MMI to enforce any provision of these Terms will be considered to be a waiver of MMI’s right to enforce such provision or any other provision at any time.
  20. Amendment. These Terms may be amended by MMI, which changes will be effective upon Your acceptance of the modified terms; provided that if you fail to accept the modified terms within 30 days after presentation to you, then without limiting any other provision of these Terms, MMI may suspend your access to EHR Data until You agree to such revised terms. If You do not agree to such revised terms, as your sole remedy, you may terminate these Terms by notice to MMI. These Terms may also be amended by a written agreement signed by authorized representatives of both parties.

If you have any questions concerning these Terms, or need to send a notice to MMI, or desire to contact MMI for any reason, you may contact MMI by email at legal@modmed.com or by mail at Modernizing Medicine, Inc., 3600 FAU Boulevard, Suite 202, Boca Raton, Florida 33431, Attention: General Counsel.