The healthcare demo pack groups synthetic events into 13 sandbox domains with FHIR R4 resources, HL7 message types, payer rule stubs, and optional multi-step scenarios. It's one of the packs in the connector catalog — agents reach it through a scoped connection exactly like any other target, and no real PHI ever touches the control plane.
Sandbox domains
| Domain | Description |
|---|---|
| clinical_adt | Admit, discharge, encounter, and observation events. |
| documents_fax | Inbound fax and document triage workflows. |
| medications | Medication requests, approvals, and denials. |
| orders_results | Clinical orders and diagnostic results. |
| scheduling | Appointment booking and cancellation. |
| prior_auth | Prior auth lifecycle with EOB scenarios and Claim/EOB resources. |
| referrals | Inbound referrals, scheduling, and completion. |
| rcm_claims | Claim submission, adjudication, denial, and payment. |
| eligibility | Coverage eligibility checks and inactive coverage. |
| webhook_reliability | Delivery retry, replay, and fault-injection observability. |
| mpi | Patient match, duplicate reconciliation, and identity linking. |
| credentialing | Practitioner onboarding and credential verification lifecycle. |
| aggregator | Cross-source aggregation with consent and provenance artifacts. |
Catalog discovery
The catalog is a list of all the domains and their descriptions. It can be discovered by sending a GET request to the /v1/sandbox/catalog endpoint.
Run a prior auth scenario
The scenario is a multi-step workflow that simulates a prior auth request. It can be run by sending a POST request to the /v1/sandbox/scenarios/{id}/run endpoint.
Inject HL7
Templates cover ADT admit, referral intake, prior auth submit, claim submit, eligibility check, and appointment scheduling. Injected messages map through your connection's HL7→FHIR rules and fire signed webhooks.
The HL7 templates are a list of all the HL7 templates and their descriptions. It can be injected by sending a POST request to the /v1/sandbox/hl7/inject endpoint.
Agent tooling
Agents reach these domains the same way as any other target: open a scoped connection to demo-fhir-synthetic (scopes like Patient:read,Encounter:read,period:2025-Q4), then query. Via hosted MCP that's discover_data_sources → connect_to_data_source → query_data_source; via the CLI it's hebrah inspect demo-fhir-synthetic → hebrah connect. See the MCP guide, the API guide, and Connectors.