Skip to Content
Chats

Chats

Wave is built around conversation. Whether you’re brainstorming with the AI, tracking integration progress, or making quick mapping tweaks, chat is where you get things done.

Types of Chats

1. Project Chat

  • Scoped to a project: Every project has its own chat, visible to your whole team.
  • Context-aware: Project chats can reference all project files, mappings, and profiles. Ask Wave about your integration plan, generate new code, or discuss mapping logic in context.
  • Persistent: All messages and generated artifacts are saved with the project for easy reference and auditability.
  • Collaboration: Mention teammates, profiles, or files (@ProfileName, @field, etc.) to bring everyone into the loop.

2. One-off Chat

  • Standalone: Use the “New Chat” button for quick questions, code snippets, or mapping advice without spinning up a full project.
  • No file/mapping creation: You can reference existing org-wide profiles, but can’t create or persist new ones from a one-off chat.
  • Great for…
    • Quick “how do I map X to Y?” questions
    • Testing data profile extraction from a PDF or schema
    • Exploring what’s possible before starting a full project
  • Convert to project anytime: If your ad hoc chat turns into real work, just promote it to a project and unlock all features.

Smart Referencing

  • Direct mention: Use @ to reference profiles, files, or even mappings directly in chat.
  • Agent awareness: The AI understands your org’s profiles — mention “the OMOP profile” and it’ll know what you mean.

Use Cases

  • Ask for help: “How do I map birthsex from OMOP to FHIR USCDI?”
  • Generate code: “Write Python code to transform my lab results CSV into the FHIR Observation resource.”
  • Update mapping: “Update the race field mapping to use US Core codes.”
  • Explain a field: “What does the status field mean in the Patient profile?”

Pro Tip

You can edit anything in context: Ask the agent to update a mapping, refine a profile, or generate a new code snippet — all without leaving chat.


Next up: How Integration Plans keep your project on track →