Evaluation packet
UltraSight AI Cardiac Ultrasound Guidance
UltraSight · Cardiology
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
- FDA 510(k) cleared (Jul 2023; expanded multi-device clearance Jan 2026); PVAD IQ cleared Feb 2026; CE, UKCA
- 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://ultrasight.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.
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
IT & security
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.
- Ask for the FDA decision summary. Check that your planned use matches the cleared intended use: patients, inputs (scanner, device, data type), users, and whether it assists a clinician or acts on its own.
- Ask whether the clearance includes a Predetermined Change Control Plan (PCCP), and how you will be told when the model changes.
- 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?
- How does it integrate with your EHR or imaging system, and where do 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 Cardiology AI guide.
Change tool type:
ECG analysis
Use this section if the tool reads ECG tracings, for example to detect arrhythmias or to flag conditions not visible to the eye, such as low ejection fraction, amyloidosis or future atrial fibrillation risk.
Physician looks for
- Whether an AI-ECG finding (low EF, amyloid, AF risk) changes management.
- What the follow-up pathway is: echo capacity, cardiology referral.
- Which ECG machines and software versions it was validated on, and whether that includes yours.
Administrator looks for
- Downstream volume (echo, MRI, clinic visits). This is revenue but also capacity strain.
- Reimbursement. Algorithmic ECG risk assessment has Category III CPT codes 0764T/0765T. Category III codes are tracking codes, and payment isn’t assured.
- Integration with your ECG management system (for example MUSE), echo PACS and the EHR.
- Testing cascades. False positives drive echos, imaging and visits that cost money and can harm patients. Model the cascade before go-live.
- Accountability for misses. If the tool screens every ECG, who is responsible when it misses a finding, and when a flagged result isn’t followed up?
- Performance by sex and body habitus, which affect ECG and echo signals.
IT looks for
- How it connects to your ECG management system (HL7 or vendor interface) and whether results return to the EHR as structured data.
- Where tracings are processed, on your servers or in the vendor’s cloud, and how data leave your network.
Compliance looks for
- Whether the cleared indication covers each finding you plan to act on. Some AI-ECG outputs are not cleared for diagnosis.
- A record showing that each flagged result was reviewed and acted on.
- Ongoing checks of performance by sex, age and race.
Evidence to ask for
- External validation in a population like yours.
- Positive predictive value (PPV) at your expected prevalence.
- A prospective study showing increased diagnosis (with actual confirmatory testing), not only AUC.
Test it locally
- Retrospectively run the tool on 6 to 12 months of your ECGs.
- Estimate how many positives per month it would generate and whether echo capacity can absorb them.
Red flags
- AUC-only claims.
- No plan for who owns a positive result.
- Performance shown only on one vendor’s ECG carts.
Questions to ask the vendor
- At our prevalence, how many flags per 1,000 ECGs, and how many true positives?
- Who receives the result, and what’s the recommended pathway?
- Which ECG carts and software versions was it validated on?
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