AT-Patch (ATP-C130/ATP-C70)
K242583ATsens Co.,Ltd. · cleared 2025-05-02 · product code DSH · Cardiovascular
Premarket evidence — what FDA accepted
source quote (p.6)
“AT-Patch consists of ECG recorder (AT-Patch device), ECG Analysis Software(AT-Report) and Real-time ECG Viewer (AT-Note). ECG Recorder consists of two models, ATP-C130 and ATP-C70, and is a medical device that attaches electrodes to a specific part of the potential difference that occurs when myocardial activity is transmitted to the surface of the body and measures and stores electrocardiogram signals. ... AT-Report is a medical device software that receives data stored in AT-Patch device using a Dedicated USB Cable and analyses it to provide information which is used to take decisions with diagnosis and can confirm the operation of AT-Patch device using the BLE communication function. ... The AT-Report software utilizes machine learning-based algorithms to automatically detect and classify arrhythmia events from ECG data recorded by the AT-Patch device.”
source quote (p.15)
“The AT-Report software utilizes machine learning-based algorithms to automatically detect and classify arrhythmia events from ECG data recorded by the AT-Patch device.”
source quote (p.18)
“Cybersecurity tests were performed in accordance the FDA recognized guidance. - Cybersecurity in medical devices: quality system considerations and content of premarket submissions. - FDA Act 524B”
Validation studies (1)
Retrospective clinical
sample size not stated
endpoints: accuracy of QRS detection; VEB/SVEB detection; atrial fibrillation (AF) detection; Couplets; Runs; Tachycardia detection; Sensitivity; Positive Predictive Value (PPV); False Positive Rate (FPR)
standards: ANSI/AAMI EC57:2012
Reported performance (1 observation)
source quote (p.19)
“Performance was assessed based on Sensitivity, Positive Predictive Value (PPV), and False Positive Rate (FPR), validated against reference data.”
Each value carries its own analysis unit and task — never compare or pool across devices. Source: 510(k) summary PDF.
Predicate network
Postmarket — what happened after clearance
- adverse_event_inflection
MAUDE adverse-event reports for product code DSH: 288 in the 12 months ending 2026-06, vs a 81.7/12mo average over the prior 3 windows (+253%). Code-level count — reports are not attributed to this specific device.
first seen 2026-07-08 · openFDA /device/event.json count=date_received product_code=DSH
Recall and MAUDE counts are product-code-level (reports aren't reliably attributable to one device); a recall is shown as device-attributed only when the recall record itself lists this clearance number. Signals are descriptive observables with sources — never a judgment that the device is unsafe or drifting. Snapshot 2026-07-08.
Reimbursement — how devices like this got paid
Not yet tracked — no payment pathway indexed for this clearance (the reimbursement corpus is a growing seed set).
Applicable FDA guidance — what the submission is measured against
FDA guidance documents and guiding principles applicable to 510(k) AI/ML devices in the Cardiovascular panel. A curated reference index, not legal or regulatory advice — each item states its own status, and a draft is never binding.
- Final guidance2026-01Clinical Decision Support Software
Clinical decision support · SaMD (general)
New final guidance issued Jan 2026, superseding the Sept 2022 version; narrows the device-CDS scope. Applies to software that informs clinical management.
- Final guidance2026-01General Wellness: Policy for Low Risk Devices
SaMD (general) · Clinical decision support
Revised final (Jan 2026); now addresses noninvasive products estimating physiologic parameters (SpO2, BP, glucose). Reshapes the device / non-device line for AI wellness features.
- Final guidance2025-09Computer Software Assurance for Production and Quality Management System Software
SaMD (general) · Postmarket
Final (Sept 2025). Covers software used in production/QMS (incl. ML development-pipeline tooling), superseding Section 6 of the 2002 GPSV — not device software functions themselves.
- Final guidance2025-06Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions
Cybersecurity · Software premarket content
Reissued June 2025 (retitled 'Quality Management System', was Sept 2023 'Quality System'); adds coverage of FD&C Act §524B cyber devices.
- Final guidance2024-12Marketing Submission Recommendations for a Predetermined Change Control Plan for Artificial Intelligence-Enabled Device Software Functions
Predetermined Change Control Plan · AI/ML lifecycle · Software premarket content
Final (Dec 2024). Supersedes the April 2023 AI/ML PCCP draft.
- Final guidance2023-10Electronic Submission Template for Medical Device 510(k) Submissions
Software premarket content
eSTAR has been mandatory for 510(k)s since Oct 2023 — operationally unavoidable, though not AI-specific.
- Final guidance2023-08Off-The-Shelf Software Use in Medical Devices
Software premarket content · SaMD (general)
Final (Aug 2023). Applies when a device incorporates off-the-shelf software components (common in ML stacks).
- Final guidance2023-06Content of Premarket Submissions for Device Software Functions
Software premarket content · SaMD (general)
Final (June 2023); replaced the May 2005 'Software Contained in Medical Devices' guidance. Documentation level drives the software content of the submission.
- Final guidance2022-09Policy for Device Software Functions and Mobile Medical Applications
SaMD (general) · Clinical decision support
Current version Sept 2022. Frames which software functions FDA regulates as devices.
- Final guidance2021-10De Novo Classification Process (Evaluation of Automatic Class III Designation)
De Novo pathway
Final (Oct 2021), issued with the De Novo final rule. Most relevant to first-of-a-kind devices without a predicate (DEN-numbered clearances).
- Final guidance2016-12Postmarket Management of Cybersecurity in Medical Devices
Cybersecurity · Postmarket
- Final guidance2002-01General Principles of Software Validation
SaMD (general) · Software premarket content
Still active except Section 6 (superseded Sept 2025 by the Computer Software Assurance final guidance).
- Draft guidance2025-01Artificial Intelligence-Enabled Device Software Functions: Lifecycle Management and Marketing Submission Recommendations
AI/ML lifecycle · Software premarket content · Transparency
Draft as of July 2026 (published Jan 2025); finalization is on CDRH's FY2026 agenda but not yet published. Treat as FDA's stated direction, not a binding expectation.
- Draft guidance2024-08Predetermined Change Control Plans for Medical Devices
Predetermined Change Control Plan · Postmarket
Draft (Aug 2024) extending PCCPs beyond AI to all devices under FD&C §515C; not final as of July 2026.
- Guiding principles2024-06Transparency for Machine Learning-Enabled Medical Devices: Guiding Principles
Transparency · AI/ML lifecycle
- Guiding principles2023-10Predetermined Change Control Plans for Machine Learning-Enabled Medical Devices: Guiding Principles
Predetermined Change Control Plan · AI/ML lifecycle
FDA/Health Canada/MHRA joint principles (Oct 2023); companion to the GMLP and Transparency principles.
- Guiding principles2021-10Good Machine Learning Practice for Medical Device Development: Guiding Principles
AI/ML lifecycle · SaMD (general)
FDA/Health Canada/MHRA joint principles (Oct 2021). Foundational, not a binding guidance; IMDRF issued a related GMLP document Jan 2025.
Applicability is derived from the device's FDA advisory panel and pathway — cross-cutting guidances apply to every AI/ML device; panel-specific ones are flagged. Titles, dates, and links verified against fda.gov as of July 2026.