Set Consultation Context

You are integrating Telepatia Synapse Public API.

Endpoint: POST /v1/set-consultation-context
Base URL: https://synapse.telepatia.ai
Auth: Authorization: Bearer ${SYNAPSE_API_KEY}

Request:
- name [body]: string (required, minLength=1, maxLength=500)
- idCountry [body]: string (required, enum: 250 values) — ISO 3166-1 alpha-2 country codes. Mirrors tanjiro's CountryCodes enum.
- idType [body]: string (required, enum: 8 values) — Supported patient identification document types.
- idValue [body]: string (required, minLength=1, maxLength=50)
- notes [body]: string (optional, maxLength=10000)
- pastMedicalHistory [body]: string (optional, maxLength=10000)
- consultationInternalId [body]: string (optional, pattern=^[a-zA-Z0-9_-]{1,128}$, maxLength=128)
- scribeSessionModality [body]: string (optional, enum: IN_PERSON, TELEMEDICINE) — Supported scribe session modalities.
- scribeSessionConfigurationId [body]: string (optional, maxLength=128)
- medicalRecordConfigurationId [body]: string (optional, maxLength=128)
- medicalRecordConfiguration [body]: object (optional) — Inline medical record configuration JSON keyed by section name (e.g. 'chiefComplaint'). Auto-persisted and deduplicated by content hash; the resolved configuration id is attached to the doctor context buffer. Mutually exclusive with `medicalRecordConfigurationId` and `scribeSessionConfigurationId`.

Success 200:
- success: boolean
- consultationInternalId: string

Errors (envelope: { error: { type, code, message, param? } }):
- 400: parameter_missing, parameter_invalid, account_invalid
- 401: authentication_required
- 404: resource_not_found
- 409: resource_conflict
- 503: service_unavailable

Generate code in the language of the current file that:
1. Reads SYNAPSE_API_KEY from env (do not hardcode it).
2. Calls the endpoint with typed request and response.
3. Maps the error envelope to typed exceptions per status code.
4. Adds one happy-path test using the Bearer token.