UMBILICAL CORD CLAMP AND WIRELESS TAG SYSTEMS, METHODS, AND APPARATUS

Systems, methods, and apparatus are disclosed involving an electronic medical records (EMR) system and security platform adapted for the safety and security of newborn babies. An exemplary device comprises a wireless-enabled umbilical cord clamp apparatus having a wireless-enabled tag and a tamper-evident switch. An exemplary system further includes a server, a wireless transceiver, a console apparatus, and a wireless-enabled umbilical cord clamp apparatus. The wireless transceiver may act as a tag reader within a matrix of other tag readers distributed throughout 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 determination by the server and/or console of the location and status of the clamp apparatus within the hospital matrix. The server and/or console may receive and interpret such tag data, and compute appropriate responses thereof, such as locking down hospital perimeter doors.

CROSS REFERENCE TO RELATED APPLICATION

This application claims priority to U.S. application Ser. No. 17/848,576 filed on Jun. 24, 2022, the contents of which is herein fully incorporated by reference in its entirety.

FIELD OF THE EMBODIMENTS

The embodiments of the present invention relate to systems, methods, and apparatus involving umbilical cord clamps, networked platforms for tracking umbilical cord clamps within a hospital, and in a particular embodiment, to an umbilical cord clamp tag and a system (to secure and protect newborn infants) involving at least one umbilical cord clamp and/or clamp tag adapted to be tracked wirelessly, at least one console unit adapted to wirelessly track the umbilical cord clamp, a server in communication (either via wired or wireless means) with the console unit that communicates clamp status content to the console unit, and at least one wireless transceiver adapted to wirelessly communicate with the umbilical cord clamp and/or clamp tag, the console, and/or the server, wherein the clamp status content is determined based in part on the position, location, operation, and integrity of the clamp, and the clamp's location relative to console unit, wireless transceiver, or server. In particular, the clamp integrity status reflects whether the clamp is intact and engaged, versus damaged and/or disengaged, indicating the possibility that an unauthorized person has tampered with the clamp and/or clamp tag.

BACKGROUND OF THE EMBODIMENTS

The related art includes, for instance, tools, products, and systems, including simple umbilical cord clamps to clamp umbilical cords of newborns to prevent bleeding at the umbilical cord; including umbilical cord tags, wrist tags, and ankle tags to identify the newborn and/or to indicate information about the newborn, such as the newborn's date of birth or blood type; and including tracking tags adapted to be attached to an umbilical cord clamp, a wrist, or an ankle, to track newborns, such as using bar codes printed on the tag, or a radio-frequency identification (RFID) transmitter in the tag. Inasmuch as tracking tags and umbilical cord clamps historically have served distinct, unrelated functions, conventional prior art technologies have separated tracking tags and umbilical cord clamps as distinct, unrelated devices, systems, and data collection sources. Conventional tracking tags have had limited tamper-indication capabilities, and such tamper-indication capabilities have included the capability to detect if a wrist band or ankle band has been cut, and the capability to detect if a wrist band, an ankle band, or an umbilical cord tag ceases to be in contact with the skin of a wearer.

In a conventional hospital setting according to the prior art, immediately after a newborn baby is born, hospital staff clamp an umbilical cord of the newborn baby, to stop blood from flowing within the umbilical cord, and then cut the umbilical cord of the newborn baby, with the clamp between the cut and the newborn to stop the umbilical cord from bleeding out from the newborn. Shortly after the newborn is born, the hospital staff prepare a tag identifying the newborn and attach the tag to the newborn around the newborn's umbilical cord clamp, wrist band, or ankle band in a fashion that prevents the tag from being removed without cutting the tag. In modern hospitals, the tag may include a radio-frequency identification (RFID) transmitter or a bar code that allows hospital staff to track, record, and document interactions with the newborn as a patient of the hospital, such as for monitoring, moving, feeding, treating, securing, and caring for the newborn. In particular, many hospitals have and use sophisticated security procedures, such as multiple checks of identification of visitors and employees, and security systems, such as double-locked doors and entrances (“mantraps”), to secure maternity wards and newborn wards, to prevent threat or abduction of babies.

In contrast to the prior art, the present invention and its embodiments are unique in its design, in its functionality, and in its intended use of the present invention. The present invention is unlike prior art concepts that have approached umbilical cord clamp technology and newborn tracking technology from other angles. The prior art lacks a dedicated platform that serves and manages clamp integrity, tamper monitoring, and location tracking in a wireless network within a wirelessly-networked environment. In contrast, the present solution seeks to pioneer the seamless wireless tracking of clamp tamper-evident integrity and location in newborns wearing wireless-enabled clamps within hospitals.

As described below, embodiments of the present invention include the use of novel features within a wireless-enabled platform comprising 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 users, and document status content data relative to a newborn, using systems and methods different from those of the prior art systems and methods.

BRIEF SUMMARY OF THE EMBODIMENTS

The embodiments of the present invention relate to systems, methods, and apparatus involving components that may be combined in multiple 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 wirelessly-networked environment, such as a hospital, for treatment, identification, and tracking of newborns.

In a hospital setting according to the present invention, immediately after a newborn baby is born, hospital staff use an umbilical cord clamp to clamp an umbilical cord of the newborn baby, to stop blood from flowing within the umbilical cord, and then cut the umbilical cord of the newborn baby, with the clamp between the cut and the newborn to stop the umbilical cord from bleeding out from the newborn. The wireless-enabled umbilical cord clamp tag includes a processor, sensors, a power supply, and wireless communication circuitry to enable wireless programming and communication to and from the clamp and/or clamp tag, so that shortly after the newborn is born, the hospital staff may program the clamp and/or clamp tag to identify the newborn and to monitor the newborn within the hospital. The clamp tag is secured to the newborn's umbilical cord with an umbilical cord clamp in a fashion that prevents the umbilical cord clamp and/or clamp tag from being removed without triggering an alert or an alarm within the monitoring system.

Some embodiments of the present invention may use a wireless-enabled tag according to aspects of the present invention, in which the wireless-enabled tag is integrated with and in a novel umbilical cord clamp as a single assembly, in which the novel umbilical cord clamp may clamp an umbilical cord in a fashion similar to that of 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, in which the wireless-enabled tag is adapted for use with a conventional umbilical cord clamp, such as being placed in the conventional annular hinge portion of the clamp, which activates a switch or button in the tag when the clamp is closed and the hinge portion presses against and depresses the switch or button. In some embodiments, the switch or button is raised relative to a cylindrical column inserted into the annual hinge portion. In other embodiments, the switch or button may be recessed in a cavity of the cylindrical column or other portion of the tag. In other embodiments, the switch or button may comprise a pressure-sensitive thin-film switch strip that is adapted to be inserted along and between an upper row of teeth and a lower row of teeth of the clamp, in which closure of the clamp involves the upper row of teeth engaging the switch strip and the umbilical cord in pressing them against the lower row of teeth of the clamp. In yet other embodiments, other sensing technologies may be employed to achieve the same end means as with the described buttons and switches.

In accordance with a first aspect of the invention, a wireless-enabled umbilical cord clamp apparatus is disclosed that is adapted for use in monitoring location of and detecting tampering with the wireless-enabled umbilical cord clamp apparatus, in which the clamp apparatus comprises: tag apparatus electronic circuitry and hardware including: a tag apparatus processor; a tag apparatus memory, the tag apparatus memory coupled to the tag apparatus processor; a tag apparatus wireless data transfer module, the tag apparatus data transfer module coupled to the tag apparatus processor; a tag apparatus wireless data transfer device, the tag apparatus data transfer device coupled to the tag apparatus processor; and a tag tamper-evident switch, the tag tamper-evident switch coupled to the tag apparatus processor; tag apparatus electronic software, the apparatus software stored in the apparatus electronic circuitry and hardware and adapted to enable, drive, and control the apparatus electronic circuitry and hardware; a tag apparatus power supply, the apparatus power supply coupled to and adapted to power the apparatus electronic circuitry and hardware; and a tag apparatus housing, the tag apparatus housing comprising a tag apparatus exterior and a tag apparatus interior, the tag apparatus interior containing the tag apparatus software, the tag apparatus power supply, and at least some of the tag apparatus electronic circuitry and hardware; wherein the tag apparatus exterior comprises a clamp apparatus frame adapted to be secured adjacent an umbilical cord of a newborn baby when the umbilical cord is clamped by an umbilical cord clamp; wherein the apparatus electronic circuitry and hardware are adapted to operate as a wireless tag that is adapted to be wirelessly read by a wireless tag reader comprising a wireless transceiver; wherein the wireless tag reader is adapted to be communicate to a server managing location data and status data applicable to the wireless tag; and wherein the tag tamper-evident switch is secured by the tag apparatus housing, is exposed in part to the tag apparatus exterior, is coupled to the tag apparatus electronic circuitry within the interior, and is adapted to be activated, deactivated, triggered, or tripped by efforts to tamper with the wireless tag or the umbilical cord clamp. The wireless tag also may be adapted to be read by and/or communicate with a console assembly or apparatus, such as for use by a nurse in a hospital maternity ward.

With respect to an exemplary server in communication with the apparatus of a first aspect of the invention, an exemplary server comprises: server electronic circuitry and hardware including: a server processor; a server memory, the server memory coupled to the server processor; a server data transfer module, the server data transfer module coupled to the server processor; a server data transfer device, the server data transfer device coupled to the server processor; server electronic software, the server software stored in the server electronic circuitry and hardware and adapted to enable, drive, and control the server electronic circuitry and hardware; a server power supply connection, the server power supply connection coupled to the electronic circuitry and hardware and couplable to a server power supply.

With respect to an console assembly adapted to read or communicate with the clamp apparatus of first aspect of the invention, an exemplary console assembly may include: 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 supply connection, the console power supply connection coupled to the console electronic circuitry and hardware and couplable to a console power supply; and a console housing, the console housing comprising a console interior and a console exterior, the console interior containing the console electronic circuitry and hardware, the console software, and the console power supply connection; and the console exterior comprising a console frame enclosing the console interior.

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

In accordance with a second aspect of the invention, a system is disclosed that is adapted for use in monitoring location and status of, managing status and events of, and detecting tampering with a wireless-enabled umbilical cord clamp apparatus, the system comprising: a server comprising: server electronic circuitry and hardware including: a server processor; a server memory, the server memory coupled to the server processor; a server data transfer module, the server data transfer module coupled to the server processor; a server data transfer device, the server data transfer device coupled to the server processor; server electronic software, the server software stored in the server electronic circuitry and hardware and adapted to enable, drive, and control the server electronic circuitry and hardware; and a server power supply connection, the server power supply connection coupled to the server electronic circuitry and hardware and couplable to a server power supply; wherein the server is adapted to determine location data and status data, interpret determinations of location data and status data, determine responses to interpretations of location data and status data, and communicate responses, based on receiving location data and status data from within the system; a wireless transceiver in communication with the server data transfer device and the server data transfer module; a wireless-enabled umbilical cord clamp apparatus comprising: tag apparatus electronic circuitry and hardware including: a tag apparatus processor; a tag apparatus memory, the tag apparatus memory coupled to the tag apparatus processor; a tag apparatus wireless data transfer module, the tag apparatus data transfer module coupled to the tag apparatus processor; a tag apparatus wireless data transfer device, the tag apparatus data transfer device coupled to the tag apparatus processor; and a tag tamper-evident switch, the tag tamper-evident switch coupled to the tag apparatus processor; tag apparatus electronic software, the apparatus software stored in the apparatus electronic circuitry and hardware and adapted to enable, drive, and control the apparatus electronic circuitry and hardware; a tag apparatus power supply, the apparatus power supply coupled to and adapted to power the apparatus electronic circuitry and hardware; and a tag apparatus housing, the tag apparatus housing comprising a tag apparatus exterior and a tag apparatus interior, the tag apparatus interior containing the tag apparatus software, the tag apparatus power supply, and at least some of the tag apparatus electronic circuitry and hardware; wherein the tag apparatus exterior comprises a clamp apparatus frame adapted to be secured adjacent an umbilical cord of a newborn baby when the umbilical cord is clamped by an umbilical cord clamp; wherein the apparatus electronic circuitry and hardware are adapted to operate as a wireless tag that is adapted to be wirelessly read by a wireless tag reader comprising the wireless transceiver; wherein the wireless tag reader is adapted to be communicate to the server managing location data and status data applicable to the wireless tag; and wherein the tag tamper-evident switch is secured by the tag apparatus housing, is exposed in part to the tag apparatus exterior, is coupled to the tag apparatus electronic circuitry within the interior, and is adapted to be activated, deactivated, triggered, or tripped by efforts to tamper with the wireless tag or the umbilical cord clamp.

