Evaluation packet
Massive Bio Clinical Network - Backend
Massive Bio, Inc. · Oncology
Prepared November 22, 2026 from the public listing on CIFoundry. It shows what the public record says and what to ask the vendor. It is not a recommendation or an endorsement.
1. What the public record shows
- Regulatory status
- Not on record
- Published evidence
- Not on record
- Named health-system users
- Not on record
- Integrations
- Not on record
- Data inputs
- Not on record
- HIPAA BAA
- Not on record
- SOC 2 / HITRUST
- Not on record
- Deployment model
- Not on record
- Website
- https://massivebio.com
Integrations, data inputs, BAA, SOC 2, HITRUST and deployment model are reported by the vendor and not checked by us. Confirm them in writing.
From public directories
Third-party directories checked by our team. These are not the vendor's own pages and not an endorsement.
- Listed in Epic Showroom
- Connection Hub: Massive Bio Clinical Network - Backend by Massive Bio, Inc.source, checked Nov 21, 2026Epic’s public app directory. Listed developers pay Epic for services; Epic does not endorse, certify or validate listed products.
2. Evaluation checklist for your role
Each question shows what the public record says: on record (with its source), reported by the maker, or not on record. It is a list of things to check, not a score.
For every reviewer
Compliance & risk
Your ticks and notes stay in this browser. Nothing is sent to us.
3. Gaps to raise with the vendor
Based on what is missing or worth confirming in this tool’s public record.
- No regulatory status is listed. Ask whether the tool is regulated by the FDA as a medical device and, if so, for the clearance number and the exact cleared intended use.
- No published study is linked. Ask for peer-reviewed validation done outside the developer’s own sites, and for results on patients and equipment like yours.
- We found no public reports naming health systems that use it. Ask for reference sites similar to yours and contact them yourself.
- Will the vendor sign a HIPAA Business Associate Agreement?
- Does the vendor have a current SOC 2 Type II report or HITRUST certification you can review?
- Where is data stored and processed (cloud region, on-premises), and which subcontractors, including any large-language-model provider, touch patient data?
- It is listed in Epic Showroom, which says nothing about how it is configured. Ask which Epic integration it uses at live sites and where results appear for the clinician.
- Is your data used to train the vendor’s models, and can it be deleted when the contract ends?
4. Questions for this kind of tool
From our Oncology AI guide.
Change tool type:
Radiation contouring and planning
Use this section if the tool draws organs at risk or target volumes, or automates treatment planning.
Questions to ask
- How much editing time does it save dosimetrists and physicians, and what share of contours are accepted with minor or no edits?
- Which disease sites, scanners and planning systems was it validated on? Does it work with yours?
- How are updates to the model handled, and are contours re-checked after an update?
Test it locally
- Run it on 20 to 30 of your own cases per disease site and measure edit time and geometric agreement with your approved contours.
Red flags
- Validated on only one planning system
- No site-by-site results
Clinical-trial matching
Use this section if the tool screens patient records against trial eligibility criteria.
Questions to ask
- Compared with coordinator review, how many suggested matches are truly eligible (precision), and how many eligible patients does it miss?
- Does it read unstructured notes and pathology reports, or only structured data?
- What is the effect on screen-to-enroll ratio and coordinator hours?
Measure
- Screened, eligible and enrolled patients per trial, before and after go-live
Treatment decision support and outcome prediction
Use this section if the tool suggests treatment options or predicts survival, toxicity or response.
Questions to ask
- Is there prospective evidence that it changes decisions or outcomes, not only retrospective accuracy?
- How well do its recommendations agree with current guidelines (for example NCCN), and how quickly is it updated when guidelines change?
- For predictions: is it calibrated in your population, and how was the outcome defined?
Red flags
- Survival predictions without calibration data
- No process for guideline updates
5. Questions for every tool
The 12 questions that apply to every tool
Fit and evidence
- Intended use. Does the stated use match the patients, setting, user and decision you plan to use it for?
- Evidence level. From weakest to strongest: vendor-internal test, retrospective external validation, prospective "silent" run, prospective live study, randomized trial, proven change in outcomes. Ask which level the claims rest on and look for peer-reviewed external validation.
- Population and equipment. Ask for results by age, sex, race and ethnicity, language and payer, and, where relevant, skin type and body habitus. Ask for results on your scanner or device vendors, EHR and protocols.
- Local validation. Before go-live, run the tool on your own recent cases and compare it to ground truth. Agree in the contract on what counts as passing.
Workflow and people
- Workflow cost. Count clicks, alerts per clinician per shift, minutes added per case, and who acts on the output. A strong tool that nobody acts on has no value.
- Integration. Native EHR or PACS integration or a separate window? Single sign-on? Where do results land?
- Human oversight. Who has the final say, how are disagreements with the tool handled, and how do you guard against over-reliance? Train users on known failure modes, not just features. Explanations matter most for risk scores and decision support.
After go-live
- Monitoring. Who checks for drift, how often, and what triggers a pause? Re-check after vendor updates, scanner or EHR changes, and shifts in your patient population. Agree in advance on the results that would retire the tool.
- Model updates. Version control, advance notice of changes, and the right to stay on a version you validated.
Data, liability and money
- Data rights and security. BAA, where data is stored and processed, encryption, retention, SOC 2 or HITRUST, whether your data trains the vendor's models, the list of subcontractors that touch patient data (including any large-language-model provider), and whether data can be deleted.
- Liability and patient notice. Who is liable when AI-assisted care goes wrong is still unsettled, and responsibility currently stays with the clinicians and organizations using the tool. Ask your malpractice carrier, and cover indemnification, audit rights and incident reporting in the contract. Joint Commission and CHAI guidance says patients should be told when AI directly affects their care, with consent where relevant.
- Money and exit. Pricing model, any real payment pathway, the return you will measure, termination for performance failure, data return, and no auto-renewal without a performance review.
6. Notes and decision
Problem we want to solve and how we will measure it
Vendor answers and follow-ups
Local test plan and what counts as passing
Decision, owner and next step