Continuous wearable ECG patch with on-device deep-learning hyperkalemia-risk screening, as a between-visit adjunct during outpatient RAASi titration in CKD and heart-failure patients
8/9
factors scored
4/4
core factors
5/39
claims verified
0
refuted
How to read a tag. Only
verified counts toward a score — it means a typed connector
resolved this against a primary US federal record.
unconfirmed means the Verifier checked and could not confirm,
which very often means the source could not be queried at all rather than that
the claim is doubtful. refuted means a primary source
contradicts it. unverified means nothing has checked it yet.
claim 1unconfirmedUS
AliveCor's KardiaK Software Platform, an ECG-based deep-learning hyperkalemia-screening algorithm, received FDA Breakthrough Device Designation in September 2018.
jurisdiction: US — confidence: unconfirmed — source: AliveCor press release / PRNewswire release (unchanged from Generator; still not a primary FDA source). No connector in this repo checks Breakthrough Device Designation status: python3 -m connectors 510k "KardiaK" --applicant "AliveCor" and `python3 -m connectors…the full check denovo "KardiaK"` were run (see claim 2 below) but those check clearance/grant status, a different fact from designation status, and neither openFDA endpoint carries a Breakthrough-designation field. FDA's public Breakthrough Devices Program list has no typed connector in this repo — this claim cannot be checked here and needs a human to consult FDA's list directly.
claim 2unconfirmedUS
As of the Generator's search, no FDA clearance (510(k)) or De Novo grant for AliveCor's KardiaK hyperkalemia algorithm has been identified — i.e. Breakthrough designation alone has not, as far as the Generator can tell, produced a cleared predicate in this space.
jurisdiction: US — confidence: unconfirmed — note: mixed — see detail — source (510(k) half): python3 -m connectors 510k "KardiaK" --applicant "AliveCor" → {"status": "refuted", "detail": "No 510(k) record found for device_name='KardiaK' applicant='AliveCor'"} — openFDA's device/510(k) database holds no…the full check cleared-predicate record under this name and applicant, which actively supports the "no 510(k) clearance" half of this claim. Source (De Novo half): python3 -m connectors denovo "KardiaK" → {"status": "unconfirmed", "detail": "No local cache at data/fda_denovo.csv..."} — this environment's data/ directory holds only README.md, no De Novo cache file, so the De Novo half was never actually queried against anything and must not be read as confirmed absence. Net: the 510(k) portion is affirmatively supported by a real openFDA query; the De Novo portion is genuinely unchecked for lack of the required data file, so the compound claim as a whole stays unconfirmed rather than verified.
claim 3unconfirmedUS
A Mayo Clinic-affiliated deep-learning model trained on paired ECG and serum-potassium data reported an AUC of approximately 0.88-0.89 for hyperkalemia screening from a standard ECG.
jurisdiction: US — confidence: unconfirmed — source: python3 -m connectors literature-detail 30942845 → PubMed PMID 30942845 (Galloway et al., JAMA Cardiology 2019, "Development and Validation of a Deep-Learning Model to Screen for Hyperkalemia From the Electrocardiogram"), structured abstract retrieved. The…the full check abstract reports, for the 2-lead (I, II) model across three validation cohorts: AUC 0.883 (95% CI 0.873-0.893) Minnesota, 0.860 (95% CI 0.837-0.883) Florida, 0.853 (95% CI 0.830-0.877) Arizona. The claimed "approximately 0.88-0.89" is close to the single highest reported figure (Minnesota, 0.883) but overstates the upper bound (no reported AUC reaches 0.89 in this abstract) and omits that two of three validation sites reported materially lower AUCs (0.853, 0.860). Not refuted — the abstract is in the right range — but not a precise match either; a literature-detail read is a structured abstract only ("a lead to read, not evidence for a claim" per the connector's own caveat), so full-text depth (methodology, any 4-lead result, external validation) is still unread.
claim 4verifiedUS
CMS's RAPID coverage-pathway notice states that RAPID eligibility requires the device to be "separately payable" — billable to Medicare in its own right.
jurisdiction: US — confidence: verified — source: python3 -m connectors policy 2026-16368 --expect "separately payable" → verified. Document 91 FR 51710 (Federal Register document_number=2026-16368, "Medicare Program; Regulatory Alignment for Predictable and Immediate Device (RAPID) Coverage Pathway," Notice,…the full check published 2026-08-11, CMS/HHS) contains the phrase verbatim, in context: "...Separately payable devices that can, if approved, be billed to Medicare; and Not otherwise excluded from coverage through law or regulation." Note the connector's own caveat: this confirms the document contains the words, not that the requirement is currently in force (comment period open, see claim below).
claim 5verifiedUS
The same notice states RAPID eligibility is limited to Class II and Class III Breakthrough-designated devices, and that entry occurs at the IDE-presubmission stage, before the device is market-authorized or already under an IDE.
jurisdiction: US — confidence: verified — source: python3 -m connectors policy 2026-16368 --expect "Class II and Class III" and --expect "presubmission", both verified against 91 FR 51710. Quoted text: "...the RAPID coverage pathway... will provide accelerated Medicare beneficiary access to certain eligible Class…the full check II and Class III U.S. Food and Drug Administration (FDA) Breakthrough- designated Devices" and "...The device must also be at the IDE presubmission stage and be the subject of an IDE study that enrolls Medicare beneficiaries..."
claim 6verifiedUS
The same notice states that IVD products are excluded from the RAPID pathway by name, with coverage for Breakthrough-designated IVDs left to Medicare Administrative Contractors instead of a national pathway. This candidate is not, on its stated intended use, an IVD.
jurisdiction: US — confidence: verified — source: python3 -m connectors policy 2026-16368 --expect "IVD products will not be accepted" → verified against 91 FR 51710. Quoted text: "...coverage determinations for IVDs which have been granted Breakthrough Device designation should continue to be determined by the MACs…the full check through existing pathways. Therefore, IVD products will not be accepted into the RAPID coverage pathway." The "this candidate is not an IVD" half is a self-description from the intended-use frontmatter (screening adjunct, not a potassium measurement), not itself a connector-checkable fact, but is consistent with the stated intended use.
claim 7verifiedUS
The same notice states RAPID is a notice with a comment period, not a final rule, with comments closing 2026-10-13; nothing in it was in force as of the date this candidate was generated.
jurisdiction: US — confidence: verified — source: python3 -m connectors policy 2026-16368 --expect-type notice --expect "comment period" → verified (type match: ACTION: Notice with comment period; no mismatch, so this is a positive type confirmation, not just a phrase hit). Document metadata: published 2026-08-11,…the full check comment period closes 2026-10-13, no effective date recorded — consistent with "not yet in force."
claim 8unconfirmedUS
Between 20% and 67% of patients with heart failure also have chronic kidney disease, across the range of studies reviewed.
jurisdiction: US — confidence: unconfirmed — source: narrative review found via web search (PMC, exact PMCID not captured by the Generator). No connector can be run without a resolvable PMID/PMCID — literature-detail takes a PubMed ID, not a claim summary — and the Generator did not capture one, so this stays…the full check unconfirmed for lack of an identifier, not because a check was attempted and failed.
claim 9unconfirmedUS
In a multi-country comparison, RAASi prescription prevalence among CKD/HF patients in the United States was reported around 52%, lower than in Germany or France.
jurisdiction: US — confidence: unconfirmed — source: study found via web search, PMC-hosted, exact PMCID not captured by the Generator. Same limitation as the claim above: no resolvable identifier, so literature-detail cannot be run against it. Stays unconfirmed for lack of an identifier.
claim 10unconfirmedUS
The US Renal Data System (USRDS) 2024 Annual Data Report provides Medicare Fee-for-Service CKD burden estimates using a 5% random sample for calendar year 2022; the Generator has not extracted a specific beneficiary count from it.
jurisdiction: US — confidence: unconfirmed — source: USRDS Annual Data Report, referenced via web search. No connector in this repo reads USRDS report content (it is not one of the five data/-backed CMS connectors — see data/README.md), and the claim itself asserts no extracted figure to check, so there is nothing…the full check here for a connector to confirm or refute.
claim 11unconfirmedUS
No HCPCS code, payment rate, or coverage policy specific to a continuous ECG-based hyperkalemia-screening service has been identified by the Generator; existing CMS remote physiologic monitoring codes may be an analog billing structure, but the Generator has not confirmed applicability and is not reproducing any AMA-licensed code descriptor here.
jurisdiction: US — confidence: unconfirmed — source: confirmed independently that data/hcpcs_level_ii.csv, data/hcpcs_payment_rates.csv, and data/medicare_coverage_policies.csv are all absent from this environment's data/ directory (only README.md present), so python3 -m connectors hcpcs, payment, and…the full checkcoverage all return unconfirmed ("no local cache") for any code. No specific candidate code (e.g. an RPM analog) is named in this claim to test in the first place, so this remains an open question rather than a checked absence.
claim 12unconfirmedUS
Assumption, not a fact: clinicians managing RAASi titration would be willing to act on an ECG-based hyperkalemia flag without an accompanying lab value, and would order a confirmatory draw promptly when flagged. This is a stated design assumption behind the device's clinical workflow, not a claim any connector in this repo can check.
jurisdiction: US — confidence: unconfirmed — source: python3 -m connectors adoption "clinicians managing RAASi titration would be willing to act on an ECG-based hyperkalemia flag without an accompanying lab value" → unverifiable ("needs primary research... stays unconfirmed permanently unless a human attaches real…the full check research"). Confirms the Generator's own framing was correct — this is not resolvable by any connector and was not answered from model judgment.
claim 13unverifiedUS
Freedom-to-operate risk: AliveCor holds Breakthrough Device Designation on a competing ECG-based hyperkalemia-screening algorithm
jurisdiction: US — confidence: unverified — note: this claim line was found truncated on 2026-08-29 (it ended mid-sentence at "Designation on a" with no jurisdiction, confidence or source field). The missing text was not recoverable and has not been invented; the assertion above is completed only as far as the…the full check surrounding claims support and must be restated by the Generator before it is checked. Kept in position rather than removed because this file and its decks reference claims by number — source: none; never checked
claim 14unconfirmedUS
FDA's Breakthrough Devices Program page states that FDA generally cannot publicly disclose whether a sponsor has submitted a Breakthrough Device designation request, or whether FDA granted or denied it, unless the sponsor discloses it; FDA's own public list of Breakthrough-designated devices includes only devices that have since received marketing authorization. Since no 510(k) or De Novo grant for AliveCor's KardiaK has been located (claim 2), KardiaK's designation status is structurally unconfirmable against any FDA registry at this time, independent of whether the designation itself is real.
jurisdiction: US — confidence: unconfirmed — source: research lane, from dossier potassium-monitoring-ckd §8 (2026-08-26) — primary source: https://www.fda.gov/medical-devices/how-study-and-market-your-device/breakthrough-devices-program — evidence class 1 (registry fact). Verifier finding: no typed connector in…the full check this repo reads FDA guidance/program-page content — 510k and denovo check clearance/grant status only, not designation-disclosure policy, and there is no "webpage" connector. Same limitation already noted at claim 1. Stays unconfirmed for lack of a connector, not because the assertion looks wrong; a human would need to read the cited FDA URL directly to confirm the exact wording.
claim 15unconfirmedUS
No FDA De Novo bulk-download file (analogous to the 510(k) pmn96cur.zip or PMA pma.zip files) exists at accessdata.fda.gov's premarket ftparea; a request for denovo.zip at that location returns HTTP 404, and no bulk-export function was located on the De Novo database search page. This is a source-availability finding distinct from 'not yet fetched': no known stable URL serves this file for engine/scripts/fetch_data_file.py to retrieve.
jurisdiction: US — confidence: unconfirmed — source: research lane, from dossier potassium-monitoring-ckd §8 (2026-08-26) — primary source: https://www.accessdata.fda.gov/premarket/ftparea/denovo.zip (HTTP 404, checked 2026-08-26) — evidence class 1 (registry fact). Verifier finding: no Stage-3 connectors…the full check subcommand checks bulk-file/URL availability (that is outside the denovo connector's scope — it only reads a local cache). As supporting due diligence I re-ran python3 engine/scripts/fetch_data_file.py --dry-run --name fda_denovo.csv --url https://www.accessdata.fda.gov/premarket/ftparea/denovo.zip, a repo tool distinct from the Stage-3 connectors, which returned Refused: HTTP 404 — nothing was written, reproducing the exact result the claim describes. That reproduction is consistent with the claim but is not itself a typed-connector verification, so this stays unconfirmed per the connector-only rule rather than verified.
claim 16unconfirmedUS
A real, live CMS URL for the January 2026 HCPCS Level II Alpha-Numeric file exists (confirmed via engine/scripts/fetch_data_file.py --dry-run: HTTP 200, 2,519,574 bytes), but it is a ZIP archive and engine/scripts/fetch_data_file.py validates and writes only CSV/TSV/JSON bodies, so it cannot currently be loaded into data/hcpcs_level_ii.csv without extending the fetch tool to unzip. No specific HCPCS code for remote ECG-based or physiologic monitoring is confirmed by this pass; secondary sources (AAPC, vendor blogs) name candidate code numbers but were not independently verified against this or any primary CMS document.
jurisdiction: US — confidence: unconfirmed — source: research lane, from dossier potassium-monitoring-ckd §8 (2026-08-26) — primary source: https://www.cms.gov/files/zip/january-2026-alpha-numeric-hcpcs-file.zip — evidence class 1 (registry fact). Verifier finding: python3 -m connectors hcpcs still returns…the full checkunconfirmed ("No local cache at data/hcpcs_level_ii.csv") — the data/ directory holds no cached CMS files in this environment. As supporting due diligence I re-ran the cited URL through engine/scripts/fetch_data_file.py --dry-run: without --expect-columns it reports would write ... 2519574 bytes (matching the claim's byte count exactly, HTTP 200 confirmed live); re-run with --expect-columns code,description (the columns hcpcs_level_ii.csv requires per data/README.md) it is Refused: the file is missing expected column(s): code, description. Found: none — i.e. the ZIP body does not parse as CSV, so the file cannot be ingested via the normal workflow today, matching the claim's substance. Neither check is a Stage-3 connectors call, so this stays unconfirmed rather than verified under the connector-only rule; no HCPCS code is confirmed or refuted by this pass either way.
claim 17unconfirmedUS
A Mayo Clinic deep-learning ECG model for hyperkalemia screening (serum K+ greater than or equal to 5.5 mEq/L), trained on 1,576,581 ECGs from 449,380 patients (Mayo Clinic Rochester, 1994-2017) and validated retrospectively on 61,965 patients with stage 3 or greater CKD across three geographically separate Mayo sites, reported AUCs (2-lead, I/II) of 0.883 (95% CI 0.873-0.893) in Minnesota, 0.860 (95% CI 0.837-0.883) in Florida, and 0.853 (95% CI 0.830-0.877) in Arizona -- correcting the prior claim's approximate '0.88-0.89' range, which overstated the upper bound and omitted the two lower-performing sites. At the 90%-sensitivity operating point, specificity was only 54.7%-63.2% across the three sites.
jurisdiction: US — confidence: unconfirmed — source: research lane, from dossier potassium-monitoring-ckd §4 (2026-08-26) — primary source: PMID 30942845 — evidence class 2 (published finding) — Verifier re-ran python3 -m connectors literature-detail 30942845 (cold re-retrieval): abstract states training on "1 576…the full check 581 ECGs from 449 380 patients seen at Mayo Clinic, Rochester, Minnesota, from 1994 to 2017," validation "included 61 965 patients with stage 3 or greater CKD," and 2-lead AUCs "0.883 (95% CI, 0.873-0.893)" Minnesota, "0.860 (95% CI, 0.837-0.883)" Florida, "0.853 (95% CI, 0.830-0.877)" Arizona — exact match, and reported specificities at 90% sensitivity (63.2%/54.7%/55.0%) also match. Stays unconfirmed, not verified: literature-detail returns a Stage 0 ScanResult (connectors/result.py), which has no to_claim_line() and structurally cannot carry a confidence tag — a verbatim abstract match is a strong lead, not a Stage 3 appraisal (no methods review, no risk-of-bias check). Corrected from an earlier verifier pass that mistakenly tagged this verified off the same connector.
claim 18unconfirmedUS
In the same Mayo Clinic study's three validation cohorts, measured hyperkalemia prevalence (the base rate the screening model was validated against) ranged from 2.6% (1,282 of 50,099, Minnesota) to 4.8% (287 of 6,011, Florida) among patients with stage 3 or greater CKD.
jurisdiction: US — confidence: unconfirmed — source: research lane, from dossier potassium-monitoring-ckd §4 (2026-08-26) — primary source: PMID 30942845 — evidence class 2 (published finding) — Verifier re-ran python3 -m connectors literature-detail 30942845: abstract states "The prevalence of hyperkalemia in the…the full check 3 validation data sets ranged from 2.6% (n = 1282 of 50 099; Minnesota) to 4.8% (n = 287 of 6011; Florida)" — exact match, including both counts and denominators. Stays unconfirmed, not verified — same structural reason as the claim above (literature-detail is a Stage 0 ScanResult, no confidence tag possible). Corrected from an earlier verifier pass that mistakenly tagged this verified.
claim 19unconfirmedUS
The USRDS 2024 Annual Data Report's CKD Reference Tables (B.1-B.6) present point-prevalent (Dec 31) counts of the fee-for-service non-ESRD Medicare population aged 18+, based on the Medicare 5% random sample, with CKD, heart failure, and diabetes each identified from claims in the reported year, and counts multiplied by 20 to represent the full Medicare population meeting the cohort definition -- confirming the methodology cited in the prior claim, though no specific beneficiary count was extracted from this methods document itself (the count lives in a separate reference-table file not retrieved in this pass).
jurisdiction: US — confidence: unconfirmed — source: research lane, from dossier potassium-monitoring-ckd §4 (2026-08-26) — primary source: USRDS 2024 Annual Data Report, CKD Reference Table Methods (Reference Table B),…the full checkhttps://usrds-adr-api.niddk.nih.gov/api/referenceTables?year=2024&referenceTable=Reference_Table_Methods — evidence class 2 (published finding). Verifier finding: no connector in this repo reads USRDS content (same limitation already noted at claim 10), and this is not a PubMed record so literature-detail cannot apply either. I attempted engine/scripts/fetch_data_file.py --dry-run against the cited usrds-adr-api.niddk.nih.gov URL as a check on retrievability; it was refused outright: "usrds-adr-api.niddk.nih.gov is not a federal publisher of these files. Allowed: accessdata.fda.gov, cms.gov, data.cms.gov, www.accessdata.fda.gov, www.cms.gov" — confirming there is no repo-sanctioned route to this source at all, not just an unpopulated cache. Stays unconfirmed; the claim itself extracts no beneficiary count to check in any case.
claim 20unconfirmedUS
Revealed-behaviour twin for the class-3 question 'would clinicians act on a hyperkalemia flag' (claim 12): in a US outpatient HFrEF registry (CHAMP-HF), over a median 18-month follow-up, RAAS-inhibitor-class drug discontinuation occurred in 12.7% of ACEi/ARB users (444/3,509), 10.4% of ARNI users (140/1,352), and 20.4% of MRA users (435/2,129); chronic kidney disease was the only independent predictor of increased discontinuation risk across all three drug classes. This is a general discontinuation rate, not one isolating hyperkalemia as the stated reason.
jurisdiction: US — confidence: unconfirmed — source: research lane, from dossier potassium-monitoring-ckd §5 (2026-08-26) — primary source: PMID 34428591 — evidence class 2 (published finding) — Verifier re-ran python3 -m connectors literature-detail 34428591: abstract reports "frequency of drug discontinuation of…the full check ACEis/ARBs, ARNIs and MRAs was 12.7% (444 of 3509 users), 10.4% (140 of 1352 users), and 20.4% (435 of 2129 users), respectively" and "Chronic kidney disease was the only independent predictor of increased risk of discontinuation of each of the RAAS inhibitor classes" — exact match on every figure. Stays unconfirmed, not verified — same structural reason as the claims above (literature-detail is a Stage 0 ScanResult, no confidence tag possible). Corrected from an earlier verifier pass that mistakenly tagged this verified.
claim 21unconfirmedUS
In a non-US (Saudi Arabia) retrospective outpatient cohort of 905 RAAS-inhibitor users followed a mean 29.8 months, hyperkalemia (K+ >= 5.1 mmol/L) occurred in 32.8% (295/905), and RAASi therapy was discontinued in 6.2% and down-titrated in 4.5% of patients specifically because of hyperkalemia.
jurisdiction: US — confidence: unconfirmed — note: see jurisdiction caveat below — source: research lane, from dossier potassium-monitoring-ckd §5 (2026-08-26) — primary source: PMID 41126484 — evidence class 2 (published finding) — Verifier re-ran python3 -m connectors literature-detail 41126484: abstract (King…the full check Abdulaziz Medical City, Jeddah, 905 patients, mean 29.8-month follow-up) reports "Hyperkalemia (K+ ≥5.1 mmol/L) was observed in 295 patients, yielding an overall incidence of 32.8%" and "RAASi therapy was discontinued in 6.2%, and down-titrated in 4.5% of patients due to hyperkalemia" — exact match. Stays unconfirmed, not verified: literature-detail is a Stage 0 ScanResult, structurally incapable of carrying a confidence tag — same reason as the claims above. Corrected from an earlier verifier pass that mistakenly tagged this verified. Jurisdiction-tag note: the study itself is Saudi Arabian (non-US), as the claim text already discloses, while the claim's jurisdiction: frontmatter-style tag reads US — flagging this as a metadata inconsistency for the record, though it does not affect whether the cited finding itself checks out (it does).
claim 22unconfirmedUS
In a non-US (Japan) target-trial-emulation cohort of 2,305 CKD patients who developed incident hyperkalemia (K+ >= 5.5 mEq/L) while on a renin-angiotensin-system inhibitor, 15% (346/2,305) discontinued the drug after the episode; discontinuation was associated with 16% higher all-cause mortality (adjusted HR 1.16, 95% CI 1.02-1.33) than continuation, with no difference in the composite kidney outcome.
jurisdiction: US — confidence: unconfirmed — note: see jurisdiction caveat below — source: research lane, from dossier potassium-monitoring-ckd §5 (2026-08-26) — primary source: PMID 40369054 — evidence class 2 (published finding) — Verifier re-ran python3 -m connectors literature-detail 40369054: abstract (Osaka…the full check Consortium for Kidney Disease Research, n=2305) reports "346 (15%) discontinued RASi," discontinuation "associated with a 16% [95% CI 2-33%] higher hazard of mortality" (equivalent to HR 1.16, 95% CI 1.02-1.33) and the "composite kidney outcome did not differ between groups (adjusted HR 1.01 [0.81-1.26])" — exact match, figures just re-expressed (percent-increase vs. HR). Stays unconfirmed, not verified — same structural reason as the claims above. Corrected from an earlier verifier pass that mistakenly tagged this verified. Jurisdiction-tag note: this is a Japanese cohort (non-US), as the claim discloses, while the jurisdiction: tag reads US — same metadata inconsistency flagged on the prior claim; does not affect the finding's accuracy.
claim 23unconfirmedUS
In a multinational heart-failure registry across 111 sites in 9 countries (CARE-HK in HF, n=2,558, not US-isolated), 29% of patients had at least one hyperkalemic event over a median 12.3-month follow-up, and RAASi/MRA therapy was down-titrated or discontinued in only 3.6% of cases within 30 days of the first hyperkalemic event.
jurisdiction: US — confidence: unconfirmed — note: see jurisdiction caveat below — source: research lane, from dossier potassium-monitoring-ckd §5 (2026-08-26) — primary source: PMID 40788620 — evidence class 2 (published finding) — Verifier re-ran python3 -m connectors literature-detail 40788620: abstract…the full check (CARE-HK in HF, 2558 patients, 111 sites, 9 countries) reports "Over a median follow-up of 12.3 (9.4-18.1) months, 29% of patients had a hyperkalaemic event" and "In the 30 days following the first hyperkalaemic event, RASi/MRA was down-titrated or discontinued in 3.6% of cases" — exact match. Stays unconfirmed, not verified — same structural reason as the claims above. Corrected from an earlier verifier pass that mistakenly tagged this verified. Jurisdiction-tag note: this is an explicitly multinational registry (111 sites, 9 countries), not US-isolated, as the claim itself states, while the jurisdiction: tag reads US — same metadata inconsistency flagged above.
claim 24unconfirmedUS
In a non-US (Manitoba and Ontario, Canada) population-based cohort of CKD patients with RAAS-inhibitor-related hyperkalemia (n=7,200 and n=71,290 respectively), discontinuing the RAAS inhibitor (versus continuing) was associated with higher all-cause mortality (Manitoba HR 1.32, 95% CI 1.22-1.41; Ontario HR 1.47, 95% CI 1.41-1.52) and higher risk of dialysis initiation (Manitoba HR 1.65, 95% CI 1.41-1.85; Ontario HR 1.11, 95% CI 1.08-1.16).
jurisdiction: US — confidence: unconfirmed — note: see jurisdiction caveat below — source: research lane, from dossier potassium-monitoring-ckd §5 (2026-08-26) — primary source: PMID 35085685 — evidence class 2 (published finding) — Verifier re-ran python3 -m connectors literature-detail 35085685: abstract…the full check (Manitoba n=7,200, Ontario n=71,290, Canada) reports "RAAS inhibitor discontinuation was associated with a higher risk of all-cause mortality (Manitoba: HR, 1.32 [95% CI, 1.22-1.41]; Ontario: HR, 1.47 [95% CI, 1.41-1.52])" and "an increased risk of dialysis initiation in both cohorts (Manitoba: HR, 1.65 [95% CI, 1.41-1.85]; Ontario: HR, 1.11 [95% CI, 1.08-1.16])" — exact match on every figure. Stays unconfirmed, not verified — same structural reason as the claims above. Corrected from an earlier verifier pass that mistakenly tagged this verified. Jurisdiction-tag note: this is a Canadian cohort (non-US), as the claim discloses, while the jurisdiction: tag reads US — same metadata inconsistency flagged above.
claim 25unconfirmedUS
No 510(k)-cleared device anywhere in the openFDA database carries hyperkalemia, electrolyte imbalance, or potassium in its device name (a direct, unrestricted openFDA device/510k query for device_name=hyperkalemia and for unqualified full-text hyperkalemia both return zero results, not merely the single-top-match result the connectors 510k CLI reports); FDA's one classification family built for ECG-based AI 'notification software' (ten product codes under regulation_number 870.2380 in openFDA's device/classification database: SBQ atrial fibrillation risk, SFR hypertension, QXX coronary artery disease, QXO general cardiovascular, SIK cardiac hypertrophy, SIJ valvular regurgitation, SHP cardiac amyloidosis, SII aortic stenosis, QYE reduced ejection fraction, SAT pulmonary hypertension) contains none for hyperkalemia, electrolyte, or potassium. This narrows the regulatory-pathway question specifically to De Novo, with no existing predicate product-code family for a follow-on 510(k) to piggyback against, whereas an analogous condition (reduced ejection fraction) already has five 510(k)s (K233409, K232699, K250119, K250649, K250652) clearing under one De Novo-established code (QYE).
jurisdiction: US — confidence: unconfirmed — note: mixed — see detail — source: Verifier re-ran the claim through the true Stage 3 connectors, not the raw web queries the research pass used. python3 -m connectors 510k "hyperkalemia" (no applicant) → `{"status": "unconfirmed", "detail": "No 510(k) record found for…the full check device_name='hyperkalemia'"} — by the connector's own design (fda.py), a device-name-only miss with no applicant returns unconfirmed, not refuted; absence via one field-restricted query does not positively rule out a differently-worded record. python3 -m connectors classification --device-name "hyperkalemia" likewise → unconfirmed, same reason. The ten-code classification-family portion is independently, positively **verified**: python3 -m connectors classification --product-code <code> for all ten (SBQ, SFR, QXX, QXO, SIK, SIJ, SHP, SII, QYE, SAT) each returned verified, confirming all ten sit under regulation_number 870.2380 and none is named for hyperkalemia, electrolyte, or potassium — this part of the claim is real, connector-confirmed. But the broader "or potassium"/"or electrolyte" clause is factually wrong as literally written: python3 -m connectors 510k "potassium" returned verified — K810253, "SODIUM & POTASSIUM TEST KIT / Mallinckrodt Critical Care," decided 1981-02-10 — and python3 -m connectors classification --device-name "electrolyte" returned verified — product code JJR, "Electrolyte Controls (Assayed And Unassayed)," a Class I IVD chemistry-control product, unrelated to ECG or cardiac monitoring. Neither is a hyperkalemia-screening predicate, so the substantive regulatory-pathway conclusion (no ECG/cardiac-ML predicate for hyperkalemia exists) stands, but the claim's literal universal wording ("no device carries ... potassium ... in its device name") is contradicted by two real registry matches and should be narrowed before being relied on as written. The supplementary K-numbers (K233409, K232699, K250119, K250649, K250652) were not checked — clearance-summary on each returned unconfirmed ("pypdf is not installed... this claim is unchecked, not negative"), an environment gap, not a finding either way. Net: unconfirmed` overall, with the core "no hyperkalemia code in the 870.2380 family" sub-finding independently verified and the "no potassium/electrolyte string anywhere" sub-finding refuted by direct evidence.
claim 26verifiedUS
FDA's device/classification database reports regulation_number 870.2380 for the 'Machine Learning-Based Notification Software' product-code family (including QYE, reduced ejection fraction), but no section 21 CFR 870.2380 exists in the eCFR as of the 2026-08-19 issue of Title 21 -- a discrepancy between the classification database's regulation_number field and the codified CFR text that anyone citing '21 CFR 870.2380' for this product family should be aware of.
jurisdiction: US — confidence: verified — source: Verifier independently re-ran python3 -m connectors regulation 870.2380 --title 21 (cold, not reusing the research pass's own prior run): `{"status": "refuted", "source_ref": "eCFR versioner title-21, issue 2026-08-19, section=870.2380", "detail": "There is no…the full check section 21 CFR 870.2380 in the Code of Federal Regulations as of 2026-08-19..."}. Note on why this is tagged verified rather than transcribed as refuted`: the connector's internal status label describes whether a queried section backs a content assertion (i.e. "section X says Y" is refuted when X doesn't exist) — but this claim's own assertion is that no such section exists. The eCFR lookup returning "no such section" is therefore a direct, positive confirmation of exactly what the claim states, not a contradiction of it. The discrepancy is real: openFDA's classification records for the 870.2380 family (confirmed above, claim 25) cite a regulation_number that does not correspond to a real, codified CFR section as of this eCFR issue.
claim 27unconfirmedUS
In the US Get With The Guidelines-Heart Failure (GWTG-HF) registry, among 365,494 heart-failure hospitalizations at 418 sites (2014-2019), 234,332 (64%) had discharge eGFR less than 60 mL/min/1.73m2 and 18,869 (5%) were on dialysis; among the 157,439 patients with HFrEF (EF<=40%), use of triple guideline-directed therapy (ACEi/ARB/ARNI + beta-blocker + MRA) fell from 38% at eGFR>=90 to 3% among those on dialysis.
jurisdiction: US — confidence: unconfirmed — source: Verifier re-ran python3 -m connectors literature-detail 33989713 (cold re-retrieval): abstract (Fudim et al., J Am Coll Cardiol 2021, GWTG-HF registry, 418 sites, 2014-2019) states "Among 365,494 hospitalizations... 234,332 (64%) had eGFR <60 ml/min/1.73 m2...…the full check 18,869 (5%) were on dialysis" and "Among 157,439 patients with HF with reduced EF (≤40%)... 'Triple therapy'... was used in 38%, 33%, 25%, 15%, 5%, and 3% for eGFR ≥90, 60 to 89, 45 to 59, 30 to 44, <30 ml/min/1.73 m2, and dialysis, respectively" — exact match on every figure. Stays unconfirmed, not verified: literature-detail returns a Stage 0 ScanResult (connectors/result.py), which has no to_claim_line() and structurally cannot carry a confidence tag — an exact abstract match is a strong lead, not a Stage 3 appraisal (no methods review, no risk-of-bias check).
claim 28unconfirmedUS
In the DISCOVER CKD multinational prospective cohort (NCT04034992, n=1,052 adults with CKD enrolled September 2019-June 2022), 61.1% (643 patients) were receiving guideline-directed medical therapy (a renin-angiotensin system inhibitor and/or an SGLT2 inhibitor) at baseline, ranging from 42.7% in the USA, the lowest of the countries reported, to 82.2% in Spain and Sweden, the highest.
jurisdiction: US — confidence: unconfirmed — note: see jurisdiction caveat below — source: Verifier re-ran python3 -m connectors literature-detail 40972017 (cold re-retrieval): abstract (DISCOVER CKD, NCT04034992, prospective cohort) states "Of 1052 prospectively enrolled patients... 643 (61.1%) were receiving GDMT…the full check [RASi only, n = 496; SGLT2i only, n = 25; both, n = 122; range 42.7% (USA) to 82.2% (Spain, Sweden)]" — exact match. Stays unconfirmed, not verified — same structural reason as above (literature-detail is a Stage 0 ScanResult). Jurisdiction-tag note: this is an explicitly multinational cohort study (the US is only the low end of a multi-country range), not a US-isolated study, while the claim's jurisdiction: tag reads US — flagging the same metadata inconsistency noted on claims 21-24; it does not affect the accuracy of the cited figures.
claim 29unconfirmedUS
In a US Medicare fee-for-service claims cohort of 621,171 patients with heart failure with preserved ejection fraction identified 2013-2018 via a validated claims-based phenotyping model, spironolactone (a mineralocorticoid receptor antagonist) initiation rate rose from 16.8 to 19.9 per 100 person-years, while hospitalization for hyperkalemia within 6 months of initiation remained stable at 12.0 to 10.6 per 1,000 person-years among initiators over the same period.
jurisdiction: US — confidence: unconfirmed — source: Verifier re-ran python3 -m connectors literature-detail 35114384 (cold re-retrieval): abstract (US Medicare FFS cohort, TOPCAT/HFpEF, J Card Fail 2022) states "A total of 621,171 patients with HFpEF... were included," spironolactone "initiation rate/100…the full check person-years of 16.8... in 2013 and increasing to 19.9... in 2018," with hyperkalemia hospitalization "incidence rates per 1000 person-years between 2013 (12.0...) and 2018 (10.6...)" — exact match on every figure. Stays unconfirmed, not verified — same structural reason as above (literature-detail is a Stage 0 ScanResult).
claim 30unconfirmedUS
In the DISCOVER CKD retrospective cohort, hyperkalemia prevalence among CKD patients was 20.9% (37,713 of 180,416) in the UK Clinical Practice Research Datalink (2008-2019) versus 7.4% (5,924 of 80,196) in the Japan Medical Data Vision database (2008-2017); following a hyperkalemia episode, RAASi therapy was discontinued during follow-up in 50.6% of UK patients versus 29.2% of Japanese patients, and a potassium binder was initiated within 3 months of the episode in fewer than 0.2% of UK patients versus 18.7% of Japanese patients.
jurisdiction: US — confidence: unconfirmed — note: see jurisdiction caveat below — source: Verifier re-ran python3 -m connectors literature-detail 39052473 (cold re-retrieval): abstract (DISCOVER CKD retrospective cohort, UK CPRD 2008-2019, Japan MDV 2008-2017, Kidney360 2024) states "In the UK Clinical Practice…the full check Research Datalink, 37,713 patients with HK and 142,703 patients without HK were included... (HK prevalence 20.9%). In the Japan Medical Data Vision, 5924 patients with HK and 74,272 patients without HK were included... (HK prevalence 7.4%)" (i.e. 37,713/180,416 and 5,924/80,196 — matches, note the claim's "5,924" vs. the abstract's stated raw count of the same number), and "<0.2% of patients with CKD and HK in the United Kingdom initiated K+ binders within 3 months of HK index versus 18.7% in Japan," with RAASi "stopped... 50.6%... in the United Kingdom, and... 29.2%... in Japan" — exact match on every figure. Stays unconfirmed, not verified — same structural reason as above. Jurisdiction-tag note: this is a UK/Japan (non-US) comparison, as the claim text itself discloses, while the jurisdiction: tag reads US — same metadata inconsistency flagged on claims 21-24 and 28; does not affect the accuracy of the cited figures.
claim 31unverifiedUS
Outpatient RAASi titration in adult CKD/heart-failure patients requires repeat venous potassium draws between scheduled clinic visits, and patients must attend or arrange a separate blood draw for each one.
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-08-30) — never checked; recorded so the Verifier can see it
claim 32unverifiedUS
No clinical practice guideline (e.g. KDIGO, ACC/AHA/HFSA) currently mentions or recommends ECG-based hyperkalemia screening as an adjunct to RAASi titration monitoring.
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-08-30) — never checked; recorded so the Verifier can see it
claim 33unverifiedUS
Patients or caregivers would be willing and able to correctly apply, continuously wear, and maintain (recharge or replace) an adhesive multi-lead ECG patch for multi-day stretches without clinical staff supervision.
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (desirability deck, 2026-08-30) — never checked; recorded so the Verifier can see it
claim 34unverifiedUS
A defined, reachable share of the RAASi-titration outpatient CKD/heart-failure population would adopt this device, distinct from and smaller than the population's raw CKD/HF prevalence.
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (viability deck, 2026-08-30) — never checked; recorded so the Verifier can see it
claim 35unverifiedUS
This device would achieve commercial viability at a price or payment rate; no such price or rate is established anywhere in this file.
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (viability deck, 2026-08-30) — never checked; recorded so the Verifier can see it
claim 36unverifiedUS
No company other than AliveCor has been identified as pursuing FDA clearance or De Novo authorization for an ECG-based hyperkalemia-screening algorithm.
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (viability deck, 2026-08-30) — never checked; recorded so the Verifier can see it
claim 37unverifiedUS
The hyperkalemia-detection accuracy (AUC, sensitivity/specificity) demonstrated on Mayo Clinic's retrospective, single-institution, clinical-grade 2-lead ECG dataset would transfer to a continuously-worn adhesive wearable patch's ECG signal, despite motion artifact and multi-day electrode-contact degradation.
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-08-30) — never checked; recorded so the Verifier can see it
claim 38unverifiedUS
A bench or retrospective validation demonstrating the hyperkalemia-screening model maintains its discrimination accuracy when run on continuously streamed wearable-patch ECG waveform data, rather than short clinical captures, would exist before any patient wears the device.
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-08-30) — never checked; recorded so the Verifier can see it
claim 39unverifiedUS
The adhesive ECG patch and paired reader would reliably operate through multi-day continuous wear (battery life, skin adhesion, wireless streaming) in an unsupervised ambulatory home setting.
jurisdiction: US — confidence: unverified — source: deck-surfaced assumption (feasibility deck, 2026-08-30) — never checked; recorded so the Verifier can see it closely-related ECG-hyperkalemia-screening mechanism (claim 1) and may hold patent claims covering ECG-morphology-based potassium-level inference; the…the full check Generator did not identify any specific patent number and this is flagged as an open FTO question, not a cleared one. — jurisdiction: US — confidence: unconfirmed — source: python3 -m connectors patent requires a specific patent_id; none is named in this claim or discoverable from claims 1-2, so no lookup could be run. Separately confirmed PATENTSVIEW_API_KEY is not set in this environment, so even a named patent could not be checked here — this remains an open FTO question requiring both a real patent-number search and a configured API key.