Platform Concepts

Core Concepts

Understand the fundamental building blocks of the HealthCloud platform — from organizations and projects to agents, workflows, and the clinical knowledge graph.

Platform Model

HealthCloud is built around a set of core primitives. Everything in the platform is expressed as one of these objects.

🏢

Organizations

Top-level entity representing a company or institution using HealthCloud.

📁

Projects

Scoped workspace within an organization for isolating use cases and environments.

🧱

Assets

Reusable components including apps, agents, AI models, datasets, and connectors.

🚀

Deployments

A running, configured instance of an asset in a specific environment.

🤖

Agents

AI-powered workers that execute clinical, administrative, or data tasks autonomously.

🔄

Workflows

Orchestration logic that coordinates agents, APIs, and data across steps.

📊

Data

FHIR-native clinical data including Patients, Observations, Conditions, and Encounters.

🏢01

Organization

Represents a company or entity using HealthCloud. An organization is the root container for all resources.

  • Manages users and role-based access control
  • Holds billing information and subscription plan
  • Owns API keys and environment credentials
  • Scopes all data and deployments
JSON
{
  "id": "org_healthcheck_pmc",
  "name": "HealthCheck PMC",
  "plan": "enterprise",
  "created_at": "2026-01-01T00:00:00Z"
}
📁02

Project

A workspace within an organization. Projects let you group assets, manage environments, and isolate different use cases.

  • Groups related assets and deployments
  • Supports sandbox, staging, and production environments
  • Isolates billing and usage metrics per use case
  • Teams can be scoped to individual projects
JSON
{
  "id": "proj_uti_screening",
  "organization_id": "org_healthcheck_pmc",
  "name": "UTI Screening",
  "environment": "production"
}
🧱03

Assets

Assets are the building blocks of the HealthCloud platform. Everything installable is an asset.

  • Applications — full clinical or operational apps
  • Agents — AI workers that execute specific tasks
  • AI Models — clinical prediction and inference models
  • Datasets — curated clinical and synthetic data
  • Connectors — EHR, lab, payer, and device integrations
JSON
{
  "id": "agent_prior_auth_v1",
  "type": "agent",
  "name": "Prior Authorization Agent",
  "publisher": "HealthCloud",
  "version": "1.2.0",
  "status": "available"
}
🚀04

Deployments

A deployment is a running, configured instance of an asset. Installing an asset does not run it — you must deploy it.

  • Bind an asset to a specific project and environment
  • Configure runtime parameters (API endpoints, credentials)
  • Monitor performance, uptime, and cost
  • Scale horizontally for high-volume workflows
JSON
{
  "id": "dep_prior_auth_prod",
  "asset_id": "agent_prior_auth_v1",
  "project_id": "proj_uti_screening",
  "environment": "production",
  "status": "active",
  "deployed_at": "2026-03-01T09:00:00Z"
}
🤖05

Agents

Agents are AI-powered components that perform tasks autonomously. They are the execution units of the HealthCloud platform.

  • Eligibility verification against payer APIs
  • Clinical triage based on symptom intake
  • Prior authorization submission and tracking
  • Diagnostic interpretation of lab and device data
  • Care coordination and follow-up scheduling
JSON
{
  "id": "agent_prior_auth",
  "capabilities": [
    "eligibility_check",
    "form_submission",
    "status_tracking"
  ],
  "supported_payers": ["CMS", "Aetna", "United"],
  "avg_response_ms": 340
}
🔄06

Workflows

Workflows orchestrate agents, APIs, and data across a sequence of steps. They define the logic of your healthcare application.

  • Define step sequences with conditional branching
  • Trigger on events (webhook, schedule, manual)
  • Pass data between agents automatically
  • Handle retries, errors, and escalations
JSON
{
  "name": "UTI Screening Workflow",
  "trigger": "patient.intake_submitted",
  "steps": [
    "collect_symptoms",
    "run_diagnostic_model",
    "generate_lab_order",
    "notify_provider"
  ]
}
🧠07

Knowledge Graph

The platform maintains a live graph of clinical relationships enabling context-aware AI and explainable recommendations.

  • Patient → Condition → Observation links
  • Condition → Model → Dataset traceability
  • Workflow → Agent → Decision audit paths
  • Continuous updates from new clinical events
🔌08

Integrations

Assets can connect to external systems via first-class integration objects. You configure — not build — integrations.

  • EHR systems: Epic, Cerner, Athenahealth
  • Lab networks: Quest, LabCorp, BioReference
  • Pharmacy: Surescripts, retail chains
  • Payers: CMS, commercial plans, clearinghouses
  • Devices: RPM, wearables, IoMT sensors
📡09

Events & Webhooks

HealthCloud is event-driven. Every meaningful platform action emits a structured event you can subscribe to.

  • deployment.created — new deployment is live
  • workflow.completed — workflow execution finished
  • diagnostic.result_ready — AI result available
  • patient.alert_triggered — clinical alert fired
🔐10

Permissions

Fine-grained access control ensures data is only accessible to authorized principals at every scope level.

  • Organization level — global admin roles
  • Project level — developer and operator roles
  • Asset level — install, configure, deploy, run
  • Data level — PHI field-level masking
💡11

Putting It Together

A complete clinical application built on HealthCloud follows this sequence from concept to production.

  • 1. Create organization and project
  • 2. Install a diagnostic agent from the marketplace
  • 3. Configure EHR integration (Epic FHIR connector)
  • 4. Deploy the agent to production environment
  • 5. Create a workflow connecting intake → diagnosis → notify
  • 6. Subscribe to diagnostic.result_ready events
  • 7. Monitor performance in Studio command center

Platform Event Reference

Every meaningful action in HealthCloud emits a structured event. Subscribe via webhooks to build reactive, event-driven healthcare systems.

EventDescriptionCategory
deployment.createdAn asset was successfully deployed to an environmentDeployment
deployment.failedA deployment attempt failed with an errorDeployment
workflow.startedA workflow execution has begunWorkflow
workflow.completedA workflow execution finished successfullyWorkflow
workflow.failedA workflow execution encountered an unrecoverable errorWorkflow
diagnostic.result_readyAn AI diagnostic model produced a resultClinical
patient.alert_triggeredA clinical alert threshold was crossedClinical
asset.installedAn asset was installed into a projectMarketplace

Permission Model

Fine-grained access control ensures every resource is only accessible to authorized principals at the appropriate scope.

🔐

Organization Scope

Global administrative capabilities across all projects

  • manage_billing
  • manage_users
  • manage_api_keys
  • view_audit_logs
🔐

Project Scope

Scoped to a specific project workspace

  • install_assets
  • configure_integrations
  • deploy_assets
  • view_metrics
🔐

Asset Scope

Fine-grained control on individual assets

  • read
  • configure
  • deploy
  • run
  • monitor

Ready to Get Started?

These concepts come to life the moment you open Studio. Create your first project, install an asset, and run a workflow — all in under 10 minutes.