OpenCode + Azure API for FHIR
OpenCode runs the task; the Azure API for FHIR connector supplies only the operations and resources allowed by the account you authorize. The Composer selects OpenCode, asks for Azure API for FHIR access before sending, and keeps both choices in one task draft.
How the combination works
OpenCode plans and executes. Azure API for FHIR supplies authorized app access.
OpenCode runs the coding-agent loop in the cloud: it explores the repository, edits files, calls tools, and executes validation with the selected compatible model.
Managed, standards-based, and healthcare data platform
OpenCode
Owns the task loop, model calls, cloud computer, tool choices, progress and final result.
Azure API for FHIR connector
Supplies the currently exposed operations for the authorized Azure API for FHIR account. It does not promise every feature in the Azure API for FHIR product.
Permission boundary
The connected identity, granted provider scopes, organization policy, resource sharing and the task's explicit instruction all constrain what OpenCode can do.
Setup and first task
Connect one Azure API for FHIR account and verify one known resource.
The Composer preselects OpenCode with GPT-5.6 Sol. Start read-only when possible, then expand to write operations only after the account and resource boundary are clear.
Open the OpenCode Composer
The Composer above carries OpenCode, GPT-5.6 Sol, and Azure API for FHIR. Add a precise target and expected result; the draft stays on this page during sign-in or connector authorization.
Authorize the intended Azure API for FHIR account
Review the Azure API for FHIR account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.
Run and verify a bounded task
Name one Azure API for FHIR resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission. Open the same resource in Azure API for FHIR and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.
Access, cost and limits
What to verify before scaling OpenCode + Azure API for FHIR
Model-flexible coding work where teams want OpenCode's workflow with a wider choice of compatible model providers.
Establish with the first run
- OpenCode and GPT-5.6 Sol remain selected after sign-in.
- Azure API for FHIR shows the intended connected account before the task is sent.
- The returned data matches one known source resource, with write actions excluded until separately authorized.
Still depends on your setup
- A catalog listing does not guarantee every Azure API for FHIR website feature is available as an agent operation.
- OAuth scopes do not replace organization policy, resource sharing or a precise task instruction.
- Total task cost can include model tokens, active computer time, paid tools, connectors and the provider's own plan or quota.
Verification and recovery
Check Azure API for FHIR itself before trusting the result.
Open the same resource in Azure API for FHIR and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.
Connection troubleshooting
If Azure API for FHIR access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.
Writes need explicit scope
Name the target record and exact allowed change. A request to summarize, analyze or draft does not authorize sending, publishing or deleting.
Re-check current state
For decisions or follow-up writes, open the resource in Azure API for FHIR and check its current state. A successful earlier read may already be stale.
Common questions
Related resources
OpenCode
Review OpenCode's supported models, capabilities and browser Composer.
Azure API for FHIR connector
Review the application-specific authorization and first-task guide.
OpenCode + GPT-5.6 Sol
Review the current default agent and model combination.
Pricing
Review model, active-computer, tool and connector charges.