---
title: "HealthEx"
description: "Personal clinical records through patient-authorized MCP. Current read tools are discovered before use. No administrative token, record refresh, writes, polling or automatic pagination."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# HealthEx

<p>Personal clinical records through patient-authorized MCP. Current read tools are discovered before use. No administrative token, record refresh, writes, polling or automatic pagination.</p>

<details data-command-index><summary>What you can do (2)</summary>
<h2>What you can do</h2>
<p>Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/healthex#command-healthex-tools-list">Discover personal clinical read tools</a> — <code>healthex.tools.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/healthex#command-healthex-records-read">Read one clinical records response</a> — <code>healthex.records.read</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/healthex">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for HealthEx, then enter the issued values in the connection form below.</p>
<ol>
<li>Use HealthEx patient MCP authorization and a supported OAuth client. Register the exact redirect URI, enter Client ID where required, save and authorize with documented patient read scopes. Access token and scope must come from that grant; never use an administrator token to select another patient.</li>
</ol>
<p><a href="https://docs.healthex.io/api-documentation/mcp-server/">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>OAuth callback URL</td>
<td>Optional</td>
</tr>
<tr>
<td>Registered public OAuth client ID</td>
<td>Optional</td>
</tr>
<tr>
<td>Personal access token</td>
<td>Optional</td>
</tr>
<tr>
<td>Granted patient read scope</td>
<td>Optional</td>
</tr>
<tr>
<td>Return URL after authorization</td>
<td>Optional</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-healthex-tools-list">
<summary><span>Discover personal clinical read tools — <code>healthex.<wbr>tools.<wbr>list</code></span></summary>
<p>Run <strong>Discover personal clinical read tools</strong> with HealthEx. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/healthex?command=healthex.tools.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/healthex/commands/healthex.tools.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 2 provider requests per invocation; timeout: 60 seconds.</p>

</details>
<details id="command-healthex-records-read">
<summary><span>Read one clinical records response — <code>healthex.<wbr>records.<wbr>read</code></span></summary>
<p>Run <strong>Read one clinical records response</strong> with HealthEx. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/healthex?command=healthex.records.read">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>tool</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>enum: [&quot;get_health_summary&quot;,&quot;get_conditions&quot;,&quot;get_medications&quot;,&quot;get_allergies&quot;,&quot;get_labs&quot;,&quot;get_vitals&quot;,&quot;get_immunizations&quot;,&quot;get_procedures&quot;,&quot;get_visits&quot;,&quot;get_clinical_notes&quot;,&quot;search_clinical_notes&quot;,&quot;check_records_status&quot;,&quot;get_consent_record&quot;]</code></td>
</tr>
<tr>
<td><code>arguments</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>maxProperties: 7</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/healthex/commands/healthex.records.read">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "tool": "get_labs",
  "arguments": {
    "beforeDate": "2026-10-01"
  }
}
</code></pre>

<p>At most 3 provider requests per invocation; timeout: 60 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://docs.healthex.io/api-documentation/mcp-server/">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/healthex/index.mdx