Developer guide

Build with Tross MCP.

Tools, approvals and data handling.

Connect your assistant

Get the current server URL and setup steps for your client.

Use the tools

Keep sandbox changes between calls

Pass the returned sandbox_session on subsequent calls to preserve changes across turns and reconnects within the sandbox.

Discovery, reads and approvals

List permitted connections with tross_list_connections.
Find an operation with tross_search_operations and inspect its schema with tross_get_operation.
Collect required inputs. Select encounters by encounter ID.
Call tross_execute_read or tross_prepare_write.
An authorized person reviews the proposal in Tross and selects Approve and execute.
Poll tross_get_action or tross_get_run. Follow result pagination when present.

Uploads and downloads

Call tross_create_upload, upload through the returned page or API, then pass the attachment ID in your proposal. Local file paths are not uploads. Staged files expire after one hour.

Call tross_get_file and open its download_pageto sign in and download. Agents can use download_url with their OAuth token.

Permissions and data

Choose permitted connections and operations. Every write needs human approval in Tross; agents cannot approve their own actions.

To change access, open Connections and select Edit access. An organization administrator saves the selection; then ask your assistant to list connections again.

Approval and data handling

Grants bind the user, organization, client, connection and operations. Revocation applies to reads, writes, approvals, polling and files.
Proposals bind exact values and attachment checksums and expire after 15 minutes. Changes require a new proposal.
Uncertain writes return outcome_unknown and are never automatically retried.
Clinical data is restricted to authorized callers. Audit events contain actors and timestamps, not clinical payloads, cookies or raw logs.

Clients and available workflows

Connect through ChatGPT, Claude, Claude Code or an MCP client using Streamable HTTP and OAuth. Your Tross connection and selected permissions determine which workflows are available.

Provider coverage and limits

Browse the capability directory for supported operations and inputs. Ask your assistant to list connections to see the operations enabled for your account.

eCW encounter lists contain up to 50 records; a missing entry does not prove that an encounter is absent. Some punctuation is normalized by eCW. Verify the saved record after a write.

Try a workflow without a production connection

The sandbox uses isolated demo records. Approved changes and files remain available in the same session. Production connects to your provider account with the access you approve.

Troubleshooting

`permission_denied`	Open Connections → Edit access. Ask an organization administrator to enable the required operation, then list connections again.
`insufficient_scope`	Reconnect your assistant with the requested Tross permissions, then check connection access.
`grant_changed`	Close and reopen the access editor to review the current selection before saving.
`session_expired`	Reconnect the provider account in Tross.
`invalid_input`	Check the operation schema and required identifiers.
`attachment_expired`	Upload the file again and create a new proposal.
`outcome_unknown`	Do not retry. Check the provider record and reconcile with Tross support.
`capacity_limit`	Wait for the active operation to finish before retrying a read.