Healthcare agent service
Healthcare agent service instance with built-in triage, medical content and healthcare safeguards.
- Provider
- azure
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autoscaling | boolean | — | no | false | ▸ true |
| channel | enum | web-chat | teams | management-api | no | — | inherited |
| criticality | enum | low | medium | high | no | medium | inherited |
| encryptionAtRest | boolean | — | no | true | inherited |
| healthcareSafeguards | boolean | — | no | true | inherited |
| hipaaReady | boolean | — | no | true | inherited |
| instancePerEntity | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| ownsData | boolean | — | no | true | ▸ true |
| runtime | string | — | no | — | inherited |
| shardingStrategy | enum | none | consistent-hash | range | lookup | no | none | inherited |
| singleWriter | boolean | — | no | false | inherited |
| stateless | boolean | — | no | true | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
A service that calls a third party synchronously, with no queue or workflow engine attached, has nowhere to park the request when the third party is slow or down. The failure becomes the user's problem instead of a retried job.
- — all of these hold:
- — the node has at least one synchronous outgoing edge to a third-party-api
- — this does not hold:
- — the node has at least one connected edge joining a workflow-engine or queue
Calling a worker synchronously puts the background job on the request path. The caller waits for the slowest part of the fan-out.
- — the node has at least one synchronous outgoing edge to a worker
A stateful service on a consistent hash ring needs something that owns the ring: detect a dead host, pick a replacement, tell everyone. Without a coordination service the ring is edited by hand during the outage.
- — all of these hold:
- — the node's `shardingStrategy` is "consistent-hash"
- — this does not hold:
- — the node has at least one connected edge joining a coordination-service
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "health-bot", component: "azure-health-bot" }# yaml-language-server: $schema=../../schema/component.schema.json # Health Bot (healthcare agent service): a multitenant instance that runs healthcare copilots with a built-in triage and symptom checker and healthcare safeguards. # "Overview - Healthcare agent service" states each instance is a multitenant cloud platform that scales with resilience, is HIPAA-ready, stores customer data in Azure Storage and Cosmos DB that are always encrypted at rest with Microsoft-managed keys, and only accepts data connections over HTTPS. schemaVersion: "1" type: "component" id: "azure-health-bot" kind: "app-server" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure/health-bot/overview" defaults: managed: true autoscaling: true ownsData: true properties: encryptionAtRest: type: "boolean" default: true hipaaReady: type: "boolean" default: true healthcareSafeguards: type: "boolean" default: true channel: type: "enum" values: ["web-chat", "teams", "management-api"]