EVALUATION OF AUTOMATIC CLASS III DESIGNATION FOR STUDIO on the Cloud Data Management Software DECISION SUMMARY



Similar documents
Medical Device Software

FDA Releases Final Cybersecurity Guidance for Medical Devices

sbchoi~kku.edu jeremy~sooil.com DANA Diabecare IlS Insulin Infusion pump Infusion pump Class II

CENTER FOR CONNECTED HEALTH POLICY

510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY

Mobile Medical Application Development: FDA Regulation

Developing a Mobile Medical App? How to determine if it is a medical device and get it cleared by the US FDA

AgaMatrucx. NV2 21 Salem, NH oz (k) Sumnmary

The Shifting Sands of Medical Software Regulation

2. Contact Person: Garo Mimaryan, MS., RAC 7 Technical Regulatory Affairs Specialist III 3. Phone Number: (914)

Mobile Medical Applications

The U.S. FDA s Regulation and Oversight of Mobile Medical Applications

DICOM Grid, Inc. January 25, Senior Consultant Biologics Consulting Group, Inc. 400 N. Washington Street, Suite 100 ALEXANDRIA VA 22314

CDRH Regulated Software

January 12, Dear Amy Yang:

Q(K SVJM~jPagelIof 3

Mobile Medical Applications: FDA s Final Guidance. M. Elizabeth Bierman Anthony T. Pavel Morgan, Lewis & Bockius, LLP

WHITEPAPER: SOFTWARE APPS AS MEDICAL DEVICES THE REGULATORY LANDSCAPE

510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY DEVICE AND INSTRUMENT TEMPLATE

Suzanne B. Schwartz, MD, MBA Director Emergency Preparedness/Operations & Medical Countermeasures (EMCM Program) CDRH/FDA

Overview of Medical Device Design Controls in the US. By Nandini Murthy, MS, RAC

Challenges in Glycemic Control in Adult and Geriatric Patients. Denyse Gallagher, APRN-BC, CDE Endocrinology Nurse Practitioner

FDA Issues Final Guidance on Mobile Medical Apps

Introducing DEXCOM STUDIO INTUITIVE. FOCUSED. SIMPLIFIED. HELP TAKE the GUESSWORK OUT of GLUCOSE PATTERN MANAGEMENT

CDRH Regulated Software Looking back, looking forward

MEDICAL DEVICE Cybersecurity.

Guidance for Industry and FDA Staff Tonometers - Premarket Notification [510(k)] Submissions

Medical Device Software Standards for Safety and Regulatory Compliance

Risk Management and Cybersecurity for Devices that Contain Software. Seth D. Carmody, Ph.D. 12 th Medical Device Quality Congress March 18, 2015

510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY

Regulation of Mobile Medical Apps

Memorandum. Factual Background

Cybersecurity for Medical Devices

Security of Medical Device Applications

Medical Software Development. International standards requirements and practice

Section 5: Quality Systems Regulation (QSR) and Good Manufacturing Practice (GMP)

Tidepool FDA Pre-submission Draft Meeting Minutes

How To Write Software

Templates. FDA Mobile Medical App Regulations. Your own sub headline This is an example text. Your Logo

PREP Course #27: Medical Device Clinical Trial Management

510(k) Summary May 7, 2012

Datrix, Inc NOV Appendix G. 510(k) Summary of Safety and Effectiveness for Datrix, Inc CardioServer ECG Management System

The HIPAA Security Rule: Cloudy Skies Ahead?

Regulatory Considerations for Medical Device Software. Medical Device Software

General. What is a laboratory test? What is a waived test?

Summary of: P890003/S285, P090013/S112, P010031/S397, P010015/S215, P980016/S436, P980035/S343. Background and Summary

How to Use the Design Process to Manage Risk: Elements of Design Controls and Why It Matters

Mobile Medical Apps. Purpose. Diane Romza Kutz Fredric E. Roth V. Regulation and Risks. Purpose of today s presentation

How To Regulate A Medical Device From A Cell Phone

KIZ 2,33-3 p8 ~ 510(k) Summary. As required by 21 CFR (c) 510(k) Premarket Notification Submission AFrame Digital MobileCare Monitor.

AND. CE IT Community Town Hall Meeting Feb. 8, 2012

May 7, Tactile Systems Technology Inc Daniel Chase V.P. Engineering & Operations 1331 Tyler St NE Minneapolis, Minnesota 55413

US & CANADA: REGULATION AND GUIDELINES ON MEDICAL SOFTWARE AND APPS OR

Mobile Medical Applications: An Overview of FDA Regulation

ORACLE CONSULTING GROUP

Medical Product Software Development and FDA Regulations Software Development Practices and FDA Compliance

MOBILE MEDICAL APPLICATIONS

Understanding Medical Device Regulation for mhealth A Guide for Mobile Operators

FDA Pre-Submission Cover Letter

Guidance for Industry Diabetes Mellitus Evaluating Cardiovascular Risk in New Antidiabetic Therapies to Treat Type 2 Diabetes

Guidance on Risk Analysis Requirements under the HIPAA Security Rule

Center for Clinical Standards and Quality/Survey & Certification Group

Guidance for Industry

0 EC V-,) 133 Lj9a

