Patient-authorized EHR integration

MCP tools

The authenticated MCP server's tools and the REST operation each mirrors.

- `get_app`: Your application and its environment. REST: `GET /app`
- `list_users`: Subjects that have shared records with your app. REST: `GET /users`
- `get_health_record`: A subject's normalized record. REST: `GET /users/{subject}/records`
- `get_category_records`: One category, paginated. REST: `GET /users/{subject}/records/{category}`
- `get_record_changes`: Changes since a cursor. REST: `GET /users/{subject}/records/{category}/changes`
- `get_consent_receipt`: One consent receipt. REST: `GET /consents/{receiptId}`
- `create_connect_session`: Start a Connect session. REST: `POST /connect/sessions`
- `get_connect_session`: Session status and subject. REST: `GET /connect/sessions/{sessionId}`
- `cancel_connect_session`: Cancel an open session. REST: `POST /connect/sessions/{sessionId}/cancel`
- `simulate_connect_session`: Complete a sandbox session with a scenario. REST: `POST /connect/sessions/{sessionId}/simulate`
- `trigger_sandbox_event`: Drive a synthetic patient event. REST: `POST /sandbox/subjects/{subject}/events`
- `start_conformance_run`: Start a conformance run. REST: `POST /conformance/runs`
- `get_conformance_run`: Run state and checks. REST: `GET /conformance/runs/{runId}`
- `advance_conformance_run`: Move a run to its next step. REST: `POST /conformance/runs/{runId}/advance`