For programs & institutions
The memory your program built, kept.
Your residents are already looking for the local answer. MARCUS is where that local answer is written down, connected, and still reachable after the people who wrote it have moved on.
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 holds the documents your program already produces — protocols, guidelines, handbooks, clinical references, departmental policies — together as one connected library. Ask a question in natural language, get an answer that points back to the source.
No manual tagging. No wiki maintenance. No single person responsible for keeping it alive. Add the documents and the program can search them immediately.
A resident on night float pulls up the post-op feeding protocol for Roux-en-Y patients in seconds. A new intern finds the central line checklist without paging a senior. An attending verifies the program’s VTE prophylaxis guideline against the document it came from. Every answer says exactly where it came from.
Start with residents. Formalize when the value is already proven.
MARCUS doesn’t require a procurement committee to get started. Here’s what adoption actually looks like:
Phase 1
A resident finds it useful.
Any resident can sign up, add their program's documents, and start asking questions. Most programs find MARCUS this way — a resident uses it on call, mentions it to co-residents, and it spreads. No IT involvement. No procurement. It runs in a browser.
Phase 2
A program formalizes the library.
Once enough residents are using it, the program director or chief resident wants to centralize — make sure the right documents are in, decide who has access, see what's being asked. Organizational accounts cover that: program directors administer the library, residents are members, viewers observe, and the program owns its own corner of the platform.
Phase 3
The institution holds it together.
When adoption crosses programs, GME leadership and hospital administration can bring everything under one institutional umbrella. SSO via SAML or OAuth connects to existing identity infrastructure. Each program keeps its own library, isolated at the data layer, while the institution gets visibility across departments.
There is no “Request Demo” button here that leads to a six-month procurement cycle. The product works today. Residents can start using it now. Institutional formalization comes when the value is already there.
For program directors and GME offices
What MARCUS delivers at the program level.
Knowledge that holds together
Every protocol, guideline, and handbook your program writes — connected to a single, citable institutional memory. No more “I think it’s in the shared drive somewhere.”
Continuity across academic cycles
Three years of working knowledge no longer leaves every July. The library — and the understanding written into it — stays with the program.
Tenant-isolated data
Your program's documents are visible only to your program's members. Multi-tenant architecture enforces that at the database level, not at the UI.
Role-based access
Program directors and designated administrators manage the library and access. Residents ask. Viewers observe. Permissions are enforced server-side.
Audit trail
Every question is logged with metadata — who asked, when, which sources were reviewed. Useful for compliance, quality improvement, and seeing what residents actually struggle to find.
No IT overhead to start
Browser-based. No app install. No VPN required. When the program is ready for SSO, MARCUS supports SAML and OAuth integration with hospital identity providers.
Source citation on every answer
No claim without a source. Every line in a MARCUS answer points back to the passage in the document it came from. If your library doesn't cover the question, MARCUS says so rather than improvising.
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
Individual residents can sign up and use MARCUS today at no cost during the beta period.
For program-level accounts with admin controls, document management, and usage analytics, contact us to discuss the program’s needs. Pricing is annual, per-program, with institutional rates for multi-program deployments.
We’re actively looking for early partner programs willing to help shape the product. If you’re a program director or GME administrator interested in piloting MARCUS, we’d like to hear from you.
A note on security
MARCUS is built with healthcare-grade security infrastructure from day one — encryption in transit and at rest, tenant isolation, role-based access control, cookie-only authentication, and audit logging. We do not sell data or use your documents to train shared models.
For our full security posture, including HIPAA readiness status, visit our security page.
→ Read our security & privacy page