Inspections, Compliance, Enforcement, and Criminal Investigations

510(K) SUMMARY. 510(k) Number KOS'00-r

AW Server 510 (k) Summary of Safety and Effectiveness

Document issued on: May 11, 2005

General Wellness: Policy for Low Risk Devices. Draft Guidance for Industry and Food and Drug Administration Staff

MEDICAL DEVICE GUIDANCE

Medical Device Data Systems, Medical Image Storage Devices, and Medical Image Communications Devices

JOURNAL OF MEDICAL INFORMATICS & TECHNOLOGIES Vol. 21/2012, ISSN

How To Know If A Mobile App Is A Medical Device

February 5, Dear Kristin Pabst,

JDRF Type One Nation Research Summit Diabetes Technology: A Bridge to a Cure

Information Sheet Guidance For IRBs, Clinical Investigators, and Sponsors

March 20, Dear Mr. Chen:

510(k) Summary GlobalMedia Group, LIC. MAY CONiM

Effective Software Verification for Medical Devices

Abbott Diabetes Care Inc. ART20494 Rev. B 02/11

Mirador. Features include: Applications:

HIPAA Security. 1 Security 101 for Covered Entities. Security Topics

August 12, Oertli Instrumente AG Ms. Karin Rohr Head of Quality Management & Regulatory Affairs Hafnerwisenstrasse 4 CH 9442 Berneck Switzerland

On Behalf of: InTouch Health

Building 6, Suite 300 RyeBrook, NY C-ontact-N~ame: --- William H-. Schofield Director of TeleHealth Operations. Signal,_Radiofrequency

WHAT CAN I DO TO REDUCE MY RISK OF DEVELOPING THE COMPLICATIONS OF TYPE 1 DIABETES?

Quality System: Design Control Procedure - Appendix

International Medical Device Regulators Forum (IMDRF) US FDA Center for Devices and Radiological Health - Update

Document issued on April 13, The draft of this document was issued on April 23, 2014.

Transcription:

A. DEN Number: DEN140016 EVALUATION OF AUTOMATIC CLASS III DESIGNATION FOR STUDIO on the Cloud Data Management Software B. Purpose for Submission: DECISION SUMMARY De novo request for adjunct data management software C. Measurand: The submission is for a continuous glucose monitor data management software device. D. Type of Test: Diabetes data management system E. Applicant: Dexcom, Inc. F. Proprietary and Established Names: STUDIO on the Cloud Data Management Software G. Regulatory Information: 1. Regulation: 21 CFR 862.2120, Continuous glucose monitor data management system. 2. Classification: Class I, exempt 3. Product code: PHV 4. Panel: Chemistry (75) H. Intended Use: 1. Intended use(s): 1

