Resources · Claude connector

Claude HealthEx connectorWhat Claude can do in your HealthEx account.

The Claude HealthEx connector exposes 9 tools. 5 read, 0 write, 4 are described by no official source. Below: which parts of your health record Claude can pull, how far back by default, and where HealthEx's documentation and the directory sheet do not list the same tools.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can read your records

You stop digging through patient portals to answer a simple question about yourself. Once HealthEx is connected, Claude can pull specific parts of your records, such as medications, vital signs, allergies, vaccinations and diagnoses, and answer from them in the conversation. HealthEx frames it as access to your records with your consent.

Prepare a new doctor's appointment. A new GP asks what you take and what you react to. get_medications brings dosing, prescriber, refills and changes over time, and get_allergies adds each allergen with its status, criticality and documented reactions.

Check a trend. You want to know how your blood pressure moved this year. get_vitals returns measurements with units, dates, reference ranges and abnormal flags, so Claude can line them up.

Sort out travel paperwork. Before a trip, get_immunizations lists the vaccines you received, with dates and dose numbers, and get_conditions shows past and current diagnoses with start and end dates.

Now what the sheet leaves out. Four of the nine listed tools are described nowhere under their names, and HealthEx's tools page documents others that the sheet does not carry. History stops at 3 years by default. And nothing runs on its own: no tool fires when a new lab result reaches your record. Background processing on events is a job for an automation tool; the Integrations hub gathers that side.

Vocabulary

The vocabulary in one minute

Five words you will meet while connecting HealthEx.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while answering you.
Tool
One named thing a connector lets Claude do. Claude picks the ones it needs by itself, and the directory lists each by name.
Authorization
The sign-in screen of the service itself, where you hand Claude its access. Granted once per person, and you can take it back.
Approval
The confirmation Claude waits for before it goes through with something that changes your account, shown right in the conversation.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Connect

Connect HealthEx to Claude in three steps

  1. 01

    Find HealthEx in Claude

    In Claude's settings, open Customize, then Connectors, and look for HealthEx in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first, before each member can sign in on their side.

  2. 02

    Start the connection

    Click Connect on its row, then sign in to HealthEx in the window HealthEx opens itself. The access granted there is yours alone, given once per person. If the link breaks later, use Disconnect and connect again.

  3. 03

    Read the authorization screen

    Check the authorization screen before you accept. It belongs to HealthEx, not to Claude, and it decides what the access covers. You can also withdraw that access later from your HealthEx account.

Tools

The 9 tools, sorted by what they do

HealthEx gives Claude 9 tools: 5 that read your account, 0 that change something in it, and 4 no official source describes.

Two groups: what Claude reads, and what no official source describes. Names stay as Claude shows them, in English.

  • 5 read
  • 4 not documented

What Claude reads (5)

5 tools

Five tools that look up parts of your record without changing it.

get_medications

Pulls detailed medication information: dosing instructions, prescribing provider, indication, start date, pharmacy, refill history, adjustments over time, discontinuation dates with reasons, and notes on side effects.

When it helps
you moved between blood-pressure pills twice and want to know which one was stopped and why.
Watch out
results are paginated, so a long history may come in several passes.

Sourcedocs.healthex.io · October 1, 2026 ↗

get_vitals

Returns your measurements, blood pressure, heart rate, temperature, breathing rate, oxygen saturation, weight, height and BMI, each with units, date, reference range and an abnormal flag.

When it helps
a cardiologist asks how your readings evolved since the last visit.

Sourcedocs.healthex.io · October 1, 2026 ↗

get_allergies

Lists allergies and intolerances with the allergen, clinical and verification status, type, criticality, onset and documented reactions.

When it helps
a dentist needs your drug allergies before prescribing an antibiotic.
Watch out
the default window is 3 years, so ask for more history when an allergy is older.

Sourcedocs.healthex.io · October 1, 2026 ↗

get_immunizations

Brings back your vaccination history: vaccine name, date given, dose number, series completion and who administered it, from childhood shots to boosters and travel vaccines.

When it helps
a new employer or a school asks for proof of a vaccine series.

Sourcedocs.healthex.io · October 1, 2026 ↗

get_conditions

Gives the list of your diagnoses and current health concerns in date order, with start dates and, for resolved or inactive ones, end dates.

When it helps
you are filling in an insurance form that asks whether you have ever had a given condition.

