NinesMeasure
Nines, Inc. • Radiology • 02/25/2021
Device Purpose
NinesMeasure is a semi-automatic software tool designed for trained radiologists to aid in the quantitative analysis of solid pulmonary nodules from adult thoracic CT images by providing measurements of their long and short axis diameters. The device leverages artificial intelligence, specifically machine learning algorithms, to automatically segment and measure nodules indicated by the user on DICOM images, with results displayed for review within a PACS environment.
Summary
NinesMeasure is a semi-automatic software tool developed by Nines, Inc., intended for use by trained radiologists. Its primary purpose is to assist in the analysis and review of adult thoracic CT images by providing quantitative information about pulmonary nodule size. The system focuses on measuring the long and short axis diameters of solid pulmonary nodules in the axial plane, which can be tracked across single or multiple studies over time. It is designed to be a measurement aid and should not replace a full patient evaluation or be used to make or confirm a diagnosis, nor does it alter the original medical image. The methodology involves the analysis of DICOM images where a radiologist first indicates the location of a pulmonary nodule. NinesMeasure then employs artificial intelligence, specifically machine learning algorithms, to automatically perform the segmentation and subsequent measurements of these nodules. These calculated axial measurements are then displayed for review and potential editing by the radiologist, integrating with standard Picture Archiving and Communication Systems (PACS). Performance testing, conducted through a retrospective, multi-center image comparison study across various scanner manufacturers and clinical sites, demonstrated that the device met its primary endpoints for normalized error on long and short axis diameter measurements for nodules of varying sizes (3-10mm), supporting its intended function as a workflow tool for nodule measurement.
AI Regulatory Concerns
Powered by
Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.
Keywords
Device Metadata
Relevant Clinical Questions
- Q1. Given its limitation to solid pulmonary nodules, what were the specific exclusion criteria for nodule types in the validation study, and are there plans to expand NinesMeasure's capabilities to subsolid or ground-glass opacities?; How does the NinesMeasure algorithm differentiate between true nodules and nodule mimics (e.g., scars, vessels), and what is the false positive rate for automatic segmentation if a radiologist broadly indicates a region of interest?; The performance data reports normalized error; could you provide absolute error measurements (e.g., in millimeters) for different nodule size categories, and what is the system's sensitivity for detecting clinically significant changes in nodule size over time compared to manual radiologist measurements?; What specific training is recommended or required for radiologists to effectively use NinesMeasure, particularly regarding the interpretation of AI-generated measurements and the capabilities for manual review or editing of segmentations?; How was the 'ground truth' for nodule measurements established in the multi-center validation study against which NinesMeasure's AI algorithm performance was compared?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class B (software safety classification); Authorized before §524B enforcement
Learn how Parasoft automates IEC 62304 compliance testing →Cybersecurity Evidence
Powered by SBOMator™Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.
Supply Chain BOM Evidence
Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.
Analysis:
• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.
• Evidence of ML-BOM, OBOM detected in AI-generated device summary.
• This device was authorized before §524B took effect. Cybersecurity evidence requirements were less prescriptive at the time.
• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.
• Not detected in AI-generated device summary: SBOM, SaaSBOM, HBOM, CBOM, VDR/VEX. These may be present in the full FDA submission.
Preparing a similar submission?
ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.
Assess Your Readiness →Or contact ESL directly