The STUDIO on the Cloud Data Manager Software is intended for use by both patients and healthcare professionals to assist people with diabetes and their healthcare professionals in the review, analysis and evaluation of historical CGM data to support effective diabetes management. It is intended for use as an accessory to CGM devices with data interface capabilities. 2. Indication(s) for use: Same as intended use 3. Special conditions for use statement(s): For prescription home use. This device is intended for display of retrospective glucose data and not for real-time display of glucose results. This device is not intended for making treatment decisions. This device is not intended for calculating insulin or other drug doses. This device is not intended for controlling insulin pumps or other drug delivery systems. 4. Special instrument requirements: Dexcom G4 PLATINUM Continuous Glucose Monitoring System I. Device Description: The STUDIO on the Cloud Data Management ( STUDIO ) Software is comprised of a data analysis and storage platform, report generation software, and an information delivery service. Specifically, the proposed STUDIO Software performs the following functions: Data Upload: the SweetSpot Fetch Utility application will be used to access data from a Receiver, using either Mac or PC operating systems; Data Analysis: certain SweetSpot Platform functions will be used to validate, aggregate, and analyze (e.g., correlate) CGM data, and to create charts and reports that mimic the current STUDIO Pattern and Glucose Strips charts and reports; Reports: The current STUDIO Pattern charts will be displayed on the user s computer screen, and both the Pattern and Glucose Strip charts can be saved to the user s computer in PDF format. Both reports may be printed by the user as a PDF document. The STUDIO Software uses only retrospective data stored on the G4 PLATINUM device to create statistical reports, and does not make treatment recommendations. 2

J. Standard/Guidance Documents Referenced: 1. Guidance for Industry, FDA Reviewers and Compliance on Off-The-Shelf Software Use in Medical Devices, September 9, 1999 2. Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices, May 11, 2005 3. Content of Premarket Submissions for Management of Cybersecurity in Medical Devices, Draft Guidance for Industry & FDA Staff, June 13, 2013 4. Cybersecurity for Networked Medical Devices Containing Off-the-Shelf (OTS) Software, January 14, 2005 5. General Principles of Software Validation, Final Guidance for Industry and FDA Staff, January 11, 2002 6. Guidance for Industry and Food and Drug Administration Staff, Factors to Consider When Making Benefit-Risk Determinations in Medical Device Premarket Approval and De Novo Classifications, March 28, 2012 7. ISO 14971:2012 Medical devices Application of risk management to medical devices 8. IEC/TR 80002-1:2009 Medical device software - Part 1: Guidance on the application of ISO 14971 to medical device software 9. ANSI/AAMI/IEC 62304:2006 Medical device software Software life cycle processes 10. ISO 13485: Quality Systems - Medical Devices - System Requirements for Regulatory Purposes 11. U.S. Food and Drug Administration, 21 CFR Part 820: Quality System Regulation 12. NIST SP 800-53 rev3: Recommended Security Controls for Federal Information Systems and Organizations 13. HIPAA: Health Insurance Portability and Accountability Act K. Test Principle: L. Performance Characteristics (if/when applicable): 1. Analytical performance: a. Reproducibility/Precision b. Linearity/assay reportable range: 3

c. Traceability, Stability, Expected values (controls, calibrators, or methods): d. Detection limit e. Analytical specificity: 2. Comparison studies: a. Method comparison with predicate device: b. Matrix comparison: 3. Clinical studies: A usability study was performed with Forty Four (44) lay and professional users with varying demographic characteristics (age, sex, and education level). The intent of the study was to verify software ease of use and label comprehension. The study determined that 96% of assigned tasks were able to be completed by users without assistance. 4. Expected Values M. Instrument Names: STUDIO on the Cloud Data Management Software N. System Description: 1. Modes of Operation: Does the applicant s device contain the ability to transmit data to a computer, webserver, or mobile device? Yes X or No. 4

Does the applicant s device transmit data to a computer, webserver, or mobile device using wireless transmission: Yes or No X. 2. Software: FDA has reviewed applicant s Hazard Analysis and software development processes for this line of product types: Yes X or No 2. Specimen Identification: Not Applicable 3. Specimen Sampling and Handling: Not Applicable 4. Calibration: Not Applicable 5. Quality Control: Not Applicable O. Other Supportive Instrument Performance Characteristics Data Not Covered In the Performance Characteristics Section above: 1. The following documentation related to the STUDIO on the Cloud Data Management Software was reviewed and found to be acceptable: level of concern, software description, device hazard analysis, software requirements specifications, architecture design chart, software design specification, traceability analysis, software development environment description, verification and validation testing, and revision level history. 2. Bench Testing was perfomed using data from forty (40) G4 PLATINUM receivers. CGM data were uploaded from the receivers using the STUDIO on the Cloud Data Management Software and were compared to the same data downloaded to a PC. All data fields were reported to be 100% accurate. P. Proposed Labeling: The labeling is sufficient and satisfies the requirements of 21 CFR Part 801, 21 CFR Part 809, and 801.109. 5