In an exemplary embodiment of the system, each console or clamp apparatus unit may include at least one configuration of the plurality of configurations. A configuration may include, for instance, a map (e.g., a floorplan of a hospital, an aerial map of the hospital, a road map of roads surrounding a hospital, a topography map of land surrounding a hospital, a resources map of resources within a hospital, a route map of a tag being relocated, a perspective view map, a plan view map, a point-of-view map, etc.), a user interface (“UI”) utility (e.g., switch points of view, reveal details, switch profiles, synchronization of accounts, etc.), a terrain (e.g., a hospital, a parking lot, a city, a town, etc.), a tool (e.g., a clamp cutter, a vehicle, a unit or type of medication, a unit or type of nutrition, etc.), a capability (e.g., applying, attaching, cutting, removing, etc.), an avatar (e.g., a nurse, a doctor, a patient, a newborn baby, an expectant mother, a post-delivery mother, a father, etc.), and a communication utility (e.g., an electronic medical records (EMR) interface, a social media connection, a message feed, etc.). A user of the platform may include, for instance, a nurse, a doctor, a patient, a consumer, a producer, a performer, a business, a developer, an administrator, etc., or a combination thereof. A user may create and/or distribute a configuration, or both, by using the platform for user-based creation and/or distribution of configurations. Each configuration may be software code in a configuration file that includes, for instance, 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. A producer user may develop the software code for the configuration file using, for instance, programming in coding languages, such as JavaScript and HTML, including open-source code, or object-oriented code assembly. The software code would be adapted to be compatible with and executable by the software of a console (e.g., an iPhone smartphone, smart watch, laptop computer, tablet, or the like or some combination thereof) on which a compatible video may be displayed, with which or within which the configuration would be used.

In an exemplary embodiment, the system may include the apparatus of the first aspect of the invention, in which the apparatus is adapted and configured to interact with the platform. The system further may be adapted to enable, permit, and allow a plurality of 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 a user to associate content with a location, a topic, and/or a subject matter, and to push such associated content to another user who is at said location, who is interested in said topic, and/or who is connected to said subject matter.

In accordance with a third aspect of the invention, a method for is disclosed that is adapted for use in monitoring location of and detecting tampering with a wireless-enabled umbilical cord clamp apparatus, in which the method comprises: providing an apparatus, the apparatus adapted to be coupled to and in communication with a server; generating location data and status data of and by the apparatus; transmitting the location data and status data from the apparatus to the server; receiving the location data and status data from the apparatus at the server; determining the location data and the status data by the server; interpreting the location data and status data based on the determinations by the server; determining responses to the interpretations made by the server; and communicating the responses to a response recipient based on interpretations; wherein the wireless-enabled umbilical cord clamp apparatus comprises: tag apparatus electronic circuitry and hardware including: a tag apparatus processor; a tag apparatus memory, the tag apparatus memory coupled to the tag apparatus processor; a tag apparatus wireless data transfer module, the tag apparatus data transfer module coupled to the tag apparatus processor; a tag apparatus wireless data transfer device, the tag apparatus data transfer device coupled to the tag apparatus processor; and a tag tamper-evident switch, the tag tamper-evident switch coupled to the tag apparatus processor; tag apparatus electronic software, the apparatus software stored in the apparatus electronic circuitry and hardware and adapted to enable, drive, and control the apparatus electronic circuitry and hardware; a tag apparatus power supply, the apparatus power supply coupled to and adapted to power the apparatus electronic circuitry and hardware; and a tag apparatus housing, the tag apparatus housing comprising a tag apparatus exterior and a tag apparatus interior, the tag apparatus interior containing the tag apparatus software, the tag apparatus power supply, and at least some of the tag apparatus electronic circuitry and hardware; wherein the tag apparatus exterior comprises a clamp apparatus frame adapted to be secured adjacent an umbilical cord of a newborn baby when the umbilical cord is clamped by an umbilical cord clamp; wherein the apparatus electronic circuitry and hardware are adapted to operate as a wireless tag that is adapted to be wirelessly read by wireless tag reader comprising a wireless transceiver; wherein the wireless tag reader is adapted to be communicate to a server managing location data and status data applicable to the wireless tag; and wherein the tag tamper-evident switch is secured by the tag apparatus housing, is exposed in part to the tag apparatus exterior, is coupled to the tag apparatus electronic circuitry within the interior, and is adapted to be activated, deactivated, triggered, or tripped by efforts to tamper with the wireless tag or the umbilical cord clamp;

In an exemplary embodiment, the method further may be adapted for the safety of a newborn, security of a newborn, and/or notification of a participant, in which the method comprises providing an apparatus adapted for interaction with the participant, in which the apparatus may be configured in accordance with the first aspect of the invention; configuring the apparatus to interact within the system; configuring the apparatus to interact with the participant; enabling the apparatus to interact with the participant; and adapting the apparatus to electronically process status data, identity data, location data, patient data (e.g., blood pressure, pulse, O2, etc.) configuration data, audio data, video data, or a combination thereof, of an interaction of the apparatus with the participant.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The invention relates to systems, methods, and apparatus involving components that may be combined in multiple 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 wirelessly-networked environment, such as a hospital, for protection identification, and tracking of newborns. As used herein the term “wireless-enabled umbilical cord clamp” means any umbilical cord clamping mechanism that is used in conjunction with the clamp tag or wireless tag of the present application as described herein.

The invention is directed to systems, methods, and apparatus involving a platform and an assembly and/or an apparatus adapted to provide a wireless monitoring system for the safety of newborn babies. In an exemplary embodiment of the invention, the apparatus embodies a wireless-enabled umbilical cord clamp apparatus adapted to function within a system that includes a handheld console, such as a smartphone or tablet computer. The apparatus may be adapted to operate as an umbilical cord clamp with an integrated or attachable configurable wireless tag having electronics, such as, a tamper-evident switch and a transceiver, and optionally a camera, a display, a microphone, a speaker, buttons, coupled to and controlled by a processor, with the apparatus adapted to be connectable to the monitoring platform, such as connectable to a data server or system, in a networked environment. The invention may be able to interface with an electronic medical record (EMR) system as well as other electronic systems such as close-captioned television (CCTV) monitoring systems and provide access (e.g., administrator) control to said systems. 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 app, while in other embodiments, the console may include an internal chargeable battery and a radio-frequency transceiver, so that the console may be wireless and portable, such as a smartphone or tablet computer, cither as a purpose-dedicated device, or as a software-configured device configured for that purpose.

Exemplary Embodiments of a System

In a hospital setting according to the present invention, immediately after a newborn baby is born, hospital staff use a wireless-enabled umbilical cord clamp to clamp an umbilical cord of the newborn baby, to stop blood from flowing within the umbilical cord, and then cut the umbilical cord of the newborn baby, with the clamp between the cut and the newborn to stop the umbilical cord from bleeding out from the newborn. The wireless-enabled umbilical cord clamp includes a wireless tag, either integrated into the clamp, or attachable to the clamp, and the wireless tag includes a processor, sensors, a power supply, and wireless communication circuitry to enable wireless programming and communication to and from the clamp, so that shortly after the newborn is born, the hospital staff may program the clamp apparatus and/or tag to identify the newborn and to monitor and track the newborn within the hospital. The wireless-enabled umbilical cord clamp is secured to the newborn's umbilical cord in a fashion that prevents the clamp from being tampered with or removed without triggering an alert or an alarm within the monitoring system, which may indicate an attempted unauthorized removal of the baby.

In a wirelessly-networked hospital environment according to an embodiment of the present invention, the hospital includes at least one wireless transceiver that may send and receive wireless signals in communication with the wireless-enabled umbilical cord clamp, and preferably includes a matrix of wireless transceivers distributed and mapped throughout the relevant portions of the hospital. The matrix may be mapped, for example, to relevant exit doors, hallway doors, room doors, staircases, elevators, windows, rooms, etc., and couple to such doors and to relevant lights, cameras, alarms, strobes, etc. The hospital's wireless system transceiver(s) may comprise, or communicate with, a wireless router (e.g., a Wi-Fi® router, a Bluetooth® router, a Bluetooth-Low-Energy® (BLER) router, a Bluetooth® beacon, BLE® beacon, and/or Near-Field-Communication (NFC) transceiver, beacon, or router) and/or a wireless-enabled console unit, such as a wireless-enabled desktop computer at a nurse station, and/or a nurse's handheld computing device. The wireless system transceiver may comprise and/or communicate with a system server that compiles and coordinates the data and content relative to the status of each wireless-enabled umbilical cord clamp, each wireless system transceiver, and each wireless-enabled console unit, in use and/or active within the system. The system server may communicate within the system using signals over either wired lines, such as connected to wireless routers, or over a wireless transceiver data transfer module directly integrated into or with the server. In some embodiments, a nurse's handheld wireless-enabled console itself may function as the system server.

The wireless-enabled umbilical cord clamp apparatus includes a radio-frequency identification (RFID) transceiver that allows hospital staff to track, record, and document interactions with the newborn as a patient of the hospital, such as for monitoring, moving, feeding, treating, securing, and caring for the newborn. In particular, the clamp transceiver may communicate (i.e., “ping”) periodically (e.g., every 5, 10, 20, or 30 seconds, etc.) a wireless system transceiver, or matrix of wireless system transceivers, in communication with a system server and console units, to update the clamp's status. Updates to the clamp status may include, for example, the status of the clamp's integrity (e.g., has the clamp been opened or removed, triggering an alert or an alarm indicative of the possibility that an abductor is removing the clamp to abduct the newborn baby without the clamp being used to track the newborn during the abduction); the status of the clamp's battery strength and remaining power supply (e.g., does the clamp need to be recharged); and the status of the clamp's location (e.g., where is the clamp within the hospital, and has the clamp moved from an approved or designated location). Within the wirelessly-networked hospital environment, the clamp location may be determined by, for instance, triangulation among system transceivers, or comparisons of relative signal strengths from the clamp tag transceiver to one or more system transceivers.

