Umbilical clamp and wireless tag systems, methods, and apparatus

Abstract

Systems, methods, and devices are disclosed relating to electronic medical record (EMR) systems and security platforms adapted for neonatal security and security assurance. An example apparatus includes a wireless-enabled umbilical clamp device having a wireless-enabled tag and a tamper-proof switch. The example system further includes a server, a wireless transceiver, a console device, and a wireless-enabled umbilical clamp device. The wireless transceiver may act as a tag reader distributed within the environment of other tag readers of a hospital. The console interacts with the wireless tag and the server. The wireless tag is used to generate location data and status data for determining, by the server and / or console, the location and status of the clamp device within the hospital environment. Servers and / or consoles may receive and interpret such tag data and compute their appropriate responses, such as locking doors around the hospital.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application does not claim priority from any patent or pending patent application. Background Art Field of the Invention

[0003] The present invention relates to systems, methods and apparatus including an umbilical cord clamp, a networked platform for tracking the umbilical cord clamp within a hospital, and in a specific embodiment, to an umbilical cord clamp tag and system (for the safety and protection of newborns), which includes at least one umbilical cord clamp and / or clamp tag adapted for wireless tracking, at least one console unit adapted for wireless tracking of the umbilical cord clamp, a server in communication with the console unit (which communicates clamp status content to the console unit), and at least one transceiver adapted for wireless communication with the umbilical cord clamp and / or clamp tag, the console and / or server, wherein the clamp status content is determined in part based on the location, position, operation and integrity of the clamp, and the position of the clamp relative to the console unit, the wireless transceiver or the server. Specifically, the clamp integrity status reflects whether the clamp is intact and engaged, versus damaged and / or disengaged, thereby indicating the possibility of unauthorized personnel tampering with the clamp and / or clamp tag.

[0004] Related technical description

