K023219 · Becton, Dickinson & CO · NBW · Dec 6, 2002 · Clinical Chemistry
Device Facts
Record ID
K023219
Device Name
BECTON DICKINSON DIABETES SOFTWARE
Applicant
Becton, Dickinson & CO
Product Code
NBW · Clinical Chemistry
Decision Date
Dec 6, 2002
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 862.1345
Device Class
Class 2
Indications for Use
The BDTM Diabetes Software is intended for use as a data management tool for acceptance, transfer, display, storage, processing (e.g. averaging), reporting, and printing of patient blood glucose monitoring data. The device is intended for use with a BD Blood Glucose Monitoring System only.
Device Story
BD Diabetes Software functions as a data management system for blood glucose monitoring. Inputs include patient blood glucose data transferred from BD Blood Glucose Monitors via serial/USB cable or via manual entry. The software processes data through averaging and storage, producing reports and printouts for clinical review. Used in home and professional settings; operated by patients or healthcare providers. The software aids in diabetes management by organizing and displaying glucose trends, facilitating clinical decision-making based on historical data.
Clinical Evidence
No clinical data. Performance summary based on system, hardware, software, packaging, and electrical safety verification and validation testing.
Technological Characteristics
Microsoft Windows-based software application (Windows 95/NT 4.0 or later). Operates on Intel-compatible PCs. Connectivity via BD Interface serial or USB cable. Data management functions include averaging, storage, and reporting.
Indications for Use
Indicated for use as a data management tool for patients using BD Blood Glucose Monitoring Systems to accept, transfer, display, store, process, report, and print blood glucose monitoring data.
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.
Predicate Devices
WinGlucofacts (Bayer Diagnostics)
Submission Summary (Full Text)
{0}------------------------------------------------
K0233219
# 510K Summary of Safety and Effectiveness
#### 1. Submitted By:
John Schalago Manager, Regulatory Affairs
Becton Dickinson Consumer Healthcare 1 Becton Drive Franklin Lakes, NJ 07417-1883
Phone: 201-847-5663 201-848-0457 Fax:
#### 2. Device Name:
BDTM Diabetes Software Trade Name: Common Names: Blood Glucose Meter and Data Management System Classification Name: Glucose test system Classification: 862.1345
#### 3. Predicate Device:
WinGlucofacts
Manufactured by: Bayer Diagnostics
#### Device Description: 4.
BD™ Diabetes Software is data management software intended for use with BD Blood Glucose Monitoring Systems only. The software is designed to operate on a Windows/Intel compatible platform, and is available in home use and professional use options. Data may be downloaded from a BD Blood Glucose Monitor or manually entered.
BD™ Diabetes Software provides data management tools for acceptance, transfer, display, storage, processing (e.g. averaging), reporting, and printing of patient blood glucose monitoring data. In addition, the BDTM Diabetes Software has an online help feature.
{1}------------------------------------------------
## 510K Summary of Safety and Effectiveness (Continued)
### ડ. Intended Use:
The BDTM Diabetes Software is intended for use as a data management tool for acceptance, transfer, display, storage, processing (e.g. averaging), reporting, and printing of patient blood glucose monitoring data.
The device is intended for use with a BD Blood Glucose Monitoring System only.
#### Technological Characteristics: 6.
The BDTM Diabetes Software is a Microsoft Windows based software application for diabetes data management. The software allows for data transfer from a BD Blood Glucose Monitor via a BD Interface serial or USB cable. BD™ Diabetes Software is designed to operate an Intel compatible PC with Microsoft Windows 95 or later, and Microsoft NT version 4.0 or later operating system.
#### 7. Performance Summary:
BD™ Diabetes Software testing consisted of system, hardware, software, packaging, electrical safety, and end-user evaluation. System verification and validation activities demonstrate that BD™ Diabetes Software will perform as intended when used in accordance with device labeling. Electrical components have been tested and certified to conform to appropriate voluntary and mandatory standards.
The term "substantial equivalence" as used in this 510(k) Notification is limited to the definition of substantial equivalence found in the Federal Food, Drug, and Cosmetic Act, as amended and as applied under 21 CFR 807, Subpart E, under which a device can be marketed without pre-approval or classification. A determination of substantial equivalency under this notification is not intended to have any bearing whatsoever on the resolution of patent infringement suits or any other patent matters. No statements related to, or in support of substantial equivalence herein shall be construed as an admission against interest under the US patent Laws or their application by the courts.
{2}------------------------------------------------
### DEPARTMENT OF HEALTH & HUMAN SERVICES
Image /page/2/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo features a stylized caduceus symbol, which is a staff with two snakes coiled around it. The caduceus is positioned to the right of the text "DEPARTMENT OF HEALTH & HUMAN SERVICES · USA", which is arranged in a circular fashion around the left side of the logo. The logo is black and white.
Food and Drug Administratio 2098 Gaither Road Rockville MD 20850
Mr. John A. Schalago MS. RAC Regulatory Affairs Manager Becton, Dickinson and Company 1 Becton Drive Franklin Lakes, NJ 07417
k023219 Re:
Trade/Device Name: Becton Dickinson Diabetes Software Regulation Number: 21 CFR 862.1345 Regulation Name: Glucose test system Regulatory Class: Class II Product Code: NBW; JQP Dated: September 18, 2002 Received: September 26, 2002
Dear Mr. Schalago:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to such additional controls. Existing major regulations affecting your device can be found in Title 21, Code of Federal Regulations (CFR), Parts 800 to 895. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Parts 801 and 809); and good manufacturing practice requirements as set forth in the quality systems (OS) regulation (21 CFR Part 820).
{3}------------------------------------------------
### Page 2
This letter will allow you to begin marketing your device as described in your Section 510(k) premarket notification. The FDA finding of substantial equivalence of your device to a legally marketed predicate device results in a classification for your device and thus, permits your device to proceed to the market.
If you desire specific information about the application of labeling requirements to your device, or questions on the promotion and advertising of your device, please contact the Office of In Vitro Diagnostic Device Evaluation and Safety at (301) 594-3084. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21CFR Part 807.97). Other general information on your responsibilities under the Act may be obtained from the Division of Small Manufacturers, International and Consumer Assistance at its toll-free number (800) 638-2041 or (301) 443-6597 or at its Internet address http://www.fda.gov/cdrh/dsma/dsmamain.html.
Sincerely yours,
Steven Sutman
Steven I. Gutman, M.D., M.B.A. Director Office of In Vitro Diagnostic Device Evaluation and Safety Center for Devices and Radiological Health
Enclosure
{4}------------------------------------------------
Attachment XI .A.1
Page l of
510(k) Number (if known):
Device Name: Becton Dickinson Diabetes Software
Indications For Use:
The BDTM Diabetes Software is intended for use as a data management tool for acceptance, transfer, display, storage, processing (e.g. averaging), reporting, and printing of patient blood glucose monitoring data.
The device is intended for use with the BD Blood Glucose Monitoring Systems only.
im
(Division Sign-Off)
vision of Clinical Laboratory Devices
510(k) Number. X02309
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
(Optional Format 3-10-98)
Rx
RTC_
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.