Sourcedocs.healthex.io · October 1, 2026 ↗

Undocumented (4)

4 tools

The directory publishes these four names and nothing more. No official text says what they do, and this page will not guess from a name.

get_health_records

This name appears in the directory's tool list and that is all there is. HealthEx's tools page does not describe it under this name, and no Claude page does either.

Watch out
whatever it does, the general approval rule below covers it.

get_lab_results

Same silence here: listed by name, described by no official text. Flagging the gap beats filling it with a guess drawn from how the name sounds.

Watch out
it falls under the same approval rule as the rest of the list.

get_care_plan

The directory carries this entry without a single line of explanation, and the publisher's tools reference skips it too. This page therefore stops at the name, on purpose.

Watch out
the default confirmation rule in the approvals section applies to it.

search_health_data

One more name the sheet lists and nobody documents: neither HealthEx nor Anthropic says what it covers or whether it modifies anything in your record.

Watch out
treat it like any action on your account, under the general approval rule described below.
Approvals

What Claude asks before acting

By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request shows up in the conversation, when it matters.

On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, keeping reads open and closing writes, and nobody overrides that from their own account. Claude works with your rights and nothing more: what HealthEx does not let you see, Claude does not see either. HealthEx describes its clinical query tools as read-only.

Plans

Which plans include it

None of the 819 sheets in the official directory shows availability by plan. That answer is published nowhere, connector by connector: a real gap in the catalogue.

The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members can connect. For the current state, check the connector's sheet in the official directory, the only place that shows it.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a new result or prescription reaches your record.

The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Only HealthEx's own documentation covers this connector, and it describes its clinical query tools as read-only: they do not edit the content of a medical record.

Need help

Need help connecting HealthEx to Claude?

A person reads every message.

FAQ

Questions about the Claude HealthEx connector

01What can Claude do with the Claude HealthEx connector?
Claude can look up parts of your health records and answer questions about them. Five tools are described by HealthEx: medications with dosing and refill history, vital signs with reference ranges, allergies with reactions and criticality, vaccinations with doses, and diagnoses with start and end dates. Four more names sit on the directory sheet with no description anywhere. History covers 3 years by default, and longer results come back in pages.
02Can Claude change or delete anything in my records?
Not with the five described tools: each reads, and HealthEx states its clinical query tools do not edit medical record content. Four listed tools have no description at all, so nobody can say what they do. HealthEx's documentation mentions a tool that requests a refresh from connected sources without letting the model change stored records, but it is not on the directory sheet. By default the sheet only exposes reading, which stays a floor: an administrator can open actions no public sheet shows.
03Does Claude ask before it acts on my health data?
By default, yes: Claude asks for confirmation before each action it carries out on an account on your behalf. No source describes a confirmation specific to any HealthEx tool, so that default rule is what covers them, including the four undocumented ones. On a Team or Enterprise workspace, owners decide whether members may let certain actions pass without being asked, and they can close writing for the whole organization. The official per-tool label only shows in a connected account's settings.
04Which plans is it available on?
No official source publishes plan availability connector by connector, and no directory sheet shows it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner has to enable a connector before members can sign in to it. The connector's own sheet in the official directory is the only place showing its current state for your account, so check it there.
05Does Claude see my whole medical history?
Not all at once, and not beyond your own access. HealthEx returns 3 years of history by default, and splits long results into pages; older data is requested with an earlier date. Claude works with your rights and nothing more, and HealthEx describes the access as resting on the patient's consent. On a Team or Enterprise workspace, an owner can also restrict what the connector may do for the whole organization.
06Why are some HealthEx tools missing or unexplained?
Because the two official sources list different catalogues. The directory sheet read on October 1, 2026 shows nine names, five of which HealthEx documents. HealthEx's tools page describes others, such as a health summary, labs and a record refresh, that the sheet does not carry. Four sheet names appear nowhere in its documentation, so this page deliberately leaves them undocumented rather than guess what they do. HealthEx's documentation is the only source specific to this connector.
07Claude or an automation tool for HealthEx?
They answer different needs, so it depends on the task. Claude works inside a conversation: you ask, it looks up the relevant part of your records and answers, and nothing else happens once you stop typing. It does not react on its own when a new result or prescription arrives. For processing that runs in the background on an event, that is the job of an automation tool. For questions about your own health, asked when you need them, the connector fits.