CIFoundry

Evaluation packet

Caption Guidance / Caption AI

Caption Health, Inc. (acquired by GE HealthCare in 2023) · 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 Cleared
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

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

Administrator & finance

Physician

IT & security

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.

  1. 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.
  2. Ask whether the clearance includes a Predetermined Change Control Plan (PCCP), and how you will be told when the model changes.
  3. 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.
  4. We found no public reports naming health systems that use it. Ask for reference sites similar to yours and contact them yourself.
  5. Will the vendor sign a HIPAA Business Associate Agreement?
  6. Does the vendor have a current SOC 2 Type II report or HITRUST certification you can review?
  7. Where is data stored and processed (cloud region, on-premises), and which subcontractors, including any large-language-model provider, touch patient data?
  8. How does it integrate with your EHR or imaging system, and where do results appear for the clinician?
  9. 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.

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?

Echocardiography and cardiac imaging

Use this section if the tool analyzes echocardiograms, cardiac CT or cardiac MRI, for example by automating measurements, guiding image acquisition or detecting disease.

Physician looks for

  • Measurement reproducibility (ejection fraction, chamber size, strain) compared with your sonographers and readers.
  • Vendor-neutral support, or a tie to one ultrasound or scanner manufacturer.
  • What it does with poor-quality images: flag them, or measure anyway.
  • If it guides less experienced sonographers, the training and oversight that requires.

Administrator looks for

  • Where results appear: in the echo reporting system and PACS, or a separate viewer.
  • Time saved per study, and whether that turns into more studies per day or shorter waits.
  • Downstream volume if it detects disease (for example, more cardiac MRI or clinic visits).
  • Licensing per machine, per study or per site.

IT looks for

  • DICOM connectivity with your echo PACS and reporting system, and whether results return as structured data (for example DICOM SR).
  • Whether processing runs on the machine, on your servers or in the vendor’s cloud.

Compliance looks for

  • That the clearance covers each measurement and machine model you plan to use.
  • A record of which measurements were automated and which a reader edited.

Evidence to ask for

  • Agreement with expert readers on studies from several machine models, including technically difficult ones.
  • For detection claims, results confirmed by a reference test, not only reader agreement.

Test it locally

  • Compare automated measurements against your readers on a few hundred recent studies, including technically difficult ones, and on each machine model you use.

Red flags

  • No handling of poor-quality images
  • Validation only on high-quality academic studies
  • Works on one manufacturer’s machines only, when you run several

Questions to ask the vendor

  • How do your measurements compare with expert readers on machines like ours?
  • What happens when an image is too poor to measure?

Risk prediction and finding undiagnosed patients

Use this section if the tool uses EHR data to predict outcomes (such as heart-failure readmission) or to find patients who may have untreated disease.

Physician looks for

  • How the outcome was defined: by clinical criteria or by billing codes.
  • What action is attached to each flag, and who takes it.

Administrator looks for

  • How many patients it will flag per month, and whether you have staff to reach them.
  • Downstream visits, testing and treatment the flags generate.

IT looks for

  • Which EHR data feeds it needs (FHIR, HL7 or bulk extracts) and how often they refresh.
  • Where flags appear for staff, and how access is limited to the care team.

Compliance looks for

  • If supplied inside a certified EHR, the ONC HTI-1 source attributes. If not, ask for the same information.
  • Whether the flag rate differs by race, payer or language for patients with the same true risk.

Evidence to ask for

  • Calibration in a population like yours, not only accuracy in ranking patients.
  • Evidence that acting on flags improved outcomes, not only that the model predicts well.

Test it locally

  • Run it retrospectively on your data and check both accuracy and the number of patients it would surface.

Questions to ask the vendor

  • How many patients per 10,000 would it flag in a population like ours, and how many truly have the condition?

Wearables, ambulatory monitors and device data

Use this section if the tool analyzes data from patches, wearables, Holter monitors or pacemakers and defibrillators.

Physician looks for

  • Which devices it supports, and whether it is cleared for those inputs.
  • The process for urgent findings outside office hours.
  • For consumer wearables, how patient-submitted data are verified.

Administrator looks for

  • Events sent per patient per month, and who reviews them, and when.
  • Staffing for the review queue as enrollment grows.

IT looks for

  • How device data reach you: the vendor’s cloud portal, or an HL7 feed into the EHR.
  • Security of any patient-facing app, and account management for patients and staff as enrollment grows.

Compliance looks for

  • Which devices and inputs the clearance covers.
  • Documented response times for urgent findings, and a record of who reviewed each event and when.

Red flags

  • No after-hours escalation plan
  • Event volume estimates missing

Questions to ask the vendor

  • How many events per patient per month should we expect, and what share need clinician action?
  • Who handles urgent findings at night and on weekends?

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

CIFoundry is an independent, vendor-neutral directory. Listing is free, and no one can pay to change a listing or this packet. Check every fact with the vendor and the primary source before relying on it.