In some embodiments, the clamp tag may use a wireless transmitter, instead of a transceiver, if the tag is designed only to transmit signals and not to receive signals, such as in low-cost, single-use disposable devices and apparatus. In some embodiments, a transceiver may be adapted or configured as a data transfer module or data transfer device that is restricted to transmitting only. If the tag uses only a transmitter, or is adapted only to transmit, the tag would operate independently of the system components, pushing information to the system, without the system influencing operation of the tag, with all programming of the data done elsewhere within the system, such as on the nurse's console or at the server, based a unique identification (ID) of the tag.

Further, in some embodiments, the clamp tag may operate as part of a mobile ad-hoc network. In some embodiments, the clamp tag acts as a wireless ad-hoc network node. Such a node may connect with one or more base station(s) and access point(s) rather than hop-by-hop forwarding. The decentralized nature of wireless ad hoc networks makes them suitable for a variety of applications including the real time location tracking features of the embodiments of the present application.

In some embodiments, the tag would operate and transmit only once the tag is activated by the closure of a clamp, such as to avoid consumption of electrical power and save battery reserves, in which closure of the clamp may complete or close a circuit required for electricity to flow within the tag. If the tag experiences a drop in power below a threshold power level, the tag may ‘wake up’ and transmit a low-power alert. If the tag is tampered with, such as the clamp being opened, the circuit would open, the tag would cease to operate, and the system immediately would detect a failure of the tag to ping or “check in” with the system at the tag's location last recorded seconds earlier. The system would prompt an alert, an alarm, a console notification, and/or a door lockdown, depending on the tag's status or location, upon detecting the tag's failure to check in. In some embodiments, the tag may have a bar code or other ID that allows the system to register the tag, the tag unique ID, and/or tag identity within the system without the tag being electrically active or electronically activated. In some embodiments, the tag temporarily may be powered and made electrically active or electronically activated, by temporarily closing the clamp to close the circuit to allow the nurse's console to read the tag without the clamp being closed on and attached to an umbilical cord yet, with the clamp being able to be reopened after temporarily being closed. In some embodiments, the tag identity would be entered into the system first when the tag is made electrically active or electronically activated upon closure of the clamp on an umbilical cord, with the nurse using the nurse's console to wirelessly read and associate the tag ID with the newborn baby in the system.

The hospital staff may use the status data received from an active (or activated) wireless-enabled umbilical cord clamp to monitor the location, security, treatment, and/or health of the newborn baby. For instance, each time the newborn is fed or changed, the clamp's RFID may be read and/or scanned by a nurse's console unit to document the activity. In some embodiments, the clamp may warn the hospital staff of potential changes to the newborn's health, such as if the newborn undesirably rolls or is placed onto its stomach for a time that exceeds a set threshold, as measured by a potential sudden drop in RFID signal strength in the clamp without a change in location, potentially indicative of the baby being on top of the clamp and impeding the clamp's RFID signal strength. In some embodiments, the clamp may include a sensor, such as a pressure sensor, an O2sensor, a weight sensor, a force sensor, an accelerometer, a moisture sensor, a temperature sensor, a light senor, and/or an audio sensor that may provide the system with status data, which may alert the hospital staff to potentially dangerous conditions affecting the newborn, if such sensor data meet or exceed set thresholds. For instance, if the newborn requires a heat lamp to maintain a desired ambient temperature, a temperature sensor in the clamp may alert the hospital staff if the ambient temperature rises or falls outside the desired temperature range, potentially indicating that the heat lamp is malfunctioning or that someone maladjusted the heat lamp. Hospital staff may receive an alert or an alarm and take appropriate action to remedy a cause that triggered the alert or the alarm, and when appropriate, reset the clamp, the alert, and/or the alarm upon remedying the cause.

Once the newborn is ready to leave the hospital with an approved adult, the hospital staff may set, deactivate, and/or inactivate the clamp within the system, such as at the tag itself, at the console, or at the server, to avoid triggering a removal alert or alarm and possible abduction warning, and then remove the clamp. By the time the newborn is ready to leave the hospital, the newborn's umbilical cord will have closed, sealed, and healed, such that the clamp no longer is needed to prevent the umbilical cord from bleeding. The used wireless-enabled umbilical cord clamp then may be recycled, if disposable as a single-use device, or disinfected and/or sterilized and prepared for reuse, if constructed and designed as a durable, disinfectable/sterilizable, rechargeable, reprogrammable, reusable, multi-use device.

Whether constructed and designed as a single-use or multi-use device, the wireless-enabled umbilical cord clamp preferably would be waterproof (e.g., subject to submersion when bathing a baby wearing the clamp) and disinfectable/sterilizable by hospital-grade topical disinfectants (e.g., alcohol swabs or sprays), to survive and function properly during the baby's stay and treatment in the hospital. Similarly, so that the baby tolerates wearing the clamp, the clamp needs to be non-irritating in materials, such as to no cause any allergic reaction (e.g. hypoallergenic), contact dermatitis, or other skin ailment, and configuration (e.g., preferably low-profile, with no sharp edges or pointy corners). If designed and manufactured as a disposable, single-use device, the manufacturing costs preferably would be lower than for a reusable, multi-use device, such that a reusable, multi-use device may include more features, functions, and components (e.g., sensors) that increase the per-device costs, which may include licenses for relevant hardware, software, and/or intellectual property to make, sell, and/or use the device.

In preferred embodiments, the manufacturing costs of a single-use, the units would be as small and light-weight as practicable, weighing about 12 grams or less (e.g., preferably 5-6 grams), to avoid strain on the healing umbilical cord or the baby. An exemplary clamp may have a clamp transceiver tag with dimensions of about 34 mm long, about 29 mm wide, and about 5 mm height. An exemplary embodiment would be made of hypoallergenic, biocompatible materials that are rigid, durable, somewhat flexible, and solvent-resistant, such as compositions, combinations, polymers, and/or co-polymers of latex, lead, DEHP, polycarbonate, trimethyl carbonate, polyethylene, polypropylene, polyvinylchloride, polytetrafluoroethylene, stainless steel, alumina, aluminum/aluminium, cobalt-chromium alloy, and silicone, among others.

In some embodiments, the power source may include a battery having a functional battery life permitting many hours of use, such as 12, 24, 36, 48, or 72 hours. In other embodiments, the battery life may last months or years depending on usage and battery type. In preferred embodiments, the power source would include a battery having a functional battery life of at least 96 hours. The power supply preferably would last the entire duration of a typical newborn's hospital stay in the U.S. In the U.S., mothers and newborns typically are discharged from the hospital within two days of a vaginal delivery, and in three days of a delivery by Caesarcan section. A battery life of about 96 hours may be achieved, for example, with a silver oxide “coin” battery beginning with 200 mAh power if the average power consumption is low enough, as low as 2.08 mA. In an embodiment with an approximate average power consumption of about 10.34 mA, a battery beginning with about 1000 mAh would have a battery life of about 96.7 hours. The clamp processor may detect or measure remaining battery power, such as using a circuit activated at a low power. When the remaining battery power nears a functional minimum power level, the clamp may detect this low battery level and send a “low battery” alert to the system.

In preferred embodiments, the clamp transceiver, such as a BLE transceiver, would emit a signal having a functional signal strength that is readable from at least about 10 feet (about 3.1 meters), and preferably longer (e.g., 20-30 feet), away from the clamp, to increase effectiveness of security precautions, such as locking a nursery door if an activated clamp set to “no exit” comes within a minimum safety distance (e.g., about 10 feet) of the nursery door. In some embodiments, an effective read range may be at least 30 feet (or more), such that the system detects an approach of an approaching tag from at least 30 feet away from an exit door, and locks the exit door when the approaching tag gets within about 10 feet of the exit door. An exemplary BLE transceiver may be integrated with a processor on a single printed circuit board (PCB), or coupled to the processor separately from the processor's PCB.

In preferred embodiments, the clamp would be applied easily by trained hospital staff, and yet be able to properly detect tampering or other efforts to disable, disengage, or remove the clamp without authorization and prior deactivation of the clamp, and trigger an alarm or an alert as the result of such unauthorized activities. An exemplary tamper detection device may include, for instance, an enclosed microswitch, pressure sensor switch, or button switch, having an enclosure that limits access, activation, or deactivation, of the tamper detection device without opening the clamp. In preferred embodiments, the clamp would be suitable for use with a wide range of newborn body types and cord conditions, possibly having an alternative clamp configuration for each specific cord condition or newborn born body type.

In some embodiments of the present invention, a system is provided that comprises a hospital security platform that connects the nurse's interface with EMR access to the security system in a networked environment, which may include connections between the building doors that may be electronically and remotely locked and unlocked as well as the ability to notify on site staff and send electronic alerts to dedicated or remote devices. The platform and system may provide a dashboard of, for instance, user activity, tag activity, tag status, and console status data.

Drawings of Exemplary Embodiments of the Invention

Referring to the Figures, a clamp apparatus or a clamp assembly may comprise a mechanical clamping mechanism, operable to clamp an umbilical cord of a newborn baby, and a computing device as an integrated tag or an attachable tag, operable to wirelessly communicate to a wireless-enabled console, a wireless-enabled checkpoint, and/or a server. The clamp apparatus or clamp assembly may be connectable to a security platform via a networked environment, and may comprise part of and/or communicate with an electronic medical records (EMR) media server platform or system, which may include a data system, including at least one server and at least one database, and a network system, including computing devices in communication with each other via network connections.

Referring toFIG.1A,FIG.1Ashows a block diagram of an exemplary system10000adapted to monitor the safety and location of a newborn baby. The system10000may comprise a wireless-enabled umbilical cord clamp apparatus11000, adapted to mechanically clamp an umbilical cord11001of a newborn baby; a wireless-enabled console unit apparatus12000, adapted to interact with the clamp apparatus11000; a wireless transceiver apparatus13000, adapted to wirelessly interact with the clamp apparatus11000; and a server apparatus14000, adapted to manage and maintain data, rules, and interaction within the system10000. Components of the system10000may communicate using wireless communication15000within the system10000, as well as wired communication between components when wiring is provided. The system10000may be used by users such as a participant12011, who may be a nurse, and a power user12021, who may be a supervising nurse or information-technology (IT) resource employee responsible for configuring, managing, and supervising the system10000and/or the nurse participant12011.

The clamp apparatus11000may comprise an umbilical cord clamp and an integrated wireless tag or an attachable wireless tag. The console apparatus12000may comprise a computing device, such as fixed-location desktop computer or nurse's workstation, or a mobile computer or other configurable device, like a laptop computer, a tablet computer, or a mobile smart device, such as a mobile smartphone. The transceiver apparatus13000may comprise a wireless receiver adapted to receive wireless signals from the clamp apparatus11000, and a wired or wireless transmitter to communicate clamp status data to the console12000or the server14000. For instance, the transceiver apparatus13000may include a wireless BLE reader adjacent a doorway, such as an entrance or an exit, adapted to detect and report BLE signals emitted by the clamp apparatus11000. Transceiver apparatus13000preferably is one of many such signal readers forming a matrix of signal detection within a hospital for granular location determination. The server14000may comprise a local server, a local area network (LAN) server, a wide-area network (WAN) server, a cloud-based network server, a further use of the console12000, or a combination thereof. As explained elsewhere, the system10000may be a part of a larger system, such as a hospital security platform and/or an EMR platform or system.

