Vista Solution Monitoring Kit, Vista Solution 2 10-day Evaluation Kit, VistaTablet 2 (Boxed)
Applicant
Vitalconnect, Inc.
Product Code
DRG · Cardiovascular
Decision Date
Apr 20, 2020
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2910
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
Vista Solution 2.1 is a software user intended for use by healthcare professionals to display physiological data collected by the VitalConnect Platform wireless remote monitoring system in home and healthcare settings. Vista Solution is a secondary, adjunct patient monitor and is not intended to replace existing standard-of-care patient monitoring practices.
Device Story
Vista Solution is a software-based remote monitoring system for displaying physiological data; inputs include data from VitalPatch biosensors and third-party devices (SpO2, blood pressure, weight). System components include VistaPoint (Android app on tablet) for local data collection/display and VistaCenter (web app) for multi-patient monitoring via VCI Cloud. Healthcare professionals (nurses/clinicians) use the interface to view live/historical data, receive notifications based on user-defined criteria, and calculate NEWS scores. The device supports patient-centric data management, body temperature monitoring, and posture/fall detection. It functions as an adjunct monitor in inpatient or outpatient settings; output informs clinical decision-making by providing remote visibility into patient status.
Clinical Evidence
No clinical data. Substantial equivalence demonstrated via benchtop performance testing, software verification (IEC 62304), and usability testing (IEC 62366).
Technological Characteristics
Standalone software user interface. Operates on Android tablets (VistaPoint) and web-based platforms (VistaCenter). Integrates with VitalPatch biosensors and third-party devices via wireless connectivity. Data management via VCI Cloud. Software validation per IEC 62304; usability per IEC 62366.
Indications for Use
Indicated for use by healthcare professionals to display physiological data collected by the VitalConnect Platform wireless remote monitoring system in home and healthcare settings. Intended as a secondary, adjunct patient monitor; not for replacement of standard-of-care monitoring.
Regulatory Classification
Identification
A radiofrequency physiological signal transmitter and receiver is a device used to condition a physiological signal so that it can be transmitted via radiofrequency from one location to another, e.g., a central monitoring station. The received signal is reconditioned by the device into its original format so that it can be displayed.
{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.
April 20, 2020
VitalConnect, Inc. Cynthia Merrell Vice President, QA & RA 224 Airport Parkway. Suite 300 San Jose, California 95110
Re: K193343/S001
Trade/Device Name: Vista Solution Regulation Number: 21 CFR 870.2910 Regulation Name: Radiofrequency Physiological Signal Transmitter And Receiver Regulatory Class: Class II Product Code: DRG Dated: December 3, 2019 Received: December 3, 2019
Dear Cynthia Merrell:
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 801); medical device reporting of medical device-related adverse events) (21 CFR 803) for
{1}------------------------------------------------
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 (OS) 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 mediation-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
Jennifer Shih Assistant Director DHT2A: Division of Cardiac Electrophysiology, Diagnostics and Monitoring Devices OHT2: Office of Cardiovascular Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K193343
Device Name Vista Solution
Indications for Use (Describe)
Vista Solution 2.1 is a software user intended for use by healthcare professionals to display physiological data collected by the VitalConnect Platform wireless remote monitoring system in home and healthcare settings. Vista Solution is a secondary, adjunct patient monitor and is not intended to replace existing standard-of-care patient monitoring practices.
Type of Use (Select one or both, as applicable)
| <span style="font-size:100%;">☑ Prescription Use (Part 21 CFR 801 Subpart D)</span> | <span style="font-size:100%;">☐ Over-The-Counter Use (21 CFR 801 Subpart C)</span> |
|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|
|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|
### 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}------------------------------------------------
### 510(k) SUMMARY
This summary of 510(k) substantial equivalence information is submitted in accordance with the requirements of 21 CFR §807.92:
1. SUBMITTER VitalConnect, Inc. Address 224 Airport Parkway, Suite 300 City San Jose, CA, 95110 USA Tel: 1-408-963-4600 Fax: 1-408-963-2828
| Contact Person: | Cynthia Merrell |
|-----------------|-----------------|
| Date Prepared: | March 19, 2020 |
| II. DEVICE | |
|------------------------------|------------------------------------------------------------------|
| Name of Device: | Vista Solution |
| Classification Name: | Transmitters and Receivers, Physiological Signal, Radiofrequency |
| Regulation: | 21 CFR § 870.2910 |
| Regulatory Class: | Class II |
| Product Classification Code: | DRG |
111. PREDICATE DEVICE Predicate Manufacturer: Predicate Trade Name: Predicate 510(k):
VitalConnect, Inc. VitalWatch Software User Interface K170973
No reference devices were used in this submission.
#### IV. DEVICE DESCRIPTION
The VitalConnect Platform, Vista Solution is a wireless remote monitoring system consisting of the VitalPatch biosensor (K190916) and the VistaCenter and VistaPoint software (formally branded as VitalWatch in K170973). This submission is a catch-up 510(k) for changes made to the software since K170973 was cleared. The principles of operation, mechanism of action, and proposed environment of use are unchanged from the predicate device (K170973).
Image /page/3/Figure/12 description: The image shows a diagram of a vital patch biosensor system. The system includes a vital patch biosensor, a VistaPoint app on a Vista tablet device, and a VistaCenter app. The vital patch biosensor is worn by a patient in an inpatient or outpatient environment. The VistaPoint app is used to collect data from the vital patch biosensor and display it on a tablet device. The VistaCenter app is used by nurses or other healthcare providers to monitor patients in a nurse station or virtual care center. The data is stored in the VitalCloud.
{4}------------------------------------------------
## VistaCenter Application
A web application that interfaces with the VCI Cloud and displays live and historical data for multiple patients and supports download of historical data for multiple patients. The application also supports the user entry of criteria for triggering notifications based on data values and for displaying notifications generated from such criteria.
### VistaPoint Application
The VistaTablet 2.0 App is a stand-alone Android Application which is delivered pre- installed on an off-the-shelf tablet and the combination called VistaTablet 2.0. It incorporates within a single distributable application the functionality of the Relay App, and VistaPoint. The VistaTablet runs a single application that is a combination of Relay App, Configuration App, VistaPoint, and a product wrapper to make it run like a native application.
The user interface on VistaTablet is substantially equivalent to the previously commercialized VistaTablet 1.0 product with the following major additions:
- Support for third-party devices for collecting additional vital signs SpO2, Blood ● Pressure, and Weight
- . Data management by patient instead of patch (i.e. multiple patches and devices supply data for one patient)
- . Support for VitalPatch 3.0 features including body temperature, 30 degree calibration, and LED blinking.
The following changes were made previously as letters to file: 1.
### RGD-007
- a. Add support for four 3rd party devices
- b. Support body temperature, 30-degree supine posture calibration, and on-command LED blinking
- Each vital sensor will be assigned a patient ID based upon the actual patient C.
- Add support for SPO2 and weight scale and NIBP (related to "a" above) d.
- Display graphical ECG streaming data e.
- Add combination heart rate / respiratory rate as a new notification; add no data f. uploading and low battery as error conditions
- 2. RGD-008
- VitalTablet changes Add support for four (4) third party pulse oximeter (Sp02), nona. invasive blood pressure (NIBP) and weight scale devices.
- b. VitalCenter changes Add support for Sp02, NIBP and weight scale device data displays. Add NEWS calculated with patient vitals, and observer input for consciousness and supplemental oxygen.
RGD-006 - Add new relay hardware (Samsung Galaxy Tab E 8.0 Android OS)
New functionality incorporated which are extensions of previously existing functionality include manual entry of data, notifications on 3rd party devices and body temperature, and universal notifications.
{5}------------------------------------------------
#### V. INDICATIONS FOR USE
Vista Solution 2.1 is a software user interface intended for use by healthcare professionals to display physiological data collected by the VitalConnect Platform wireless remote monitoring system in home and healthcare settings. Vista Solution is a secondary, adjunct patient monitor and is not intended to replace existing standard-of-care patient monitoring practices.
### COMPARISON OF TECHNOLOGICAL CHARACTERISTICS WITH THE VI. PREDICATE DEVCE
The following characteristics were compared between the subject device and the predicate device in order to demonstrate substantial equivalence:
| Feature | Subject Device | Predicate Device (K170973) |
|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Indications for Use | Vista Solution 2.1 is a software<br>user interface intended for use by<br>healthcare professionals to display<br>physiological data collected by the<br>VitalConnect Platform wireless<br>remote monitoring system in home<br>and healthcare settings. Vista<br>Solution is a secondary, adjunct<br>patient monitor and is not intended<br>to replace existing standard-of-care<br>patient monitoring practices. | VitalWatch is a software user<br>interface intended for use by<br>healthcare professionals to display<br>physiological data collected by the<br>VitalConnect Platform wireless<br>remote monitoring system in home<br>and healthcare settings.<br>VitalWatch is a secondary, adjunct<br>patient monitor and is not intended<br>to replace existing standard-of-care<br>patient monitoring practices. |
| Classification | Class II | Class II |
| Classification<br>Name | Transmitters and Receivers,<br>Physiological Signal,<br>Radiofrequency | Transmitters and Receivers,<br>Physiological Signal,<br>Radiofrequency |
| Product Code | DRG | DRG |
| Trade Name | Vista Solution | VitalConnect Platform®,<br>HealthPatch® MD,<br>VitalPatch®,<br>VitalWatch TM |
| Physiological<br>Data Monitored | Heart rate, electrocardiography<br>(ECG), heart rate variability, R-R<br>interval, respiratory rate, body<br>temperature, activity (including<br>step count), and posture (body<br>position relative to gravity<br>including fall)<br>Pulse oximeter, Weight and Blood<br>Pressure via 3rd Party Devices.<br>NEWS score calculated with above<br>patient vitals, and observer input for<br>consciousness and supplemental<br>oxygen. | Heart rate,<br>electrocardiography<br>(ECG), heart rate variability, R-R<br>interval, respiratory rate, skin<br>temperature, activity (including step<br>count), and posture (body position<br>relative to gravity including fall) |
| Principles of<br>Operation | Display of data from validated<br>Relay device using Graphical<br>User Interface (VistaPoint) and<br>transmission of data to Secure<br>Server (VCI Cloud). | Display of data from<br>validated Relay device<br>using third-party<br>developed Graphical<br>User Interface, or<br>VitalWatch, and<br>optional transmission<br>of data to Secure<br>Server. |
{6}------------------------------------------------
### Electrical safety and electromagnetic compatibility (EMC)
Not Applicable (Standalone Software)
### Software Verification and Validation Testing
Software validation was performed in accordance with IEC 62304.
### Benchtop Testing
Usability testing was performed in accordance with IEC 62366.
### Animal Study
Animal performance testing was not required to demonstrate substantial equivalence to the predicate device.
### Clinical Studies
Clinical testing was not required to demonstrate the substantial equivalence of The Proposed Vista Solution Software User Interface. Instead, substantial equivalence is based upon benchtop performance testing.
### VII. CONCLUSIONS
The Proposed Vista Solution Software User Interface is substantially equivalent to the predicate device. The modifications described in this 510(k) do not raise different questions of safety and effectiveness.
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.