# Custom Connectors

iCure ensures the transferability of data stored in a compliant way. 

{% tabs %}
{% tab title="iCure REST API" %}

* Run on the server the iCure implementation
* Serve encrypted data
* Industry Standard interfacing with the [REST API calls](/icure/icure-data-stack/rest-api-calls.md)
  {% endtab %}

{% tab title="SDKs " %}

* Are based on the iCure REST API
* Are executed on the Healthcare Provider terminal
* Serves decrypted data
* [Mobile/Web SDKs](/icure/icure-data-stack/mobile-web-sdks.md) for all major programming languages
  {% endtab %}

{% tab title="IHE Profiles " %}

* Runs inside the Hospital / Healthcare Provider data secure perimeter
* Serve decrypted data
* Industry Standard [IHE XDS calls](/icure/interoperability/iti-registry-repository.md) and [IHE IPS call](/icure/interoperability/icure-api.md)
  {% endtab %}

{% tab title="FHIR REST API" %}

* Is based on the iCure REST API
* Are executed on the Healthcare Provider terminal
* Serves decrypted data
  {% endtab %}

{% tab title="OpenEHR REST API" %}

* Is based on the iCure REST API
* Is executed on the Healthcare Provider terminal
  {% endtab %}
  {% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://icure.gitbook.io/icure/customizable-features/custom-connectors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.