K131812 · Siemens Medi Cal Solutions, Inc. · DQK · Jul 25, 2013 · Cardiovascular
Device Facts
Record ID
K131812
Device Name
SENSIS, SENSIS LITE
Applicant
Siemens Medi Cal Solutions, Inc.
Product Code
DQK · Cardiovascular
Decision Date
Jul 25, 2013
Decision
SESE
Submission Type
Special
Regulation
21 CFR 870.1425
Device Class
Class 2
Attributes
Pediatric
Indications for Use
The Sensis recording system is intended to be used as a diagnostic and administrative tool supporting hemodynamic cardiac catheterizations and/or intracardiac electrophysiology studies. The system is equipped by modules, enabling various configurations ranging from a stand-alone acquisition unit with limited administrative functionality to multiunit installations with a common database and satellite workstations accessing the data using the administrative tools. The device is intended to be used on either or both of the following populations: 1. Adult and pediatric populations requiring intracardiac electrophysiology examinations, typically when the patient is suffering from cardiac arrhythmias. 2. Adult and pediatric populations requiring intracardiac hemodynamic examinations, typically when the patient has a heart disease resulting in insufficient hemodynamic functionality.
Device Story
Sensis is a multi-channel, computer-based stationary system for measuring, displaying, and recording bio-physiological events during cardiac catheterization and electrophysiology studies. Inputs include intracardiac pressure, ECG signals, and intracardiac electrograms (ICEG). The system processes these signals to monitor and assess hemodynamic and electrophysiological parameters; users perform calculations based on manual inputs and signal data. Used in clinical settings (e.g., cath labs) by healthcare professionals. The system supports multi-unit configurations with shared databases and satellite workstations for post-processing and reporting. It interfaces with angiography X-ray systems. Output provides clinicians with real-time monitoring and diagnostic data to support clinical decision-making during invasive cardiac procedures.
Clinical Evidence
No clinical data. Bench testing only. Verification and validation testing, including integration and functional testing, confirmed software specifications met acceptance criteria. Risk management and hazard analysis were performed. Electrical and mechanical safety verified per IEC standards.
Technological Characteristics
Multi-channel computer-based stationary system. Interfaces with angiography X-ray systems (e.g., Artis Q zen, Artis zee/zeego). Software version VC12. Connectivity via network for satellite workstations. No patient-contact parts; accessories sourced from OEMs with existing clearances. Electrical safety per IEC standards.
Indications for Use
Indicated for adult and pediatric patients requiring intracardiac electrophysiology examinations (e.g., cardiac arrhythmias) or intracardiac hemodynamic examinations (e.g., heart disease with insufficient hemodynamic functionality).
Regulatory Classification
Identification
A programmable diagnostic computer is a device that can be programmed to compute various physiologic or blood flow parameters based on the output from one or more electrodes, transducers, or measuring devices; this device includes any associated commercially supplied programs.
{0}------------------------------------------------
JUL 2 5 2013
## SIEMENS
### Special 510(k) Submission: Sensis
### 510(k) Summary: Sensis
Siemens Medical Systems, Inc. Company: 51 Valley Stream Parkway Malvern, PA 19355
June 25, 2013 Date Prepared:
This 510(k) summary of safety and effectiveness information is being submitted in accordance with the requirements of SMDA 1990 and 21 CFR § 807.92.
- 1. General Information:
Importer / Distributor: Siemens Medical Systems, Inc. 51 Valley Stream Parkway Malvern, PA 19355
Establishment Registration Number: 2240869
Manufacturing Site: SIEMENS AG Sector Healthcare Siemensstraße 1 D-91301 Forchheim, Germany
Establishment Registration Number: 3004977335
### 2. Contact Person:
Ms. Patricia D Jones Technical Specialist, Regulatory Submissions Siemens Medical Solutions USA, Inc. 51 Valley Stream Parkway D-02 Malvern, PA 19355 Fax: (610) 448-1787 Phone: (610) 448 -3536 Email: patricia.d.jones@siemens.com
### Device Name and Classification: 3.
Trade Name: Classification Name: Classification Panel: CFR Section:
Sensis Programmable diagnostic computer Cardiovascular Diagnostic Devices 21 CFR §870.1425
{1}------------------------------------------------
### Special 510(k) Submission: Sensis
| Device Class: | Class II |
|-----------------------------------|-----------------------------------|
| Product Code: | DQK |
| Legally Marketed Predicate Device | |
| Trade Name: | AXIOM Sensis |
| 510(k) #: | K020440 |
| Clearance Date: | December 3, 2002 |
| Classification Name: | Programmable diagnostic computer |
| Classification Panel: | Cardiovascular Diagnostic Devices |
| Classification Regulation: | 21 CFR §870.1425 |
| Device Class: | Class II |
| Product Code: | DQK |
- 4. Device Description:
The Sensis Electrophysiological and Hemodynamic Recording System with software VC12 is a further SW and HW development of the commercially available Siemens AXIOM Sensis K020440.
The Sensis is a multi-channel computer-based stationary system for the measurement, display, and printout of bio-physiological events. Hemodynamic and electrophysiological signals such as intracardiac pressure, ECG signals, and intracardiac electrograms (ICEG) are measured and displayed by the system. Sensis software provides the ability to monitor and assess invasive blood pressure, ECG signals, and optionally intracardiac electrograms (ICEG) The user can perform a number of calculations based on manual input and / or on the input signals and other hemodynamic parameter values from the Sensis system.
For more flexibility in the department, additional post processing and reporting workplaces can always be connected to the network.
The software and hardware modification does not affect the intended use of the device nor does it alter its fundamental scientific technology.
#### ട. Indication for Use:
The Sensis recording system is intended to be used as a diagnostic and administrative tool supporting hemodynamic cardiac catheterizations and/or intracardiac electrophysiology studies. The system is equipped by modules, enabling various configurations ranging from a stand-alone acquisition unit with limited administrative functionality to multiunit installations with a common database and satellite workstations accessing the data using the administrative tools.
The device is intended to be used on either or both of the following populations:
{2}------------------------------------------------
- 1. Adult and pediatric populations requiring intracardiac electrophysiology examinations, typically when the patient is suffering from cardiac arrhythmias.
- 2. Adult and pediatic populations requiring intracardiac hemodynamic examinations, typically when the patient has a heart disease resulting in insufficient hemodynamic functionality.
### Substantial Equivalence: 6.
The Sensis Electrophysiological and Hemodynamic Recording System with software VC12 is substantially equivalent to the commercially available Siemens AXIOM Sensis which was described in premarket notification K020440 which received 510(k) clearance on December 03, 2002.
- Summary of Technological Characteristics of the Subject Device as 7. Compared with the Predicate Device:
The Sensis Electrophysiological and Hemodynamic Recording System with software VC12 is a further SW and HW development of the commercially available Siemens AXIOM Sensis K020440.
The Sensis features the same Indications for use. Acquisition, Monitoring, Recording, Imaging and Administrative Functions as the predicate AXIOM Sensis. It interfaces with Angiograhy X-ray systems e.q. Artis Q zen, Artis zee / zeego. The user function is similar to the predicate AXIOM Sensis device.
#### Performance Testing: 8.
Siemens claims conformance to a signed statements of conformance to This submission contains performance data to performance standards. demonstrate continued conformance with special controls for medical devices containing software. Non clinical tests (integration and functional) were conducted on the Sensis software during product development. The Risk Analysis was completed and risk control implemented to mitigate identifed hazards. The testing results supports that all software specifications have met the acceptance criteria.
Testing for verification and validation of the device was found acceptable to support the claims of substantial equivalence.
EMC/electrical safety was evaluated according to the IEC Standards. Siemens certify to conformance Voluntary Standards covering Electrical and Mechanical Safety. In conclusion, the identified risk of electrical hazards was mitigated and is substantially equivalent to the predicate device in terms of safety and effectiveness. All testing and validation have been completed.
Clinical testing was not applicable as Sensis has no new indications for use nor new clinical applications were introduced to the system.
{3}------------------------------------------------
The Sensis uses the same sensors applied to the patients as the predicate device. These sensors are provided by OEM manufacturer and have their own 510(k) clearances.
All Sensis components do not come into direct contact with patients. For those accessories which come into direct contact with patient, it is ensured that legal manufacturing and supplier provides this biocompatibility and stellization (where applicable) before integration or use with Sensis itself does not have any parts which would require sterilization
### ರ್. General Safety and Effectiveness Concerns:
Instructions for use are included within the device labeling, and the information provided will enable the user to operate the device in a safe and effective manner.
Risk management is ensured via a hazard analysis, which is used to identify potential hazards. These potential hazards are controlled via software development, verification and validation testing. To minimize electrical, and mechanical hazards, Siemens adheres to recognized and established industry practice, and all equipment is subject to final performance testing. Furthermore the operators are health care professionals familiar with and responsible for the evaluating and post processing of X-ray images.
#### 10. Conclusion as to Substantial Equivalence:
The Sensis Electrophysiological and Hemodynamic Recording System with software VC12 is intended for the same indications as cleared in the predicate AXIOM Sensis. The predicate device hardware has 2 PC's. The subject device has only one PC and a nurse workstation with the same functionality as the Sensis PC. It allows a faster, more efficient workflow directly in the examination room.
The functionality of Sensis VC12 is similar to the predicate device. It is Siemens opinion, that the Sensis VC12 is substantially equivalent to the AXIOM Sensis (K020440).
{4}------------------------------------------------
Public Health Service
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-002
July 25, 2013
Siemens Medical Solutions, Inc. Patricia Jones 51 Valley Stream Parkway Malven, PA 19355 US
Re: K131812 Trade/Device Name: Sensis and Sensis Lite Regulation Number: 21 CFR 870.1425 Regulation Name: Programmable Diagnostic Computer Regulatory Class: Class II Product Code: DQK Dated: June 18, 2013 Received: June 24, 2013
Dear Patricia Jones:
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. 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 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
{5}------------------------------------------------
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please go to http://www.fda.gov/AboutFDA/CentersOffices/CDRH/CDRHOffices/ucm115809.htm for the Center for Devices and Radiological Health's (CDRH's) Office of Compliance. Also, please note the regulation entitled, Misbranding by reference to premarket notification (21CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to http://www.fda.gov/MedicalDevices/Safetv/ReportaProblem/default.htmfor the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Small Manufacturers, International and Consumer Assistance at its toll-free number (800) 638 2041 or (301) 796-7100 or at its Internet address http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely yours.
Feli Aguel Felipe Aguel
for
Bram D. Zuckerman, MD Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{6}------------------------------------------------
Special 510(k) Submission: Sensis
### Indications for Use Statement
510(k) Number (if known): K131812
Device Name: Sensis
Indications for Use:
The Sensis recording system is intended to be used as a diagnostic and administrative tool supporting hemodynamic cardiac catheterizations and/or intracardiac electrophysiology studies. The system is equipped by modules, enabling various configurations ranging from a stand-alone acquisition unit with limited administrative functionality to multiunit installations with a common database and satellite workstations accessing the administrative tools.
The device is intended to be used on either or both of the following populations:
- Adult and pediatric populations requiring intracardiac electrophysiology 1. examinations, typically when the patient is suffering from cardiac arrhythmias.
- Adult and pediatric populations requiring intracardiac hemodynamic 2. examinations, typically when the patient has a heart disease resulting in insufficient hemodynamic functionality.
Prescription Use _ × (Part 21 CFR 801 Subpart D) Over-The-Counter Use (21 CFR 807 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF NEEDED)
AND/OR
Feli Aguel for BDZ
2013.07.25 15:45:33
-04'00'
Concurrence of CDRH: Office of Device Evaluation (ODE)
Page 1 of 1
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.