K191285 · Brainlab AG · OLO · Jun 11, 2019 · Neurology
Device Facts
Record ID
K191285
Device Name
Spine & Trauma Navigation
Applicant
Brainlab AG
Product Code
OLO · Neurology
Decision Date
Jun 11, 2019
Decision
SESE
Submission Type
Special
Regulation
21 CFR 882.4560
Device Class
Class 2
Indications for Use
Spine & Trauma Navigation System is intended as an intraoperative image-guided localization system to enable minimally invasive surgery. It links a freehand probe, tracked by a passive marker sensor system to virtual computer image space on a patient's preoperative or Intraoperative 2D or 3D image data. Spine & Trauma Navigation System enables computer-assisted navigation of medical image data, which can either be acquired preoperatively or intraoperatively by an appropriate image acquisition system. The software offers screw implant size planning and navigation on rigid bone structures with precalibrated and additional individually-calibrated surgical tools. The system is indicated for any medical condition in which the use of stereotactic surgery may be appropriate and where a reference to a rigid anatomical structure, such as the skull, the pelvis, a long bone or vertebra can be identified relative to the acquired image (CT, MR, 2D fluoroscopic image or 3D fluoroscopic image reconstruction) and/or an image data based model of the anatomy.
Device Story
Image-guided surgery system for spine and trauma procedures; utilizes infrared passive marker-based optical tracking to link physical surgical instruments to virtual 3D/2D patient image data (CT, MR, XT). System components include navigation station, optical camera, and surgical instruments. Surgeon uses system in operating room to visualize tracked instruments relative to patient anatomy; enables screw implant planning and trajectory navigation. Registration of patient to image space performed manually or automatically. Output displayed on navigation screen to assist surgeon in minimally invasive procedures; improves accuracy of instrument placement on rigid bony structures. Software modification addressed display orientation issue for anatomical slices during workflow switching.
Clinical Evidence
Bench testing only. Verification included interactive tests of changed and unchanged software parts, code review, software memory leakage tests (VLD), and static code analysis (Lint). Testing confirmed the fix for the display issue and verified no negative impact on system performance via regression testing.
Technological Characteristics
Optical tracking system using infrared passive markers; navigation station with display; precalibrated and individually-calibrated surgical instruments. Software-based navigation; supports CT, MR, and 3D fluoroscopic data. Connectivity via navigation station. Sterilization of instruments per standard surgical protocols. Software modification involved 14 lines of code change in two source files.
Indications for Use
Indicated for patients requiring stereotactic surgery on rigid anatomical structures (skull, pelvis, long bone, vertebra) where image-guided localization is appropriate using CT, MR, or 2D/3D fluoroscopic data.
Regulatory Classification
Identification
A stereotaxic instrument is a device consisting of a rigid frame with a calibrated guide mechanism for precisely positioning probes or other devices within a patient's brain, spinal cord, or other part of the nervous system.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
June 11, 2019
Brainlab AG Julia Mehltretter Manager Product Surveillance Olof-Palme-Str. 9 Munich, 81829 De
Re: K191285
Trade/Device Name: Spine & Trauma Navigation System Regulation Number: 21 CFR 882.4560 Regulation Name: Stereotaxic Instrument Regulatory Class: Class II Product Code: OLO Dated: May 10, 2019 Received: May 13, 2019
## Dear Julia Mehltretter:
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. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. 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. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. 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 Part
{1}------------------------------------------------
801); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
For; Shumaya Ali, MPH Assistant Director DHT6C: Division of Stereotaxic. Trauma and Restorative Devices OHT6: Office of Orthopedic Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K191285
#### Device Name Spine & Trauma Navigation System
#### Indications for Use (Describe)
Spine & Trauma Navigation System is intended as an intraoperative image-guided localization system to enable minimally invasive surgery. It links a freehand probe, tracked by a passive marker sensor system to virtual computer image space on a patient's preoperative or Intraoperative 2D or 3D image data.
Spine & Trauma Navigation System enables computer-assisted navigation of medical image data, which can either be acquired preoperatively or intraoperatively by an appropriate image acquisition system.
The software offers screw implant size planning and navigation on rigid bone structures with precalibrated and additional individually-calibrated surgical tools.
The system is indicated for any medical condition in which the use of stereotactic surgery may be appropriate and where a reference to a rigid anatomical structure, such as the skull, the pelvis, a long bone or vertebra can be identified relative to the acquired image (CT, MR, 2D fluoroscopic image or 3D fluoroscopic image reconstruction) and/or an image data based model of the anatomy.
X Prescription Use (Part 21 CFR 801 Subpart D)
| Over-The-Counter Use (21 CFR 801 Subpart C)
## CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
## K191285
# SPECIAL 510(K) CORRECTIVE ACTION BEING EFFECTED SUMMARY
## SPINE & TRAUMA NAVIGATION SYSTEM
IN ACCORDANCE WITH REQUIREMENTS OF 21 CFR PART 807.92
| Manufacturer: | Brainlab AG<br>Olof-Palme-Str. 9<br>81829 Munich<br>Germany |
|--------------------------------------|----------------------------------------------------------------|
| | Phone: +49 89 99 15 68 0<br>Fax: +49 89 99 15 68 5033 |
| Submitter: | Rainer Birkenbach |
| Contact person: | Julia Mehltretter |
| Summary date: | 6/11/2019 |
| Device: | Spine & Trauma Navigation System |
| Trade name: | Spine & Trauma 3D |
| Common Name: | Brainlab Image Guided Surgery System / Instrument, Stereotaxic |
| Device Classification<br>Regulation: | 21 CFR 882.4560 |
| Classification Name: | Orthopedic Stereotaxic Instrument |
| Regulatory Class: | Class II |
| Product Code: | OLO |
| Predicate Device: | VectorVision Fluoro 3D (K070106) |
#### INTENDED USE: 1
Spine & Trauma Navigation System is intended as an intraoperative image-guided localization system to enable minimally invasive surgery. It links a freehand probe, tracked by a passive marker sensor system to virtual computer image space on a patient's preoperative 2D or 3D image data.
Spine & Trauma Navigation System enables computer-assisted navigation of medical image data, which can either be acquired preoperatively or intraoperatively by an appropriate image acquisition system.
The software offers screw implant size planning and navigation on rigid bone structures with precalibrated and additional individually-calibrated surgical tools.
The system is indicated for any medical condition in which the use of stereotactic surgery may be appropriate and where a reference to a rigid anatomical structure, such as the skull, the pelvis, a long bone or vertebra can be identified relative to the acquired image (CT, MR, 2D fluoroscopic image or 3D fluoroscopic image reconstruction) and/or an image data based model of the anatomy.
{4}------------------------------------------------
#### DEVICE DESCRIPTION: 2
This device is an image guided surgery system for navigated treatments in the fields of spine and trauma surgery, whereas the user may use 3D image data based on CT, MR or XT. The Software supports the surgeon in clinical procedures by displaying tracked instruments in patient image data.
### Operator profile
The operator's profile for this devices are Neuro / Ortho / Spine / Trauma surgeons or their assistants having a 3D image acquisition system (such as CT or 3D C-arm) in combination with a Brainlab navigation system.
#### Patient population
The patient population includes any medical condition in which the use of stereotactic surgery may be appropriate and where a reference to a rigid anatomical structure, such as the skull, the pelvis, a long bone or vertebra can be identified relative to the acquired image (CT, MR, 2D fluoroscopic image or 3D fluoroscopic image reconstruction).
#### Intended use environment
The application shall be used in an operating room / suite.
#### Operating principle
Infrared passive marker based tracking as provided by the optical tracking camera unit of the navigation station is used to determine the instrument's and patient's position between the patient and the reference attached to the patient is realized with a registration (manually or automatic).
#### Primary operating functions
| Primary Operating Function | Frequently<br>used<br>function | Safety<br>related<br>function |
|--------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------|
| Set up system, start software | ✓ | |
| Loading of already (automatically or manually) registered pre-/ intra-<br>operatively acquired CT or Fluoro3D data | ✓ | ✓ |
| Registration of intra-operatively acquired Fluoro 3D data | ✓ | ✓ |
| Navigate on fused pre- / or intra-operatively acquired 3D spinal data<br>(CT/ XT fused to MR/ XT/ CT/ PET) | | ✓ |
| Navigating CT/ XT and fused MR/XT/ CT/PET data with pre-<br>planned content (objects, screws, etc.) | | ✓ |
| General navigation in 3D datasets | ✓ | |
| Navigation of manually calibrated instruments | ✓ | ✓ |
| Navigation of pre-calibrated instruments | ✓ | ✓ |
| Verification of registration accuracy | ✓ | ✓ |
| Verification of instrument accuracy | ✓ | ✓ |
| Store data, shut down system, store system | ✓ | ✓ |
{5}------------------------------------------------
#### Use scenarios
The system is placed in a way that the surgeon can easily watch the screen(s) and interact with the system during the procedure, but sterility is not compromised. The camera is positioned in a way that it has an unobstructed view on the surgical field.
The patient is positioned and draped in the usual manner, taking into account that the reference geomety has to be attached to the relevant anatomical structure in a way that it is not disturbing the latter workflow. The surgical approach is performed. A reference arrav is attached to the relevant bony structure using conventional surgical techniques (either under sight or minimally invasive). The 3D dataset is either acquired or loaded and subsequently registered.
After the scan has been transmitted to the navigation system or the registration computation has been performed, the surgeon is asked to verify the success of the registration with a general instrument or a dedicated pointer.
After successful verification the surgeon is able to access pre-planned objects, to plan or re-plan screws / trajectories and to visualize manually or pre-calibrated surgical instruments.
#### Intended part of the body or type of tissue applied to or interacted with
This system has different components, whereas most of them are software. Therefore, only instruments may get in contact with a patient, some instruments are included to perform the surgery. All Instruments are used temporarily for orientation within the situs or for preparations to be able to implant 3rd party devices, which are not part of this system.
Such instruments can be used at rigid bony structures, such as a long bone or vertebra, where the user wants to use this navigation software according to the indications for use.
#### SUBSTANTIAL EQUIVALENCE ന
The Spine & Trauma Navigation System has similar functionality, intended use, technological characteristics, and typical users as the predicate device.
The proposed software modification was performed to correct a display issue within the Spine & Trauma Navigation System software that can occur when a user changes navigation workflows. The issue was caused by an erroneous orientation of the anatomical slices that were displayed together with a projected instrument representation within axial and coronal/sagittal views of the image data, while the instrument tip was permanently correctly displayed.
The proposed software modification required a local software consisting of 14 lines of code and is restricted to two source files.
Since the programming structure for the current display logic was already intended in the detailed design, the software correction did not require any change to the existing software architecture or to the unit tests.
There was no change of intended use, technological characteristics or typical users.
{6}------------------------------------------------
#### VERIFICATION/VALIDATION SUMMARY ব
### Performance Testing
The following verification methods were successfully applied:
- Interactive tests according to verification documents related to changed software parts (software . code change verification)
- . Interactive tests according to verification documents related to unchanged software parts (regression tests)
- Code review of the software change
- Software memory leakage tests using VLD (Visual Leak Detector)
- . Static code analysis (Lint) for changed software parts
Worst case scenarios were considered. New verification activities were performed after extension of existing test cases. They cover switching between different applications within one navigation session and now additionally comprise the missing test scenario for the display issue which caused the software modification request. In order to prevent software changes to have impact on non-changed design parts, regression tests were included to the test protocols.
Design verification testing that was performed to support modifications to the Spine & Trauma Navigation System software met all design and performance requirements.
#### CONCLUSION 5
The modified device is substantially equivalent to the currently marketed Spine & Trauma Navigation System based upon design verification test results and the indications for use.
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.