The Context Engine Studio is now open source.  View on GitHub →
Clinia

What the Context Engine Studio Is

The open-source tool for understanding how the engine handles a patient's records.

The Context Engine Studio is an open-source app, under the Apache-2.0 license, that you run on your own machine against your workspace. The studio lets you ingest a patient's records, browse what the engine made of them and ask a chat assistant about the patient.

Every action in the studio is a call to the Context Engine API, so the studio shows how the engine handles a record before you build your own integration. Its code is also a reference for connecting an app and an agent to a workspace, as described in Use the Studio as a Starting Point for Your App.

The studio with a patient open: the virtual file system in the sidebar and a chat with the assistant

How the studio connects to your workspace

The studio's server sends its requests to three places:

  • The workspace's REST API, through @clinia/context-engine-js, to create and delete patients, ingest FHIR and CDA files, list ingestions, browse and read the VFS, and import chats as sessions.
  • The workspace's MCP server, at the workspace URL followed by /mcp, for the chat assistant's tools and its system prompt.
  • The Anthropic API, for the chat assistant's model.

Both workspace channels share one OAuth token, which the studio obtains from the client credentials set in your local environment file.

The studio keeps no copy of the patient records, which stay in the workspace. It stores only the chat history on your machine, and imports each chat into the workspace as a session, which forms Learned Memory for the patient.

What the studio is for

The studio serves three uses:

  • Exploring the engine before writing code, by ingesting a record and reading the patient's VFS files and condition stories.
  • Trying the engine on your own de-identified records, to see how it handles the data your systems produce.
  • Learning how to build on the engine, by reading the studio's code as a reference for your own integration.

The studio is a developer tool that you run yourself, which Clinia neither hosts nor supports as an end-user product. You do not need it to use the engine, since everything it does is available through the API.

How the repository is maintained

The clinia/context-engine-studio repository is a read-only copy that Clinia publishes on each release, with the same version number as the engine and its clients. What changed in each version is listed in the changelog, which covers the studio and the engine together.

Each kind of request has its own channel.

You haveGo to
A question about the studio, or an ideaGitHub Discussions
A bug in the studioGitHub Issues
A workspace, credential, ingestion or API problemsupport@clinia.com

Next steps

On this page