In Simple Terms
Doctors sometimes ask AI tools questions that include private details about patients or the people providing their care. MDCalc says its new tool, CrossCover, removes some sensitive details before a question is sent to an AI chatbot. The idea could help protect privacy, but the announcement does not show how well the tool works or whether it improves medical care.
A Question of Privacy
Doctors may turn to AI with a quick question to make sense of a piece of information or check a possible clinical explanation. But even a short question can contain details about a patient—or about the doctor asking for help. That makes privacy a concern from the moment the question is typed. On November 11, 2026, MDCalc announced the launch of CrossCover, a tool the company says is designed to make medical chatbots easier to use while reducing the risks associated with sensitive information.
A Medical Question May Not Be Anonymous
A question submitted by a doctor to an AI system may sound general, yet its clinical context can make it more specific than it appears. Information about someone’s health or care can be highly sensitive. Some details may identify a patient directly, while others could reveal who they are when combined with additional information. Privacy, then, is about more than a patient’s name or record number: it also includes details in a description of their condition and the circumstances of their care.
There is another layer of privacy involving the healthcare provider. The wording of a question, or information submitted alongside it, could reveal something about the doctor or the organization where they work. MDCalc says CrossCover is intended to protect both patients and care providers. But the announcement does not explain in detail what kinds of information the tool can detect or how it handles cases where useful clinical context is hard to separate from details that could identify someone.
This matters because a doctor may need enough context to make a question understandable, without needing to include every piece of information available about the patient. CrossCover is an attempt to navigate that gap: the tool processes a question so that fewer identifying details and less protected health information reach the chatbot. Rather than solving the problem by adding more data, this approach focuses on sending less.
How Is This Different From Other Approaches?
MDCalc describes CrossCover as taking a different approach from other medical AI products. According to the report, OpenEvidence, Abridge, and electronic health-record company Epic are working to incorporate broader sets of information about patients, care providers, and payers into the material their systems can use to make recommendations. MDCalc, by contrast, says its tool focuses on removing those kinds of details from doctors’ queries instead of making their inclusion a condition of use.
That difference does not, by itself, mean one approach is better in every situation. Giving a system more context may be part of how some products are designed, while reducing sensitive data may limit how much information is exposed in a question. The practical trade-offs depend on what information a system needs in order to respond, how data are protected, and how clearly the tool’s limits are explained to doctors. The announcement does not provide enough detail for a full technical comparison between CrossCover and the other products.
The launch description also does not say that CrossCover replaces health-record systems or makes clinical decisions. It says the tool aims to remove information from doctors’ queries, and that MDCalc sees it as a way to help speed up the use of generative AI in clinical work. That description should be kept in perspective: as presented, the tool handles the input to a question; it does not take responsibility away from the doctor for assessing the answer.
What Is CrossCover Trying to Change?
Graham Walker, MDCalc’s head of AI, says the tool could ease some of the obstacles and risks involved in using this technology, potentially making doctors more comfortable turning to it. That is the company’s stated vision for CrossCover: reducing the friction between the need for digital assistance and concerns about privacy and trust.
Trust has practical consequences here. If a doctor feels that using a tool requires sharing information that should not be disclosed, they may hesitate to use it or may have to phrase the question in a way that makes it less useful. If sensitive details can be reduced before a query is sent, using AI could become easier from a data-protection perspective. But that possibility does not establish that CrossCover has improved care decisions or increased users’ trust. The available material reports the company’s goal and explanation; it does not present test results or measurements of doctors’ views.
Walker’s description of the tool as an accelerator for clinical AI reflects a broader view of its role: removing some of the barriers that make adoption more difficult. But it does not say how much faster adoption might become, how many organizations will use the tool, or how long it takes to prepare and process a question. For now, “accelerator” should be understood as a stated ambition, not a published quantitative result.
Privacy Does Not Automatically Mean Complete Security
Limiting the information that reaches an AI system is relevant to privacy, but it is not enough on its own to determine how well data are protected. That assessment would require knowing exactly what the tool removes, how it handles details that might indirectly identify someone, and what information the system retains after receiving a query. MDCalc’s announcement does not answer these questions. It would therefore be wrong to assume that every risk disappears simply because the tool is said to remove sensitive information.
The clinical question itself also has to be phrased carefully. If too much detail is removed, the request may become vague or lose context the system needs to respond. If too much information remains, the goal of reducing exposure may not be met. This is a general challenge for any effort to separate information needed for an answer from information that does not need to be shared. The source does not explain how CrossCover handles this tension in practice.
That makes it important for users to understand what the tool does—and what it does not do. Doctors need to know the limits of its filtering, whether they should review a question before submitting it, and what to do when a case is complex or involves highly sensitive information. The announcement gives no details about usage procedures or training, so these are among the points that would need clarification before readers can form a complete picture of the experience.
Trust in the Answer Is a Separate Question
MDCalc’s pitch is that reducing some of the risks and barriers associated with the technology may make doctors more comfortable using it. But protecting privacy does not establish that a chatbot’s medical answer is correct or appropriate for a particular case. These are separate questions: one concerns what information a query reveals; the other concerns the quality of the response and how it should be checked before it informs care.
Based on the information available, CrossCover should not be seen as a guarantee that AI outputs are correct or as a substitute for professional judgment. The announcement provides no comparative results on chatbot accuracy when used with the tool, and it mentions neither a clinical trial nor figures on errors avoided. It also offers no data on how many doctors have tried CrossCover or how it affects their work time. The absence of such information does not rule out possible benefits, but it means that judging the tool’s impact requires evidence the announcement does not include.
This distinction helps prevent two goals that may seem related from being conflated. Processing a question may make sharing data feel less concerning, while the answer still needs to be assessed independently. A doctor needs to ask not only whether the system protected privacy, but also whether the response relied on appropriate information, applies to the patient in question, and has limits that should be taken into account. The announced tool addresses one part of the issue; the source does not say that it resolves the others.
What We Know—and What We Don’t
The announcement confirms a limited set of facts: MDCalc, known for a medical reference tool, launched CrossCover on Wednesday, November 11, 2026. The company says the tool is intended to help doctors feel more confident in answers from medical AI chatbots while protecting the privacy of patients and care providers. Its stated design focuses on removing certain kinds of sensitive information from doctors’ queries. The company’s head of AI also said the goal is to ease some of the difficulties and risks that come with using the technology.
By contrast, the announcement does not describe how the tool works, how accurately it detects sensitive information, how it was tested, or what results it has achieved since launch. It does not specify whether CrossCover deletes, masks, or rewrites information, so it would be inaccurate to claim that it uses any particular technical method. The material also contains no figures on usage or effectiveness and no information about the tool’s cost or availability.
Distinguishing what has been announced from what has been demonstrated is essential when discussing AI tools in healthcare. A new name and a promising goal are no substitute for a clear account of what happens to the data or an independent assessment of results. The more directly a tool handles sensitive health information, the more important it is to answer questions about protection and transparency—and to establish whether risks are reduced without undermining the usefulness of the medical question.
Why This Approach Is Worth Watching
CrossCover raises an important question about how digital medical assistants should be designed: should these systems rely on taking in more data to shape their recommendations, or can their use become more cautious by reducing the information sent to them? MDCalc’s product does not answer that question for every application, but it presents an option that puts data minimization at the center of the idea, rather than treating ever-greater context as the only path to wider use.
The value of this approach will depend on how it is implemented. If the tool reliably removes unnecessary information while preserving the clinical meaning a system needs, it could help address one source of concern about privacy. If its limits are unclear, or users cannot tell what information remains in a question, some of that concern will persist. These are questions for evaluation, not results the company has announced, and a product description alone cannot settle them.
So the real test for a tool like this goes beyond its promise to reduce data. It includes making clear what the tool processes, showing users where its limits lie, and providing performance information that can be examined. Without those details, CrossCover can be understood as an attempt to address a real problem—not as a final solution to every concern about privacy or trust in medical AI.
The Bottom Line
With CrossCover, MDCalc is proposing a different way to use medical AI. Instead of expanding the information fed into recommendations, the company says its tool focuses on filtering certain types of sensitive data from doctors’ questions while seeking to protect patients’ and care providers’ privacy. Graham Walker presented the approach as a way to reduce some of the obstacles and risks that can limit doctors’ trust in the technology.
So far, however, the announcement establishes the goal without revealing the full details of the tool’s performance. The available information includes no figures on its accuracy or effect on clinical work, no technical explanation of how it removes information, and no evidence that it makes chatbot answers correct. CrossCover matters both for what it says it does and for the question it raises: how can medicine benefit from AI tools while sending as little sensitive information as possible—and still leave answer-checking and professional responsibility where they belong?