> For the complete documentation index, see [llms.txt](https://docs.mymedtrics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mymedtrics.com/api-reference/graphql-gateway/health-and-audit.md).

# Health and audit

Whether each integration is working, and who changed what.

Whether each integration is working, and who changed what. 5 queries; send any of them to the endpoint on the [GraphQL gateway](/api-reference/graphql-gateway.md) page, the same way as the first query there.

### integrationHealth

A health summary per enabled integration — the first page only.

Arguments: **`institutionId`** (ID, required) · `first` (Int)

```graphql
query {
  integrationHealth(institutionId: "…", first: 20) { institutionIntegrationId institutionId integrationId integrationName integrationSlug }
}
```

Returns `[IntegrationHealthSummary!]!`:

#### IntegrationHealthSummary

| Field                      | Type                   |
| -------------------------- | ---------------------- |
| `institutionIntegrationId` | `ID!`                  |
| `institutionId`            | `ID!`                  |
| `integrationId`            | `ID!`                  |
| `integrationName`          | `String!`              |
| `integrationSlug`          | `String!`              |
| `category`                 | `IntegrationCategory!` |
| `isEnabled`                | `Boolean!`             |
| `activationMode`           | `ActivationMode!`      |
| `syncStatus`               | `SyncStatus!`          |
| `lastSyncAt`               | `String`               |
| `currentHealth`            | `HealthStatus!`        |
| `lastLatencyMs`            | `Int`                  |
| `lastHealthCheck`          | `String`               |
| `checksLast24h`            | `Int!`                 |
| `healthyChecks24h`         | `Int!`                 |
| `avgLatency24h`            | `Float`                |

### healthConnection

The same health summaries, paged with cursors.

Arguments: **`institutionId`** (ID, required) · `first` (Int) · `after` (String)

```graphql
query {
  healthConnection(institutionId: "…", first: 20) { edges { cursor node { institutionIntegrationId institutionId integrationId integrationName integrationSlug } } }
}
```

Returns `IntegrationHealthConnection!`:

#### IntegrationHealthConnection

| Field      | Type                        |
| ---------- | --------------------------- |
| `edges`    | `[IntegrationHealthEdge!]!` |
| `pageInfo` | `PageInfo!`                 |

Nested: `edges` → [`IntegrationHealthEdge`](/api-reference/graphql-gateway/types.md#integrationhealthedge), `pageInfo` → [`PageInfo`](/api-reference/graphql-gateway/types.md#pageinfo).

### integrationHealthConnection

Same as healthConnection; kept for existing clients.

Arguments: **`institutionId`** (ID, required) · `first` (Int) · `after` (String)

```graphql
query {
  integrationHealthConnection(institutionId: "…", first: 20) { edges { cursor node { institutionIntegrationId institutionId integrationId integrationName integrationSlug } } }
}
```

Returns `IntegrationHealthConnection!` — fields as under [IntegrationHealthConnection](#integrationhealthconnection) above.

### integrationAuditLog

Configuration changes to integrations — who did what, when; offset paging.

Arguments: **`institutionId`** (ID, required) · `integrationId` (ID) · `actionType` (String) · `limit` (Int) · `offset` (Int)

```graphql
query {
  integrationAuditLog(institutionId: "…") { logId institutionId institutionName institutionIntegrationId integrationName }
}
```

Returns `[IntegrationAuditEntry!]!`:

#### IntegrationAuditEntry

| Field                      | Type                   |
| -------------------------- | ---------------------- |
| `logId`                    | `ID!`                  |
| `institutionId`            | `ID!`                  |
| `institutionName`          | `String`               |
| `institutionIntegrationId` | `ID!`                  |
| `integrationName`          | `String!`              |
| `integrationSlug`          | `String!`              |
| `category`                 | `IntegrationCategory!` |
| `actionType`               | `String!`              |
| `status`                   | `String!`              |
| `actorId`                  | `ID`                   |
| `actorName`                | `String`               |
| `loggedAt`                 | `String!`              |

### integrationActivityLog

Runtime activity of one enabled integration (syncs, deliveries, errors).

Arguments: **`institutionIntegrationId`** (ID, required) · `activityType` (String) · `limit` (Int)

```graphql
query {
  integrationActivityLog(institutionIntegrationId: "…") { id institutionIntegrationId activityType status createdBy }
}
```

Returns `[IntegrationActivityEntry!]!`:

#### IntegrationActivityEntry

| Field                      | Type      |
| -------------------------- | --------- |
| `id`                       | `ID!`     |
| `institutionIntegrationId` | `ID!`     |
| `activityType`             | `String!` |
| `status`                   | `String!` |
| `createdBy`                | `ID`      |
| `createdAt`                | `String!` |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mymedtrics.com/api-reference/graphql-gateway/health-and-audit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.