Referring toFIG.1B,FIG.1Bshows a block diagram of an exemplary clamp apparatus11000adapted for use in system10000. The clamp apparatus11000may be a self-contained cord clamp, if sufficient computing power and memory are integrated therein, or the clamp apparatus11000may comprise an assembly of an umbilical cord clamp and a wireless tag, in which the wireless tag is adapted interoperate with the umbilical cord clamp, such as to permit detection of efforts to tamper with or remove the clamp. The present invention envisions that components of the system10000may be sold separately, and the present invention encompasses, as a separate embodiment of the present invention, a non-integrated wireless tag attachable to a conventional umbilical cord clamp. The apparatus11000may be configured for unidirectional or bidirectional communication adapted for use by participants12011. As depicted, the apparatus11000comprises a wireless-enabled clamp apparatus, having an exterior housing11100, such as that of a combination of clamps90000, inFIG.9AtoFIG.9D, and wireless tags100000or110000, inFIG.10AtoFIG.11D. Exterior housing11100may define an interior compartment11200containing electronic circuitry11300. The housing11100may include a frame11110. The exterior housing11100and frame11110may be made from a suitably durable material, such as polycarbonate or other biocompatible material.

The electronic circuitry11300includes an integrated electronic hardware system11310and an integrated software operating system11320stored and executable on the integrated electronic hardware system11310. The software11320may include, for example, firmware, an operating system, applications, drivers, libraries, and application programming interfaces. The electronic software11320may be stored in the electronic circuitry11300and hardware11310and may be adapted to enable, drive, and control the electronic circuitry11300and hardware11310. The integrated electronic hardware system11310may include, for instance, one or more printed circuit boards (“PCB”), such as a motherboard, integrating an internal processor11311coupled to an internal memory11312, an internal power source11313, an integrated data transfer module11314, and an integrated switch or button input device11315, and interoperable with software11320, a dataset11330, and a data transfer device11340.

Other optional integrated components may include an integrated speaker11316(such as to beep as an alarm), an integrated illumination device11317(such as a light-emitting-diode (LED) light to flash as an alert or an alarm), an integrated microphone or audio sensor11318, and an integrated camera11319. The optional components presumably would be integrated into a more-expensive, reusable apparatus, whereas fewer components presumably would be integrated into a less-expensive, single-use apparatus.

Button or switch11315may be adapted to activate the apparatus11000and to detect efforts to tamper with and/or remove the apparatus11000, such as in an attempt to abduct a newborn baby. Switch11315may comprise, for instance, a switch120000depicted inFIG.12AtoFIG.12C. In some embodiments, a switch or button11315might include a locking button that is readily depressed by a finger, but once depressed, locks, and remains locked in the depressed position and activated state, until and requiring release using a special-purpose tool or key, operable from without the exterior housing11100. If a button11315locks to keep the clamp apparatus11000activated, a separate tamper-evident switch11315may be used to detect tampering, such that tampering readily activates or deactivates the separate tamper-evident switch11315, while a locking activation button keeps the clamp apparatus11000active and transmitting within the system10000to allow the system10000to track and find a tampered-with or removed clamp apparatus11000.

In other embodiments, button or switch11315may be a force sensing resistor (FSRs) which are pressure-sensitive components that change their resistance based on applied force making such switches suitable for detecting pressure or touch, piezo sensors that generate an electrical signal when subjected to mechanical stress (such as pressure or vibration), capacitive touch systems that detect changes in capacitance caused by proximity or touch, pressure-sensitive mats which are similar to the concept of pressure-sensitive alarm pads which encompass mats using layers of conductive material (e.g., silver foil) separated by insulating material (e.g., neoprene), or smart fabrics/textiles which are conductive fabrics and/or textiles embedded with sensors can detect pressure, touch, and/or movement.

Remember that the choice of alternative depends on factors such as sensitivity, durability, cost, and the specific application requirements.

The processor11311may include, dependent on the needs of the integrated components, a central processor unit (“CPU”), a graphics processor (i.e., a graphics card or video card), or combination thereof. The software11320and the hardware11310may be adapted to enable a participant12011and/or a power user12021to set up the apparatus11000from or by the console12000, such as to create in the software11320and store in the memory11312a dataset11330including a first profile11331identifying a first newborn baby, and to download, install, select, and run an EMR app11332and an EMR app configuration11333for, and compatible with, a configurable app, such as EMR app11333.

In some more-expensive embodiments, the hardware11310further may include a portable, small or mini display as the illumination device11317, similar to the display of a smartwatch, and wherein the software11320may be adapted to render on the display11317, for instance, a settings menu, an audiovisual file, an image file, on-screen text, on-screen text-entry icons, or any combination thereof. In some embodiments, the display11320may be touch-sensitive. Although the display11320may emit light, such as using a backlight or illuminated pixels (e.g., such as in displays in which each pixel is an organic light emitting diode (“OLED”)), the hardware11310further may include a simple illumination device adapted to illuminate at least a portion of the exterior housing11100. For instance, the illumination device11317may include a light emitting diode (“LED”) adapted to illuminate a portion of the exterior housing11100surrounding the switch or button11315. An LED light11317may indicate a status of the apparatus11000, such as an off/no light indicating no alert or alarm, flashing white light indicating pinging signal transmissions, flashing green light indicating programming mode, flashing yellow light indicating a low-battery warning, flashing red light indicating very-low-battery alert, and non-flashing red light indicating an alarm, such as a perimeter violation alarm.

The apparatus11000includes a data transfer device11340adapted to interoperate with the electronic circuitry11210. The data transfer device11340may include at least one wireless communication module, such as a wireless transmitter or wireless transceiver, and possibly one or more wired communication modules and/or device, as explained in further detail relative toFIG.3. For instance, a wire-based data transfer device might be used to recharge the apparatus11000.

As depicted, the apparatus11000includes a positioning device11350adapted to generate positioning data for use in determining the position, orientation, movement, motion, and/or perspective of apparatus11000. In some embodiments, this is done in real-time via a combination of hardware, software, and communication technologies to determine and relay the real-time location of tagged items or people within a defined area of interest. In some embodiments, the positioning device11350is “non-computative” and comprises the data transfer device11340that is adapted to transmit the apparatus-outbound wireless signals used to determine the location of the apparatus11000within the system10000. In more sophisticated and complicated embodiments of apparatus11000, such as an embodiment described above that is reminiscent of a smartwatch, the positioning device11350may comprise other technology components, mentioned below, and also may be called a position measurement device. The positioning device11350may generate or be used to generate data about the relative position of the apparatus11000, but the positioning device11350does not “position” the apparatus, in the sense that a gimble might “position” or a tripod might support the apparatus in a fixed position.