Q. Identified Potential Risks and Required Mitigations Table Identified Risks and Required Mitigations Identified Risk Required Mitigation Device malfunction (e.g., incorrect data General controls, including design controls and analysis, etc.) restriction as a prescription device that must comply with 21 CFR 801.109. Device malfunction (e.g., incorrect data analysis, etc.) may lead to diabetes mismanagement and poor glycemic control. This risk can be adequately mitigated by general controls, including design controls and restriction as a prescription device that must comply with 21 CFR 801.109. R. Benefit/Risk Analysis Summary Summary of the Benefit(s) The STUDIO on the Cloud Data Management Software is convenient to use since it analyzes and correlates several sources of diabetes management-relevant information (e.g. user glucose levels, meals, insulin delivery, and exercise data) into one software program. The data sorting and presentation functions of the STUDIO on the Cloud Data Management Software provide patients and their doctors access to a more complete clinical picture of a patient s current disease, as well as of the impact of past diabetes management decisions on a patient s glucose levels. The convenience of using the device should translate into better record-keeping compliance by the patient, and the greater access provided to data should assist the patient and their physician with the identification of the patient s unique glucose excursion triggers; together, these benefits should allow patients and their doctors to make rational modifications to the patient s diabetes management plan, with the goal of achieving better glycemic control. 6

Summary of the Risk(s) Device malfunction may lead to diabetes mismanagement and poor glycemic control. Decisions made based on incorrect data or faulty analyses may put the patient at risk of more frequent acute episodes of hypoglycemic and/or hyperglycemic excursions. These episodes increase the likelihood of hospitalization and/or death. Chronic poor glycemic control could lead to irreversible diabetes-related sequelae (e.g. retinopathy, neuropathy, nephropathy and arteriosclerosis). These risks can be adequately mitigated by the sponsor s verification and validation and design control activities which ensure that the risk of malfunction is very low. Continuous glucose meters are only approved for tracking and trending; therefore another risk is that users could modify their current insulin dosage based directly on current CGM glucose values provided by the STUDIO on the Cloud Data Management Software. This risk is mitigated by product labeling which states that users should not make changes in their treatment program without talking to their healthcare providers. In addition, only retrospective CGM glucose values are provided by the software, so real-time CGM glucose values are not readily available to users. Risks are mitigated by general controls, including requiring design controls and restriction as a prescription device that must comply with 21 CFR 801.109. Summary of Other Factors Patients are willing to tolerate the low risk associated with use of the STUDIO on the Cloud Data Management Software because they benefit from a substantial improvement in the analysis and correlation of retrospective continuous glucose monitoring information (e.g. glucose values over time, paired with meal, exercise, and insulin bolus information), which can be used by the patients and their doctors to assist in making adjustments to their diabetes management program, with the goal of reducing glucose excursions and maintaining proper glycemic control. Conclusions Do the probable benefits outweigh the probable risks? Yes. The device is likely to provide benefits in improved diabetes management with a low associated risk. S. Conclusion: The information provided in this de novo submission is sufficient to classify this device into class I, exempt from premarket notification requirements subject to the limitations in 21 CFR 862.9, under regulation 21 CFR 862.2120. As a software containing device, this device type is also subject to design controls. FDA believes that applicable general controls, including design controls, provide reasonable assurance of the safety and effectiveness of the device type. The device is classified under the following: 7

Product Code: PHV Device Type: Continuous glucose monitor data management system Class: I (general controls) Regulation: 21 CFR 862.2120 (a) Identification. A continuous glucose monitor data management system is an electronic device intended to analyze and correlate retrospective data from a continuous glucose monitoring device. This device is intended to be used by patients or their healthcare providers as an aid in diabetes management. A continuous glucose monitor data management system provides only adjunctive information and does not provide treatment recommendations. (b) Classification. Class I (general controls). The device is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in 862.9. 8