> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arlohealth.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Update care region

> Change the region (state/province) a conversation is licensed for. Use
when the patient is now physically somewhere different than when the
conversation was started — care is licensed by where the patient
currently is.

The new region applies to the NEXT provider request; it does not
re-route a request already in flight. To re-route an in-flight request,
cancel it first, update the region, then send a message.




## OpenAPI

````yaml /api-reference/openapi.yaml patch /api/consultations/{id}/region
openapi: 3.1.0
info:
  title: Arlo Health MCP Server
  version: 1.0.0
  description: >
    Healthcare infrastructure for AI agents. Everything an agent needs

    to act in healthcare for its user.


    ## Overview


    This server exposes two interfaces:

    - **MCP** (Model Context Protocol) over streamable HTTP at `/` for AI agents

    - **REST API** at `/api/*` for bots, skills, and direct HTTP clients


    Both interfaces use the same tool handlers and authentication.


    ## Authentication


    OAuth 2.1 with PKCE. All `/api/*` endpoints require a Bearer token.


    Discovery endpoints (no auth required):

    - `/.well-known/oauth-protected-resource`

    - `/.well-known/oauth-authorization-server`

    - `/.well-known/mcp.json` (MCP Server Card)


    ## Service Regions


    Available in Ontario, Canada (`CA-ON`) and California, United States
    (`US-CA`).
  contact:
    name: Arlo Health
    url: https://arlohealth.ai
  license:
    name: Proprietary
    url: https://arlohealth.ai/tos
servers:
  - url: https://mcp.arlohealth.ai
    description: Production MCP Server
security:
  - oauth2:
      - openid
      - profile
      - email
      - offline_access
tags:
  - name: Discovery
    description: MCP and OAuth discovery endpoints (no auth required)
  - name: Profile
    description: User profile and patient information
  - name: Consultations
    description: Healthcare consultation management
  - name: Messaging
    description: Conversation messaging and media
  - name: Prescriptions
    description: Prescription and pharmacy management
  - name: Payment
    description: Billing and pay-per-use payment management
  - name: Webhooks
    description: Webhook registration and status
paths:
  /api/consultations/{id}/region:
    patch:
      tags:
        - Consultations
      summary: Update care region
      description: |
        Change the region (state/province) a conversation is licensed for. Use
        when the patient is now physically somewhere different than when the
        conversation was started — care is licensed by where the patient
        currently is.

        The new region applies to the NEXT provider request; it does not
        re-route a request already in flight. To re-route an in-flight request,
        cancel it first, update the region, then send a message.
      operationId: updateConsultationRegion
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: Consultation/conversation ID
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - region
              properties:
                region:
                  type: string
                  description: >-
                    ISO 3166-2 code for the patient's current location (e.g.
                    US-CA, CA-ON)
                  example: US-CA
      responses:
        '200':
          description: Region updated
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  region:
                    type: string
                    description: >-
                      The normalized ISO 3166-2 region the conversation is now
                      set to
                  appliesToNextRequest:
                    type: boolean
                    description: >-
                      True when a provider request was in flight at update time
                      — that request keeps its original region
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  responses:
    BadRequest:
      description: Invalid request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unauthorized:
      description: Missing or invalid authentication
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: string
              needsAuth:
                type: boolean
  schemas:
    Error:
      type: object
      description: Error response
      properties:
        error:
          type: string
          description: Error code
        reason:
          type: string
          description: Human-readable explanation
        code:
          type: string
          description: Detailed error code
  securitySchemes:
    oauth2:
      type: oauth2
      description: OAuth 2.1 with PKCE
      flows:
        authorizationCode:
          authorizationUrl: /oauth/authorize
          tokenUrl: /oauth/token
          scopes:
            openid: OpenID Connect
            profile: User profile
            email: Email address
            offline_access: Refresh tokens

````