A workspace scoped to one case
Literature, guidelines, laboratory results and discharge summaries are uploaded to the workspace for a specific case. Answers are produced from that workspace and nothing else — the boundary is the product.
Case-scoped clinical workspaces that answer only from the documents placed in them, with file-and-page citations.
The medical vertical of the CoralMeshAI sectoral second-brain platform, serving two audiences behind one account-type selection. Clinicians open a workspace per case and upload the material that case rests on — literature, guidelines, laboratory results and discharge summaries — then ask questions answered strictly from the contents of that workspace and nothing outside it. Every answer carries the file and page it derives from, and drug-interaction and vital-risk warnings are surfaced rather than left inside a paragraph. Patients receive a different surface: an assistant over their own documents, built on three published workflows covering medication and dosage information, laboratory result interpretation and clinical study analysis. iOS first; the backend contract is specified against FastAPI, Weaviate and Dify, and the application currently runs against a mock client while that service is built.
Literature, guidelines, laboratory results and discharge summaries are uploaded to the workspace for a specific case. Answers are produced from that workspace and nothing else — the boundary is the product.
Every answer indicates the file and the page it derives from, so a clinician can verify the source rather than accept a summary.
Drug-interaction and vital-risk findings are raised out of the answer body and marked, rather than left for the reader to notice inside a paragraph.
An account-type picker separates the clinician surface from the patient surface. Clinicians work in case workspaces; patients get an assistant over their own documents.
Medication and dosage information, laboratory result interpretation and clinical study analysis are delivered as separate prepared workflows rather than a single general-purpose chat.
Patients build their own retrieval library from their records, so the assistant answers about their own history rather than in general terms.
The medical vertical is one instance of a shared second-brain architecture; the legal and engineering verticals are specified in the same platform but deliberately not yet implemented.
Portfolio products serving the same audience.
No per-seat licensing, no vendor lock-in, no unpredictable invoicing. Our teams are available to scope an evaluation for any product in the portfolio.