K073699 · Mycare Team, Inc. · NBW · Mar 26, 2008 · Clinical Chemistry
Device Facts
Record ID
K073699
Device Name
MCT-DIABETES
Applicant
Mycare Team, Inc.
Product Code
NBW · Clinical Chemistry
Decision Date
Mar 26, 2008
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 862.1345
Device Class
Class 2
Attributes
Software as a Medical Device, Pediatric
Indications for Use
The MCT-Diabetes™ software serves as an interface between the software in personal glucose monitoring devices and a general purpose health management database to assist in the review, analysis and evaluation of blood glucose test results. MCT Diabetes is designed for home use and professional healthcare settings.
Device Story
MCT-Diabetes is an Internet-based software interface connecting personal blood glucose monitors to a secure health management database. It supports various commercial glucose monitor models. Users upload blood glucose data to a central location for review and analysis. The system provides four types of chart displays for visualizing glucose trends over time and comparing to previous periods. Patients can also manually log body weight, blood pressure, and exercise. Healthcare professionals and family members with authorized access can view reports to monitor the patient's status. The device is intended for home and professional clinical settings to assist in diabetes treatment regulation and glucose control.
Clinical Evidence
No clinical efficacy or safety studies were required. The device underwent human factors usability testing in September/October 2006 with 47 participants (Type 1 and Type 2 diabetes, including children and adults). The study evaluated setup, data upload, and interface readability per ISO 15197:2003 and FDA guidance. Results led to UI redesigns, improved error-checking, and enhanced USB upload protocols. Final software version 2.0 was validated through these usability assessments.
Technological Characteristics
Software-only device; web-based interface compatible with Internet Explorer and Firefox. Requires Windows 98 SE/2000/XP, 600 MHz Pentium III, 128 MB RAM. Connectivity via USB/serial data cables for meter-to-PC transfer. Data stored on secure remote server. Implements Active X controls for data upload. Complies with ISO 14971 (risk management) and ISO 15197 (glucose monitoring systems).
Indications for Use
Indicated for patients with diabetes, their families, and healthcare professionals in home or clinical settings to assist in the review, analysis, and evaluation of historical blood glucose test results to support diabetes management.
Regulatory Classification
Identification
A glucose test system is a device intended to measure glucose quantitatively in blood and other body fluids. Glucose measurements are used in the diagnosis and treatment of carbohydrate metabolism disorders including diabetes mellitus, neonatal hypoglycemia, and idiopathic hypoglycemia, and of pancreatic islet cell carcinoma.
Special Controls
*Classification.* Class II (special controls). The device, when it is solely intended for use as a drink to test glucose tolerance, is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 862.9.
{0}
# 510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY ASSAY AND INSTRUMENT COMBINATION TEMPLATE
A. 510(k) Number:
k073699
B. Purpose for Submission:
New submission for an accessory data management software application for glucose meters
C. Measurand:
Whole Blood Glucose
D. Type of Test:
The MyCare Team (MCT)-Diabetes is a software-only medical device which serves as an internet-based accessory which interfaces between the software in personal glucose monitoring devices and the MCT general-purpose health management database.
E. Applicant:
MyCare Team, Inc.
F. Proprietary and Established Names:
MCT-Diabetes
G. Regulatory Information:
1. Regulation section:
21CFR Sec.-862.1345-Glucose test system.
21CFR Sec.-862.2100 - Calculator/data processing module for clinical use.
2. Classification:
Class II and I, respectively
3. Product code:
NBW - System, Test, Blood Glucose, Over the Counter
JQP-Calculator/Data Processing Module, For Clinical Use
4. Panel:
Chemistry (75)
H. Intended Use:
1. Intended use(s):
See indications(s) for use below
2. Indication(s) for use:
The MCT-Diabetes™ software serves as an interface between the software in personal glucose monitoring devices and a general purpose health management database to assist in the review, analysis and evaluation of blood glucose test
{1}
results. MCT Diabetes is designed for home use and professional healthcare settings.
3. Special conditions for use statement(s): Not Applicable
4. Special instrument requirements: Compatible glucose meters for home use such as glucose meters by Roche Diagnostics, Bayer, BD, Johnson & Johnson, Abbott, and Nova Biomedical.
I. Device Description:
MCT-Diabetes is a software-only device. MCT-Diabetes allows the patient to transfer their blood glucose readings from their glucose meter(s) over a secure connection to the MCT-Diabetes server. The glucose readings are then stored in a secure database for the patient to review. MCT-Diabetes allows the patient to group their readings into specific timeslots and then review their readings for each timeslot over long periods of time. This type of analysis provides the patient with a better view of how they are managing their diabetes and the convenience of viewing the output from all blood glucose monitors in one place. The patient can then also allow others that assist them in the management of their disease to view their data and send secure messages back to the patient about their readings.
J. Substantial Equivalence Information:
1. Predicate device name(s): Home Diagnostics, Inc., TrackRecord Data Management Software
2. Predicate 510(k) number(s): k070593
3. Comparison with predicate:
2 of 9
{2}
| | MCT-Diabetes (New Device) | Predicate Device TrackRecord Data Management Software (k070593) | EQUIVALENT OR DIFFERENT |
| --- | --- | --- | --- |
| COMPARISON OF GENERAL CHARACTERISTICS | | | |
| Indications for Use Statement | The MCT-Diabetes™ software serves as an interface between the software in personal glucose monitoring devices and a general purpose health management database to assist in the review, analysis and evaluation of blood glucose test results. MCT Diabetes is designed for home use and professional healthcare settings. | TrackRecord Data Management Software is intended for use in the home or in clinical settings, for single or multi-patient use, to assist people with diabetes as well as their healthcare professionals in the review, analysis and evaluation of historical blood glucose test results to support effective diabetes management. | Equivalent |
| Intended Use | Home use or Clinical Assist diabetics, families, and professionals in management of blood glucose Support diabetes management Single or multi-patient use | Home use or Clinical Assist diabetics, families, and professionals in management of blood glucose Support diabetes management Single or multi-patient use | Equivalent |
| Data Source | Compile data from multiple different brands of glucose meters for display in one place on user's personal computer | Compile data from Home Diagnostics brand glucose meters | Equivalent |
| Classification | NBW, system, test, blood glucose, over the counter 862.1345, Class II JQP, calculator/data processing module, for clinical use, 862.2100, Class I | NBW, system, test, blood glucose, over the counter 862.1345, Class II JQP, calculator/data processing module, for clinical use, 862.2100, Class I | Equivalent |
| Panel | Clinical Chemistry | Clinical Chemistry | Equivalent |
| Software Use | Single (individual) or multiple user (clinical) settings | Single or multiple user settings | Equivalent |
| Use in Clinic | Patient list available | Search for specific patient | Equivalent |
| Report types | Logbook Readings Line Chart Average Bar Chart Percentage Pie Chart | Logbook Glucose Trend Pie Chart (Conformance) Summary | Equivalent |
3 of 9
{3}
| | MCT-Diabetes (New Device) | Predicate Device TrackRecord Data Management Software (k070593) | EQUIVALENT OR DIFFERENT |
| --- | --- | --- | --- |
| | Percentage Readings by Time of Day | | |
| **COMPARISON OF TECHNICAL SPECIFICATIONS** | | | |
| **Special Glucose Monitor Instrument Requirements** | Wide range of supported meters are listed on website;
As additional software protocols are obtained and devices are validated, capabilities will be broadened to include other blood glucose meters | Home Diagnostics brand blood glucose meters only | Different
However, the same validation/verification of software protocols (from blood glucose manufacturers) with MyCare Team software prior to addition to list |
| **Capable of uploading data from various glucose monitoring devices? Software download requirements** | Yes. Acceptable devices are listed and include the majority of currently available devices. Software resides on the Internet and not on the User's Personal Computer (PC) | Yes, for Home Diagnostics brand monitors.
Software driver must be uploaded on the device or installed on the PC | Equivalent |
| **User's Personal Computer (PC) Requirements** | Windows 98 Second Edition (SE), Windows 2000 and Windows XP Home and Professional
600 MHz Intel Pentium III or equivalent
Minimum 128 MB RAM
100-200 MB RAM used | Windows 98 Second Edition (SE), Windows 2000 and Windows XP Home and Professional
600 MHz Intel Pentium III or equivalent
Minimum 128 MB RAM
100-200 MB RAM used | Equivalent
Equivalent
Equivalent
Equivalent |
| **User's Personal Computer (PC) Requirements** | | | |
4 of 9
{4}
| | MCT-Diabetes (New Device) | Predicate Device TrackRecord Data Management Software (k070593) | EQUIVALENT OR DIFFERENT |
| --- | --- | --- | --- |
| | during installation and 100 | during installation and 100 | |
| | MB used after installation | MB used after installation | |
| | CD ROM drive | CD ROM drive | Equivalent |
| | Manufacturer's required cable can be ordered as a service to the customer. | 9-pin/25-pin COM or USB port required with a serial or USB data cable CD ROM required | Equivalent |
| | Installed from MyCareTeam Website | Installed using CD | Different Installation is performed via the Internet; thus, no CD is required |
| Technical Support | Yes | Yes | Equivalent |
| User's Manual | Available on Internet while using program ("Help System") | Link via icon | Equivalent Both programs have Help system (but different access) |
| Cable Availability | Manufacturer cable ordered for customer at their request; original manufacturer equipment with no re-labeling | Serial cable, cable available separately | Equivalent |
| Auto-detect COM port | Yes | Yes | Equivalent |
| Installation of program | Installed from internet link | Installed using CD | Equivalent |
| DATA INPUT AND OUTPUT | | | |
| Required data on patient entry includes patient ID, name, address, etc. | Yes | Yes | Equivalent |
| Insurance information | No | Yes | Different |
| Physician information | Multiple individuals | Multiple individuals | Equivalent |
| Diabetes educator information | Multiple individuals | Multiple individuals | Equivalent |
| Types of information that can be manually | Insulin list, medication list, exercise, blood pressure | Insulin list and medication list | Different More information |
5 of 9
{5}
| | MCT-Diabetes (New Device) | Predicate Device TrackRecord Data Management Software (k070593) | EQUIVALENT OR DIFFERENT |
| --- | --- | --- | --- |
| entered | data, laboratory results | | can be entered in MCT-Diabetes |
## K. Standard/Guidance Document Referenced (if applicable):
Software guidance documents:
- Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices. Issued May 11, 2005.
- General Principles of Software Validation. Issued January 11, 2002.
- Guidance for Off-the-Shelf Software Use in Medical Devices. Issued September 9, 1999.
- Guidance for Industry – Cybersecurity for Networked Medical Devices Containing Off-the-Shelf (OTS) Software. Issued January 14, 2005.
Non-Software guidance and standards
- ISO 15197: 2003. In vitro diagnostic test systems – Requirements for blood-glucose monitoring systems for self-testing in managing diabetes mellitus. First edition.
- Guidance for Industry and FDA Staff - Total Product Life Cycle for Portable Invasive Blood Glucose Monitoring Systems. Issued 10/24/2006.
- ISO 14971: 2007. Medical Devices – Application of risk management to medical devices. Second edition.
## L. Test Principle:
The MyCare Team (MCT)-Diabetes software is an accessory to compatible meters, which use specific test principles such as in Accu-Chek Active (k021827), Accu-Chek Advantage (k000365), Accu-Chek Aviva (k043474), Accu-Chek Compact (k022171), Accu-Chek Compact Plus (k031755), Accu-Chek Complete (k000364), Ascensia Breeze (k024062), Ascensia Breeze 2 (k062347), Ascensia Contour (k023657), Ascensia Dex 2 (k963500), Ascensia Elite XL (k951537), BD Logic (k022581), BD Paradigm Link (k040603), Lifescan OneTouch Profile (k950727), Lifescan OneTouch Ultra (k011479), Lifescan OneTouch Ultra 2 (k053529), Lifescan OneTouch Ultra Smart (k021819), MediSense Optium (k051213), MediSense Precision Xtra (k040814), Nova Max (k040603), TheraSense FreeStyle (k012014), TheraSense FreeStyle Freedom (k051839), TheraSense FreeStyle Lite (k070850).
## M. Performance Characteristics (if/when applicable):
1. Analytical performance:
a. Precision/Reproducibility: see above associated devices
b. Linearity/assay reportable range: see above associated devices
c. Traceability, Stability, Expected values (controls, calibrators, or methods): see above associated devices
d. Detection limit:
{6}
see above associated devices
e. Analytical specificity:
see above associated devices
f. Assay cut-off:
see above associated devices
2. Comparison studies:
a. Method comparison with predicate device:
see above associated devices
b. Matrix comparison:
Not Applicable
3. Clinical studies:
a. Clinical Sensitivity:
Not Applicable
b. Clinical specificity:
Not Applicable
c. Other clinical supportive data (when a. and b. are not applicable):
Usability studies were designed to test human factors such as ease of operation, readability of the measured results, unambiguous messages to the user, and evaluation of the instructions for use (i.e., the help features) as described in Sections 4.4 and 8.4 of ISO 15197:2003 and in Section 3 of the FDA Total Product Life Cycle guidance document (2006). As recommended in Section 8.3 of ISO 15197, study participants were given two surveys to evaluate their understanding of the system and were not given additional training, instructions, or assistance than those routinely provided with the MCT-Diabetes system. The studies were conducted in September and October 2006, respectively, with 47 completed responders out of 65 total participants.
The survey group included a near-even representation of individuals with Type 1 and Type II diabetes, including both children and adults. All responses were kept confidential and participants remained anonymous throughout both surveys. Data were reported in aggregate and no identifying information was linked back to individual responses.
The human factors that were most applicable to this software-only device are the user characteristics (individuals with vision problems must be able to understand the system) and the device-user interface ensuring ease of operation, readability of the result, and unambiguous messages to the user.
The first survey was designed to evaluate the set up process for MCT-Diabetes, including registering with MyCare Team, uploading of blood glucose data, and the initial display of the blood glucose data. The outcome of this survey resulted in the following changes to the MCT-Diabetes software:
7 of 9
{7}
- Enhancements to the Active X control for uploading data from various meters in order to make the upload process proceed more smoothly from USB ports.
- Support for additional meters
- Additional error-checking and updated help files for users
The second survey was designed to evaluate the usability experience for the participants including evaluations of all features of the MCT-Diabetes software. The outcome of this survey resulted in the following changes to the MCT-Diabetes software:
- Redesign of the user interface for a number of web pages, including new icons for better readability and navigation.
- Addition of new features & functionality, including date of last upload, user setting of blood glucose ranges, and user adjustment of times of day
The usability testing and results was factored appropriately into the Risk Analysis. As problems were identified, software changes were made and documented. The final version after usability testing was identified as Version 2.0.
4. Clinical cut-off: Not Applicable
5. Expected values/Reference range: see above associated devices
N. Instrument Name:
MyCare Team, Inc, MCT-Diabetes software
O. System Descriptions:
1. Modes of Operation:
MCT-Diabetes provides a Web Based user interface that is compatible with Microsoft Internet Explorer and Mozilla Firefox. The data upload control is not directly accessible by the user, but only as provided through the web based user interface.
- Windows 98 Second Edition (SE), Windows 2000 and Windows XP Home and Professional
- 600 MHz Intel Pentium III or equivalent
- Minimum 128 MB RAM
- 100-200 MB RAM used
2. Software:
{8}
FDA has reviewed applicant’s Hazard Analysis and software development processes for this line of product types:
Yes ☐ X or No ☐
3. Specimen Identification:
Meter controlled, by time and date stamp
4. Specimen Sampling and Handling:
Not Applicable
5. Calibration:
Not Applicable
6. Quality Control:
Not Applicable
P. Other Supportive Instrument Performance Characteristics Data Not Covered In The “Performance Characteristics” Section above:
Q. Proposed Labeling:
The labeling is sufficient and it satisfies the requirements of 21 CFR Part 809.10.
R. Conclusion:
The submitted information in this premarket notification is complete and supports a substantial equivalence decision.
9 of 9
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.