For programs & institutions
A controlled institutional workspace for approved non-PHI knowledge.
MARCUS is preparing a bounded pilot lane for curated protocols, guidelines, pathways, policies, and research procedures. It is not approved for PHI, patient-specific content, or autonomous clinical decisions.
Every July, three years of working knowledge walks out the door.
Interns arrive. The departing seniors take what they learned with them. The shared drive has 400 files, half of them outdated and none of them connected. The chief’s handbook from two years ago lives in someone’s Google Drive — maybe.
Residents spend their first months asking the same questions their predecessors asked. Attendings answer the same curbside consults they answered last year. The protocols exist, but no one can find them at 2 AM, mid-call, with five minutes to act.
This isn’t a search problem. It’s a memory problem — and it repeats every academic cycle until someone writes it down somewhere that holds.
One library for everything your program knows.
MARCUS processes documents your institution approves for the pilot — protocols, guidelines, pathways, policies, and research procedures — as a searchable, source-grounded library. Users can ask questions and inspect the passages and citations returned with a response.
The institution remains responsible for source authority and classification. MARCUS must verify file handling, extraction, chunking, indexing, version identity, and access before a source is pilot-ready.
A citation is evidence to inspect, not a guarantee that every generated statement is correct. Pilot assessment separates security and isolation, source integrity and version authority, and answer support and citation fidelity.
Approval first, then a bounded pilot.
Institutional use starts with explicit scope, named owners, and evidence gates. The proposed path is:
Phase 1
Define the approved non-PHI scope.
The information owner identifies a curated corpus and classifies each source as public, internal institutional, restricted non-PHI, or prohibited. PHI and patient-specific material stay out of the workspace.
Phase 2
Complete institutional review.
Named product, security, privacy, legal, and institutional owners review deployment isolation, access, custody, retention, provider settings, incident ownership, and the exact pilot charter. Approval requirements depend on the institution and hosting context.
Phase 3
Run a bounded evidence pilot.
A fixed, named user cohort works only with the approved corpus. The pilot records custody and evidence receipts, indexing checks, access and audit evidence, incidents, closeout reconciliation, and deletion proof before any broader use.
This page is not institutional approval or an invitation to upload institutional material. A pilot can begin only after the trust packet is approved for customer use and the institution ratifies the exact charter, deployment, data classes, cohort, and closeout plan.
For program directors and GME offices
The proposed controlled-pilot contract.
Curated institutional corpus
Approved protocols, guidelines, pathways, policies, and research procedures can be organized into a bounded non-PHI workspace.
Named access roles
Pilot participants and administrators are named in the charter, assigned least-privilege roles, and reconciled at closeout.
Source-grounded responses
Answers are designed to carry source passages and citations. Pilot evaluation measures source authority, evidence coverage, citation fidelity, and unsupported claims separately.
Inspectable custody
The pilot defines what is retained, where it lives, who can access it, provider processing, retention settings, deletion behavior, and the evidence needed to prove closeout.
Evidence before expansion
A pilot does not establish paid-deployment or PHI readiness. Expansion depends on documented acceptance evidence and named institutional approvals.
The people who feel this problem
The program director who gets the same Slack message every July: “Where do I find the call schedule template?”
The chief resident who built a beautiful Notion wiki that died six months after they graduated.
The GME office trying to standardize training resources across 15 programs, each with its own SharePoint graveyard.
The attending who answered the same protocol question from four different residents this week and wondered why the answer isn't just... somewhere.
The new intern on their first night of call who needs to know the insulin drip protocol and doesn't know who to ask at 3 AM.
How to start
Start with a scope conversation. Identify the information owner, the candidate non-PHI corpus, the proposed named cohort, and the institution’s required review path. Do not upload institutional material through self-service signup.
A controlled pilot is separate from a paid institutional deployment. Commercial terms, support commitments, service levels, deployment options, and procurement evidence require written review and are not promised by this page.
A note on security
MARCUS implements security controls in code, including scoped authorization and role checks, but code presence is not deployed assurance. Tenant isolation, encryption, provider controls, logging, telemetry, retention, deletion, backup and restore, and incident readiness must be evidenced for the exact pilot deployment.
The initial institutional lane is non-PHI only. It is not a security certification, paid-service commitment, or authorization for PHI use.
→ Read our security & privacy page