[0005] The prior art includes, for example, tools, products, and systems including a simple umbilical cord clamp for clamping the umbilical cord of a newborn to prevent bleeding at the umbilical cord; including umbilical cord tags, wrist tags, and ankle tags for identifying the newborn and / or indicating information about the newborn (such as the newborn's date of birth or blood type); and including tracking tags adapted to be attached to the umbilical cord clamp, wrist, or ankle to track the newborn, such as using a bar code printed on the tag or a radio frequency identification (RFID) transmitter in the tag. Because tracking tags and umbilical cord clamps have historically served different, unrelated functions, conventional prior art has separated tracking tags and umbilical cord clamps into different, unrelated devices, systems, and data collection sources. Conventional tracking tags have limited tamper indication capabilities, and such tamper indication capabilities include the ability to detect whether a wristband or ankleband has been cut, and the ability to detect whether a wristband, ankleband, or umbilical cord tag has ceased to be in contact with the wearer's skin.

[0006] In a conventional hospital setting according to the prior art, just after a newborn is born, the medical staff clamps the umbilical cord of the newborn to stop blood from flowing in the umbilical cord, then cuts the umbilical cord of the newborn and clamps it between the incision and the newborn with a clamp to stop bleeding of the umbilical cord of the newborn. Shortly after the birth of the newborn, the medical staff prepares a tag to identify the newborn and attaches the tag to the umbilical cord clamp, wristband or ankleband of the newborn to prevent the tag from being removed without cutting. In modern hospitals, the tag may include a radio frequency identification (RFID) transmitter or a barcode, which allows the medical staff to track, record and record interactions with the newborn as a hospital patient, such as for monitoring, moving, feeding, treating, fixing and nursing the newborn. Specifically, many hospitals have and use complex security procedures (such as multiple checks on the identity of visitors and employees) and security systems (such as double-locked doors and entrances ("mantraps")) to protect obstetric wards and neonatal wards to prevent babies from being threatened or abducted.

[0007] Contrary to the prior art, the present invention is unique in its design, its functionality, and its intended use. The present invention is different from the prior art concepts that approach umbilical cord clamp technology and neonatal tracking technology from other angles. The prior art lacks a dedicated platform that provides services and management for clamp integrity, tamper monitoring, and location tracking in wireless networks in a wireless networking environment. In contrast, the present solution attempts to create seamless wireless tracking of clamp tamper-resistant integrity and location in neonates wearing wireless-enabled clamps in hospitals.

[0008] As described below, embodiments of the present invention include the use of novel features within a wireless-enabled platform that includes a tracking system involving multiple system components including at least one wireless transceiver, at least one server, at least one console unit, and at least one wireless-enabled umbilical cord clamp and / or clamp tag, the system and system components running software adapted to track, record, notify and / or alert a user and log status content data about a newborn using systems and methods that are different from those of the prior art systems and methods. Summary of the invention

[0009] The present invention relates to systems, methods and devices including components that can be combined in a variety of ways and may include one or more of a wireless-enabled umbilical cord clamp tag, a wireless transceiver, a wireless-enabled console unit and / or a server adapted to operate within a wireless networking environment (such as a hospital) for treatment, identification and tracking of newborns.

[0010] According to the hospital environment of the present invention, just after the birth of a newborn, the medical staff clamps the umbilical cord of the newborn with an umbilical cord clamp to stop the blood from flowing in the umbilical cord, and then cuts the umbilical cord of the newborn and clamps the clamp between the incision and the newborn to stop the bleeding of the umbilical cord of the newborn. The wireless-enabled umbilical cord clamp tag includes a processor, a sensor, a power supply, and a wireless communication circuit to enable wireless programming and communication to the clamp and / or the clamp tag, as well as wireless programming and communication from the clamp and / or the clamp tag, so that shortly after the birth of the newborn, the medical staff can program the clamp and / or the clamp tag to identify the newborn and monitor the newborn in the hospital. The clamp tag is fixed to the umbilical cord of the newborn with the umbilical cord clamp in a manner that prevents the removal of the umbilical cord clamp and / or the clamp tag without triggering a warning or alarm in the monitoring system.

[0011] Some embodiments of the present invention may use a wireless-enabled tag according to aspects of the present invention, wherein the wireless-enabled tag is integrated with a new umbilical cord clamp as a single component, or the wireless-enabled tag is integrated into a new umbilical cord clamp as a single component, wherein the new umbilical cord clamp can clamp the umbilical cord in a manner similar to a conventional umbilical cord clamp. Some other embodiments of the present invention may use a wireless-enabled clamp tag according to aspects of the present invention, wherein the wireless-enabled tag is adapted for use with a conventional umbilical cord clamp (such as placed in a conventional annular hinged portion of the clamp), and the conventional umbilical cord clamp activates a switch or button in the tag when the clamp is closed and the hinged portion presses and depresses the switch or button. In some embodiments, the switch or button is raised relative to a cylindrical post inserted into the annular hinged portion. In other embodiments, the switch or button may be recessed in a cavity of the cylindrical post or other portion of the tag. In other embodiments, the switch or button may include a pressure sensitive membrane switch strip adapted to be inserted along and between the upper and lower rows of teeth of the clamp, wherein closing of the clamp involves the upper row of teeth engaging the switch strip and the cord to press them against the lower row of teeth of the clamp. In other embodiments, other sensing technologies may be employed to implement the same end devices as the buttons and switches described.

[0012] According to a first aspect of the present invention, a wireless-enabled umbilical cord clamp device is disclosed, which is suitable for monitoring the position of the wireless-enabled umbilical cord clamp device and detecting tampering with the wireless-enabled umbilical cord clamp device, wherein the clamp device includes: a tag device electronic circuit and hardware, the tag device electronic circuit and hardware including: a tag device processor; a tag device memory, the tag device memory is coupled to the tag device processor; a tag device wireless data transmission module, the tag device data transmission module is coupled to the tag device processor; a tag device wireless data transmission device, the tag device data transmission device is coupled to the tag device processor; and a tag anti-tamper switch, the tag anti-tamper switch is coupled to the tag device processor; tag device electronic software, the device software is stored in the device electronic circuit and hardware and is adapted to enable, drive and control the device electronic circuit and hardware; a tag device power supply, the device power supply is coupled to the device electronic circuit and hardware and is adapted a tag device housing comprising a tag device exterior and a tag device interior, the tag device interior housing the tag device software, the tag device power supply, and at least some of the tag device electronic circuitry and hardware; the tag device exterior comprising a clamp device frame adapted to be secured adjacent to the umbilical cord when the umbilical cord of a newborn is clamped by an umbilical cord clamp; wherein the device electronic circuitry and hardware are adapted to operate as a wireless tag adapted to be wirelessly read by a wireless tag reader comprising a wireless transceiver; wherein the wireless tag reader is adapted to communicate to a server that manages location data and status data applicable to the wireless tag; and wherein a tag tamper-proof switch is secured by the tag device housing, partially exposed to the tag device exterior, coupled to the tag device electronic circuitry within the interior, and adapted to be activated, deactivated, triggered, or tripped by an attempt to tamper with the wireless tag or the umbilical cord clamp. The wireless tag may also be adapted to be read by and / or communicate with a console component or device, such as for use by a nurse in a maternity ward of a hospital.

[0013] Regarding an exemplary server that communicates with the device of the first aspect of the present invention, the exemplary server includes: server electronic circuits and hardware, the server electronic circuits and hardware including: a server processor; a server memory, the server memory is coupled to the server processor; a server data transmission module, the server data transmission module is coupled to the server processor; a server data transmission device, the server data transmission device is coupled to the server processor; server electronic software, the server software is stored in the server electronic circuits and hardware and is adapted to enable, drive and control the server electronic circuits and hardware; a server power connection, the server power connection is coupled to the electronic circuits and hardware and can be coupled to the server power supply.

[0014] With respect to a console component adapted to read or communicate with the fixture device of the first aspect of the present invention, an exemplary console component may include: console electronic circuitry and hardware, the console electronic circuitry and hardware including: a console processor; a console camera, the console camera coupled to the console processor; a console display, the console display coupled to the console processor; a console memory, the console memory coupled to the console processor; a console positioning device, the console positioning device coupled to the console processor; a console data transfer module, the console data transfer module coupled to the console processor; a console data transfer device, the console data transfer device coupled to the console processor; console electronic software, the console software stored in the console electronic circuitry and hardware and adapted to enable, drive and control the console electronic circuitry and hardware; a console power connection, the console power connection coupled to the console electronic circuitry and hardware and coupleable to a console power supply; and a console housing, the console housing including a console interior and a console exterior, the console interior accommodating the console electronic circuitry and hardware, the console software and the console power connection; and the console exterior including a console frame enclosing the console interior.

[0015] In some embodiments, the data transmission device can be adapted to enable data transmission between the console and a separate computing device, wherein the data transmission device can be adapted to enable the console to communicate with a separate computing device and transmit electronic data feeds to the separate computing device, and enable a separate computing device to communicate with the console and transmit electronic data to the console. The data transmission device may include, for example, a cable, a wireless transceiver, or both. The console can be enabled to transmit data, software, and configuration files to a separate computing device and / or receive data, software, and configuration files from a separate computing device, and enable a separate computing device to transmit other software and files to the console. The cable or separate power cable may also be adapted to power the console when the cable is coupled to an external power source and / or enable the console to recharge an internal power source.

[0016] According to a second aspect of the present invention, a system suitable for monitoring the position and status of a wireless-enabled umbilical cord clamp device, managing the status and events of the wireless-enabled umbilical cord clamp device, and detecting tampering with the wireless-enabled umbilical cord clamp device is disclosed, the system comprising: a server, the server comprising: server electronic circuits and hardware, the server electronic circuits and hardware comprising: a server processor; a server memory, the server memory coupled to the server processor; a server data transmission module, the server data transmission module coupled to the server processor; a server data transmission device, the server data transmission device coupled to the server processor; server electronic software, the server software storage in the server electronic circuitry and hardware and adapted to enable, drive and control the server electronic circuitry and hardware; and a server power connection, the server power connection being coupled to the server electronic circuitry and hardware and being coupleable to the server power supply; wherein the server is adapted to determine position data and status data based on receiving position data and status data from within the system, interpret the determination of the position data and status data, determine a response to the interpretation of the position data and status data, and communicate the response; a wireless transceiver, the wireless transceiver communicating with the server data transmission device and the server data transmission module; a wireless-enabled umbilical cord clamp device, the wireless-enabled umbilical cord clamp device comprising: a tag device electronic circuit and hardware The tag device electronic circuit and hardware include: a tag device processor; a tag device memory, the tag device memory is coupled to the tag device processor; a tag device wireless data transmission module, the tag device data transmission module is coupled to the tag device processor; a tag device wireless data transmission device, the tag device data transmission device is coupled to the tag device processor; and a tag anti-tamper switch, the tag anti-tamper switch is coupled to the tag device processor; the tag device electronic software, the device software is stored in the device electronic circuit and hardware and is adapted to enable, drive and control the device electronic circuit and hardware; the tag device power supply, the device power supply is coupled to the device electronic circuit and hardware and is adapted to powering the device electronic circuitry and hardware; and a tag device housing comprising a tag device exterior and a tag device interior, the tag device interior housing the tag device software, the tag device power supply, and at least some of the tag device electronic circuitry and hardware; the tag device exterior comprising a clamp device frame adapted to be secured adjacent to the umbilical cord of a newborn when the umbilical cord is clamped by an umbilical cord clamp; wherein the device electronic circuitry and hardware are adapted to operate as a wireless tag adapted to be wirelessly read by a wireless tag reader comprising a wireless transceiver; wherein the wireless tag reader is adapted to communicate to a server that manages location data and status data applicable to the wireless tag;and wherein the tag tamper switch is secured by the tag device housing, partially exposed to the exterior of the tag device, coupled to the tag device electronic circuitry within the interior, and adapted to be activated, deactivated, triggered, or tripped by an attempt to tamper with the wireless tag or the umbilical clamp.;

[0017] In an exemplary embodiment of the system, each console or fixture device unit may include at least one of a plurality of configurations. Configurations may include, for example, maps (e.g., floor plans of hospitals, flight routes of hospitals, road maps of roads around hospitals, topographic maps of land around hospitals, resource maps of resources within hospitals, route maps of relocated labels, perspective maps, plan maps, viewpoint maps, etc.), user interfaces ("UI"), utilities (e.g., switching points, display details, switching profiles, account synchronization, etc.), terrain (e.g., hospitals, parking lots, cities, towns, etc.), tools (e.g., clamping cutting tools, vehicles, drug units or types, nutrition units or types, etc.), capabilities (e.g., applications, attachments, cutting, removal, etc.), identities (e.g., nurses, doctors, patients, newborns, pregnant women, postpartum mothers, fathers, etc.), and communication utilities (e.g., electronic medical records (EMR) interfaces, social media connections, message feeds, etc.). Users of the platform may include, for example, nurses, doctors, patients, consumers, producers, performers, businesses, developers, administrators, etc., or combinations thereof. Users can create and / or distribute configurations, or both, by using a user-based creation and / or distribution platform for configurations. Each configuration can be software code in a configuration file, which includes, for example, one or more of a settings file, a configuration file, a profile file, an applet file, an application file, a plug-in file, an application programming interface ("API") file, an executable file, a library file, an image file, a video file, a text file, a database file, a metadata file, and a message file. The producer user can develop software code for the configuration file using, for example, programming in a coding language such as JavaScript and HTML, including open source code or object-oriented code assembly. The software code will be adapted to be compatible with and executable by the software of a console (e.g., an iPhone smart phone, a smart watch, a laptop, a tablet computer, etc., or some combination thereof), a compatible video can be displayed on the console, and the configuration will be used with or within the console.

[0018] In an exemplary embodiment, the system may include the device of the first aspect of the invention, wherein the device is adapted and configured to interact with the platform. The system may be further adapted to enable, permit and allow multiple users to interact with each other, against each other, with one or more system-generated team members, or a combination thereof. The system may be adapted to enable, permit and allow users to associate content with a location, topic and / or theme, and push such associated content to another user who is located at the location, interested in the topic and / or connected to the theme.

[0019] According to a third aspect of the present invention, a method for monitoring the position and detecting tampering of a wireless-enabled umbilical cord clamp device is disclosed, wherein the method comprises: providing a device adapted to be coupled to and communicate with a server; generating position data and status data of the device, and the position data and status data are generated by the device; transmitting the position data and status data from the device to the server; receiving the position data and status data from the device at the server; determining the position data and status data by the server; interpreting the position data and status data based on the determination of the server; determining a response to the interpretation made by the server; and communicating the response to a response recipient based on the interpretation; wherein the wireless-enabled umbilical cord clamp device comprises: a tag device electronic circuit and hardware, the tag device electronic circuit and hardware comprising: a tag device processor; a tag device memory, the tag device memory coupled to the tag device processor; a tag device wireless data transmission module, the tag device data transmission module coupled to the tag device processor; a tag device wireless data transmission device, the tag device data transmission device coupled to the tag device processor; and a tag anti-tamper switch, the tag anti-tamper A switch coupled to a tag device processor; tag device electronic software, the device software being stored in the device electronic circuit and hardware and being adapted to enable, drive and control the device electronic circuit and hardware; a tag device power supply, the device power supply being coupled to the device electronic circuit and hardware and being adapted to power the device electronic circuit and hardware; and a tag device housing, the tag device housing comprising a tag device exterior and a tag device interior, the tag device interior accommodating the tag device software, the tag device power supply, and at least some of the tag device electronic circuit and hardware; the tag device exterior comprising a fixture device frame, the fixture device frame being adapted to be secured adjacent to the umbilical cord of a newborn infant when the umbilical cord is clamped by the umbilical cord clamp; wherein the device electronic circuitry and hardware are adapted to operate as a wireless tag adapted to be wirelessly read by a wireless tag reader including a wireless transceiver; wherein the wireless tag reader is adapted to communicate to a server that manages location data and status data applicable to the wireless tag; and wherein the tag tamper switch is secured by the tag device housing, partially exposed to the exterior of the tag device, coupled to the tag device electronic circuitry within the interior, and adapted to be activated, deactivated, triggered, or tripped by an attempt to tamper with the wireless tag or the umbilical cord clamp;

[0020] In an exemplary embodiment, the method may be further adapted for neonatal safety, neonatal security, and / or participant notification, wherein the method includes providing a device adapted for interacting with a participant, wherein the device may be configured according to the first aspect of the present invention; configuring the device to interact within a system; configuring the device to interact with a participant; enabling the device to interact with the participant; and enabling the device to electronically process status data, identity data, location data, configuration data, audio data, video data, or a combination thereof, of the device's interaction with the participant.

[0021] Further aspects of the invention are described herein. Details of exemplary embodiments of the invention are described in the drawings and the following description. Other features, objects and advantages of the invention will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The detailed description provided below explains in detail the different features, advantages and aspects of the present invention by reference to the accompanying drawings showing exemplary embodiments of the present invention. Therefore, the features of the present invention can be more clearly understood from the following detailed description considered in conjunction with the following drawings, wherein the same reference numerals always represent the same, similar or similar elements. The exemplary embodiments shown in the drawings are not necessarily to scale or shaped, and should not be considered to limit the scope thereof, because as set forth in the appended claims, the present invention may allow for other equally effective embodiments with different combinations of features.

[0023] Figure 1A A block diagram of an exemplary embodiment of a system according to aspects of the invention is shown.

[0024] Figure 1B A block diagram of an exemplary embodiment of a wireless-enabled fixture or fixture tag device according to aspects of the present invention is shown.

[0025] Figure 1C A block diagram of an exemplary embodiment of a console device according to aspects of the present invention is shown.

[0026] Figure 2 A block diagram illustrating an exemplary embodiment of a method of using an exemplary device of the prior art according to the present invention.

[0027] Figure 3 A block diagram illustrating an exemplary embodiment of the operation of the inventive apparatus according to aspects of the invention.

[0028] Figure 4 A block diagram of an exemplary computer environment according to aspects of the invention is shown for use with systems and methods according to embodiments of the invention.

[0029] Figure 5 A block diagram of an exemplary system according to aspects of the present invention and an exemplary set of databases for use within an exemplary computer environment and an exemplary database for use with systems and methods according to embodiments of the present invention is shown.

[0030] Figure 6 A block diagram of an exemplary embodiment of a method of using an exemplary system according to aspects of the invention is shown.

[0031] Figure 7 A conceptual block diagram illustrating exemplary system functional operational flows within systems and methods according to exemplary embodiments of the present invention, in accordance with aspects of the present invention.

[0032] Figure 8 A conceptual block diagram illustrating the operation of an exemplary device according to aspects of the present invention as a device within a system used in accordance with a method according to an exemplary embodiment of the present invention.

[0033] 9A to 9D Various exemplary fixtures according to aspects of the present invention are shown as devices within a system used in accordance with a method according to an exemplary embodiment of the present invention.

[0034] FIG. 10A to FIG. 10E Wireless tags depicted from different perspectives according to aspects of the present invention are shown that may be used in exemplary devices within a system used in accordance with a method according to an exemplary embodiment of the present invention.

[0035] FIG. 11A to FIG. 11D Other wireless tags depicted from different perspectives according to aspects of the present invention are shown and may be used in exemplary devices within a system used in accordance with a method according to an exemplary embodiment of the present invention.

[0036] FIG. 12A to FIG. 12C Switches depicted from different perspectives are shown according to aspects of the invention that may be used in exemplary devices within a system used in accordance with a method according to an exemplary embodiment of the invention.

[0037] Reference numerals list

[0038] The following are reference numerals that indicate the same, similar or analogous elements in the drawings and detailed description of the present invention:

[0039] 10000 systems

[0040] 11000 Wireless-enabled Umbilical Cord Clamp Device

[0041] 11001 Newborn umbilical cord

[0042] 11100 External housing

[0043] 11110 Framework

[0044] 11120 Fixture or fixture interface

[0045] 11200 Internal

[0046] 11300 Electronic Circuits

[0047] 11310 Integrated electronic hardware system

[0048] 11311 Internal processor

[0049] 11312 Internal memory

[0050] 11313 Internal power supply

[0051] 11314 integrated data transmission module

[0052] 11315 Integrated input button or switch

[0053] 11316 Integrated speaker

[0054] 11317 lighting fixtures

[0055] 11318 Integrated microphone or audio sensor

[0056] 11319 Integrated camera or light sensor

[0057] 11320 Integrated software operating system

[0058] 11330 Database

[0059] 11331 First Profile

[0060] 11332 Electronic Medical Records (EMR) Applications

[0061] 11333EMR Configuration

[0062] 11340 Data Transmission Device

[0063] 11350 positioning device

[0064] 11351 Accelerometer or Inertial Motion Unit (IMU)

[0065] 12000 wireless-enabled console unit devices

[0066] 12010 Nurse Console

[0067] 12011 Participating nurses

[0068] 12020 Hospital Workstation Console

[0069] 12021 Power Users

[0070] 12100 External housing

[0071] 12110 Framework

[0072] 12120 handle

[0073] 12200 Internal

[0074] 12300 Electronic Circuits

[0075] 12310 Integrated Electronic Hardware System

[0076] 12311 integrated camera

[0077] 12312 integrated microphone

[0078] 12313 Integrated speakers

[0079] 12314 internal processor

[0080] 12315 internal memory

[0081] 12316 internal power supply

[0082] 12317 integrated data transmission module

[0083] 12318 integrated input button

[0084] 12319 Mini Display

[0085] 12319'Lighting fixture

[0086] 12320 integrated software operating system

[0087] 12330 Database

[0088] 12332 First Profile

[0089] 12334 Electronic Medical Records (EMR) Application

[0090] 12336EMR Configuration

[0091] 12400 Data Transmission Device

[0092] 12500 positioning device

[0093] 12510 Accelerometer or Inertial Motion Unit (IMU)

[0094] 12520 Infrared (IR) Sensor

[0095] 13000 wireless transceiver equipment

[0096] 14000 server devices

[0097] 15000 wireless communication

[0098] How to use 20000 fixture equipment

[0099] 21000 Start testing

[0100] 21100 Detect input in progress (for example, a button being activated)

[0101] 21200 Detection Command

[0102] 21300 Detecting the location or movement of a device

[0103] 22000 starts responding

[0104] 22100 Update status

[0105] 22200 Display warning

[0106] 23000 follow-up detection and response

[0107] 23100 Detection Status

[0108] 23200 Display status

[0109] 23300 Record Status

[0110] 23400 Response Response

[0111] 24000 End of detection

[0112] 24100 Testing completed

[0113] 24200 Detecting ongoing input

[0114] 25000 End Response

[0115] 25100 Display confirmation or confirmation end to the first participant

[0116] 25200 displays the end status and stores the record of the interaction as an interactive EMR file as a computer-readable file on a computer-readable storage medium

[0117] 30000 data transmission device

[0118] 30010 Cable

[0119] 30020 Wireless Transceiver

[0120] 31000 data transmission

[0121] 31100 Electronic Data

[0122] 31110 Standalone Device Software Application

[0123] 31120EMR File

[0124] 31130 Setting up the database

[0125] 31140 Image Files

[0126] 31150 EMR Applications

[0127] 31160 EMR Application Configuration

[0128] 32000 Remote devices, e.g., fixture equipment or EMR console

[0129] 32100 Internal Power Supply

[0130] 33,000 individual computing devices

[0131] 33010 Auxiliary Processing Unit

[0132] 33012 Wireless Transceiver

[0133] 34000 External Power Supply

[0134] 40000 Computer Environment

[0135] 41000 EMR Data System

[0136] 41100 EMR Console Device

[0137] 41200 Fixture Equipment

[0138] 42000 Network

[0139] 43,000 network connections

[0140] 44000 computing devices

[0141] 44100 Smart Device

[0142] 44200 Mobile Phone

[0143] 44300 Tablet

[0144] 45000 EMR data servers

[0145] 45100 EMR data account

[0146] 45110 EMR data selected for delivery to user device

[0147] 50000 Data System

[0148] 51000 computing devices

[0149] 51010 EMR Device Console

[0150] 51100 processor

[0151] 51200 Memory

[0152] 51300 Volatile and Nonvolatile Memory

[0153] 51400 Removable storage

[0154] 51500 Non-removable storage

[0155] 51600 communication connection

[0156] 51700 Input Device

[0157] 51800 Output Device

[0158] 52000 Network

[0159] 53000 servers

[0160] 54000 Database

[0161] 54100 Database

[0162] 54200 Database

[0163] 54300 Database

[0164] 54400 Database

[0165] 54500 Database

[0166] 54600 Database

[0167] 55000 Tracking Devices

[0168] 55010 Tag Reader Device

[0169] How to use the 60000EMR system

[0170] 61000 state capture and position detection

[0171] 61100 Detection Input

[0172] 61200 Detection Status

[0173] 61300 Detect position or motion

[0174] 62000 fixture position and status data feed transmission

[0175] 62100 Send location ping data feed

[0176] 62200 Send fixture status data feed

[0177] 63000 server calculations and responses

[0178] 63100 Determine the location of a fixture or fixture tag

[0179] 63200 Calculate position status

[0180] 63300 Send status, warning, alarm or lock command update

[0181] 64000 Receive and Response Combinations

[0182] 64100 Receive updated status, etc.

[0183] 64200 Combined Updated Data Feed and EMR Data

[0184] 65000EMR records or data reception and display

[0185] 65100 Receive combined EMR data feed

[0186] 65200 Display combined EMR data feed

[0187] 70000 System Function Overview

[0188] 70010 System

[0189] 70100 server output, console or APU input function

[0190] 70200 console or APU output, label input function

[0191] 70300 tag output, console or APU input function

[0192] 70400 console or APU output, server input function

[0193] 71000 Server Features

[0194] 72000 servers

[0195] 71010 Console or APU Function

[0196] 72010 Console or Auxiliary Processor Unit (APU)

[0197] 73000 tag functions

[0198] 73010 Fixture Equipment Label

[0199] 80000 System Function Overview

[0200] 80010 System

[0201] 80100 server output, APU input function

[0202] 80200APU output, label or console input function

[0203] 80300 label or console output, APU input function

[0204] 80400APU output, server input function

[0205] 81000 Server Features

[0206] 81010 Server

[0207] 82000 Auxiliary Processor Unit (APU) Functionality

[0208] 82010 Auxiliary Processing Unit

[0209] 83000 tag or console function

[0210] 83010 Tag or console

[0211] 90000 fixture

[0212] 90010 fixture

[0213] 90011 hinge and hinge cavity

[0214] 90012 First opposite row of teeth

[0215] 90013 Second opposite row of teeth

[0216] 90014 Locking mechanism

[0217] 90015 convex part

[0218] 90016 concave part

[0219] 90020 clamp

[0220] 90024 Locking mechanism

[0221] 90025 convex part

[0222] 90026 concave part

[0223] 90030 fixture

[0224] 90035 convex part

[0225] 90036 concave part

[0226] 90037 Open unlock position

[0227] 90038 Pin

[0228] 90039 button

[0229] 90040 clamp

[0230] 90047 Closed locked position

[0231] 100000 wireless tags

[0232] 100010 wireless tag

[0233] 100011 Hexagonal Shell

[0234] 100012 handle

[0235] 100013 support

[0236] 100014 button

[0237] 110000 wireless tags

[0238] 110010 wireless tag

[0239] 110011 rectangular shell

[0240] 110012 handle

[0241] 110013 support

[0242] 120000 switches

[0243] 120010 switch

[0244] 120011 hinge

[0245] 120012 rods

[0246] 120013 Button

[0247] 120020 switch

[0248] 120023 button

[0249] 120030 switch

[0250] 120033 membrane switch DETAILED DESCRIPTION

[0251] The present invention relates to systems, methods and devices including components that can be combined in a variety of ways and may include one or more of a wireless-enabled umbilical cord clamp and / or clamp tag, a wireless transceiver, a wireless-enabled console unit and / or a server adapted to operate within a wireless networking environment (such as a hospital) for treatment, identification and tracking of newborns. As used herein, the term "wireless-enabled umbilical cord clamp" refers to any umbilical cord clamping mechanism used in conjunction with a clamp tag or wireless tag of the present application as described herein.

[0252] The present invention relates to systems, methods and devices including platforms and components and / or devices adapted to provide a wireless monitoring system for the safety of newborns. In an exemplary embodiment of the present invention, the device includes a wireless-enabled umbilical cord clamp device adapted to function within a system including a handheld console (such as a smart phone or tablet). The device can be adapted to operate as an umbilical cord clamp having an integrated or attachable configurable wireless tag having electronic devices (such as tamper-proof switches and transceivers, and optional cameras, displays, microphones, speakers, buttons) coupled to and controlled by a processor, wherein the device is adapted to be connectable to a monitoring platform, such as a data server or system in a networked environment. The present invention is capable of interacting with an electronic medical record (EMR) system. In some embodiments, the console may be wired and connectable to a fixed location, such as a workstation or desktop computer operating a browser or desktop application, while in other embodiments, the console may include an internal rechargeable battery and a radio frequency transceiver so that the console may be wireless and portable, such as a smartphone or tablet, as a dedicated device, or as a device configured with software for that purpose.

[0253] Exemplary Embodiments of the System

[0254] According to the hospital environment of the present invention, just after the birth of a newborn, medical staff use a wireless-enabled umbilical cord clamp to clamp the umbilical cord of the newborn to stop blood from flowing in the umbilical cord, and then cut the umbilical cord of the newborn and clamp the clamp between the incision and the newborn to stop the bleeding of the umbilical cord of the newborn. The wireless-enabled umbilical cord clamp includes a wireless tag integrated into the clamp or attachable to the clamp, and the wireless tag includes a processor, a sensor, a power supply, and a wireless communication circuit to achieve wireless programming and communication to and from the clamp, so that shortly after the birth of the newborn, the medical staff can program the clamp device and / or the tag to identify the newborn and monitor and track the newborn in the hospital. The wireless-enabled umbilical cord clamp is fixed to the umbilical cord of the newborn in a manner to prevent the clamp from being tampered with or removed without triggering a warning or alarm in the monitoring system, which may indicate that someone is trying to move the baby without authorization.

[0255] In a wirelessly networked hospital environment according to an embodiment of the present invention, the hospital includes at least one wireless transceiver that can send and receive wireless signals for communicating with a wireless-enabled umbilical cord clamp, and preferably includes a matrix of wireless transceivers distributed and mapped throughout relevant parts of the hospital. The matrix can be mapped to, for example, relevant exit doors, corridor doors, room doors, stairs, elevators, windows, rooms, etc., and coupled to these doors and relevant lights, cameras, alarms, flashing lights, etc. The hospital's wireless system transceiver may include a wireless router (e.g., router, router, router, Beacon, The wireless system transceiver may include or communicate with a system server that compiles and coordinates data and content relative to the status of each wireless-enabled cord clamp, each wireless system transceiver, and each wireless-enabled console unit used and / or active within the system. The system server may communicate within the system using signals via a wired line (such as connected to a wireless router) or via a wireless transceiver data transmission module that is directly integrated into or with the server. In some embodiments, the nurse's handheld wireless-enabled console may itself serve as the system server.

[0256] The wireless-enabled umbilical cord clamp device includes a radio frequency identification (RFID) transceiver that allows medical personnel to track, record, and log interactions with a newborn as a patient of the hospital, such as for monitoring, moving, feeding, treating, immobilizing, and caring for the newborn. Specifically, the clamp transceiver may periodically (e.g., every 5, 10, 20, or 30 seconds, etc.) communicate (i.e., "ping") a wireless system transceiver or a matrix of wireless system transceivers that communicate with a system server and a console unit to update the status of the clamp. Updates to the clamp status may include, for example, the status of the clamp's integrity (e.g., whether the clamp has been opened or removed, triggering a warning or alarm indicating that an abductor may be removing the clamp to abduct a newborn without using the clamp to track the newborn during the abduction process); the status of the clamp's battery strength and remaining power (e.g., whether the clamp needs to be recharged); and the status of the clamp's location (e.g., where the clamp is within the hospital, and moving the clamp from an approved or designated location). In a wirelessly networked hospital environment, fixture location may be determined, for example, by triangulation between system transceivers or comparison of relative signal strengths from a fixture tag transceiver to one or more system transceivers.

[0257] In some embodiments, the fixture tag may use a wireless transmitter instead of a transceiver if the tag is designed to transmit signals only and not receive signals, such as in low-cost, single-use disposable devices and equipment. In some embodiments, the transceiver may be adapted or configured as a data transmission module, or the data transmission device may be limited to transmission only. If the tag uses only a transmitter, or is only adapted to transmit, the tag operates independently of the system components, pushing information to the system without affecting the operation of the tag, and all data programming is completed elsewhere in the system, such as on the nurse's console or at the server, based on the unique identification (ID) of the tag. In some embodiments, the tag will only run and transmit when the tag is activated by closing the fixture, so as to avoid power consumption and save battery reserves, wherein the closure of the fixture can complete or close the circuit required for power to flow in the tag. If the tag experiences a power drop below a threshold power level, the tag can "wake up" and send a low power warning. If the tag is tampered with, such as the fixture is opened, the circuit will be disconnected, the tag will stop operating, and the system will immediately detect the failure of the tag to ping or "check in" with the system a few seconds before the tag was last recorded. When a tag is detected to be not signed in, the system will prompt, alarm, console notification and / or door lock based on the status or location of the tag. In some embodiments, the tag may have a barcode or other ID, allowing the system to register the tag, tag unique ID and / or tag identity within the system without the tag being in an electrically or electronically activated state. In some embodiments, the tag can be temporarily powered and electrically or electronically activated by temporarily closing the clamp to close the circuit to allow the nurse's console to read the tag without closing the clamp and not yet attached to the umbilical cord, allowing the clamp to be reopened after the temporary closure. In some embodiments, when the tag is electrically or electronically activated when the clamp on the umbilical cord is closed, the tag identity will first be entered into the system, and the nurse uses the nurse's console to wirelessly read the tag ID and associate the tag ID with the newborn in the system.

[0258] Medical staff can use the status data received from the activated (or activated) wireless-enabled umbilical cord clamp to monitor the position, safety, treatment and / or health of the newborn. For example, each time the newborn is fed or changed, the clamp's RFID can be read and / or scanned by the nurse's console unit to record the activity. In some embodiments, the clamp can alert medical staff to potential changes in the newborn's health, such as if the newborn rolls or is placed on its abdomen for a time exceeding a set threshold unexpectedly, as measured by a potential sudden drop in RFID signal strength in the clamp while the position remains unchanged, potentially indicating that the baby is on top of the clamp and obstructing the clamp's RFID signal strength. In some embodiments, the clamp may include sensors such as pressure sensors, weight sensors, force sensors, accelerometers, humidity sensors, temperature sensors, light sensors, and / or audio sensors that can provide status data to the system, which can alert medical staff to potential dangerous conditions affecting the newborn if these sensor data meet or exceed a set threshold. For example, if a newborn requires a heat lamp to maintain a desired ambient temperature, a temperature sensor in the clamp can alert medical personnel if the ambient temperature rises or falls outside of the desired temperature range, potentially indicating that the heat lamp is malfunctioning or someone has mis-adjusted the heat lamp. Medical personnel can receive the warning or alarm and take appropriate action to remedy the cause of the triggering warning or alarm, and, if appropriate, reset the clamp, warning, and / or alarm when the cause is remedied.

[0259] Once the newborn is ready to leave the hospital with an approved adult, the medical staff can set, deactivate and / or disarm the clamp within the system, such as at the tag itself, at the console, or at the server, to avoid triggering a removal warning or alarm and possible abduction reminder, and then remove the clamp. When the newborn is ready to leave the hospital, the newborn's umbilical cord will be closed, sealed and healed, so that the clamp is no longer needed to prevent umbilical cord bleeding. If it is a disposable single-use device, the used wireless umbilical cord clamp can be recycled, or if it is constructed and designed as a durable, disinfectable / sterilizable, rechargeable, reprogrammable, reusable, multiple-use device, it can be disinfected and / or sterilized and prepared for reuse.

[0260] Whether constructed and designed as a single-use device or a multiple-use device, the wireless-enabled umbilical cord clamp will preferably be waterproof (e.g., easily submerged when the infant wearing the clamp is bathed) and sterilizable by a hospital-grade topical disinfectant (e.g., an alcohol swab or spray) in order to function properly during the infant's hospitalization and treatment. Similarly, in order for the infant to tolerate the clamp, the clamp needs to be non-irritating in materials so as not to cause any allergic reactions, such as not causing any allergic reactions (e.g., hypoallergenic), contact dermatitis or other skin diseases, and configuration (e.g., preferably low profile, without sharp edges or corners). If designed and manufactured as a disposable, single-use device, the manufacturing cost will preferably be lower than the manufacturing cost of a reusable, multiple-use device, so that the reusable, multiple-use device may include more features, functions and components (e.g., sensors) that increase the cost per device, which may include a license for the relevant hardware, software and / or intellectual property for manufacturing, selling and / or using the device.

[0261] In a preferred embodiment, the units will be as small and lightweight as possible, weighing about 12 grams or less (e.g., preferably 5-6 grams), for single-use manufacturing costs, to avoid strain on the healing umbilical cord or the infant. An exemplary clamp may have a clamp transceiver tag with dimensions of about 34 mm long, about 29 mm wide, and about 5 mm high. Exemplary embodiments will be made of hypoallergenic, biocompatible materials that are rigid, durable, somewhat flexible, and solvent resistant, such as compositions, combinations, polymers, and / or copolymers of, among others, latex, lead, DEHP, polycarbonate, trimethyl carbonate, polyethylene, polypropylene, polyvinyl chloride, polytetrafluoroethylene, stainless steel, alumina, aluminum / aluminum, cobalt chromium alloys, and silicone.

[0262] In some embodiments, the power source may include a battery with a functional battery life that allows use for many hours (such as 12, 24, 36, 48, or 72 hours). In other embodiments, the battery life may last for months or years, depending on the use and battery type. In a preferred embodiment, the power source will include a battery with a functional battery life of at least 96 hours. The power source will preferably last for the entire course of a typical newborn in the United States. In the United States, mothers and newborns are typically discharged from the hospital within two days of vaginal delivery and within three days of delivery by cesarean section. For example, if the average power consumption is low enough, as low as 2.08mA, a battery life of about 96 hours can be achieved with a silver oxide "coin" battery starting from 200mAh power. In an embodiment with an approximate average power consumption of about 10.34mA, a battery starting from about 1000mAh will have a battery life of about 96.7 hours. The fixture processor can detect or measure the remaining battery power, such as using a circuit activated at low power. When the remaining battery power approaches the functional minimum power level, the fixture can detect this power level and send a "low battery" warning to the system.

[0263] In a preferred embodiment, the fixture transceiver (such as a BLE transceiver) will transmit a signal with a functional signal strength that is readable from at least about 10 feet (about 3.1 meters) away from the fixture, and preferably longer (e.g., 20 feet to 30 feet), so as to increase the effectiveness of safety precautions, such as locking the baby room door if an activated fixture set to "no exit" enters within a minimum safe distance (e.g., about 10 feet) of the baby room door. In some embodiments, the effective read range can be at least 30 feet (or more), so that the system detects the approach of an approaching tag from at least 30 feet away from the exit door, and locks the exit door when the approaching tag is within about 10 feet of entering the exit door. The exemplary BLE transceiver can be integrated with the processor on a single printed circuit board (PCB), or coupled to the processor separately from the processor's PCB.

[0264] In a preferred embodiment, the clamp will be easily applied by trained medical personnel and still be able to appropriately detect tampering or other attempts to disable, disengage or remove the clamp without authorization and pre-deactivate the clamp and trigger a warning or alarm due to such unauthorized activity. Exemplary tamper detection devices may include, for example, an enclosed microswitch, pressure sensor switch, or push button switch with a housing that limits access, activation, or deactivation of the tamper detection device without opening the clamp. In a preferred embodiment, the clamp will be suitable for a wide range of newborn sizes and umbilical cord conditions, possibly with alternative clamp configurations for each of the specific umbilical cord conditions or newborn sizes.

[0265] In some embodiments of the present invention, a system is provided that includes a hospital security platform that connects a nurse's interface with EMR access to a security system in a networked environment that may include connections between building doors that can be electronically and remotely locked and unlocked. The platform and system may provide dashboards for example of user activity, tag activity, tag status, and console status data.

[0266] FIGURES OF EXEMPLARY EMBODIMENTS OF THE INVENTION

[0267] Referring to the accompanying drawings, a clamp device or clamp assembly may include: a mechanical clamp mechanism operable to clamp the umbilical cord of a newborn; the computing device as an integrated tag or attachable tag, the computing device operable to wirelessly communicate with a wireless-enabled console, a wireless-enabled checkpoint, and / or a server. The clamp device or clamp assembly may be connectable to a secure platform via a networked environment, and may include and / or communicate with a portion of an electronic medical record (EMR) media server platform or system, the EMR media server platform or system may include a data system and a network system, the data system including at least one server and at least one database, the network system including computing devices that communicate with each other via a network connection.

[0268] refer to Figure 1A , Figure 1A A block diagram of an exemplary system 10000 adapted to monitor the safety and position of a newborn is shown. The system 10000 may include: a wireless-enabled umbilical cord clamp device 11000 adapted to mechanically clamp the umbilical cord 11001 of a newborn; a wireless-enabled console unit device 12000 adapted to interact with the clamp device 11000; a wireless transceiver device 13000 for wirelessly interacting with the clamp device 11000; and a server device 14000 for managing and maintaining data, rules, and interactions within the system 10000. When wiring is provided, the components of the system 10000 may communicate using wireless communications 15000 within the system 10000 as well as wired communications between components. System 10000 may be used by users, such as participant 12011 , who may be a nurse, and power user 12021 , who may be a supervisory nurse or information technology (IT) resource employee responsible for configuring, managing, and overseeing system 10000 and / or nurse participant 12011 .

[0269] The clamp device 11000 may include an umbilical cord clamp and an integrated wireless tag or an attachable wireless tag. The console device 12000 may include a computing device, such as a fixed-position desktop computer or nurse's workstation, or a mobile computer or other configurable device, such as a laptop, tablet computer, or mobile smart device (such as a mobile smart phone). The transceiver device 13000 may include a wireless receiver adapted to receive wireless signals from the clamp device 11000 and a wired or wireless transmitter for communicating the clamp status data to the console 12000 or the server 14000. For example, the transceiver device 13000 may include a wireless BLE reader adjacent to a doorway (such as an entrance or exit), which is adapted to detect and report a BLE signal emitted by the clamp device 11000. The transceiver device 13000 is preferably one of many such signal readers that form a signal detection matrix within the hospital for particle position determination. Server 14000 may include a local server, a local area network (LAN) server, a wide area network (WAN) server, a cloud-based network server, further use of console 12000, or a combination thereof. As explained elsewhere, system 10000 may be part of a larger system such as a hospital security platform and / or an EMR platform or system.

[0270] refer to Figure 1B , Figure 1B A block diagram of an exemplary clamp device 11000 adapted for use in system 10000 is shown. Clamp device 11000 may be a self-contained cord clamp if sufficient computing power and memory are integrated into the clamp, or clamp device 11000 may include an assembly of an umbilical cord clamp and a wireless tag, wherein the wireless tag is adapted to interoperate with the umbilical cord clamp, for example to allow detection of tampering with or efforts to remove the clamp. The present invention contemplates that components of system 10000 may be sold separately, and as separate embodiments of the present invention, the present invention includes a non-integrated wireless tag that may be attached to a conventional umbilical cord clamp. Device 11000 may be configured for one-way or two-way communication adapted for use by participant 12011. As depicted, device 11000 includes a wireless-enabled clamp device having an external housing 11100, such as in 9A to 9D The fixture 90000 in FIG. 10A to FIG. 11D The outer housing 11100 may define an inner compartment 11200 containing electronic circuit 11300. The housing 11100 may include a frame 11110. The outer housing 11100 and the frame 11110 may be made of a suitable durable material, such as polycarbonate or other biocompatible material.

[0271] The electronic circuit 11300 includes an integrated electronic hardware system 11310 and an integrated software operating system 1132 stored and executable on the integrated electronic hardware system 11310. The software 11320 may include, for example, firmware, operating systems, applications, drivers, libraries, and application programming interfaces. The electronic software 11320 may be stored in the electronic circuit 11300 and the hardware 11310, and may be used to enable, drive, and control the electronic circuit 11300 and the hardware 11310. The integrated electronic hardware system 11310 may include, for example, one or more printed circuit boards (“PCBs”), such as a motherboard, an internal processor 11311 integratedly coupled to an internal memory 11312, an internal power supply 11313, an integrated data transfer module 11314, and an integrated switch or button input device 11315, and may interoperate with the software 11320, the database 11330, and the data transfer device 11340.

[0272] Other optional integrated components may include an integrated speaker 11316 (such as for beeping as a warning), an integrated lighting device 11317 (such as a light emitting diode (LED) light that flashes as a warning or alarm), an integrated microphone or audio sensor 11318, and an integrated camera 11319. These optional components will presumably be integrated into more expensive, reusable devices, while fewer components will presumably be integrated into cheaper, single-use devices.

[0273] The button or switch 11315 may be adapted to activate the device 11000 and detect attempts to tamper with and / or remove the device 11000, such as attempts to abduct a newborn. The switch 11315 may include, for example FIG. 12A to FIG. 12C 120000. In some embodiments, the switch or button 11315 may include a locking button that is easily depressed with a finger, but once depressed, locks and remains locked in the depressed position and activated state until and need to be released using a special tool or key that can be operated without the external housing 11100. If the button 11315 is locked to keep the clamp device 11000 activated, a separate tamper-proof switch 11315 can be used to detect tampering, such that tampering easily activates or deactivates the separate tamper-proof switch 11315, while the locked activation button keeps the clamp device 11000 activated and transmitted within the system 10000 to allow the system 10000 to track and discover clamp devices 11000 that have been tampered with or removed.

[0274] Depending on the needs of the integrated components, the processor 11311 may include a central processing unit ("CPU"), a graphics processor (i.e., a graphics card or video card), or a combination thereof. The software 11320 and hardware 11310 may be adapted to enable the participant 12011 and / or power user 12021 to set up the device 11000 from and by the console 12000, such as creating a database 11330 in the software 11320 and storing the database 11330 in the memory 11312, the database 11330 including a first profile 11331 identifying a first newborn, and downloading, installing, selecting, and running an EMR application 11332 and an EMR application configuration 11333 for and compatible with a configurable application (such as EMR application 11333).

[0275] In some more expensive embodiments, the hardware 11310 may further include a portable, small, or mini display as an illumination device 11317, similar to the display of a smart watch, and wherein the software 11320 may be adapted to present, for example, a settings menu, an audiovisual file, an image file, on-screen text, an on-screen text input icon, or any combination thereof on the display 11317. In some embodiments, the display 11320 may be touch-sensitive. Although the display 11320 may emit light, such as using a backlight or illuminated pixels (e.g., in a display in which each pixel is an organic light emitting diode ("OLED")), the hardware 11310 may further include a simple lighting device adapted to illuminate at least a portion of the external housing 11100. For example, the illumination device 11317 may include a light emitting diode ("LED") adapted to illuminate a portion of the external housing 11100 surrounding the switch or button 11315. LED light 11317 can indicate the status of device 11000, such as off / no light to indicate no warning or no alarm, flashing white light to indicate ping signal transmission, flashing green light to indicate programming mode, flashing yellow light to indicate low battery reminder, flashing red light to indicate very low battery warning, and non-flashing red light to indicate a warning (such as a perimeter violation warning).

[0276] The device 11000 includes a data transmission device 11340 adapted to interoperate with the electronic circuit 11210. The data transmission device 11340 may include at least one wireless communication module (such as a wireless transmitter or a wireless transceiver) and possibly one or more wired communication modules and / or devices, such as those described with respect to Figure 3 For example, the wired data transfer device can be used to recharge the device 11000 .

[0277] As depicted, the device 11000 includes a positioning device 11350 adapted to generate positioning data for determining the position, orientation, motion, movement, and / or perspective of the device 11000. In some embodiments, the positioning device 11350 is "non-computing" and includes a data transmission device 11340 adapted to transmit a device-outgoing wireless signal for determining the position of the device 11000 within the system 10000. In more advanced and complex embodiments of the device 11000, such as the above-described embodiment reminiscent of a smartwatch, the positioning device 11350 may include other technical components mentioned below, and may also be referred to as a position measurement device. The positioning device 11350 may generate or be used to generate data regarding the relative position of the device 11000, but the positioning device 11350 does not "position" the device in the sense that a gimbal may "position" or a tripod may support a device in a fixed position.

[0278] An "active" or "computational" positioning device 11350 may include a global positioning system (GPS) receiver and / or GPS module from which an "absolute" position relative to the earth may be measured and calculated locally within the device 11000. In some embodiments, the importance of the positioning device 11350 to the device 11000 may be more related to the relative perspective of the device 11000 within the system 10000 (such as the position within a hospital) than to the absolute position of the device 11000. Exemplary positioning devices 11350 may include gyroscopes, infrared (IR) sensors, accelerometers, inertial motion units (IMUs) 11351, and / or other sensors that may be adapted to detect beacons on a platform or other tracking devices that transmit signals suitable for triangulating the position of the device 11000 (see FIG. 10 ). Figure 5 ). In some embodiments, the sensor may include a sensor-emitter pair (e.g., light detection and ranging (“LiDAR”) or laser detection and ranging (“LaDAR”)) for local active distance determination. Alternatively, the software 11320 may be programmed to use machine vision and / or artificial intelligence (“AI”) to determine the location of the device 11000 (such as using triangulation or comparable AI calculations) to identify artifacts within the field of view captured by the camera 11319 in the video data (e.g., identifiable background objects, like a crib, to identify whether a newborn is leaving or has left the newborn's crib).

[0279] Different data settings for the device 11000 may include creating a first profile 11331 to include, for example, a first baby name of a newborn to which the clamp device 11000 is attached, a first participant name of a first participant 12011 or a power user 12021 (e.g., a nurse who attached the clamp), or a biographical event (e.g., a birthday), and storing a first facial image of the newborn or the first participant 12011 or the power user 12021 or an image of the mother of the newborn. The camera 11319 and the software 11320 may be adapted to recognize the face of the first participant 12011 or the power user 12021 based on a comparison with the first facial image. The user may associate the first facial image with the user's profile for inclusion in a user post on an online EMR platform or EMR media system. In addition, the configuration 11333 may be specific to a user profile and may be configured to automatically load when the face of the first participant 12011 or the power user 12021 is recognized within a specified distance of the device 11000.

[0280] In other possible variations, the software 11320 may be further adapted to enable the power user 12021 to select one of a plurality of languages ​​programmed into the software 11320; select one of a plurality of settings programmed into the software 11320; establish a first profile by inputting first profile parameters comprising a first performance, a first role, a first position, a first location, a first event, the like, or any combination thereof relative to a first participant and / or a first biographical event; and configure the software 11320 to adjust interaction parameters based on the entered first profile parameters.

[0281] Technical variations may include, for example, adapting the camera 11329 and software 11320 to measure ambient light, motion, or both, such that the device 11000 may be adapted to alternate between a less activated state, a deactivated state, and an activated state based on the presence or absence of a minimum threshold for measuring ambient light, motion, or both.

[0282] refer to Figure 1C , Figure 1C A block diagram of a console unit device 12000 adapted to include and / or operate as a nurse's console 12010, and / or a workstation console 12020, or other configurable device such as a laptop, tablet, or mobile smart device (such as a mobile smart phone) is shown. The device 12000 may be self-contained if sufficient computing power and memory are integrated therein (e.g., in a smart phone), or the device 12000 may include and / or interoperate with a separate computing device, such as Figure 3and as described below. The device 12000 can be configured for interactive communication adapted for use by a participant 12011 in a hospital environment. As explained below, the device 12000 can be part of a larger system (e.g., an EMR platform and / or a hospital security platform or system). As depicted, the device 12000 includes a nurse's console 12010 or a workstation console 12020 having an external housing 12100 defining and having an internal compartment 12200 housing electronic circuitry 12300. The housing 12100 may include a frame 12110 and an optional handle 12120. The external housing 12100 and the frame 12110 may be made of conventional, suitably durable materials for the construction of smartphones, tablet computers, and laptop computers.

[0283] The electronic circuit 12300 includes an integrated electronic hardware system 12310 and an integrated software operating system 12320 stored on and executable on the integrated electronic hardware system 12310. The software 12320 may include, for example, firmware, operating systems, applications, drivers, libraries, and application programming interfaces. The electronic software 12320 may be stored in the electronic circuit 12300 and the hardware 12310 and may be adapted to enable, drive, and control the electronic circuit 12300 and the hardware 12310. The integrated electronic hardware system 12310 may include, for example, one or more printed circuit boards ("PCBs"), such as a motherboard, integrating a variety of optional components, such as an integrated camera 12311, an integrated microphone 12312, an integrated speaker 12313, all of which are coupled to an internal processor 12314, coupled to an internal memory 12315, an internal power supply 12316, an integrated data transfer module 12317 interoperable with the data transfer device 12400, and at least one integrated input device 12318 (e.g., buttons, switches, dials, sliders, keyboards, joysticks, touch pads, touch screens, fingerprint sensors, cameras, photoelectric sensors, infrared sensors, microphones, audio sensors, motion sensors, gyroscopes, accelerometers, inertial motion units ("IMU"), etc.) that can be operated without an external housing 12100. Depending on the needs of the components, the processor 12314 may include a central processing unit ("CPU"), a graphics processor (i.e., a graphics card or video card), or a combination thereof. The software 12320 and the hardware 12310 can be adapted to enable the power user 12021 to establish a configurable console 12000, such as creating a database 12330 in the software 12320 and storing the database 12330 in the memory 12315, and downloading, installing, selecting and running an EMR application 12334 and an EMR application configuration 12336 for and compatible with a configurable application (such as the EMR application 12334), the database 12330 including a first profile 12332 identifying the first participant 12011.

[0284] The hardware 12310 further includes a portable, medium, small or mini display 12319, such as found on a smartphone or tablet, and wherein the software 12320 is adapted to present, for example, a settings menu, an audiovisual file, an image file, on-screen text, an on-screen text input icon, or any combination thereof, on the display 12319. In some embodiments, the display 12319 may be touch-sensitive. Although the display 12319 may emit light, for example, using a backlight or illuminated pixels (e.g., in a display in which each pixel is an organic light emitting diode ("OLED")), the hardware 12310 may further include a simple lighting device 12319' adapted to illuminate at least a portion of the external housing 12100. For example, the lighting device 12319' may include a light emitting diode ("LED") adapted to illuminate a portion of the external housing 12100, such as for use as a flashlight, or as a prompt around the input button 12318. The LED light 12319' may indicate the status of the nurse console 12010.

[0285] Different data settings of the device 12000 may include creating a first profile 12332 to include, for example, inputting a first participant name, a newborn's name, or a biographical event (e.g., birthday) of the first participant 12011 or power user 12021, and storing a first facial image of the face of the first participant 12011 or power user 12021, or an image of the mother. The camera 1231 and software 12320 may be adapted to recognize the face of the first participant 12011 or power user 12021 based on a comparison with the first facial image. The user may associate the first facial image with the user's profile for inclusion in a user post on an online EMR platform or EMR media system. In addition, the EMR configuration 12336 may be specific to the user's profile and may be configured to be automatically loaded when the face of the first participant 12011 or power user 12021 within a specified distance of the device 11000 is recognized.

[0286] In other possible variations, the software 12320 may be further adapted to enable the power user 12021 to select one of a plurality of languages ​​programmed into the software 12320; select one of a plurality of settings programmed into the software 12320; establish a first profile by inputting first profile parameters including a first performance, a first role, a first position, a first location, a first event, the like, or any combination thereof relative to a first participant and / or a first event; and configure the software 12320 to adjust interaction parameters based on the input first profile parameters.

[0287] Technical variations may include, for example, adapting the camera 1231 and software 12320 to measure ambient light, motion, or both, such that the device 12000 may be adapted to alternate between a less activated state, a deactivated state, and an activated state based on the presence or absence of a minimum threshold for measuring ambient light, motion, or both.

[0288] The device 12000 includes a data transmission device 12400 adapted to interoperate with the electronic circuit 12300. The data transmission device 12400 may include at least one wireless transceiver, and may include one or more other wired and / or wireless communication devices or modules, such as with respect to Figure 3 Explained in more detail.

[0289] The device 120000 may include a positioning device 12500 adapted to generate positioning data for determining the position, orientation, movement, motion and / or perspective of the console 12010. The positioning device 12500 may also include and be referred to as a position measurement device. The positioning device 12500 may generate data about the relative position of the console device 12000, but does not "position" the device 12000, in the sense that a gimbal may "position" or a tripod may support the device in a fixed position. The positioning device 12500 may include a global positioning system (GPS) receiver and / or a GPS module, from which the "absolute" position relative to the earth can be measured and calculated. In some embodiments, the importance of the positioning device 12500 to the device 12000 may be more related to the relative position of the device 12000 within the system 10000 than to the absolute position of the device 12000. The exemplary positioning device 12500 may include a gyroscope, an accelerometer, an inertial motion unit (IMU) 12510, and / or an infrared (IR) sensor 12520 or may be adapted to detect (refer to Figure 5 ) a local, stationary beacon (e.g., a wireless transceiver device 13000) or other tracking device (e.g., a wireless-enabled fixture device 11000) that transmits a signal suitable for triangulation of the position of the console 12010 relative to other devices. In some embodiments, the sensor may include a sensor-transmitter pair (e.g., light detection and ranging (“LiDAR”) or laser detection and ranging (“LaDAR”)) for active distance determination. Alternatively, the software 12320 may be programmed to use machine vision and / or artificial intelligence (“AI”) to determine the position of the device 12000 (such as using triangulation or comparable AI calculations) to identify artifacts within the field of view captured by the camera 12319 in the video data (e.g., identifiable background objects such as a nurse's station).

[0290] refer to Figure 2 , Figure 2A method of using a fixture device 11000 (such as Figure 1A or Figure 1B Flowchart of an exemplary method 20000 for a device 11000 of a server 14000). The method 20000 may be adapted to perform a load configuration start detection 21000, a start response 22000 when an EMR application configuration 11333 is detected. For example, the start detection 21000 may include detecting an input button being activated (21100), detecting a command provided by a nurse on the console device 12000 (21200), detecting a position or movement of a clamp device (21300), or any combination thereof. Similarly, the start response 22000 may include using the console 12000 to update (22100) the status of the clamp device 11000 as activated within the server 14000, and may optionally include a speaker 11316 to play audio or an illumination device 11317 to display a light, such as to confirm activation. The start response 22000 may include using the console 12000 to display (22200) a warning when the start detection 21000 is detected, such as advising the first participant 12011 to activate the clamp device 11000 within the system 10000, or to activate the input button 11315 by closing the clamp 11120 on the umbilical cord of the newborn, or both. After initiating response 22000, method 20000 may be adapted to perform subsequent detection and responses 23000, such as detecting (23100) an update to the status of the clamp device 11000, displaying (23200) the updated status of the clamp device 11000 on the nurse's console 12000 (e.g., a warning if a low battery status is indicated, or a warning if a tamper detection status or a perimeter violation detection status is indicated), recording (23300) the status update as an interaction file in the EMR application 12334 and possibly in memory 11312 or EMR configuration 11333, and in response thereto, utilizing system 10000 to respond (23400) to the updated status or other response, such as by a nurse on the console 12000 or from the EMR application 12334. For example, a response to a warning if a low battery state is indicated may include replacing and / or recharging the clamp device 11000, while a response to an alert if a tamper detection state or a perimeter violation detection state is indicated may include sending a signal to electronically lock a perimeter door near the last recorded position of the clamp device 11000.

[0291] The method configuration 20000 may be configured to enable the software 12320 and the hardware 12310 to be further adapted to enable the power user 12021 to set the method configuration 20000 to select an end detection 24000 and an end response 25000 to the end detection 24000, wherein the method 20000 is further adapted to execute the end response 25000 upon detecting the end detection 24000. The end detection 24000 may include, for example, detecting an end (24100), such as the end of use of the clamp device 11000 when a newborn is discharged from the hospital; detecting an input (24200), such as the lock input button 11315 is released or the anti-tamper switch 11315 is activated when the clamp device 11000 is authorized to be opened and removed by a nurse, or both, so as to interrupt the tracking of the clamp device 11000. End detection 24000 may initiate an end response 25000 that ends the interaction of method 20000 of the clamp device 11000 with the system 10000 via the nurse console 12000 used by the first participant 12011. End response 25000 may include confirming (25100) the end in the EMR application 12334, such as sounding a deactivation beep to the first participant using speaker 11316 and / or 12313, or illuminating a deactivation lighting pattern using light 11317 and / or displaying a deactivation confirmation screen using display 12319. End response 25000 may further include updating, displaying, and recording (25200) the end state of the interaction as an interaction file as a computer-readable file on a computer-readable storage medium, such as EMR file 12334 in the EMR application 12336. The end response 25000 may also include connecting to a network, connecting to the EMR server 14000 or platform, and sending an alert to the power user 12021 to notify the power user 12021 that the participant 12011 has ended the interaction with the device 11000, and that the files 12334 of the interaction are available on the EMR server 14000 and / or stored in the console 12010.

[0292] refer to Figure 3 , Figure 3A block diagram of an exemplary embodiment 30000 of the present invention specifically for a data transfer apparatus 13000 is shown. The data transfer apparatus 30000 may be adapted to enable data transfer 31000 between a remote device 32000, such as a fixture device 11000 or an EMR console 12000, and a separate computing device 33000, such as a server including an auxiliary processing unit ("APU") 33010 or an EMR platform, for providing additional computing, video capture, video processing, image capture, image processing, data processing, communication, networking, and / or storage capabilities, wherein the data transfer apparatus 30000 may be adapted to enable the remote device 32000 to communicate with the separate computing device 32000 and transfer electronic data 31100 thereto, and enable the separate computing device 33000 to communicate with the remote device 32000 and transfer electronic data 31100 thereto. For example, in situations where multiple remote devices 32000 may attempt to communicate with a backend server simultaneously from the same general location (such as when users are distributed throughout rooms in a hospital), the computing device 33000 may act as an intermediate buffer, data aggregator, network bus, cache, or router to facilitate simultaneous high-capacity, high-data communications between multiple local consoles and the backend system server over the Internet. In some embodiments, the computing device 33000 may include components of a matrix of wireless transceiver devices 13000, each of which may be adapted to function as a beacon, location reader, peripheral port, data bridge, sub-router, data communication range extender, or a combination thereof.

[0293] The data transfer device 30000 may include, for example, a cable 30010, a wireless transceiver 30020, or both, possibly in combination with a wireless transceiver 33012 of the APU 33010, wherein the remote device 32000 may be enabled via the data transfer module 32020 to transmit to or receive from a separate computing device 33000, for example, a separate device software application 31110 and an EMR file 31120. The cable may include, for example, an Ethernet cable, an RJ45 cable, a coaxial cable, a USB cable, a Thunderbolt cable, a lightning cable, an HDMI cable, a VGA cable, a MIDI cable, etc. The wireless transceivers 30020, 33012 may include, for example, a Wi-Fi transceiver, a WiLAN transceiver, a near field communication (NFC) transceiver, a Bluetooth transceiver, or a Bluetooth low energy (BLE) transceiver; a 1G, 2G, 3G, 4G, or 5G cellular transceiver; a long term evolution (LTE) cellular transceiver, etc. Likewise, a separate computing device 33000 may be enabled to transmit or receive, for example, a settings database 31130 and an image file 31140 to or from a remote device 32000. For example, the applications 31110 may include an EMR application 31150, and the settings 31130 may include an EMR application configuration 31160.

[0294] Additionally, when the cable 30010 is coupled to the external power source 34000, the cable 30010 can be adapted to enable the remote device 32000 to recharge the internal power source 32100. The internal power source 32100 can include, for example, a rechargeable battery, a non-rechargeable battery, a battery backup, an uninterruptible power supply ("UPS"), a solar generator, a photovoltaic cell or battery array, and the like.

[0295] Refer to the following Figures 4 to 5, an exemplary embodiment of the present invention may include a system for interactive communications adapted for professional use by a participant in a hospital or other healthcare environment, wherein the system includes an EMR platform, and possibly an integrated EMR server platform, a networked EMR data server, and / or a third-party EMR server, platform or service, and a device adapted to interact with the EMR platform and the EMR platform. The system may further include a separate device software application running on at least one separate computing device, wherein the separate device software application may be adapted to enable the separate computing device to: interact with the fixture device 11000, the EMR console 12000 and / or the wireless transceiver device 14000; modify the settings of the fixture device 11000, the EMR console 12000 and / or the wireless transceiver device 14000; upload data and files to the fixture device 11000, the EMR console 12000 and / or the wireless transceiver device 14000; download data and files from the fixture device 11000, the EMR console 12000 and / or the wireless transceiver device 14000; and control the features and functions of the fixture device 11000, the EMR console 12000 and / or the wireless transceiver device 14000.

[0296] The system may further include a remote computing network and a user account platform, the user account platform being accessible via the remote computing network and being adapted to communicate with the EMR platform, the fixture device, and the EMR console, and to transmit electronic data to and from the EMR platform, the fixture device and the EMR console being adapted to communicate with and transmit electronic data to and from the separate computing devices, and being adapted to enable the fixture device and / or the EMR console to communicate with and transmit electronic data to and from the separate computing devices via the remote computing network. The system may further include a user account accessible via the user account platform, the user account enabling the power user to log into the user account to remotely manage, view, and share data and settings of the EMR console and the user account on the EMR platform, available in the user account via the remote computing network, or because the data and settings have been uploaded to the user account platform, or because the EMR console communicates with the user account platform via the remote computing network while the power user accesses the user account platform and logs into the user account. In some embodiments, the user account may be adapted to enable the power user to set an alert option to cause an alert to be generated and sent to a separate computing device if an interaction with the first participant occurs and notification of the interaction has been communicated from the EMR console and the user account platform via the remote computing network. The user account may also be adapted to enable the power user to email, upload, download, otherwise electronically share, or any combination thereof, an EMR application, EMR application configuration, or other data file, such as an interaction file that is a record of the first participant's interaction with the EMR console.

[0297] The system may further include an EMR application configuration data file stored on a remote computing network and downloadable from a user account platform to a separate computing device and an EMR console, wherein the EMR configuration data file is adapted to enable the EMR console to add further features, perform additional functions, or both. The EMR configuration may include, for example, details related to performance or experience, such as maps (e.g., ariel maps, road maps, terrain maps, resource maps, route maps, perspective maps, plan maps, viewpoint maps, etc.), user interface ("UI") utilities (e.g., switching points, display details, switching profiles, account synchronization, etc.), terrain (e.g., hospital, parking lot, city, town, etc.), tools (e.g., clamping cutting tools, vehicles, drug units or types, nutrition units or types, etc.), capabilities (e.g., apply, attach, cut, remove, etc.), identities (e.g., nurse, doctor, patient, newborn, pregnant, postpartum mother, father, etc.), and communication utilities (e.g., electronic medical record (EMR) interface, social media connection, message feed, etc.).

[0298] Users of the EMR platform may include, for example, nurses, doctors, patients, consumers, producers, performers, enterprises, developers, administrators, etc. or combinations thereof. Users may create and / or distribute configurations, or both, by using a user-based creation and / or distribution platform for configuration. Each configuration may be a software code in a configuration file, which may include, for example, a settings file, a configuration file, a profile file, a small program file, an application file, a plug-in file, an application programming interface ("API") file, an executable file, a library file, an image file, a video file, a text file, a database file, a metadata file, and a message file. Producer users may use, for example, programming in a coding language (such as JavaScript and HTML) to develop software codes for configuration files, including open source code or object-oriented code compilation. The software code will be adapted to be compatible with and executable by the software of a console (e.g., an iPhone smart phone), a compatible video may be displayed on the console, and the configuration will be used with or within the console.

[0299] refer to Figure 4 , Figure 4 A diagram of an exemplary computer environment for use with systems and methods according to embodiments of the present invention is shown according to aspects of the present invention. Figure 4 A schematic diagram of an exemplary computer environment 40000 for creating, receiving, sending, exchanging, updating, and processing data according to an embodiment of the present invention is shown.

[0300] In the depicted embodiment, computer environment 40000 includes, among other things, an EMR data system 41000, a network 42000, a connection 43000, and at least one computing device 44000, such as a computing device smart device 44100, a mobile smart phone 44200, and a tablet 44300. Data system 41000 may include an EMR console device 41100 and a supporting device 41200 for use in an EMR platform, which may have its own integrated media server and / or service, or may be connected to a third-party EMR server and / or system 45000 for data and media content, such as for a hospital. Network 42000 may be connected to EMR data system 45000, which accesses an EMR console data account 45100 to transfer EMR console account data 45110. Computing devices 44100, 44200, and 44300 are connected to network 42000 via connection 43000, which may be any form of network connection known in the art or yet to be invented. Connection 43000 may include, but is not limited to, telephone lines (e.g., xDSL, T1, dedicated lines, etc.), cable lines, power lines, wireless transmissions, etc. Computing devices 44100, 44200, and 44300 include any necessary equipment known in the art (e.g., modems, routers, etc.) to facilitate such communications with network 42000. EMR data system 41000 may also be connected to network 42000 using one of the aforementioned methods or other such methods known in the art.

[0301] Use as shown in Figure 1 to Figure 5 , a user may access the computer environment 40000 via a computing device (such as computing device 44000) connected to the network 42000. The computing device 44000 may include an auxiliary processing unit ("APU") 33010, which may act as an intermediate computing device used between the EMR console device 41100, the fixture device 41200, and the EMR data system 41000. Such a computing device may be, for example, a beacon, a location reader, a peripheral port, a data bridge, a sub-router, a data communication range extender, or a combination thereof, possibly as a commercial embodiment of the APU 33010, or alternatively a personal private computer, an Internet coffee machine, a reader matrix, a computerized portable electronic device (e.g., a laptop, a tablet, a personal data assistant, a cellular phone, etc.), etc. For example, a smartphone 44200 or tablet 44300 may act as an APU 33010 that acts as a communication bridge for the fixture device 41200 by providing a “hotspot” to allow the fixture device 41200 to connect to the server 42000 using the smartphone's 44200 network connection.

[0302] Use Figure 1 to Figure 5 In the apparatus, systems, and methods depicted in the present disclosure, such user access may include downloading data and / or uploading data (e.g., information in electronic form) from computing devices 44100, 44200, and 44300 to an EMR data system 41000 (e.g., a server, mainframe, computer, etc.) via a network 42000, wherein the EMR data system 41000 is typically provided and / or managed by the hospital entity implementing the process or its affiliates, subcontractors, etc.

[0303] Although the systems and methods disclosed herein have focused on embodiments in which a user access initiates a process, those skilled in the art will readily appreciate that such systems and methods may be equally applicable to other scenarios in which a process is not initiated by a user, and in which the process is performed under the control of the EMR data system 41000, which may initiate the EMR process according to settings or parameters, such as at the start of an event, e.g., a tamper alarm, a removal or perimeter warning, a low battery warning, etc. For example, the EMR data system 41000 may push content to a user when the user arrives at or connects from a specified location, wherein the content is associated with the specified location, such as a crib for a particular newborn, or is associated with a topic or theme related to the specified location, such as medication for a particular newborn.

[0304] refer to Figure 5 , Figure 5 A block diagram of an exemplary system and an exemplary set of databases according to aspects of the present invention is shown, the exemplary set of databases being used within an exemplary computer environment, the exemplary databases being used with systems and methods according to embodiments of the present invention. In addition, Figure 5 An exemplary set of databases, libraries, or data tables for use with an exemplary computer environment according to aspects of the present invention are shown. Figure 5 It is used to allow the user of the system 50000 to perform the operations related to FIG. 1 to FIG. Figure 4 An exemplary computing system environment for the described methods.

[0305] The depicted computing system environment is only one example of a suitable computing environment and is not intended to suggest any limitation on the scope of use or functionality. In addition to the customized EMR device 51010 and the new fixture device as tracking device 55000, many other general or special computing devices, system environments, or configurations may be used within appropriate application-specific customizations. Examples of well-known computing systems, environments, and / or configurations that may be suitable for use include, but are not limited to: a personal computer ("PC"), a server computer, a handheld or laptop device, a multiprocessor system, a microprocessor-based system, a network PC, a minicomputer, a mainframe computer, a cellular phone, a smart phone, a tablet computer, an embedded system, a distributed computing environment including any of the above systems or devices, and the like.

[0306] Computer executable instructions, such as program modules executed by a computer, may be used. Typically, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. Distributed computing environments may be used in which tasks are performed by remote processing devices linked through a communication network or other data transmission medium. In a distributed computing environment, program modules and other data may be located in local and remote computer storage media including memory storage devices.

[0307] Figure 5 An exemplary system 50000 for implementing an embodiment of the present invention is depicted. The exemplary system includes, among other things, one or more computing devices 51000, a network 52000, and at least one server 53000 that interface with each other via the network 52000 and access at least one database 54000 to track at least one fixture device as a tracking device 55000, such as using at least one reader device 55100, such as in a matrix of reader devices 55010 placed throughout a hospital. The computing device 51000 may include a console device 12000, an EMR console 32000, an EMR device 51010, an auxiliary processing unit 33010 of the device 51010, and / or an EMR device 51010 having an auxiliary processing unit 3301 connected to the EMR console 32000, such as shown in FIGS. 1 to 3. Figure 3 In its most basic configuration, the computing device 51000 includes at least one processing unit, a processor 51100, and at least one memory unit 51200. Depending on the exact configuration and type of the computing device, the memory 51200 may be volatile (such as random access memory ("RAM")), non-volatile (such as read-only memory ("ROM"), solid-state drive ("SSD"), flash memory, etc.), or some combination of the two. Figure 5A basic configuration is shown in FIG51 by non-volatile memory 51300. Except as described herein, computing device 51000 can be any web-enabled handheld device (e.g., a cellular phone, a smart phone, etc.) or a personal computer, including those operating via Android, Apple, and / or Windows mobile or non-mobile operating systems.

[0308] The computing device 51000 may have additional features and / or functionality. For example, the computing device 51000 may include additional storage (removable and / or non-removable), including but not limited to magnetic or optical disks or tapes, thumb drives, and external hard drives where applicable. Such additional storage may be stored on a computer or computer. Figure 5 The example is shown by removable storage 51400 and non-removable storage 51500.

[0309] The computing device 51000 typically includes or is provided with various computer-readable media. Computer-readable media can be any available media that can be accessed by the computing device 51000, and includes volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer-readable media may include computer storage media and communication media.

[0310] Computer storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Storage 51200, removable storage 51400 and non-removable storage 51500 are all examples of computer storage media. Computer storage media include, but are not limited to, RAM, ROM, electrically erasable programmable read-only memory ("EEPROM"), flash memory or other memory technology, CD-ROM, digital versatile disk ("DVD") or other optical storage, cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by the computing device 51000. If applicable, any such computer storage media can be part of the computing device 51000.

[0311] The computing device 51000 may also include a communication connection 51600 that allows the device to communicate with other devices. Such a communication connection 51600 is an example of a communication medium. Communication media typically embody computer-readable instructions, data structures, program modules, and / or other data in a modulated data signal (such as a carrier wave or other transmission mechanism), and include any information delivery media. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed in a manner that encodes the information in the signal. By way of example and not limitation, communication media include wired media (such as a wired network or a direct wired connection) and wireless media (such as acoustic, radio frequency ("RF"), infrared, and other wireless media). The term computer-readable media as used herein includes both storage media and communication media.

[0312] The computing device 51000 may also have (multiple) input devices 51700, such as a keyboard, a mouse, a pen, a camera, a light sensor, a motion sensor, an infrared ("IR") sensor, an accelerometer, an inertial motion unit ("IMU"), a voice input device, a touch input device, and the like. Output devices 51800 may also be included, such as a display, a speaker, an LED light, a printer, and the like. Some input devices 51700 may be considered output devices 51800 for other components, such as a camera that provides a video feed or a sensor that provides data about sensed activity. All of these devices are well known to those skilled in the art and, therefore, need not be discussed in detail herein unless provided.

[0313] It is noteworthy that computing device 51000 may be one of a plurality of computing devices 51000 interconnected by network 52000. As can be appreciated, network 52000 may be any suitable network, and each computing device 51000 may be connected to the network via connection 51600 in any suitable manner. In some examples, each computing device 51000 may communicate only with server 53000, while in other examples, computing device 51000 may communicate with one or more of the other computing devices 51000 in network 52000 in any suitable manner. For example, network 52000 may be a wired network, a wireless network, or a combination thereof within an organization or home, and may include direct or indirect coupling to an external network (such as the Internet, etc.). Similarly, network 52000 may be such an external network.

[0314] Computing device 51000 may be connected to server 53000 via such an internal or external network. Server 53000 may, for example, act as an EMR platform, a media server, a service or platform, or both. Figure 5The computing device 51000 is depicted as being located near the server 53000, but this depiction is not intended to define any geographic boundaries. For example, when the network 52000 is the Internet, the computing device may have any accessible physical location. For example, the computing device may be a tablet, a cellular phone, a smart phone, a personal computer, etc. located in any user's office, home, or other location. Alternatively, the computing device may be located near the server 53000 without departing from its range. Furthermore, although Figure 5 Computing device 51000 is depicted coupled to server 53000 via network 52000 , but the computing device may be coupled to server 53000 via any other compatible network including, but not limited to, an intranet, a local area network, or the like.

[0315] The system may use a standard client-server technology architecture that allows users of the system to access information stored in a relational database via a customized user interface. The application may be hosted on a server, such as server 53000, which may be accessed via the Internet using a publicly addressable uniform resource locator ("URL"). For example, a user may access the system using any web-enabled device equipped with a web browser. Communication between software components and subsystems is accomplished through a combination of direct function calls, publish and subscribe mechanisms, stored procedures, and direct SQL queries.

[0316] In some embodiments, for example, server 53000 may be provided as a service, such as via Amazon Web Services ("AWS"), or as a dedicated standalone service, such as the Edge R200 server manufactured by Dell, however, alternative servers may be substituted without departing from the scope of the present invention. System 50000 and / or server 53000 utilize the PHP scripting language to implement the processes described in detail herein. However, alternative scripting languages ​​may be utilized without departing from the scope of the present invention.

[0317] Exemplary embodiments of the present invention may utilize, for example, a Linux variant messaging subsystem. However, alternative messaging subsystems may be substituted, including but not limited to the Windows Communication Foundation ("WCF") messaging subsystem of the Microsoft Windows operating system using the .NET Framework 3.0 programming interface.

[0318] Moreover, in the depicted embodiment, computing device 51000 may interact with server 53000 via a Transmission Control Protocol / Internet Protocol ("TCP / IP") communications protocol; however, other communications protocols may be substituted.

[0319] The computing devices 51000 may be equipped with one or more web browsers to allow them to interact with the servers 53000 via the Hypertext Transfer Protocol ("HTTP") and / or secure versions (e.g., "https") of associated uniform resource locators ("URLs"). HTTP is used as a request-response protocol in client-server computing. For example, a web browser operating on the computing device 51000 may execute a client application that allows it to interact with an application executed by the server 53000. The client application submits an HTTP request message to the server. The server 53000, which provides resources such as HTML files and other content or performs other functions on behalf of the client application, returns a response message to the client application upon request. The response typically contains completion status information about the request as well as the requested content. However, alternative methods of computing device / server communication may be substituted without departing from its scope.

[0320] In the exemplary system 50000, the server 53000 includes: Figure 5 One or more databases 54000 are shown, which may include multiple libraries or database tables, including but not limited to template, user, event, memory, time, map, utility, user upload, management information, transaction, status, tracking, and / or location database tables, such as 54100 to 54600. As can be appreciated, (one or more) databases 54000 can be any suitable database capable of storing data, and they can be included in or connected to server 53000 or any multiple servers similar to 53000 in any suitable manner.

[0321] exist Figure 5 In the exemplary embodiment of the invention depicted, database 54000 may be a structured query language ("SQL") database with a relational database management system, i.e., MySQL, as is known and used in the art. Database 54000 may reside within server 53000. However, other databases may be substituted without departing from the scope of the invention, including but not limited to PostgreSQL, SQL Server 2008 MySQL, and Oracle database, and such database can be inside or outside the server 53000.

[0322] The various techniques described herein may be implemented in conjunction with hardware or software or, as appropriate, with a combination of both. Thus, the methods and apparatus of the presently disclosed subject matter, or certain aspects or portions thereof, may take the form of program code (i.e., instructions, scripts, etc.) implemented in a tangible medium (e.g., a floppy disk, a CD-ROM, a hard drive, or any other machine-readable storage medium), wherein, when the program code is loaded into a machine (e.g., a computer) and executed by the machine, the machine becomes an apparatus for practicing the presently disclosed subject matter.

[0323] In the case where the program code is executed on a programmable computer, the interface unit generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device. One or more programs can implement or utilize the processes described in conjunction with the disclosed subject matter (e.g., by using an application programming interface ("API"), reusable controls, etc.). Such programs can be implemented in high-level procedural or object-oriented programming languages ​​to communicate with the computer system. However, if necessary, the program can be implemented in assembly or machine language. In any case, the language can be a compiled or interpreted language and combined with a hardware implementation.

[0324] Although exemplary embodiments may refer to utilizing aspects of the presently disclosed subject matter in the context of one or more separate computer systems, the subject matter is not limited thereto, but may be implemented in conjunction with any computing environment, such as system 50000 or distributed computing environment 40000. Still further, aspects of the presently disclosed subject matter may be implemented in or across multiple processing chips or devices, and similarly, storage may be created on multiple devices in system 50000. Such devices may include, for example, private computers, network servers, and handheld devices (e.g., cell phones, tablet computers, smart phones, etc.).

[0325] In an exemplary embodiment, server 53000 and its associated database are programmed to perform a number of processes, including those described in more detail in FIGS. 1 to 3. Figure 4 Those processes shown in .

[0326] Methods according to aspects of the invention include, for example, a method for interactive communication adapted to track electronic medical records, including those of a fixture device, wherein the method includes providing a device, such as a fixture device 11000 and / or a console device 12000, adapted to interact with a participant (such as a nurse participant 12011); configuring the device to interact with the participant; enabling the device to interact with the participant; and electronically capturing in the device state data, state data, or both of the interaction of the device with the participant. Other embodiments of the method may include performing the same as in FIGS. 1 to 13. Figure 5 Actions associated with the functionality described in, such as using fixture device 11000 with EMR console device 12000, within computing environment 40000, and within system 10000 and / or 50000.

[0327] refer to Figure 6 , Figure 6 A block diagram of an exemplary embodiment of a method 60000 of using an exemplary EMR system according to aspects of the present invention is shown. Figure 6In the method 60000 depicted in , the AR system may perform a state capture and position detection step 61000 at the device. The state capture and position detection step 61000 may include, for example, detecting 61100 an input (such as a switch or button press) to activate the device; detecting 61200 a state of the device captured or generated by a console device, such as detecting the state during attachment of the clamp device to the umbilical cord of a newborn; and detecting a position or movement 61300 to generate positioning data and / or indicate a location within the hospital where the clamp device is located or is being moved or manipulated by a user. The EMR system may perform a step 62000 of sending a position ping signal output at the clamp device, which may be received at the console device or wireless transceiver device and sent to a server, for example, via an auxiliary processor unit. The transmitting step 62000 may include: sending 62100 the location ping signal reception data from the signal reader to the server, possibly via an auxiliary processor unit, for combination with the EMR file of the newborn; and sending 62200 the clamping state data feed from the clamp device to the server via the reader or auxiliary processor unit; for location calculation and determination of an appropriate EMR response. The EMR system may perform the server calculation of step 63000 and the response to the sending step 62000 at the server. The calculation and response step 63000 may include determining 63100 the location (e.g., in the nursery, in the mother's room, etc.) and / or the state (e.g., operational, activated, low battery, etc.) of the clamp device within the hospital; calculating 63200 the corresponding location interpretation and response (e.g., the clamp device is in an authorized position, so no action is required; the clamp device is moving from the authorized position toward the exit, so a warning and lock is required; the clamp device is not in an authorized position, so a possible outreach alarm is required; etc.) and / or the state interpretation and response (e.g., operational state, so no action is required; low battery state, so replacement or recharging is required; no longer operational or deactivated, so a warning of a possible abduction event is required), and sending 63300 the response to the console device. The EMR system may perform a step 64000 of receiving and combining responses from the server at the console device. The receiving and combining of the response step 64000 may include receiving 64100 the location and state updates and responses, and combining 64200 the location updates, state updates, and associated responses in the corresponding EMR file for the newborn. The EMR system may perform step 65000 at a console device that receives and displays the updated and combined data. The receive and display EMR data step 6500 may include: receiving 65100 a combined data feed including the determined position, calculated position interpretation, calculated position response, determined state, calculated state interpretation, calculated state response of the fixture device; and displaying 65200 the combined data feed on a display of the console device.

[0328] Reference Figure 7 , Figure 7 A conceptual block diagram illustrating exemplary system functionality 70000 operational flow within a system 70010 and method according to exemplary embodiments of the present invention, in accordance with aspects of the present invention. Figure 7 The embodiments of the present invention describe exemplary embodiments of the system and do not limit the present invention as a whole. The depicted system functionality 70000 can be conceptually divided into server functionality 71000 of a server 71010, console or auxiliary processing unit (APU) functionality 72000 of a console or APU 72010, and fixture device tag functionality 73000 of a wireless tag 73010 of a fixture device. The system functionality 70000 can be conceptually divided into server output, console or APU input functionality 70100; console or APU output, tag input functionality 70200; tag output, console or APU input functionality 70300; and console or APU output, server input functionality 70400. In the embodiments depicted herein, the APU 72010 may be a wireless transceiver device 13000, such as a tag reader in a tag reader matrix distributed throughout a hospital, communicating with a server 71010, and the console 72010 may be a smart phone running an application that serves as a nurse console device 12000 that communicates with the server 71010.

[0329] At a high conceptual level, the data flow may be represented by server output, console or APU input function 70100; console or APU output, tag input function 70200; tag output, console or APU input function 70300; and console or APU output, server input function 70400. For example, server 71010 may connect to console 72010 using server output, console input function 70100 to push patient-based EMR data to console 72010. Console 72010 may then transmit some patient-based EMR data to tag 73010 to initiate activation and state capture of tag 73010 using console output, tag input function 70200. For location data and state data to be combined with the EMR content received from server 71010, tag 73010 may send the location data and state data back to console 72010 using tag output, console input function 70300. The console 72010 may transmit some positioning data and / or status data to the server 71010 using the console output, server input function 70400. For example, the tag output console input function 70300 may include the tag 73010 generating low battery status data that is transmitted to the console 72010. The APU 72010 may receive the tag positioning ping signal as a tag output, APU input function 70300, and send the positioning ping data to the server 71010 as an APU output, server input function 70400 for the server 71010 to generate the positioning data for the tag. As the server function 71000, the server 71010 may use the position data and status data to generate an appropriate interpretation and response to the position data and status data, including the timing of the position data or status data related to an event in the EMR data (e.g., the scheduled discharge of a newborn from the hospital), and send a response to the console 72010. As console function 72000, console 72010 can combine the location interpretation, location response, status interpretation, and status response with the EMR data to create and display an updated EMR data feed, and possibly send the updated data feed to tag 73010, such as if tag 73010 is to be deactivated by an authorized user. If tag 73010 is updated, tag function 73000 includes storing the updated data. If console 72010 includes a display, console function 72000 can include displaying the EMR data on the display of the console for viewing by the user.

[0330] refer to Figure 8 , Figure 8 A conceptual block diagram illustrating exemplary system functionality 80000 operational flow within a system 80010 and method according to exemplary embodiments of the present invention, in accordance with aspects of the present invention. Figure 8The embodiments of the present invention describe exemplary embodiments of the system and do not limit the present invention as a whole. The depicted system functionality 80000 can be conceptually divided into server functionality 81000 of a server 81010, auxiliary processing unit functionality 82000 of an auxiliary processing unit ("APU") 82010, and tag or console functionality 83000 of a tag or console 83010. The system functionality 80000 can be conceptually divided into server output, APU input functionality 80100; APU output, console or tag input functionality 80200; tag or console output, APU input functionality 80300; and APU output, server input functionality 80400. In the embodiments depicted herein, the APU 82010 can be a separate computing device, such as a tablet, laptop, or desktop computer; or a wireless transceiver device 13000, such as in a matrix of wireless routers, wireless range extenders, and / or wireless tag readers distributed throughout a hospital; or an intermediate buffer server that communicates with the wireless tag 83010 of the fixture device 11000, and / or with a console 83010, which can be a nurse console device 12010 that communicates with the server 81010 at least in part via the APU 82010.

[0331] At a high conceptual level, the data flow may be represented by server output, APU input functionality 80100; APU output, tag or console input functionality 80200; tag or console output, APU input functionality 80300; and APU output, server input functionality 80400. For example, the server 81010 may connect to the APU 82010 using the server output APU input functionality 80100 to push patient-based EMR data to the APU 82010. The APU 82010 may then transmit the patient-based EMR data to the console 83010 to update the EMR data displayed by the console 83010 using the APU output, console input functionality 80200. The console 83010 may send the fixture device status data back to the APU 82010 using the console output, APU input functionality 80300 for the status data to be forwarded by the APU 82010 to the server 81010 and combined with other EMR data once received by the server 81010. The APU 82010 may communicate data to the server 81010 using the APU output, server input function 80400. For example, the console output APU input function 80300 may include the console 83010 generating tag activation status data that is communicated to the APU 82010. The tag 83010 generates location ping signal data and status data that the tag 83010 may send to the APU 82010 as the tag output APU input function 80300. The APU 82010 may communicate the location ping signal data and status data to the server 81010 as the APU output, server input function 80400. As a server function 81000, the server 81010 may use the position data and / or status data relative to other EMR data to generate appropriate interpretations and responses to the position data and status data and the timing of the position data and status data relative to other EMR data, and the server 81010 may send the interpretation and response data to the APU 82010 to be forwarded to and displayed on the console 83010. As a potential APU function 82000, the APU 82010 may combine the interpretation and response data with the EMR data to create an updated EMR data feed that is sent to the console 83010. As a console function 83000, the console 83010 may display the updated EMR data feed. If the APU 82010 also includes a display, the APU function 82000 may include also displaying the updated EMR data on the display of the APU, such as for detecting what the user is viewing on the console 83010. For example, APU 82010 may include a tag reader and a tablet computer, wherein the tablet computer displays an image of a hospital floor plan with flashing beacon dots indicating the approximate location of wireless tags detected on the hospital floor.

[0332] As presented differently, the tag or console functionality 83000 may include the tag or console 83010 generating EMR data (such as status data or position data of a fixture device) and sending the EMR data to the auxiliary processing unit 82010. The auxiliary processing unit functionality 82000 may include the APU 82010 receiving the EMR data from the tag or console 83010 and communicating with the server 81010 to cause the server 81010 to perform the server functionality 81000, which includes: generating updated EMR data, the updated EMR data including appropriate interpretations of the updated EMR data and responses to the updated EMR data; and the timing of the updated EMR data relative to other EMR data; and sending the interpretations and responses from the server 81010 to the APU 82010. The APU functionality 82000 also includes the APU 82010 forwarding updated EMR data to a tag or console 83010, and possibly combining aspects of the EMR data with other EMR data or system data to create an APU-specific data feed (e.g., an animation of a flat image with beacon points indicating tag locations). The tag or console functionality 83000 includes a tag or console 83010 storing updated EMR data and possibly displaying the updated EMR data on a display of the console 83010 for viewing by a user (such as a nurse).

[0333] refer to 9A to 9D , 9A to 9D Various exemplary clamps 90000 according to aspects of the present invention are shown as part of an umbilical cord clamping device 11000 within a system 10000 for use in accordance with an exemplary embodiment of the present invention. Fig.9AAs shown, the clamp 90010 includes a hinge clamp having a hinge and a hinge cavity 90011, a first opposing row of teeth 90012, a second opposing row of teeth 90013, and a locking mechanism 90014 having a male portion 90015 and a female portion 90016. The hinge cavity is partially annular, forming an open partial ring when the clamp is open, and forming a closed ring when the clamp is closed. The hinge 90011 is adapted to align the first opposing row of teeth 90012 with the second opposing row of teeth, so that when the clamp 90010 is closed, the first opposing row of teeth 90012 are opposite and engaged, but do not hinder the second opposing row of teeth 90013. The hinge 90011 is also adapted to align the male portion 90015 and the female portion 90016 of the locking mechanism 90014 so that the male portion 90015 is opposed, inserted and engaged with the female portion 90016 when the clamp 90010 is closed. The female portion 90016 includes a cavity with an inner lip (not visible in the drawings) at the opening. The male portion 90015 is similar to two flexible, opposing flanges that can bend inward after being inserted into the female portion 90016, and then bend outward within the female portion 90016 to engage the inner lip. The umbilical cord of a newborn baby can be inserted between the first opposing row of teeth 90012 and the second opposing row of teeth 90013 and the clamp 90010 can be closed, compressing the umbilical cord between the rows 90012 and 90013, thereby preventing further bleeding from the umbilical cord and acting as a tourniquet to stop circulation to the end of the umbilical cord, causing the end to dry out and eventually fall off.

[0334] like Fig. 9B As shown, clamp 90020 comprises a variation of an articulated clamp in which the locking mechanism 90024 comprises a convex portion 90025 comprising a tapered plug adapted to compress and deform when inserted into a concave portion 90026 and to decompress and engage an inner lip to lock the mechanism 90024.

[0335] like Fig. 9CAs shown, the clamp 90030 comprises a variation of a hinged clamp in which the locking mechanism 90034 comprises a male portion 90035 comprising a flexible flange lip adapted to flex outwardly when inserted into a female portion 90036, and flex inwardly and engage the lip of the female portion 90036 to lock the mechanism 90034. If the male portion 90035 is separated from the female portion 90036, the locking mechanism 90034 can be reopened. The clamp 90030 is depicted in an open, unlocked position 90037, revealing a pin 90038 that can engage a button 90039. The button 90039 can comprise an electrical switch. The pin 90038 and button 90039 may include a tamper-proof switch that indicates possible tampering if the pin 90038 ceases to engage the button 90039 after the locking mechanism 90034 is closed (e.g., in the closed, locked position 90047), but is subsequently reopened.

[0336] like Fig.9D As shown, clamp 90040 comprises a variation of clamp 90030, which is depicted in a closed, locked position 90047. While clamps 90010, 90020, 90030, and 90040 are variations of hinged clamps, some clamps may omit the hinge and replace the hinge with a second locking mechanism such that the locking mechanisms are located on either side of opposing rows of teeth.

[0337] refer to FIG. 10A to FIG. 10E , FIG. 10A to FIG. 10E Depictions of wireless tags 100000 and special tags 100010 are shown from different viewpoints, according to aspects of the present invention, which may be used in exemplary devices within a system used in accordance with methods according to exemplary embodiments of the present invention. FIG. 10A to FIG. 10E The embodiment shows an exemplary proposed commercial embodiment of the system and does not limit the invention in general. Fig. 10A A top perspective side view of label 100010 is depicted; Fig. 10B A top perspective plan view of label 100010 is depicted; Fig. 10C A side view of label 100010 is depicted; Fig. 10D depicts a bottom perspective side view of label 100010; and Fig.10EDepicted is a top plan view of a tag 100010. The tag 100010 includes a hexagonal housing 100011 including a cylindrical post frame handle 100012 and a cylindrical post frame seat 100013, wherein the handle 100012 is depicted as having a button 100014 along the handle 100012. The handle 100012 is adapted to fit within, for example, a hinge cavity 90011 with the clamp 90010 in an open, unlocked position 90037 such that the seat 100013 and the hexagonal housing 100011 are wider than the hinge cavity 90037 and prevent the tag 100010 from being removed from the clamp in the closed, locked position 90047 without tampering with the clamp 90010. Closure of the clamp 90010 closes the annular ring of the hinge cavity 90037 and depresses the button 100014, thereby engaging the tamper-proof switch within the wireless tag 100010. In the event that the clamp 90010 is tampered with in a manner that moves the handle 100012 out of the hinge cavity 90037, the button 100014 can be moved out of the hinge cavity 90037 in a manner that the button 100014 is no longer depressed or engaged, thereby changing or interrupting the state of the tamper-proof switch as the case may be so that the system 10000 interprets the interrupt state change data as a possible tampering event that requires a response of a warning or alarm.

[0338] refer to Figures 11A-11D , Figures 11A-11D Depictions of other wireless tags 11000 and special tags 1110010 are shown from different perspectives, and according to various aspects of the present invention, these other wireless tags and special tags can be used in exemplary devices within a system used in accordance with methods according to exemplary embodiments of the present invention. Figures 11A-11D The embodiments show exemplary alternative embodiments of the system and do not limit the invention in general. Fig.11A A top perspective side view of label 1110010 is depicted; Fig. 11B Another top perspective side view of label 1110010 is depicted; Fig. 11C depicts a bottom perspective side view of label 1110010; and Fig.11DA top perspective plan view of a tag 1110010 is depicted. The tag 110010 includes a rectangular housing 110011 that includes a cylindrical frame handle 110012 and a cylindrical frame seat 110013. Although not depicted, the handle 110012 may have a button similar to the button 100014 along the handle 110012. The handle 110012 is adapted to be mounted within, for example, a hinge and hinge cavity 90011 with the clamp 90010 in an open, unlocked position 90037 such that the seat 110013 and rectangular housing 110011 are wider than the hinge cavity 90037 and prevent the tag 11010 from being removed from the clamp in the closed, locked position 90047 without tampering with the clamp 90010. Closure of the clamp 90010 closes the annular ring of the hinge and the hinge cavity 90037 and depresses the button, engaging the tamper-proof switch within the wireless tag 110010. In the event that the clamp 90010 is tampered with in a manner that moves the handle 100012 out of the hinge cavity 90037, the button can be moved out of the hinge cavity 90037 in a manner that the button is no longer depressed or engaged, changing or interrupting the state of the tamper-proof switch to allow the system 10000 to interpret the interruption state change data as a possible tampering event requiring a response of a warning or alarm, as the case may be.

[0339] refer to FIG. 12A to FIG. 12C , FIG. 12A to FIG. 12C Various switches 120000 and depictions of specific switches 120010, 120020, 120030 are shown from different perspectives, which switches can be used alone or in combination in exemplary devices within a system used by a method according to an exemplary embodiment of the present invention in accordance with various aspects of the present invention. FIG. 12A to FIG. 12C The embodiments illustrate exemplary potential commercial embodiments of a switch for a wireless-enabled tag using the wireless-enabled fixture device 11000 of the system 10000 and do not limit the present invention in general. Fig. 12A A switch 120010 is shown having a hinge 120011, a hinged lever 120012, and a depressible button 120013 adapted to be engaged to activate the switch when the lever 120012 is pressed to close the hinge 120011. Fig. 12B A switch 12020 is depicted having an exposed depressible button 120023 adapted to engage to activate the switch when the button 120023 is depressed. Fig. 12C Depicted is a switch 12030 having a compressible membrane printed circuit switch 120033 adapted to be engaged when the membrane switch 120033 is compressed to activate the switch.

[0340] These switches 120000 and variations thereof may be adapted as tamper-resistant switches for use in a fixture device 11000, such as with reference to Fig. 9C Button 90039 and Fig. 10D 14. For example, the button 90039 may include the button 120023 of the switch 12020 and be pressed by the pin 90038. For example, the locking mechanism 90014 is equipped with the switch 120010, wherein the rod 120012 acts as the male portion 90015 or is engaged by the male portion 90015 to press the button 120013 when the clamp 90010 is closed. For example, the button 100014 may include the button 120023 of the switch 12020 and be pressed by closing the hinge cavity 90011. For example, the membrane switch 120033 can be positioned between and aligned with the rows of teeth 90012, 90013, such that closing the clamp 90010 causes the rows of teeth 90012, 90013 to compress the membrane switch 120033, such as when the umbilical cord is positioned between the rows of teeth 90012, 90013, thereby engaging and activating the membrane switch 120033. For example, the membrane switch 120033 can be positioned around the stem 100012, 110012, such that closing the clamp 90010 causes the hinge cavity 90011 to compress the membrane switch 120033, thereby engaging and activating the membrane switch 120033. For example, the membrane switch 120033 can be positioned around the male portion 90015 and / or within the female portion 90016 of the locking mechanism 90014 such that closing the clamp 90010 causes the locking mechanism 90014 to compress the membrane switch 120033, thereby engaging and activating the membrane switch 120033.

[0341] The above description discloses exemplary embodiments of the present invention. Although the invention disclosed herein has been described by specific embodiments and applications thereof, a person skilled in the art may make various modifications and variations thereto without departing from the scope of the present invention as set forth in the claims. Modifications of the above disclosed apparatus and methods that fall within the scope of the claimed invention will be apparent to a person of ordinary skill in the art. Therefore, other embodiments may fall within the spirit and scope of the claimed invention as defined by the appended claims.

[0342] In the above description, many specific details are set forth in order to provide a more thorough understanding of embodiments of the present invention. However, it will be apparent to those of ordinary skill in the art that the present invention can be practiced without incorporating all aspects of the specific details described herein. All possible embodiments of the present invention are not set forth verbatim herein. Various combinations of aspects of the present invention may be formed to produce different embodiments falling within the scope of the claims below. In addition, in order not to obscure the present invention, the specific details well known to those of ordinary skill in the art are not described in detail. The reader should note that, although examples of the present invention are set forth herein, the full scope of the claims and any equivalents is to limit the limits and scope of protection of the present invention.

Claims

1. A wireless-enabled tag for use with an umbilical cord clamp, the tag comprising: Label device electronic circuit and hardware, the label device electronic circuit and hardware include: Tag device processor; a tag device memory, the tag device memory being coupled to the tag device processor; A tag device wireless data transmission module, wherein the tag device data transmission module is coupled to the tag device processor; A tag device wireless data transmission device, the tag device data transmission device is coupled to the tag device processor; and a label anti-tampering mechanism, the label anti-tampering mechanism being coupled to the label device processor; tag device electronic software, said device software being stored in said device electronic circuitry and hardware and being adapted to enable, drive and control said device electronic circuitry and hardware; a tag device power supply coupled to the device electronic circuitry and hardware and adapted to power the device electronic circuitry and hardware; and A tag device housing, the tag device housing comprising a tag device exterior and a tag device interior, the tag device interior accommodating the tag device software, the tag device power supply, and at least some of the tag device electronic circuits and hardware.

2. The label according to claim 1, wherein: The tag anti-tamper mechanism is a push button switch, which includes a button partially housed within the locking mechanism of the umbilical cord clamp; wherein the button is adapted to be partially exposed to the convex portion when the convex portion of the locking mechanism is placed in the concave portion of the locking mechanism; and wherein the button is adapted to be depressed when the convex portion enters and engages the concave portion of the locking mechanism when the umbilical cord clamp is closed and placed in a closed, locked position.

3. The label according to claim 1, wherein: The tag device comprises a hexagonal shell, which contains the tag device processor, the tag device memory, the tag device wireless data transmission module and the tag device wireless data transmission device.

4. The label according to claim 1, wherein: The tag device comprises a rectangular shell, which receives the tag device processor, the tag device memory, the tag device wireless data transmission module and the tag device wireless data transmission device.

5. The label according to claim 1, wherein: The fixture equipment framework further includes: The column handle; and Column support; wherein the column handle extends outwardly from the label portion of the label device housing at a proximal end; Wherein, the column support is located at the distal end of the column handle, and the distal end is located at the distal side of the proximal end and the distal side of the label part of the label device housing; wherein the column support is wider than the column handle; wherein the label portion is wider than the column handle; wherein the post handle is sized to fit tightly within the hinge cavity of the hinge of the umbilical clamp; wherein the post handle is adapted to be placed into the articulation cavity when the umbilical cord clamp is in an open, unlocked position; wherein the post handle is adapted to be fixed within the articulation cavity when the umbilical cord clamp is in a closed, locked position; wherein when the umbilical cord clamp is in the closed, locked position and when the post handle is secured within the hinge cavity, the post mount and the tag portion are positioned on opposite sides of the hinge; and Wherein, the post support and the label portion are both wider than the post handle, preventing the post handle from being removed from the hinge cavity when the umbilical cord clamp is in the closed locked position.

6. The label according to claim 5, wherein: The tag tamper-proof mechanism is positioned proximal to the post handle; is adapted to mate closely with the articulation cavity; is adapted to be engaged by the hinge when the umbilical cord clamp is closed and placed in the closed, locked position, when the articulation cavity is reduced; and is adapted to be activated, deactivated, triggered or tripped by an attempt to remove or dislodge the post handle from within the articulation cavity.

7. The label according to claim 6, wherein: The tag tamper-proof mechanism is a push button switch, which includes a button partially housed within the stem; wherein the button is adapted to be partially exposed to the hinge when the stem is placed in the hinge cavity; and wherein the button is adapted to be depressed when the umbilical cord clamp is closed and placed in the closed, locked position.

8. The label according to claim 7, wherein: The tag anti-tamper mechanism is an articulated lever switch, which includes an articulated lever partially housed within the post handle; wherein, when the post handle is placed in the articulation cavity, the articulated lever is adapted to be partially exposed to the hinge; and wherein the articulated lever is adapted to be pivoted and depressed when the umbilical cord clamp is closed and placed in the closed, locked position.

9. The label according to claim 7, wherein: The tag anti-tamper mechanism is a membrane switch, the membrane switch including a membrane printed circuit, the membrane printed circuit being at least partially positioned around an outer surface of the post handle; wherein the membrane printed circuit is adapted to contact the hinge when the post handle is placed in the hinge cavity; and wherein the membrane printed circuit is adapted to be compressed when the umbilical cord clamp is closed and placed in the closed, locked position.

10. The label according to claim 1, wherein: The tag anti-tamper mechanism is a membrane switch, the membrane switch including a membrane printed circuit, the membrane printed circuit being adapted to be at least partially positioned within the umbilical cord clamp; wherein the membrane printed circuit is adapted to contact the opposing multiple rows of teeth of the umbilical cord clamp when the umbilical cord is placed in the umbilical cord clamp and between the opposing multiple rows of teeth of the umbilical cord clamp; and wherein the membrane printed circuit is adapted to be compressed when the umbilical cord clamp is closed and placed in the closed, locked position.

11. A system adapted to monitor the position of and detect tampering with a wireless enabled umbilical cord clamp device, the system comprising: A server, the server comprising: Server electronic circuits and hardware, the server electronic circuits and hardware comprising: Server processors; a server memory coupled to the server processor; A server data transmission module, the server data transmission module is coupled to the server processor; a server data transmission device, the server data transmission device being coupled to the server processor; server electronic software stored in and adapted to enable, drive and control the server electronic circuitry and hardware; and a server power connection coupled to the server electronic circuitry and hardware and couplable to a server power supply; wherein the server is adapted to determine the location data and the status data based on receiving the location data and the status data from within the system, interpret the determination of the location data and the status data, determine a response to the interpretation of the location data and the status data, and communicate the response; a wireless transceiver, the wireless transceiver communicating with the server data transmission device and the server data transmission module; A wireless umbilical cord clamp device, the wireless umbilical cord clamp device comprising: Label device electronic circuit and hardware, the label device electronic circuit and hardware include: Tag device processor; a tag device memory, the tag device memory being coupled to the tag device processor; A tag device wireless data transmission module, wherein the tag device data transmission module is coupled to the tag device processor; A tag device wireless data transmission device, the tag device data transmission device is coupled to the tag device processor; and a tag anti-tamper switch, the tag anti-tamper switch coupled to the tag device processor; tag device electronic software, said device software being stored in said device electronic circuitry and hardware and being adapted to enable, drive and control said device electronic circuitry and hardware; a tag device power supply coupled to the device electronic circuitry and hardware and adapted to power the device electronic circuitry and hardware; and a tag device housing, the tag device housing comprising a tag device exterior and a tag device interior, the tag device interior housing the tag device software, the tag device power supply, and at least some of the tag device electronic circuits and hardware; wherein the label device exterior includes a clamp device frame, and the clamp device frame is adapted to be fixed adjacent to the umbilical cord when the umbilical cord of a newborn is clamped by the umbilical cord clamp; wherein the device electronic circuitry and hardware are adapted to operate as a wireless tag adapted to be wirelessly read by a wireless tag reader including the wireless transceiver; wherein the wireless tag reader is adapted to communicate to the server that manages location data and status data applicable to the wireless tag; and Wherein, the tag anti-tamper switch is fixed by the tag device housing, partially exposed to the outside of the tag device, coupled to the tag device electronic circuit within the interior, and is adapted to be activated, deactivated, triggered or tripped by attempting to tamper with the wireless tag or the umbilical clamp.

12. The system according to claim 12, wherein: The fixture equipment framework further comprises: The column handle; and Column support; wherein the column handle extends outwardly from the label portion of the label device housing at a proximal end; Wherein, the column support is located at the distal end of the column handle, and the distal end is located at the distal side of the proximal end and the distal side of the label part of the label device housing; wherein the column support is wider than the column handle; wherein the label portion is wider than the column handle; wherein the post handle is sized to fit tightly within the hinge cavity of the hinge of the umbilical clamp; wherein the post handle is adapted to be placed into the articulation cavity when the umbilical cord clamp is in an open, unlocked position; wherein the post handle is adapted to be fixed within the articulation cavity when the umbilical cord clamp is in a closed, locked position; wherein when the umbilical cord clamp is in the closed, locked position and when the post handle is secured within the hinge cavity, the post mount and the tag portion are positioned on opposite sides of the hinge; and Wherein, the post support and the label portion are both wider than the post handle, preventing the post handle from being removed from the hinge cavity when the umbilical cord clamp is in the closed locked position.

13. The system according to claim 13, wherein: The tag tamper switch is positioned proximal to the post handle; is adapted to mate closely with the articulation cavity; is adapted to be engaged by the hinge when the umbilical cord clamp is closed and placed in the closed, locked position, when the articulation cavity is reduced; and is adapted to be activated, deactivated, triggered or tripped by an attempt to remove or dislodge the post handle from within the articulation cavity.

14. The system according to claim 14, wherein: The tag tamper switch is a push button switch comprising a button partially housed within the post; wherein the button is adapted to be partially exposed to the hinge when the post is placed in the hinge cavity; and wherein the button is adapted to be depressed when the umbilical cord clamp is closed and placed in the closed, locked position.

15. A method adapted for monitoring the position of a wireless enabled umbilical cord clamp device and detecting tampering with the wireless enabled umbilical cord clamp device, the method comprising: wirelessly communicating data from the wireless-enabled umbilical clamp device, the clamp device being adapted to couple to and communicate with a local software application and a server; Wherein, the wireless umbilical cord clamp device includes: Label device electronic circuit and hardware, the label device electronic circuit and hardware include: Tag device processor; a tag device memory, the tag device memory being coupled to the tag device processor; A tag device wireless data transmission module, wherein the tag device data transmission module is coupled to the tag device processor; A tag device wireless data transmission device, the tag device data transmission device is coupled to the tag device processor; and a tag anti-tamper switch, the tag anti-tamper switch coupled to the tag device processor; tag device electronic software, said device software being stored in said device electronic circuitry and hardware and being adapted to enable, drive and control said device electronic circuitry and hardware; a tag device power supply coupled to the device electronic circuitry and hardware and adapted to power the device electronic circuitry and hardware; and a tag device housing, the tag device housing comprising a tag device exterior and a tag device interior, the tag device interior housing the tag device software, the tag device power supply, and at least some of the tag device electronic circuits and hardware; wherein the label device exterior includes a clamp device frame, and the clamp device frame is adapted to be fixed adjacent to the umbilical cord when the umbilical cord of a newborn is clamped by the umbilical cord clamp; wherein the device electronic circuitry and hardware are adapted to operate as a wireless tag adapted to be wirelessly read by a wireless tag reader including the wireless transceiver; wherein the wireless tag reader is adapted to communicate to the server that manages location data and status data applicable to the wireless tag; and wherein the tag tamper switch is secured by the tag device housing, partially exposed to the exterior of the tag device, coupled to the tag device electronic circuit within the interior, and adapted to be activated, deactivated, triggered, or tripped by an attempt to tamper with the wireless tag or the umbilical clamp; determining location data and status data of the wireless tag based on wireless communication data generated by the wireless tag and transmitted to the server; interpreting the location data and the status data of the wireless tag based on the determination made by the server; determining a response to the location data, the status data, or a combination thereof based on the interpretation by the server; and A response made by the server is communicated to a response recipient that has been selected as part of the response determination, and includes information regarding any immediate actions that need to be taken based on the interpretation made by the server.

16. The method according to claim 16, further comprising: communicating from said server to a console device; providing the server; Wherein, the server includes: Server electronic circuits and hardware, the server electronic circuits and hardware comprising: Server processors; a server memory coupled to the server processor; A server data transmission module, the server data transmission module is coupled to the server processor; a server data transmission device, the server data transmission device being coupled to the server processor; server electronic software stored in and adapted to enable, drive and control the server electronic circuitry and hardware; and a server power connection coupled to the server electronic circuitry and hardware and couplable to a server power supply; wherein the server is adapted to generate server-generated content including the determination, the interpretation, and the response based on the position data and the status data received from the fixture device; wherein the server is adapted to transmit EMR data to the console device when generating the server-generated content; receiving, at and by the server, the position data and the status data from the fixture device; generating the server-generated content at and by the server based on the location data and the state data; and The server-generated content is transmitted by the server to the console device, and the server-generated content is transmitted from the server to the console device.

17. The method according to claim 17, further comprising: wirelessly transmitting the position data and the status data from the fixture device to the console device; receiving, at the console device, the position data and the status data wirelessly transmitted from the device; transmitting the position data and the status data from the console device to the server; wirelessly transmitting the content generated by the server from the console device to the fixture device; as well as wirelessly receiving, at the fixture device, the server-generated content transmitted from the console device; Wherein, the console device comprises a console data transmission device, and the console data transmission device comprises a console wireless transceiver; and The server data transmission device communicates with a network wireless transceiver, and the network wireless transceiver communicates with the console wireless transceiver wirelessly.

18. The method according to claim 18, further comprising: transmitting the location data and the status data to the server using an intermediate computing device; receiving, using the intermediate computing device, content generated by the server from the server; as well as transmitting the server-generated content to the console device using the intermediate computing device; wherein the console includes a console processor, a console camera, a console display, a console memory, a console positioning device, a console data transfer module, a console data transfer device, a console software, a console housing, and a console power connection; wherein the intermediate computing device comprises another processor, another memory, another data transfer module, another data transfer device, other aspects of the device software, another housing, and another power connection; Wherein, the intermediate computing device can be referred to as an auxiliary processing unit; wherein the auxiliary processing unit is electronically coupled to the console; and Wherein the auxiliary processing unit is adapted to handle aspects of data transmission and data processing separately from the console when generating, transmitting and processing the server-generated content.

19. The system of claim 16, wherein: The fixture equipment framework further comprises: The column handle; and Column support; wherein the column handle extends outwardly from the label portion of the label device housing at a proximal end; Wherein, the column support is located at the distal end of the column handle, and the distal end is located at the distal side of the proximal end and the distal side of the label part of the label device housing; wherein the column support is wider than the column handle; wherein the label portion is wider than the column handle; wherein the post handle is sized to fit tightly within the hinge cavity of the hinge of the umbilical clamp; wherein the post handle is adapted to be placed into the articulation cavity when the umbilical cord clamp is in an open, unlocked position; wherein the post handle is adapted to be fixed within the articulation cavity when the umbilical cord clamp is in a closed, locked position; wherein when the umbilical cord clamp is in the closed, locked position and when the post handle is secured within the hinge cavity, the post mount and the tag portion are positioned on opposite sides of the hinge; and wherein the post support and the label portion are both wider than the post handle, preventing the post handle from being removed from the articulation cavity when the umbilical cord clamp is in the closed, locked position; wherein the tag tamper switch is positioned proximal to the post; adapted to mate with the articulation cavity; adapted to be engaged by the hinge when the umbilical cord clamp is closed and placed in the closed, locked position, when the articulation cavity is reduced; and adapted to be activated, deactivated, triggered or tripped by attempting to remove or dislodge the post from within the articulation cavity; and wherein the tag tamper switch is a push button switch comprising a button partially housed within the column handle; wherein the button is adapted to be partially exposed to the hinge when the column handle is placed in the hinge cavity; and wherein the button is adapted to be pressed when the umbilical cord clamp is closed and placed in the closed, locked position.

Images