The LifeBed Network Patient Vigilance System is intended to measure heart rate, respiratory rate, and bed exit in adult patients for use by health care professionals.
Device Story
System extends LifeBed Patient Vigilance System (K082366) by adding centralized network controller and wireless adapter; collects/stores/reports historical patient data (heart rate, respiratory rate, bed exit status) from bedside sensor arrays. Operates via TCP/IP over Ethernet/wireless; controller located in non-patient vicinity (e.g., IT department). Users access historical data/reports via controller interface or email/SMS gateway; system does not provide real-time monitoring, does not alarm, and does not replace nurse call systems. Security system restricts access based on user roles. Benefits include centralized data management and historical reporting for clinical information systems.
Clinical Evidence
No clinical data; bench testing only. Device utilizes same algorithm and patient interface as predicate K082366; submission limited to addition of networking/wireless capabilities.
Technological Characteristics
System components: bedside display, wireless adapter, network controller. Connectivity: TCP/IP over Ethernet/wireless. Controller located in non-patient vicinity. Software: proprietary protocol 'Beacon'. No changes to patient-contacting 'Coverlet' material.
Indications for Use
Indicated for adult patients to measure heart rate, respiratory rate, and bed exit status in a hospital environment by healthcare professionals.
Regulatory Classification
Identification
A cardiac monitor (including cardiotachometer and rate alarm) is a device used to measure the heart rate from an analog signal produced by an electrocardiograph, vectorcardiograph, or blood pressure monitor. This device may sound an alarm when the heart rate falls outside preset upper and lower limits.
Diagnostic Ultrasound BVM6500 with ScanPoint (K030763)
Submission Summary (Full Text)
{0}------------------------------------------------
3 2009
## SECTION 5 - 510(k) Summary
| Submitted By: | Hoana Medical, Inc<br>828 Fort Street Mall, Suite 620<br>Honolulu, HI 96813<br>Phone: (808) 523-1225<br>Fax: (808) 523-5480 | APR |
|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|
| Contact: | Nancy Gertlar<br>Director of Regulatory Affairs and Quality<br>Assurance | |
| Date Summary Prepared: | November 10, 2008 | |
| Trade Name: | Lifebed Network Patient Vigilance System | |
| Common/Classification Name: | Monitor, Cardiac<br>74DRT, 870.2300 | |
| Substantially Equivalent Devices: | LG1 Patient Vigilance System<br>(K052446);<br>LifeBed Patient Vigilance System<br>(K082366)<br>Verathon Corp.<br>BVI 9400 with ScanPoint<br>(K071217)<br>Diagnostic Ultrasound<br>BVM6500 with ScanPoint<br>(K030763) | |
#### Description of the LifeBed Network Patient Vigilance System:
The LifeBed Network Patient Vigilance System is identical to the LifeBed Patient Vigilance System described in the LifeBed Patient Vigilance System, K082366 with three exceptions.
A Controller as been added which will not be in the patient vicinity, A wireless adapter has been added, and the Indications for Use have been reworded.
The LifeBed Network integrates with the LifeBed Display to collect, store and report patient medical and status information.
The Display can be configured from the Network or from the Display. The Network and Display are connected using TCP/IP protocols. To ease logistical considerations at the
Hoana Medical, Inc.
<sup>510(</sup>k) Premarket Reports
{1}------------------------------------------------
installation site, these two components are usually bridged across a wireless network using a LifeBed Wireless Adapter.
The Network also provides an interface which may be used to integrate with a clinical information system (CIS). When used in this way, an adapter box isolates and translates protocols between the Network and the CIS.
The Network centralizes information access and configuration for a group of Displays. It DOES NOT change the manner in which alerts are sent through the Nurse Call system of the hospital.
Each Display is a bedside unit that collects and processes data from a sensor array on the patients' bed. It reports patient heart rate, respiration rate, alarm and if the patient is in bed or out of bed to the Controller. This information is NOT displayed real time and is NOT to be used as a method to monitor the patient.
The hub of the Network is the LifeBed Controller which serves one unit (e.g., a hospital ward). From the Controller the user has full access to the information gathered from the unit and configuration of all of the Displays in the unit. The Controller also provides the interface used to integrate into a CIS or with a future product.
All user access to the Network is constrained by a security system. There are two factors involved: the individual user's role and the specific access permissions assigned to the user. The user's role constrains the type of data the user has access to (e.g. medical, device status, etc.). By default, all users have specific access to information sourced by their organization. Permission to access data sourced by another organization is denied unless specifically allowed.
The Network operates in a medical setting and must comply with relevant regulatory agency and legal requirements. As a medical product the Network must protect patient privacy. It must comply with all the requirements of the HIPAA Act.
#### Indication for Use
LifeBed Network Patient Vigilance System is intended to measure heart rate, respiratory rate, and bed exit in adult patients for use by health care professionals.
LifeBed Patient Vigilance System is intended to measure heart rate and respiratory rate in adult patients, in bed, in a general care hospital environment. The system will also monitor bed exit. K082366
Hoana Medical, Inc. 510(k) Premarket Reports
{2}------------------------------------------------
## Principles of Operation
The LifeBed Network is an extension of the LifeBed Display that collects, stores and reports patient medical and device status information. It is not intended to replace nurse call or other reports systems. It does not alarm. The LifeBed Network does not provide real time data for the purposes of diagnosing or treatment.
The LifeBed Network extends the LifeBed Display to collect, store and report patient medical and status information. The Network and Display are connected using TCP/IP protocols. To ease logistical considerations at the installation site, these two components (The Network and the Display) are usually bridged across a wireless network using a LifeBed Wireless Adapter.
The Network centralizes information access for a group of Displays. Each Display is a bedside unit that collects and processes data from a sensor array on the patient's bed. It reports patient heart rate, respiratory rate, alarm, and status information to the Controller.
The hub of the Network is the LifeBed Controller which serves one unit (e.g. a hospital ward. From the Controller the user has full access to the information gathered from the unit and configuration of all the Displays in its unit. The Network also allows for reports to be configured and sent by email, using an email to SMS gateway to mobile phones. These reports are NOT alarms and are not real time. Just as when reading from the Controller, the data in the reports is historical in perspective, only.
Users access information via the user interface, which runs on the Controller. All user access to the Network is constrained by a security system. Each user is assigned a role which constrains what type of data the user can access.
The Network operates in a medical setting and complies with the relevant regulatory agency and legal requirements. Wireless components are used to connect Displays to the Controller. The Controller will not be in the patient vicinity. As a medical product the Network must protect patient privacy. It must comply with all the requirements of the HIPAA Act.
All components of the Network interface via TCP/IP over Ethernet. There may be intermediate hardware to transport TCP/IP. Commonly, this will be a wireless network and the LifeBed Wireless Adapter will accommodate the configuration.
There are two software interfaces in the Network, the connection to the Display. The user interface and the proprietary protocol. Beacon.
Hoana Medical, Inc. 510(k) Premarket Reports
{3}------------------------------------------------
## Electrical, Mechanical and EMC Testing for the LifeBed Network Patient Vigilance System, patient vicinity components:
Test reports are found in section 17.
## Electrical, Mechanical and EMC Testing for the LifeBed Network Patient Vigilance System, non-patient vicinity components:
- o The LifeBed Network Controller is located in the IT department equipment areas within the hospital and classified as non-patient vicinity or contacting equipment. This equipment falls within the Information Technology Equipment category and is tested to the appropriate standards for safety and EMI compliance.
- The Wireless Adapter is attached to the LifeBed Display in the patient room and, 0 therefore, is test to the appropriate standards for patient monitoring equipment.
Test reports are found in section 17.
#### Biocompatibility Testing
No changes were made to the Coverlet, which is the patient contacting surface. No biocompatibility tests were conducted as part of this submission.
### Clinical Testing
No changes were made to the LifeBed Patient Vigilance System which contains the algorithm and controls the patient interface (K082366). The LifeBed Network Patient Vigilance System only adds the networking capabilities. Therefore, no clinical trial tests were required to support this submission.
#### Conclusion
All verification and validation testing conducted demonstrate that the LifeBed Network Patient Vigilance System is substantially equivalent to the LifeBed Patient Vigilance System, K082366.
It has been further demonstrated that the wireless addition to the LifeBed Patient Vigilance System is substantially equivalent to the wireless Verathon BVI 9400, Diagnostic Ultrasound BVM 6500, and ScanPoint which transmits data, wirelessly, to an office or facility for later viewing, diagnosing, calibrating or archiving, K071217.
{4}------------------------------------------------
Image /page/4/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo features a stylized eagle with three stripes forming its wing. The text "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" is arranged in a circular fashion around the eagle.
Food and Drug Administration 9200 Corporate Boulevard Rockville MD 20850
APR 1 3 2009
Hoana Medical, Inc. c//o Ms. Nancy Gertlar Director, Regulatory Affairs and Quality Assurance 828 Fort Street Mall, Suite 620 Honolulu, HI 96813
Re: K083534
Trade/Device Name: LifeBed Network Patient Vigilance System Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor Regulatory Class: Class II (two) Product Code: DRT Dated: April 1, 2009 Received: April 3, 2009
Dear Ms. Gertlar:
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. Insting of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration.
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}------------------------------------------------
Page 2 - Ms. Nancy Gertlar
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Center for Devices and Radiological Health's (CDRH's) Office of Compliance at (240) 276-0120. 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 contact the CDRH/Office of Surveillance and Biometrics/Division of Postmarket Surveillance at 240-276-3464. For more information regarding the reporting of adverse events, please go to http://www.fda.gov/cdrh/mdr/.
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 (240) 276-3150 or at its Internet address http://www.fda.gov/cdrh/industry/support/index.html.
Sincerely yours,
Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{6}------------------------------------------------
# Indications for Use
510(k) Number (if known): K083534
## Device Name: LIFEBED NETWORK PATIENT VIGILANCE SYSTEM
Indications for Use:
The LifeBed Network Patient Vigilance System is intended to measure heart rate, respiratory rate, and bed exit in adult patients for use by health care professionals.
Prescription Use × (Part 21 CFR 801 Subpart D)
AND/OR
Over-The-Counter Use (21 CFR 801 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE OF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
(Division Sign-Off) 4/8/09
Division of Cardiovascular Devices
510(k) Number K0803534
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.