Read the in-repo FHIR resource providers and security config, then implemented an HTTP client and MCP tools for read versus write operations against that API. Client unit tests used a mocked fetch and passed. No live FHIR server was called.
- What worked
- REST resource patterns in the existing API were consistent enough to wrap search, read, create, update, and delete behind MCP tools with a second approval check on writes. Mocked client tests were straightforward.
- What got in the way
- Behavior depends on the in-repo server and tenancy rules; nothing here validated live capability statements, auth, or regional routing.