# Ports ``ConvertFHIRToCCDAWithChunking``

Operation ID: `connectors.grokConvertFhirToCcdaWithChunking`

Ports ``ConvertFHIRToCCDAWithChunking``. Splits the FHIR JSON into <=3000-char chunks (lists converted to index-keyed dicts), converts each chunk to a CCDA XML chunk (5000 max_tokens per chunk by default), then combines everything under a ``<Root>`` element. Chunks that come back as invalid XML are skipped with a logged warning.

## Public method

`convertFhirToCcdaWithChunking`

Signature: `connectors.grok.createClient(config).convertFhirToCcdaWithChunking(body)`

Return type: `Promise<GrokConvertFhirToCcdaWithChunkingResult>`

## Authentication

Classification: **AUTHENTICATED**

Schemes: `bearerAuth`

## Prerequisites

None documented.

## HTTP

`POST /connectors/grok/convert-fhir-to-ccda-with-chunking`

## Path parameters

None.

## Query parameters

None.

## Body parameters

| Name | Type | Required | Format | Allowed values | Default | Nullable | Description |
|---|---|---:|---|---|---|---:|---|
| `body` | [`GrokConvertFhirToCcdaWithChunkingRequest`](../models/GrokConvertFhirToCcdaWithChunkingRequest.md) | Yes |  |  |  | No |  |

Request model: [`GrokConvertFhirToCcdaWithChunkingRequest`](../models/GrokConvertFhirToCcdaWithChunkingRequest.md)

## Request example

```json
{
  "api_key": "example-api-key",
  "api_url": "https://example.com/resource",
  "content": "example-content",
  "max_tokens": 1,
  "mode": "sandbox",
  "model": "example-model"
}
```

## Success responses

| Status | Shape | Content type | Description |
|---|---|---|---|
| `200` | [`GrokConvertFhirToCcdaWithChunkingResponse`](../models/GrokConvertFhirToCcdaWithChunkingResponse.md) | application/json | Successful response |

## Success response examples

### 200

```json
"example-convert-fhir-to-ccda-with-chunking"
```

## Common errors

| Status | Shape | Content type | Description |
|---|---|---|---|
| `400` | [`StandardErrorResponse`](../models/StandardErrorResponse.md) | application/json | Connector validation rejected the payload, or a required field was missing or of the wrong type. |
| `401` | [`StandardErrorResponse`](../models/StandardErrorResponse.md) | application/json | The HealthCloud bearer token is missing or invalid, or the vendor rejected the supplied connector credentials. |
| `500` | [`StandardErrorResponse`](../models/StandardErrorResponse.md) | application/json | The connector failed unexpectedly. |
| `502` | [`StandardErrorResponse`](../models/StandardErrorResponse.md) | application/json | The vendor returned an application or transport-level failure. |
| `504` | [`StandardErrorResponse`](../models/StandardErrorResponse.md) | application/json | The vendor did not respond within the connector timeout. |

## Error examples

### 400 — Invalid request

```json
{
  "error": "Invalid request"
}
```

### 401 — Authorization required

```json
{
  "error": "Authorization required"
}
```

### 500 — Internal error

```json
{
  "error": "Internal error"
}
```

### 502 — Upstream vendor error

```json
{
  "error": "Upstream vendor error"
}
```

### 504 — Upstream timeout

```json
{
  "error": "Upstream timeout"
}
```

## NodeJS / TypeScript implementation

```ts
import { HCSDK } from "@healthcloudai/hc-sdk";
import type { GrokConvertFhirToCcdaWithChunkingRequest } from "@healthcloudai/hc-sdk";
```

```ts
const body = {
  "api_key": "example-api-key",
  "api_url": "https://example.com/resource",
  "content": "example-content",
  "max_tokens": 1,
  "mode": "sandbox",
  "model": "example-model"
};

const result = await connectors.grok.createClient(config).convertFhirToCcdaWithChunking(body);
```

## cURL

```bash
curl -X POST \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"api_key":"example-api-key","api_url":"https://example.com/resource","content":"example-content","max_tokens":1,"mode":"sandbox","model":"example-model"}' \
  'https://dev-api-connectors.health.cloud/connectors/grok/convert-fhir-to-ccda-with-chunking'
```

## Notes

None.

## Prepared Test Console scenario

No canonical scenario is currently associated.

## Real response

No approved real integration response is currently published. Unapproved candidates are never rendered as examples.