An “active” or “computative” positioning device11350may include a global positioning system (GPS) receiver and/or GPS module, from which an “absolute” position relative to Earth might be measured and calculated locally within the apparatus11000. In some embodiments, the importance of the positioning device11350for the apparatus11000may relate more to the relative point of view of the apparatus11000within the system10000(such as a location within a hospital), than to the absolute location of the apparatus11000. Exemplary positioning devices11350may include a gyroscope, an infrared (IR) sensor, an accelerometer, an inertia motion unit (IMU)11351, and/or other sensor that may be adapted to detect on-stage beacons or other tracking devices (seeFIG.5) that emit signals suitable for triangulation of a location of the apparatus11000. In some embodiments, a sensor may comprise a sensor-transmitter pair (e.g., light detection and ranging (“LiDAR”), or laser detection and ranging (“LaDAR”)) for active range determinations locally. Alternatively, the software11320may be programed to recognize in-view artifacts (e.g., identifiable background objects, like a crib, to identify if a newborn is leaving or has left the newborn's crib), captured in the video data by the camera11319, using machine vision and/or artificial intelligence (“AI”) for determination of the location of the apparatus11000, such as using triangulation or comparable AI calculation.

Various data settings of the apparatus11000may include creating the first profile11331to include, for example, entering a first baby name of the newborn to whom the clamp apparatus11000was attached, a first participant name of the first participant12011or power use12021(e.g., the nurse who attached the clamp apparatus), or a biographical event (e.g., a birthdate), and storing a first face image of a face of the newborn or the first participant12011or power use12021, or an image of the newborn's mother. The camera11319and the software11320may be adapted to recognize the face of the first participant12011or power use12021based on a comparison with the first face image. The user may associate the first face image with the user's profile for inclusion in the user's postings on the online EMR platform or EMR media system. Moreover, the configuration11333may be specific to the user's profile and may be configured to load automatically upon recognizing the face of the first participant12011or power use12021within a specified distance of the apparatus11000.

Among other possible variations, the software11320may be further adapted to enable the power user12021to select one of a plurality of languages programmed into the software11320; to select one of a plurality of settings programmed into the software11320; to set up the first profile by entering first profile parameters including a first performance, a first role, a first position, a first location, a first event, etc., or any combination thereof, relative to the first participant and/or first biographical event; and to configure the software11320to adjust interaction parameters based on the first profile parameters entered.

Technical variations may include, for example, having the camera11329and the software11320adapted to measure ambient light, motion, or both, such that the apparatus11000may be adapted to alternate between a less-active state, an inactive state, and an active state based on measuring a presence or an absence of a minimum threshold of ambient light, motion, or both.

Referring toFIG.1C,FIG.1Cshows a block diagram of a console unit apparatus12000adapted to comprise and/or operate as a nurse's console12010, and/or a workstation console12020, or other configurable device like a laptop computer, a tablet computer, or a mobile smart device, such as a mobile smartphone. The apparatus12000may be self-contained, if sufficient computing power and memory are integrated therein (e.g., in a smartphone), or the apparatus12000may comprise and/or interoperate with a separate computing device, as depicted inFIG.3et seq. The apparatus12000may be configured for interactive communication adapted for use by participants12011in a hospital environment. As explained below, the apparatus12000may be a part of a larger system, such as an EMR platform and/or a hospital security platform or system. As depicted, the apparatus12000comprises a nurse's console12010or a workstation console12020, having an exterior housing12100, defining and having an interior compartment12200containing electronic circuitry12300. The housing12100may include a frame12110, and an optional handle12120. The exterior housing12100and frame12110may be made of suitably durable materials as conventionally used in the construction of smartphones, tablets, and laptops.

The electronic circuitry12300includes an integrated electronic hardware system12310and an integrated software operating system12320stored and executable on the integrated electronic hardware system12310. The software12320may include, for example, firmware, an operating system, applications, drivers, libraries, and application programming interfaces. The electronic software12320may be stored in the electronic circuitry12300and hardware12310and may be adapted to enable, drive, and control the electronic circuitry12300and hardware12310. The integrated electronic hardware system12310may include, for instance, one or more printed circuit boards (“PCB”), such as a motherboard, integrating an assortment of optional components, such as an integrated camera12311, an integrated microphone12312, and an integrated speaker12313, that are coupled to an internal processor12314, coupled to an internal memory12315, an internal power source12316, an integrated data transfer module12317, interoperable with a data transfer device12400, and at least one integrated input device12318(e.g., button, switch, dial, slider, keypad, keyboard, joystick, touchpad, touchscreen, fingerprint sensor, camera, photosensor, infrared sensor, microphone, audio sensor, motion sensor, gyroscope, accelerometer, inertia motion unit (“IMU”), etc.) operable from without the exterior housing12100. The processor12314may include, dependent on the needs of the components, a central processor unit (“CPU”), a graphics processor (i.e., a graphics card or video card), or combination thereof. The software12320and the hardware12310may be adapted to enable a power user12021to set up the configurable console12000, such as to create in the software12320and store in the memory12315a dataset12330including a first profile12332identifying a first participant12011, and to download, install, select, and run an EMR app12334and an EMR app configuration12336for, and compatible with, a configurable app, such as EMR app12334.

The hardware12310further includes a portable, medium, small or mini display12319, such as found on a smartphone or tablet computer, and wherein the software12320is adapted to render on the display12319, for instance, a settings menu, an audiovisual file, an image file, on-screen text, on-screen text-entry icons, or any combination thereof. In some embodiments, the display12319may be touch-sensitive. Although the display12319may emit light, such as using a backlight or illuminated pixels (e.g., such as in displays in which each pixel is an organic light emitting diode (“OLED”)), the hardware12310further may include a simple illumination device12319′ adapted to illuminate at least a portion of the exterior housing12100. For instance, the illumination device12319′ may include a light emitting diode (“LED”) adapted to illuminate a portion of the exterior housing12100, such as for use as a flashlight, or as a prompt surrounding the input button12318. An LED light12319′ may indicate a status of the nurse's console12010.

Various data settings of the apparatus12000may include creating the first profile12332to include, for example, entering a first participant name of the first participant12011or power user12021, a name of a newborn baby, or a biographical event (e.g., a birthdate), and storing a first face image of a face of the first participant12011or power user12021, or an image of the mother. The camera12311and the software12320may be adapted to recognize the face of the first participant12011or power user12021based on a comparison with the first face image. The user may associate the first face image with the user's profile for inclusion in the user's postings on the online EMR platform or EMR media system. Moreover, the EMR configuration12336may be specific to the user's profile and may be configured to load automatically upon recognizing the face of the first participant12011or power user12021within a specified distance of the apparatus12000.

Among other possible variations, the software12320may be further adapted to enable the power user12021to select one of a plurality of languages programmed into the software12320; to select one of a plurality of settings programmed into the software12320; to set up the first profile by entering first profile parameters including a first performance, a first role, a first position, a first location, a first event, etc., or any combination thereof, relative to the first participant and/or first event; and to configure the software12320to adjust interaction parameters based on the first profile parameters entered.

Technical variations may include, for example, having the camera12311and the software12320adapted to measure ambient light, motion, or both, as well as measuring patient vitals (e.g., blood pressure, pulse, temperature, skin contact, etc.) such that the apparatus12000may be adapted to alternate between a less-active state, an inactive state, and an active state based on measuring a presence or an absence of a minimum threshold of ambient light, motion, or both.

The apparatus12000includes a data transfer device12400adapted to interoperate with the electronic circuitry12300. The data transfer device12400may include at least one wireless transceiver, and possibly one or more other wired and/or wireless communication devices or modules, as explained in further detail relative toFIG.3.

The apparatus120000may include a positioning device12500adapted to generate positioning data for use in determining the position, orientation, movement, motion, and/or perspective of console12010. The positioning device12500also may comprise and be called a position measurement device. The positioning device12500may generate data about the relative position of the console apparatus12000, but does not “position” the apparatus12000, in the sense that a gimble might “position” or a tripod might support the apparatus in a fixed position. The positioning device12500may include a global positioning system (GPS) receiver and/or GPS module, from which an “absolute” position relative to Earth might be measured and calculated. In some embodiments, the importance of the positioning device12500for the apparatus12000may relate more to the relative location of the apparatus12000within the system10000than to the absolute location of the apparatus12000. Exemplary positioning devices12500may include a gyroscope, an accelerometer, an inertia motion unit (IMU)12510and/or an infrared (IR) sensor12520or other sensor that may be adapted to detect (seeFIG.5) local, stationary beacons (e.g., wireless transceiver apparatus13000) or other tracking devices (e.g., wireless-enabled clamp apparatus11000) that emit signals suitable for triangulation of a location of the console12010relative to the other devices. In some embodiments, a sensor may comprise a sensor-transmitter pair (e.g., light detection and ranging (“LiDAR”), or laser detection and ranging (“LaDAR”)) for active range determinations. Alternatively, the software12320may be programmed to recognize in-view artifacts (e.g., identifiable background objects, like the nurse's station), captured in the video data by the camera12311, using machine vision and/or artificial intelligence (“AI”) for determination of the location of the console12010, such as using triangulation or comparable AI calculation.

Referring toFIG.2,FIG.2shows a flow diagram of an exemplary method20000of using a clamp apparatus11000, such as the apparatus11000ofFIG.1AorFIG.1B, according to aspects of the invention. The method20000may be adapted to perform, upon detecting an EMR app configuration11333, loading a configuration beginning detection21000, a beginning response22000. For example, the beginning detection21000may include detecting the input button being activated (21100), detecting a command being provided (21200) by a nurse on console apparatus12000, detecting a location or motion of the clamp apparatus (21300), or any combination thereof. Likewise, the beginning response22000may include using the console12000to update (22100) the status of the clamp apparatus11000as activated within the server14000, and may optionally include the speaker11316to play audio or illumination device11317display lights, such as to confirm the activation. The beginning response22000may include using the console12000to display (22200) an alert, such as advising the first participant12011that the clamp apparatus11000is activated within the system10000, or to activate the input button11315by closing the clamp11120on the newborn's umbilical cord, or both, upon detecting the beginning detection21000. Following the beginning response22000, the method20000may be adapted to perform a subsequent detection and response23000, such as to detect (23100) updates to the status of the clamp apparatus11000, to display (23200) an updated status of the clamp apparatus11000on the nurse's console12000(e.g., an alert if the low-battery status is indicated, or an alarm if the tamper detection status or perimeter violation detection status is indicated), to record (23300) the status update as an interaction file in the EMR app12334and possibly the memory11312or EMR configuration11333, and in response to which, to respond (23400) to updated status or other response with the system10000, such as by the nurse on console12000or from EMR app12334. For example, a response to an alert if the low-battery status is indicated may include replacing and/or recharging (inductive charging, photoelectric charging, kinetic recharging, USB charging, etc.) the clamp apparatus11000, whereas a response to an alarm if the tamper detection status or perimeter violation detection status is indicated may include sending signals to electronically lock perimeter doors near the last-recorded location of the clamp apparatus11000.

The method configuration20000may be configured to have the software12320and the hardware12310further be adapted to enable a power user12021to set up the method configuration20000to select an ending detection24000and an ending response25000to the ending detection24000, wherein the method20000further is adapted to perform the ending response25000upon detecting the ending detection24000. The ending detection24000may include, for instance, detecting an ending (24100), such as the end of the use of the clamp apparatus11000upon discharge of the newborn baby from the hospital; detecting an input (24200), such as a locking input button11315being inactivated, or a tamper-evident switch11315being activated upon making a nurse-authorized opening and removal of the clamp apparatus11000, such as to discontinue tracking of the clamp apparatus11000, or both. The ending detection24000may initiate the ending response25000that concludes an interaction of the method20000with the clamp apparatus11000by the system10000via the nurse console12000used by the first participant12011. The ending response25000may include confirming (25100) the ending in the EMR app12334, such as using the speaker11316and/or12313to sound a deactivation chime to the first participant, or using the light11317to illumination a deactivation lighting pattern and/or the display12319to display a deactivation confirmation screen. The ending response25000further may include storing, updating, displaying, and recording (25200) the ending status of the interaction as an interaction file as a computer-readable file on a computer-readable storage medium, such as an EMR file12334in EMR app12336. The ending response25000might also include connecting to the network, connecting to a EMR server14000or platform, and sending an alert to the power user12021to notify the power user12021that a participant12011has concluded interacting with the apparatus11000and that a file12334of the interaction may be available on the EMR server14000and/or stored in the console12010.

Referring toFIG.3,FIG.3shows a block diagram of an exemplary embodiment30000of the present invention specific to a data transfer device13000. A data transfer device30000may be adapted to enable a data transfer31000between a remote device32000, such as a clamp apparatus11000or an EMR console12000, and a separate computing device33000, such as to provide additional computing, video-capturing, video-processing, image-capturing, image-processing, data processing, communicating, networking, and/or storing capabilities, such as including an auxiliary processing unit (“APU”)33010or a server of an EMR platform, wherein the data transfer device30000may be adapted to enable the remote device32000to communicate with and transfer electronic data31100to the separate computing device32000and to enable the separate computing device33000to communicate with and transfer electronic data31100to the remote device32000. For example, in situations in which multiple remote devices32000may attempt to communicate with a backend server simultaneously from the same general location, such as while users are distributed throughout rooms in a hospital, a computing device33000may act as an intermediate buffer, data aggregator, network bus, cache, or router to facilitate simultaneous high-volume, high-data communication between multiple local consoles and a backend system server over the Internet. In some embodiments, the computing device33000may comprise a component of a matrix of wireless transceiver apparatus13000, each of which may be adapted to serve as a beacon, a location reader, a perimeter port, a data bridge, a sub-router, a data communication range extender, or a combination thereof.

The data transfer device30000may include, for instance, a wire cable30010, a wireless transceiver30020, or both, possibly in combination with wireless transceiver33012of APU33010, wherein the remote device32000may be enabled via a data transfer module32020to transfer to, or receive from, the separate computing device33000, for example, a separate device software application31110and an EMR file31120. Wired cables may include, for instance, an Ethernet cable, RJ45 cable, coaxial cable, USB cable, Thunderbolt cable, Lightning cable, HDMI cable, VGA cable, MIDI cable, etc. A wireless transceiver30020,33012may comprise, for instance, a Wi-Fi transceiver; WiLAN transceiver; a Zigbee transceiver, a Z-wave transceiver, a 6LoWPAN 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, or other low-power IoT enabled technology, etc. Likewise, the separate computing device33000may be enabled to transfer to, or receive from, the remote device32000, for instance, a settings dataset31130and an image file31140. For example, an app31110might include an EMR app31150, and settings31130might include an EMR app configuration31160.

In addition, the wire cable30010may be adapted to enable the remote device32000to recharge an internal power source32100when the wire cable30010is coupled to an external power source34000. An internal power source32100may include, for instance, a rechargeable battery, a non-rechargeable battery, a battery backup, an uninterrupted power supply (“UPS”), a solar-powered generator, a photovoltaic cell or array of cells, etc.

Referring toFIGS.4-5below, exemplary embodiments of the present invention may include a system for interactive communication adapted for professional use in a hospital or other medical care environment by a participant, wherein the system comprises 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 an apparatus adapted to interact with EMR platform and the EMR platform. The system further may comprise 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 clamp apparatus11000, EMR console12000, and/or wireless transceiver apparatus14000; to modify settings of the clamp apparatus11000, EMR console12000, and/or wireless transceiver apparatus14000; to upload data and files to the clamp apparatus11000, EMR console12000, and/or wireless transceiver apparatus14000; to download data and files from the clamp apparatus11000, EMR console12000, and/or wireless transceiver apparatus14000; and to control features and functions of the clamp apparatus11000, EMR console12000, and/or wireless transceiver apparatus14000.

The system further may comprise a remote computing network and a user account platform accessible via the remote computing network and adapted to communicate with and transfer electronic data to and from the EMR platform, the clamp apparatus, and the EMR console, adapted to communicate with and transfer electronic data to and from the separate computing device, and adapted to enable the clamp apparatus and/or the EMR console to communicate with and transfer electronic data to and from the separate computing device via the remote computing network. The system further may comprise a user account accessible via the user account platform that enables 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's account on the EMR platform that are available in the user account via the remote computing network, either because the data and settings have been uploaded to the user account platform, or because the EMR console is in communication with the user account platform via the remote computing network while the power user is accessing the user account platform and logged into the user account. In some embodiments, the user account may be adapted to enable the power user to set alert options to have an alert generated and sent to the separate computing device if an interaction with the first participant happens and notification of the interaction has been communicated from an EMR console and the user account platform via the remote computing network. The user account further may be adapted to enable the power user to email, upload, download, otherwise electronically share, or any combination thereof, an EMR app, an EMR app configuration, or other data file, such as an interaction file of a record of an interaction of the first participant with the EMR console.

The system further may comprise an EMR app configuration data file stored on the remote computing network and downloadable from the user account platform to the separate computing device and to the EMR console, wherein the EMR configuration data file is adapted to enable the EMR console to add further features, perform additional functions, or both. An EMR configuration may include, for instance, details relevant to a performance or experience, such as a map (e.g., an ariel map, a road map, a topography map, a resources map, a route map, a perspective view map, a plan view map, a point-of-view map, etc.), a user interface (“UI”) utility (e.g., switch points of view, reveal details, switch profiles, synchronization of accounts, etc.), a terrain (e.g., a hospital, a parking lot, a city, a town, etc.), a tool (e.g., a clamp cutter, a vehicle, a unit or type of medication, a unit or type of nutrition, etc.), a capability (e.g., applying, attaching, cutting, removing, etc.), an avatar (e.g., a nurse, a doctor, a patient, a newborn baby, an expectant mother, a post-delivery mother, a father, etc.), and a communication utility (e.g., an electronic medical records (EMR) interface, a social media connection, a message feed, etc.).

A user of the EMR platform may include, for instance, a nurse, a doctor, a patient, a consumer, a producer, a performer, a business, a developer, an administrator, etc., or a combination thereof. A user may create and/or distribute a configuration, or both, by using the platform for user-based creation and/or distribution of configurations. Each configuration may be software code in a configuration file that includes, for instance, 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. A user may develop the software code for the configuration file using, for instance, programming in coding languages, such as JavaScript and HTML, including open-source code, or object-oriented code assembly. The software code would be adapted to be compatible with and executable by the software of a console (e.g., an iPhone smartphone) on which a compatible video may be displayed, with which or within which the configuration would be used.

Referring toFIG.4,FIG.4shows a diagram of an exemplary computer environment for use with the systems and methods in accordance with an embodiment of the present invention, and according to aspects of the invention.FIG.4illustrates a schematic diagram of an exemplary computer environment40000for creating, receiving, sending, exchanging, updating, and processing data in accordance with an embodiment of the present invention.

In the depicted embodiment, computer environment40000includes, inter alia, EMR data system41000, network42000, connections43000, and at least one computing device44000, such as computing devices smart device44100, mobile smartphone44200, and tablet computer44300. The data system41000may comprise an EMR console apparatus41100and claim apparatus41200for use in EMR platform, possibly with its own integrated media server and/or service, or connectable to a third-party EMR server and/or system45000for data and media content, such as for a hospital. The network42000may connect to an EMR data system45000that accesses an EMR console data account45100for the transfer of EMR console account data45110. Computing devices44100,44200, and44300are connected to network42000via connections43000, which may be any form of network connection known in the art or yet to be invented. Connections43000may include, but are not limited to, telephone lines (e.g., xDSL, TI, leased lines, etc.), cable lines, power lines, wireless transmissions, and the like. Computing devices44100,44200, and44300include any equipment necessary (e.g., switches, modems, routers, etc.), as is known in the art, to facilitate such communication with the network42000. EMR data system41000also may be connected to network42000using one of the aforementioned methods or other such methods known in the art.

Using inventive apparatus, system, and methods, such as depicted inFIGS.1-5, a user may access the computer environment40000via a computing device connected to network42000such as computing device44000. Computing device44000may include an auxiliary processing unit (“APU”)33010, which may function as an intermediate computing device for use between EMR console apparatus41100, clamp apparatus41200, and EMR data system41000. Such a computing device may be, for instance, a beacon, a location reader, a perimeter port, a data bridge, a sub-router, a data communication range extender, or a combination thereof, possibly as a commercial embodiment of APU33010, or alternatively an individual's personal computer, an Internet café computer, a matrix of readers, a computerized portable electronic device (e.g., a laptop, a tablet, a personal data assistant, a cell phone, etc.), or the like. For example, a smartphone44200may or a tablet computer44300act as an APU33010serving as a communications bridge to a clamp apparatus41200by providing a “hotspot” to allow the clamp apparatus41200to use the network connectivity of the smartphone44200to connect to a server42000.

Using the apparatus, system, and methods depicted inFIGS.1-5, such user access may include a download of data to, and/or an upload of data (e.g., an electronic form of information) from, a computing device44100,44200, and44300via network42000to EMR data system41000(e.g., server, mainframe, computer, etc.), wherein EMR data system41000is typically provided and/or managed by the hospital entity implementing the process or its affiliate, subcontractor, or the like.

Although the systems and methods disclosed herein have focused on embodiments in which user access initiates the process, one of skill in the art may easily appreciate that such systems and methods may be equally applied for other scenarios in which the process is not initiated by the user, and in which the process proceeds under the control of the EMR data system41000, which may initiate the EMR process in accordance with settings or parameters, such as upon the commencement of an event, such as a tamper alert, a removal or perimeter alarm, a low-battery alert, etc. For example, EMR data system41000may push content to a user upon the user arriving at or connecting from a specified location, in which the content is associated with the specified location, such as the crib of a specific newborn baby, or with a topic or a subject matter relevant to the specified location, such as medication for the specific newborn baby.

Referring toFIG.5,FIG.5shows a block diagram of an exemplary data system for use with systems and methods in accordance with an exemplary embodiment of the present invention, according to aspects of the invention. In addition,FIG.5shows an exemplary set of databases, libraries, or data tables for use with the exemplary computer environment, in accordance with the exemplary embodiment of the present invention, according to aspects of the invention.FIG.5depicted herein represents an exemplary computing system environment for allowing a user of system50000to perform the methods described with respect toFIGS.1-4.

The depicted computing system environment is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality. Apart from a customized EMR apparatus51010, and a novel clamp apparatus as a tracking device55000, numerous other general-purpose or special-purpose 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, personal computers (“PCs”), server computers, handheld or laptop devices, multi-processor systems, microprocessor-based systems, network PCs, minicomputers, mainframe computers, cell phones, smartphones, tablets, embedded systems, distributed computing environments, cloud-based systems, that include any of the above systems or devices, and the like.

FIG.5depicts an exemplary system50000for implementing embodiments of the present invention. This exemplary system includes, inter alia, one or more computing devices51000, a network52000, and at least one server53000, which interface to each other via network52000, and access at least one database54000, to track at least one clamp apparatus as a tracking device55000, such as using at least one reader device55010, such as in a matrix of reader devices55010placed throughout a hospital. A computing device51000may include a console apparatus12000, an EMR console32000, an EMR apparatus51010, an auxiliary processing unit33010of an apparatus51010, and/or an EMR apparatus51010having an auxiliary processing unit33010connected to the EMR console32000, such as described in the embodiments ofFIGS.1-3. In its most basic configuration, computing device51000includes at least one processing unit, processor51100, and at least one memory unit51200. Depending on the exact configuration and type of the computing device, memory51200may 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. A basic configuration is illustrated inFIG.5by non-volatile memory51300. In addition to that described herein, computing devices51000can be any web-enabled handheld device (e.g., cell phone, smart phone, or the like) or personal computer including those operating via Android, Apple, and/or Windows mobile or non-mobile operating systems.

Computing device51000may have additional features and/or functionality. For example, computing device51000may include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape, thumb drives, and external hard drives as applicable. Such additional storage is illustrated inFIG.5by removable storage51400and non-removable storage51500.

Computing device51000typically includes or is provided with a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by computing device51000and includes both volatile and non-volatile media, removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media.

Computer storage media includes volatile and non-volatile, 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. Memory51200, removable storage51400, and non-removable storage51500are all examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, electrically erasable programmable read-only memory (“EEPROM”), flash memory or other memory technology, CD-ROM, digital versatile disks (“DVD”) or other optical storage, magnetic 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 that can be accessed by computing device51000. Any such computer storage media may be part of computing device51000as applicable.

Computing device51000may also contain a communications connection51600that allows the device to communicate with other devices. Such communications connection51600is an example of communication media. Communication media typically embodies computer-readable instructions, data structures, program modules and/or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or 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.

Computing device51000may also have input device(s)51700such as keyboard, mouse, pen, camera, light sensor, motion sensor, infrared (“IR”) sensor, accelerometer, inertia motion unit (“IMU”), voice input device, touch input device, etc. Output device(s)51800such as a display, speakers, LED light, printer, etc. may also be included. Some input devices51700may be considered output devices51800for other components, such as a camera providing a video feed, or a sensor providing data on the activity that is sensed. All these devices are generally known to the relevant persons of skill in the art and therefore need not be discussed in any detail herein except as provided.

Notably, computing device51000may be one of a plurality of computing devices51000inter-connected by a network52000. As may be appreciated, network52000may be any appropriate network and each computing device51000may be connected thereto by way of connection51600in any appropriate manner. In some instances, each computing device51000may communicate with only the server53000, while in other instances, computing device51000may communicate with one or more of the other computing devices51000in network52000in any appropriate manner. For example, network52000may be a wired network, wireless network, or a combination thereof within an organization or home, or the like, and may include a direct or indirect coupling to an external network such as the Internet or the like. Likewise, the network52000may be such an external network. Network5200may allow for a number of computing devices51000with capabilities utilizing internet of things (IoT) to establish secure connections between physical products online connected tag readers and the like. The IoT environment may be particularly useful for smart tags, which unlike simple RFID tags, are sensor-enabled tags that actively generate and send metrics and other data in real-time. This expansion of capabilities makes connected devices truly “smart.” For example, the tags may further monitor ambient or body temperature, O2saturation, pulse rate, respiratory, and the like or some combination thereof.

Computing device51000may connect to a server53000via such an internal or external network. Server53000may serve, for instance, as an EMR platform, a media server, service, or platform, or both. AlthoughFIG.5depicts computing device51000located in close proximity to server53000, this depiction is not intended to define any geographic boundaries. For example, when network52000is the Internet, computing device can have any accessible physical location. For example, the computing device may be a tablet, cell phone, smartphone, personal computer, or the like located at any user's office, home, or other venue, etc. Or computing device could be located proximate to server53000without departing from the scope hereof. Also, althoughFIG.5depicts computing devices51000coupled to server53000via network52000, computing devices may be coupled to server53000via any other compatible networks including, without limitation, an intranet, local area network, or the like.

The system may use a standard client-server technology architecture, which allows users of the system to access information stored in the relational databases via custom user interfaces. An application may be hosted on a server such as server53000, which may be accessible via the Internet, using a publicly addressable Uniform Resource Locator (“URL”). For example, users can access the system using any web-enabled device equipped with a web browser. Communication between software component and sub-systems are achieved by a combination of direct function calls, publish and subscribe mechanisms, stored procedures, and direct SQL queries.

In some embodiments, for instance, server53000may be provided as a service, such as via Amazon Web Services (“AWS”), or as a dedicated stand-alone service, such as an Edge R200 server manufactured by Dell, Inc., however, alternate servers may be substituted without departing from the scope hereof. System50000and/or server53000utilize a PHP scripting language to implement the processes described in detail herein. However, alternate scripting languages may be utilized without departing from the scope hereof.

An exemplary embodiment of the present invention may utilize, for instance, a Linux variant messaging subsystem. However, alternate messaging subsystems may be substituted including, without limitation, a Windows Communication Foundation (“WCF”) messaging subsystem of a Microsoft Windows operating system utilizing a .NET Framework 3.0 programming interface.

Also, in the depicted embodiment, computing device51000may interact with server53000via a Transmission Control Protocol/Internet Protocol (“TCP/IP”) communications protocol; however, other communication protocols may be substituted.

Computing devices51000may be equipped with one or more Web browsers to allow them to interact with server53000via a HyperText Transfer Protocol (“HTTP”) and/or a secure version (e.g., “https”) of a related Uniform Resource Locator (“URL”). HTTP functions as a request-response protocol in client-server computing. For example, a web browser operating on computing device51000may execute a client application that allows it to interact with applications executed by server53000. The client application submits HTTP request messages to the server. Server53000, 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, alternate methods of computing device/server communications may be substituted without departing from the scope hereof.

In the exemplary system50000, server53000includes one or more databases54000as depicted inFIG.5, which may include a plurality of libraries or database tables including, without limitation, Templates, Users, Events, Memories, Moments, Maps, Utilities, User Uploads, Admin Info, Transactions, Status, Tracking, and/or Location database tables, e.g.,54100through54600. As may be appreciated, database(s)54000may be any appropriate database capable of storing data and it may be included within or connected to server53000or any plurality of servers similar to53000in any appropriate manner.

In the exemplary embodiment of the present invention depicted inFIG.5, database(s)54000may be structured query language (“SQL”) database(s) with a relational database management system, namely, MySQL as is commonly known and used in the art. Database(s)54000may be resident within server53000. However, other databases may be substituted without departing from the scope of the present invention including, but not limited to, PostgreSQL, Microsoft® SQL Server 2008 MySQL, Microsoft® Access®, and Oracle databases, and such databases may be internal or external to server53000.

In the case of program code execution on programmable computers, 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 may implement or utilize the processes described in connection with the presently disclosed subject matter (e.g., through the use of an application programming interface (“API”), reusable controls, or the like). Such programs may be implemented in a high-level procedural or object-oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

Although exemplary embodiments may refer to utilizing aspects of the presently disclosed subject matter in the context of one or more stand-alone computer systems, the subject matter is not so limited, but rather may be implemented in connection with any computing environment, such as a system50000or a distributed computing environment40000. Still further, aspects of the presently disclosed subject matter may be implemented in or across a plurality of processing chips or devices, and storage similarly may be created across a plurality of devices in system50000. Such devices might include personal computers, network servers, and handheld devices (e.g., cell phones, tablets, smartphones, etc.), for example.

In the exemplary embodiment, server53000and its associated databases are programmed to execute a plurality of processes including those shown inFIGS.1-4as discussed in greater detail herein.

Methods in accordance with aspects of the invention include, for instance, a method for interactive communication adapted for tracking electronic medical records, including those of a clamp apparatus, wherein the method comprises providing an apparatus, such as clamp apparatus11000and/or console apparatus12000, adapted for interaction with a participant, such as a nurse participant12011; configuring the apparatus to interact with the participant; enabling the apparatus to interact with the participant; and capturing electronically in the apparatus status data, status data, or both, of an interaction of the apparatus with the participant. Further embodiments of the method may include performing the actions associated the functionalities set forth inFIGS.1-5, such as using clamp apparatus11000with the EMR console apparatus12000, within the computing environment40000, and within the system10000and/or50000.

Referring toFIG.6,FIG.6shows a block diagram of an exemplary embodiment of a method60000of use of an exemplary EMR system, according to aspects of the invention. In the method60000as depicted inFIG.6, the AR system may perform a step61000of status capture and location detection at the apparatus. The status capture and location detection step61000may include, for instance, detecting61100an input, such as a switch or button press to activate the apparatus; detecting61200a status of the apparatus captured or generated by a console apparatus, such as in which the status is detected during an attachment of a clamp apparatus to an umbilical cord of a newborn baby; and detecting location or motion61300, in some embodiments in real time (both in tracking as well as locating), such as to generate positioning data and/or to indicate a location within a hospital that the clamp apparatus is located or is being moved or handled by a user. The EMR system may perform a step62000at the clamp apparatus of transmission of location ping signal output, which may be received at a console apparatus or a wireless transceiver apparatus, and sent to a server, such as via an auxiliary processor unit. This transmission step62000may include sending62100the location ping signal receipt data from the signal reader to the server, possibly via the auxiliary processor unit, for combination with an EMR file for the newborn; and sending62200the clamp status data feed from the clamp apparatus, via a reader or auxiliary processor unit, to the server; for location calculations and determinations of the appropriate EMR response. The EMR system may perform a step63000at the server of server computation and response(s) to the transmission step62000. This computation and response step63000may include determining63100a location (e.g., in a nursery, in mother's room, etc.) and/or a status (e.g., operational, activated, low-battery, etc.) of the clamp apparatus within the hospital; computing63200a corresponding location interpretation and response (e.g., the clamp apparatus is within authorized location, so no action is needed; the clamp apparatus is being moved toward an exit from an authorized location, so an alert and a lockdown are needed; the clamp apparatus is not within authorized location, so an alarm for possible abduction is needed; etc.) and/or status interpretation and response(s) (e.g., operational status, so no action needed; low battery status, so replacement or recharging is needed; no longer operational or deactivated, so a tamper alert or removal alarm is needed; etc.), and sending63300the response(s) to the console apparatus. The EMR system may perform a step64000at the console apparatus of receipt and combination of responses from the server. The receipt and combination of responses step64000may include receiving64100the location and status updates and responses, and combining64200the location updates, status updates, and associated responses in the corresponding EMR file for the newborn baby. The EMR system may perform the step65000at the console apparatus of receipt and display of the updated and combined data. The receipt and display EMR data step65000may include receiving65100the combined data feed comprising the clamp apparatus' determined location, the computed location interpretation, the computed location response, the determined status, the computed status interpretation, the computed status response, and displaying65200the combined data feed on the display of the console apparatus.

Referring toFIG.7,FIG.7shows a conceptual block diagram of an exemplary system functions70000operation flow within a system70010and with methods in accordance with an exemplary embodiment of the present invention, according to aspects of the invention. The embodiment ofFIG.7depicts an exemplary embodiment of the system and is not limiting of the invention overall. The depicted system functions70000conceptually may be divided into the server functions71000of server71010, console or auxiliary processing unit (APU) functions72000of console or APU72010, and clamp apparatus tag functions73000of a wireless tag73010of a clamp apparatus. The system functions70000conceptually may be divided into the server output, console or APU input functions70100; the console or APU output, tag input functions70200; the tag output, console or APU input functions70300; and the console or APU output, server input functions70400. In this depicted embodiment, the APU72010might be a wireless transceiver apparatus13000, such as a tag reader in a matrix of tag readers distributed through a hospital, that communicates with a server71010, whereas console72010that may be a smartphone running an app functioning as a nurse's console apparatus12000that communicates with the server71010.

At a high conceptual level, a data flow may be represented by the server output, console or APU input functions70100; the console or APU output, tag input functions70200; the tag output, console or APU input functions70300; and the console or APU output, server input functions70400. For example, the server71010may connect to the console72010using the server output, console input functions70100to push patient-based EMR data to the console72010. The console72010may then communicate some of the patient-based EMR data to the tag73010to initiate activation and status capture by the tag73010, using the console output, tag input functions70200. The tag73010may send location data and status data back to the console72010, using tag output, console input functions70300, for the location data and status data to be combined with EMR content received from the server71010. The console72010may transfer some location data and/or status data to the server71010using the console output, server input functions70400. For example, the tag output, console input functions70300might comprise the tag73010generating low-battery status data that are transferred to the console72010. An APU72010might receive tag location ping signals as a tag output, APU input function70300, and send the location ping data to the server71010as an APU output, server input function70400, for the server71010to generate location data for the tag. As a server function71000, the server71010may use the location data and status data to generate an appropriate interpretation and response to the location data and status data, including timing of the location data or status data relative to the events in the EMR data (e.g., a scheduled discharge of a newborn from the hospital), and sending the response to the console72010. As a console function72000, the console72010may 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 sending an updated data feed to the tag73010, such as if the tag73010is to be deactivated by an authorized user. If the tag73010is updated, a tag function73000includes storing the updated data. If the console72010includes a display, the console functions72000may include displaying the EMR data on the display of the console for viewing by a user.

Referring toFIG.8,FIG.8shows a conceptual block diagram of an exemplary system functions80000operation flow within a system80010and with methods in accordance with an exemplary embodiment of the present invention, according to aspects of the invention. The embodiment ofFIG.8depicts an exemplary embodiment of the system and is not limiting of the invention overall. The depicted system functions80000conceptually may be divided into the server functions81000of server81010, auxiliary processing unit functions82000of auxiliary processing unit (“APU”)82010, and tag or console functions83000of a tag or console83010. The system functions80000conceptually may be divided into the server output, APU input functions80100; the APU output, console or tag input functions80200; the tag or console output, APU input functions80300; and the APU output, server input functions80400. In this depicted embodiment, the APU82010might be a separate computing device, such as a tablet, laptop, or desktop computer; or a wireless transceiver apparatus13000, such as in a matrix of wireless routers, wireless range extenders, and/or wireless tag readers distributed throughout a hospital; or an intermediate buffering server; that communicates with a wireless tag83010of a clamp apparatus11000, and/or with a console83010that may be a nurse's console apparatus12010that communicates with the server81010via, at least in part, the APU82010.

At a high conceptual level, a data flow may be represented by the server output, APU input functions80100; the APU output, tag or console input functions80200; the tag or console output, APU input functions80300; and the APU output, server input functions80400. For example, the server81010may connect to the APU82010using the server output, APU input functions80100to push patient-based EMR data to the APU82010. The APU82010may then communicate the patient-based EMR data to the console83010to update the EMR data displayed by the console83010, using the APU output, console input functions80200. The console83010may send clamp apparatus status data back to the APU82010, using console output, APU input functions80300, for the status data to be forwarded by the APU82010to the server81010and combined with other EMR data, once received by the server81010. The APU82010may transfer the data to the server81010using the APU output, server input functions80400. For example, the console output, APU input functions80300might comprise the console83010generating tag activation status data that are transferred to the APU82010. The tag83010might generate location ping signal data and status data that the tag83010may send to the APU82010as a tag output, APU input function80300. The APU82010might transfer the location ping data and status data to the server81010as an APU output, server input function80400. As a server function81000, the server81010may use the location data and/or status data to generate an appropriate interpretation and response to the location data and the status data, relative to the other EMR data and timing of the location data and status data relative to the other EMR data, and the server81010may send the interpretation and response data to APU82010to be forwarded to and displayed on the console83010. As a potential APU function82000, the APU82010may combine the interpretation and response data with the EMR data to create an updated EMR data feed sent to the console83010. As a console function83000, the console83010may display the updated EMR data feed. If the APU82010includes a display as well, the APU functions82000may include displaying the update EMR data on the display of the APU also, such as for monitoring what a user is viewing on the console83010. For example, an APU82010may comprise a tag reader and a tablet computer, in which the tablet computer displays an image of a hospital floorplan with blinking beacon dots indicating approximate locations of wireless tags detected on that hospital floor.

As presented differently, the tag or console functions83000may comprise the tag or console83010generating EMR data, such as status data or location data of a clamp apparatus, and sending the EMR data to the auxiliary processing unit82010. The auxiliary processing unit functions82000may include the APU82010receiving the EMR data from the tag or console83010and communicating with the server81010to have the server81010perform the server functions81000comprising generating updated EMR data that include an appropriate interpretation of and response to the updated EMR data and timing of the updated EMR data relative to the other EMR data, and sending the interpretations and responses from the server81010to the APU82010. The APU functions82000further include the APU82010forwarding the updated EMR data to the tag or console83010, and possibly combining aspects of the EMR data with other EMR data or system data to create an APU-specific data feed (e.g., animation of floorplan image with beacon dots indicating tag locations in real time). The tag or console functions83000include the tag or console83010storing the updated EMR data, and possibly displaying the updated EMR data on the display(s) of the console83010for viewing by a user, such as a nurse.

Referring toFIGS.9A-9D,FIGS.9A-9Dshows various exemplary clamps90000, as part of an umbilical cord clamp apparatus11000within a system10000used pursuant to a method in accordance with an exemplary embodiment of the present invention, according to aspects of the invention. As shown inFIG.9A, clamp90010comprises a hinged clamp having a hinge and hinge cavity90011, a first opposing row of teeth90012, a second opposing row of teeth90013, and a locking mechanism90014, having a male portion90015, and a female portion90016. The hinge cavity is partially annular, forms an open partial ring when the clamp is open, and forms a closed ring when the clamp is closed. The hinge90011is adapted to align the first opposing row of teeth90012with the second opposing row of teeth, so that the first opposing row of teeth90012oppose and engage, but do not obstruct, the second opposing row of teeth90013when the clamp90010is closed. The hinge90011also is adapted to align the male portion90015and the female portion90016of the locking mechanism90014, so that the male portion90015opposes, inserts into, and engages the female portion90016when the clamp90010is closed. The female portion90016comprises a cavity with an interior lip (not visible in the drawing) at the opening. The male portion90015resembles two flexible, opposing flanges, which may flex inward upon insertion into female portion90016, and then flex outward within female portion90016, to engage the interior lip. An umbilical cord of a newborn baby may be inserted between the first opposing row of teeth90012and the second opposing row of teeth90013, and the clamp90010may closed to compress umbilical cord between rows90012,90013, thereby impeding further bleeding from the umbilical cord and serving as a tourniquet stopping circulation to the distal tip of the umbilical cord, causing the distal tip to dry out and eventually fall off.

As shown inFIG.9B, clamp90020comprises a variation of a hinged clamp, in which the locking mechanism90024includes a male portion90025comprising a tapered plug adapted to compress and deform when inserted into a female portion90026, and decompress and engage an interior lip to lock the mechanism90024.

As shown inFIG.9C, clamp90030comprises a variation of a hinged clamp, in which the locking mechanism90034includes a male portion90035comprising a flexible flanged lip adapted to flex outward when inserted into a female portion90036, and flex inward and engage a lip of the female portion90036to lock the mechanism90034. The locking mechanism90034may be reopened if the male portion90035is disengaged from the female portion90036. The clamp90030is depicted in an open, unlocked position90037, revealing a pin90038that may engage a button90039. Button90039may comprise an electrical switch. Pin90038and button90039may comprise a tamper-evident switch that indicates possible tampering if the pin90038ceases to engage the button90039after the locking mechanism90034is closed (e.g., in a closed, locked position90047), but then is reopened.

As shown inFIG.9D, clamp90040comprises a variation of clamp90030, depicted in a closed, locked position90047. Although clamps90010,90020,90030, and90040are variations of hinged clamps, some clamps may omit the hinge and replace the hinge with a second locking mechanism, such that a locking mechanism is on either side of the opposing rows of teeth.

Referring toFIGS.10A-10E,FIGS.10A-10Eshows depictions of wireless tags100000and specific tag100010from different viewpoints that may be used in an exemplary apparatus within a system used pursuant to a method in accordance with an exemplary embodiment of the present invention, according to aspects of the invention. The embodiment ofFIGS.10A-10Eshows an exemplary proposed commercial embodiment of the system and is not limiting of the invention overall.FIG.10Adepicts a top perspective side view of tag100010;FIG.10Bdepicts a top perspective plan view of tag100010;FIG.10Cdepicts a side elevation view of tag100010;FIG.10Ddepicts a bottom perspective side view of tag100010; andFIG.10Edepicts a top plan view of tag100010. Tag100010includes a hexagonal housing100011that includes a cylindrical column frame stem100012and a cylindrical column frame pedestal100013, with the stem100012depicted as having a button100014along the stem100012. The stem100012is adapted to fit within, for example, a hinge cavity90011with the clamp90010in the open, unlocked position90037, such that the pedestal100013and the hexagonal house100011are wider than the hinge cavity90037and prevent the tag100010from being removed from the clamp in the closed, locked position90047without tampering with the clamp90010.

In some embodiments, the hexagonal housing100011take various other form factors including circular, spherical, domed, triangular, quadrilateral, and the like. The shape of the housing may vary as needed by the end user and/or required application but generally has no sharp edges, does not pose a hazard to third parties, is low weight, is compatible with umbilical cord clamps, has a waterproof (e.g., IP68) housing, is made of patient friendly, non-reactive materials, and can easily be cleaned without causing degradation to the housing. In order to help ensure the housing is waterproof, the housing may be sonically welded, have one or more rubber membranes, and/or a rubber or other water impermeable sleeve covering the housing.

Closure of the clamp90010closes the annular ring of the hinge cavity90037and depresses the button100014, engaging a tamper-evident switch within the wireless tag100010. In the event that the clamp90010is tampered with in a way that dislodges the stem100012from the hinge cavity90037, the button100014may be dislodged from within the hinge cavity90037in a way that the button100014no longer is depressed or engaged, changing or interrupting the state of the tamper-evident switch to cause the system10000to interpret the interruption state change data as a possible tampering event that requires a response of an alert or an alarm, depending on the circumstances.

Referring toFIGS.11A-11D,FIGS.11A-11Dshows depictions of other wireless tags110000and specific tag110010from different viewpoints that may be used in an exemplary apparatus within a system used pursuant to a method in accordance with an exemplary embodiment of the present invention, according to aspects of the invention. The embodiment ofFIGS.11A-11Dshows an exemplary alternative embodiment of the system and is not limiting of the invention overall.FIG.11Adepicts a top perspective side view of tag110010;FIG.11Bdepicts another top perspective side view of tag110010;FIG.11Cdepicts a bottom perspective side view of tag110010; andFIG.11Ddepicts a top perspective plan view of tag110010. Tag110010includes a rectangular housing110011that includes a cylindrical column frame stem110012and a cylindrical column frame pedestal110013. Although not depicted, the stem110012may have along the stem110012a button analogous to button100014. The stem110012is adapted to fit within, for example, a hinge and hinge cavity90011with the clamp90010in the open, unlocked position90037, such that the pedestal110013and the rectangular house110011are wider than the hinge cavity90037and prevent the tag110010from being removed from the clamp in the closed, locked position90047without tampering with the clamp90010. Closure of the clamp90010closes the annular ring of the hinge and hinge cavity90037and depresses the button, engaging a tamper-evident switch within the wireless tag110010. In the event that the clamp90010is tampered with in a way that dislodges the stem100012from the hinge cavity90037, the button may be dislodged from within the hinge cavity90037in a way that the button no longer is depressed or engaged, changing or interrupting the state of the tamper-evident switch to cause the system10000to interpret the interruption state change data as a possible tampering event that requires a response of an alert or an alarm, depending on the circumstances.

Referring toFIGS.12A-12C,FIGS.12A-12Cshow depictions of various switches120000and specific switches120010,120020,120030from different perspective viewpoints that may be used, alone or in combination, in an exemplary apparatus within a system used pursuant to a method in accordance with an exemplary embodiment of the present invention, according to aspects of the invention. The embodiments ofFIGS.12A-12Cshows exemplary potential commercial embodiments of switches for use a wireless-enabled tag of a wireless-enabled clamp apparatus11000of the system10000and are not limiting of the invention overall.FIG.12Adepicts a switch120010having a hinge120011, a hinged lever120012, and a depressible button120013, adapted to be engaged when the lever120012is pressed to close the hinge120011, to activate the switch.FIG.12Bdepicts a switch120020having an exposed depressible button120023, adapted to be engaged when the button120023is pressed, to activate the switch.FIG.12Cdepicts a switch120030having a compressible thin-film printed-circuit switch120033, adapted to be engaged when the thin-film switch120033is compressed, to activate the switch.

These switches120000, and variations thereof, may be adapted to serve a tamper-evident switch in a clamp apparatus11000, such as in the ways described in reference to button90039inFIG.9Cand to button100014inFIG.10D. For instance, button90039may comprise button120023of switch120020and be depressed by pin90038. For instance, locking mechanism90014be fitted with switch120010, in which lever120012acts as, or is engaged by, male portion90015, to depress button120013upon closing the clamp90010. For instance, button100014may comprise button120023of switch120020and be depressed by closure of hinge cavity90011. For instance, thin-film switch120033may be positioned between and aligned with rows of teeth90012,90013, such that closing the clamp90010causes the rows of teeth90012,90013to compress the thin-film switch120033, such as when the umbilical cord is between the rows of teeth90012,90013, thereby engaging and activating the thin-film switch120033. For instance, thin-film switch120033may be positioned around the stem100012,110012, such that closing the clamp90010causes the hinge cavity90011to compress the thin-film switch120033, thereby engaging and activating the thin-film switch120033. For instance, thin-film switch120033may be positioned around the male portion90015, and/or within the female portion90016, of locking mechanism90014, such that closing the clamp90010causes the locking mechanism90014to compress the thin-film switch120033, thereby engaging and activating the thin-film switch120033.

The foregoing description discloses exemplary embodiments of the invention. While the invention herein disclosed has been described by means of specific embodiments and applications thereof, numerous modifications and variations could be made thereto by those skilled in the art without departing from the scope of the invention set forth in the claims. Modifications of the above disclosed apparatus and methods that fall within the scope of the claimed invention will be readily apparent to those of ordinary skill in the art. Accordingly, other embodiments may fall within the spirit and scope of the claimed invention, as defined by the claims that follow hereafter.

FIGS.13A-Cdemonstrates another form factor of an embodiment of the present invention. The components and operation of the tag are consistent with the proceeding disclosure. Here, the exterior housing11100is a quadrilateral in shape and is clear. However, the exterior housing11100may be opaque. When the exterior housing11100is clear, it allows the internal components to be visible which may indicate operation or lack thereof (by a status LED) that would be visible to the user, service provider, etc.

In the description above, numerous specific details are set forth in order to provide a more thorough understanding of the embodiments of the invention. It will be apparent, however, to an artisan of ordinary skill that the invention may be practiced without incorporating all aspects of the specific details described herein. Not all possible embodiments of the invention are set forth verbatim herein. A multitude of combinations of aspects of the invention may be formed to create varying embodiments that fall within the scope of the claims hereafter. In addition, specific details well known to those of ordinary skill in the art have not been described in detail so as not to obscure the invention. Readers should note that although examples of the invention are set forth herein, the claims, and the full scope of any equivalents, are what define the metes and bounds of the invention protection.