WO2025035147A2 - Dispositif de détection physiologique ayant une couche d'accès à des données, et ses procédés de fonctionnement - Google Patents

Dispositif de détection physiologique ayant une couche d'accès à des données, et ses procédés de fonctionnement Download PDF

Info

Publication number
WO2025035147A2
WO2025035147A2 PCT/US2024/041912 US2024041912W WO2025035147A2 WO 2025035147 A2 WO2025035147 A2 WO 2025035147A2 US 2024041912 W US2024041912 W US 2024041912W WO 2025035147 A2 WO2025035147 A2 WO 2025035147A2
Authority
WO
WIPO (PCT)
Prior art keywords
data
physiological
data access
access layer
layer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/041912
Other languages
English (en)
Other versions
WO2025035147A3 (fr
Inventor
Srikanth Jadcherla
Michael H. BURNAM
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Centrus Diagnostics Inc
Original Assignee
Centrus Diagnostics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Centrus Diagnostics Inc filed Critical Centrus Diagnostics Inc
Publication of WO2025035147A2 publication Critical patent/WO2025035147A2/fr
Publication of WO2025035147A3 publication Critical patent/WO2025035147A3/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/63—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for local operation
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
    • G16H50/70—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for mining of medical data, e.g. analysing previous cases of other patients

Definitions

  • Physiological sensors commonly include electrodes and optical sensors.
  • ECG sensors are commonly implemented as a set of electrodes to measure electrical signals
  • PPG sensors commonly include a light source and optical sensor to illuminate the skin and measure light absorption.
  • the raw signals measured by the physiological sensors e.g., light absorption, an electrical signal(s)
  • the raw signals may not be the signals that are of interest to a user (e.g., heart rate, ECG waveform, blood oxygen).
  • the raw signals are processed to obtain physiological data (e.g., heart rate, ECG waveform, blood oxygen).
  • the physiological data is then commonly stored and/or displayed to a user.
  • the sensor, data processing, storage and/or display functions can be performed by multiple devices operating in communication with each other, for example a wearable physiological sensor may be in communication with one or more computing devices.
  • implementations of the present disclosure include a system including: a physiological sensor module; and a mobile device including an application layer and a data access layer, wherein the mobile device is operably coupled to the physiological sensor; a processor connected to memory with computer-readable instruction stored thereon, wherein execution of the computer-readable instruction by the processor causes the processor to: receive raw physiological data from the physiological sensor; store the raw physiological data in a first memory of the data access layer; and in response to receiving a data request from the application layer at the data access layer, provide, using the data access layer, a response to the application layer, wherein the response includes a data structure of the raw physiological data.
  • implementations of the present disclosure include a system, wherein the physiological sensor module includes a plurality of physiological sensors, and wherein the raw physiological data includes a plurality of raw physiological datasets.
  • implementations of the present disclosure include a system, wherein the data structure includes data a subset of the plurality of raw physiological datasets.
  • implementations of the present disclosure include a system wherein the memory further includes instructions that cause the processor to: process the raw physiological data to obtain processed physiological data; and store the processed physiological data in a second memory of the data access layer.
  • implementations of the present disclosure include a system, wherein the raw physiological data includes light absorbance data.
  • implementations of the present disclosure include a system, wherein the raw physiological data includes electrical potential data.
  • implementations of the present disclosure include a system, wherein the processed physiological data includes blood pressure.
  • implementations of the present disclosure include a system, wherein the processed physiological data includes a single-lead ECG signal.
  • implementations of the present disclosure include a system, further including a remote device in operable communication with the mobile device, wherein the remote device includes a remote device application layer configured provide a data request to the data access layer of the mobile device and receive a response from the data access layer.
  • implementations of the present disclosure include a system, wherein the physiological sensor module includes a filter configured to filter an output of a sensor of the sensor module, and wherein the raw physiological data includes filtered data output by the filter.
  • implementations of the present disclosure include a system, wherein the raw physiological data includes both filtered data output by the filter and data output by the sensor.
  • implementations of the present disclosure include a system, wherein the data request includes a data access function.
  • implementations of the present disclosure include a computer-implemented method including: storing raw physiological data in a first memory of a data access layer; processing the raw physiological data into processed physiological data; storing the processed physiological data in a second memory of the data access layer; and selectively providing access to a data structure including the raw physiological data and/or processed physiological data using the data access layer.
  • implementations of the present disclosure include a method, wherein selectively providing access to the data structure includes outputting a data structure including raw physiological data in response to receiving a data access function. [0017] In some aspects, implementations of the present disclosure include a method, wherein the data structure including raw physiological data includes less than all the physiological data stored in the first memory of the data access layer.
  • implementations of the present disclosure include a method, wherein selectively providing access to the data structure includes outputting a data structure including processed physiological data in response to receiving a data access function.
  • implementations of the present disclosure include a method, wherein the data structure includes less than all the physiological data stored in the first memory of the data access layer.
  • implementations of the present disclosure include a method, wherein the data structure including processed physiological data includes less than all the processed physiological data stored in the second memory of the data access layer.
  • implementations of the present disclosure include a method, wherein selectively providing access to the data structure includes transmitting the data to a remote device.
  • implementations of the present disclosure include a method, wherein the data access layer is configured to only provide access to the first memory and second memory of the data access layer in response to a predetermined data access function.
  • FIG. 1A illustrates a block diagram of an example physiological sensing device, according to implementations of the present disclosure.
  • FIG. IB illustrates a block diagram of an example physiological sensing device, according to implementations of the present disclosure.
  • FIG. 1C illustrates a block diagram of an example physiological sensing device configured to supply different data to multiple applications, according to implementations of the present disclosure.
  • FIG. ID illustrates a block diagram of an example physiological sensing device configured to supply different data to multiple applications, according to implementations of the present disclosure.
  • FIG. IE illustrates an example physiological sensing device including example sensors, according to implementations of the present disclosure.
  • FIG. IF illustrates an example physiological sensing device including example sensors and data processing circuitry, according to implementations of the present disclosure.
  • FIG. 1G illustrates an example an example physiological sensing device including example sensors and data processing circuitry, according to implementations of the present disclosure.
  • FIG. 2A illustrates an example wearable/implantable sensing device including a data access layer extension, according to implementations of the present disclosure.
  • FIG. 2B illustrates an example wearable/implantable sensing device including a data access layer extension and data access layer, according to implementations of the present disclosure.
  • FIG. 3A illustrates an example wearable sensing device, communications, and server/storage/database, according to implementations of the present disclosure.
  • FIG. 3B illustrates an example wearable sensing device in operable communication with an edge computing system, according to implementations of the present disclosure.
  • FIG. 3C illustrates an example wearable sensing device in operable communication with an edge computing system, where the edge computing system is in operable communication with the sensing device, according to implementations of the present disclosure.
  • FIG. 3D illustrates an example an example wearable sensing device in operable communication with an edge computing system and a sensing device, according to implementations of the present disclosure.
  • FIG. 4A illustrates an example method of accessing data from a programming model.
  • FIG. 4B illustrates an example method of accessing data from a data access layer in the hardware and/or physical layer, according to implementations of the present disclosure.
  • FIG. 4C illustrates an example feature set of the example data access layer of FIG. 4B, according to implementations of the present disclosure.
  • FIG. 5A illustrates an example of a conventional data flow, according to implementations of the present disclosure.
  • FIG. 5B illustrates an example data flow in a system according to implementations of the present disclosure.
  • FIG. 6 illustrates an example system for performing physiological monitoring using a data access layer, according to implementations of the present disclosure.
  • FIG. 7 illustrates an example method of providing access to a data structure using a data access layer, according to implementations of the present disclosure.
  • FIG. 8 illustrates an example computing device.
  • Implementations of the present disclosure include improvements to data access and control in systems including one or more computing devices.
  • Example embodiments described herein include wearable systems with sensors that are configured to operate with one or more computing devices and/or applications to process and store patient physiological data.
  • Wearable systems and devices are used to monitor the health and performance of individuals.
  • Common wearable devices include "smartwatches” (e.g., on a person's wrist), heart rate monitoring bands (e.g., placed around a person's chest), and fitness trackers (commonly on a patient's limb, including fingers).
  • implantable devices also commonly monitor the health and performance of individuals. For example, pacemakers and glucose monitors commonly perform monitoring functions.
  • Implantable and wearable devices can collect large amounts of patient data, including important and/or sensitive physiological data.
  • implantable and wearable devices often include limited computing capabilities.
  • wearable and implantable devices can be limited in size by the location that they are worn or implanted, and/or limited in processing power by the battery capacity that can be practically implemented in the device.
  • wearable and implantable devices are often configured to operate with external computing devices.
  • wearable and implantable devices can include networking features to connect to a mobile device (e.g., a cell phone or laptop), local computing devices (e.g., a personal computer or specialized diagnostic equipment), and/or remote computing devices (e.g., networked computing devices including remote servers or a "cloud" of remote servers.)
  • the external computing devices may not include the same limitations of the wearable/implantable device, and therefore can include more processing power, storage, etc.
  • Implementations of the present disclosure address these and other problems. Implementations of the present disclosure include an alternative to the conventional programming model for access to stored data that is configured for use with physiological monitoring devices.
  • An example implementation of the present disclosure includes a data access layer that can be implemented to control access to one or more memories and configured to store raw physiological data from physiological sensors.
  • the data access layer can be further configured to process raw physiological data (e.g., to obtain a physiological measurement) and store the processed physiological data in memory of the data access layer.
  • the raw physiological data and/or processed physiological data in memory of the data access layer can selectively be provided to applications to maintain privacy and security.
  • the data access layer can be configured to only provide processed data to certain application(s) (e.g., output an average blood pressure, or peak blood pressure to a health tracking application) while providing access to some or all of the raw data to other applications (e.g., for remote health monitoring, additional data processing, and/or research purposes).
  • certain application(s) e.g., output an average blood pressure, or peak blood pressure to a health tracking application
  • the data access layer of the present disclosure provides improved systems and methods for interfacing one or more applications on a mobile or remote computing devices with sensitive physiological data collected by wearable and/or implantable medical devices.
  • the present disclosure can therefore improve privacy and/or security of physiological data.
  • FIGS. 5A and 5B illustrate a comparison of example block diagram of data flow 500 in a conventional system (FIG. 5A) vs. a data flow 550 in an example implementation of the present disclosure (FIG. 5B).
  • a hardware abstraction layer 504 is configured to provide access to device 502 (e.g., physiological sensor data).
  • the programming layer 506 in the conventional data flow 500 provides free access to the hardware abstraction layer 504 using conventional programming interfaces.
  • an application 510 in in the conventional data flow may be able to access any data provided by the device 502 to the hardware abstraction layer 504.
  • a data access layer 512 is defined according to implementations of the present disclosure.
  • the data access layer 512 includes memory to store the raw data from the device 502 and/or processed data based on the raw data from the device 502.
  • the data access layer can define data access functions that can restrict the access of some or all applications to the data stored in the memory of the data access layer 512. Accordingly, any subset of the raw data or processed data stored in the data access layer 512 can be provided (or not provided) to any applications (shown as application 510a, 510b, 510c).
  • the applications 510a, 510b, 510c are each permitted to access different subsets of the data of the data access layer, which can therefore improve security and/or privacy by preventing unauthorized access to physiological data from the device 502.
  • the system includes a physiological sensor module 610, a microcontroller 620, and a mobile device 630.
  • the physiological sensor module 610 can include any number and/or combination of physiological sensors 612. Non-limiting examples of physiological sensors 612 that can be used in the physiological sensor module 610 are described with reference to the sensor circuitry 130 of FIG. IE, for example.
  • the physiological sensor module 610 can further include wired and/or wireless communication links (e.g., the network connections 816 described with reference to FIG. 8).
  • the physiological data collected by the physiological sensor module 610 can be in any form.
  • the physiological data can be “raw” physiological data including light absorption, electrical potential, etc.
  • raw physiological data refers to the outputs of a sensor that senses any part of a person's physiology.
  • the present disclosure means that the physiological data can be unfiltered and lack the processing that is generally required to convert raw physiological data into useful physiological measurements.
  • light absorbance can be used to determine blood oxygen or other parameters, but a light absorbance measurement must be converted into a blood oxygen or other measurement to be meaningful.
  • an electrical potential measurement indicating a voltage measurement on the skin surface must be combined with many electrical potential measurements over a time period and analyzed to determine a heart rate during that time period.
  • the physiological sensor module 610 can be operably coupled (e.g., by any kind of wireless or wired network connections described herein) to a microcontroller 620, for example to provide the raw physiological data from the sensor(s) 612 to the microcontroller 620.
  • the microcontroller 620 can include any/all of the components of the computing device 800 described with reference to FIG. 8.
  • the microcontroller 620 and/or physiological sensor module 610 can be part of the same wearable device (e.g., a wristband or ring).
  • the microcontroller 620 can be part of a wearable device (e.g., a wristband or ring) or an implantable device (e.g., a pacemaker) while the physiological sensor module 610 is located on (or in) a different part of the patient and configured to wirelessly communicate with the microcontroller 620.
  • the microcontroller 620 can include a filter 622 for performing processing of the raw physiological data.
  • the microcontroller 620 can include memory 624 for storing raw and/or filtered physiological data.
  • the microcontroller 620 can be operably coupled to the mobile device 630.
  • the mobile device 630 can optionally include any/all of the components of the computing device 800 shown in FIG. 8, and the microcontroller 620 and mobile device 630 can optionally be in communication by the network device(s) described with reference to FIG. 8.
  • the raw physiological data (optionally including filtered and/or unfiltered physiological data from the sensor(s) 612) can be transmitted by the microcontroller 620 to the mobile device 630.
  • the received raw physiological data can be received by the data access layer 632.
  • the data access layer 632 includes one or more memories. As shown in FIG. 6, a first memory 634 can store the raw physiological data, and a second memory 636 can store processed physiological data.
  • the data access layer 632 can include a processor (e.g., the computing device 800 of FIG. 8) and be configured to process raw physiological data stored in the first memory 634 into processed physiological data and store the processed physiological data in the second memory 636.
  • the processed physiological data can include blood pressure estimates, an ECG signal (e.g., a singlelead ECG signal), blood glucose estimates, blood oxygen estimates, heart rate estimates, etc., which can be derived from raw physiological data.
  • the raw physiological data and/or processed physiological data can include one or more data sets.
  • the raw and/or processed physiological data can include multiple data sets corresponding to different physiological sensors 612.
  • the multiple data sets can correspond to different time periods of data from the same sensors.
  • the system can further include an application layer 638.
  • the application layer 638 can be configured to run any number of applications 510a, 510b, 510c.
  • the applications 510a, 510b, 510c can be configured to process, store, and/or display data (e.g., physiological data).
  • Applications 510a, 510b, 510c can send, using the application layer 638, data requests to the data access layer 632.
  • the data requests can include data access functions (e.g., operations to verify that the application requesting the data has the appropriate permissions to access the data).
  • the data access layer 632 can provide a data structure to the application layer 638 and thereby to one or more of the applications 510a, 510b, 510c.
  • the data structure described herein can include any or all of the data stored in the first memory 634 and/or second memory 636.
  • the data access layer 632 can be configured to limit access to based on a request provided by the applications 510a, 510b, 510c of the application layer 638.
  • the request can be configured as a data access function that the data access layer 632 selectively responds to.
  • the "data access function" can optionally be a predetermined data access function, for example a including a predetermined code or other authentication system to determine that the request for the data structure is a valid request (e.g., a request by an application or computing device that is preapproved).
  • the predetermined access function can include license information (e.g., a password or cryptographic code that indicates that the application is licensed to access the data structure that is requested).
  • a first application 510a can include a first data access function that only permits access to processed physiological data and does not permit access to raw physiological data. Accordingly, the data access layer 632 can transmit to the first application 510a a data structure including only processed physiological data.
  • the second application 510b can include a second data access function that provides access to only the most recent item of processed physiological data (e.g., the most recent estimate of blood oxygen). Accordingly, the data access layer 632 can transmit to the second application 510b a data structure including only the most recent piece of processed physiological data.
  • the third application 510c can include a third data access function that permits data to only the raw physiological data in the first memory 634 of the data access layer 632.
  • the data access layer 632 can transmit to the third application 510c a data structure including only the raw physiological data.
  • the three applications and data access functions described herein are intended only as non-limiting examples, and that any number or type of applications and data access functions are contemplated by the present disclosure.
  • a data access function can permit an application to only raw and/or processed physiological data from a subset of the sensors, and/or to specific time periods of raw and/or processed physiological data.
  • both the application layer 638 and the data access layer 632 can be implemented by the same mobile computing device 630.
  • the application layer 638 and data access layer 632 can be implemented using separate devices.
  • the application layer can be implemented using a second mobile device or personal computer (or any other computing device as described with reference to FIG. 8) that is operably coupled to the mobile device 630 by a network.
  • the system further includes a remote device 640.
  • the remote device can include any/all of the components described with reference to the computing device 800 of FIG. 8.
  • the remote device 640 can optionally be implemented using cloud computing, remote servers/storage/databases, remote computing devices, etc.
  • the remote device 640 can be configured to receive raw and/or filtered physiological data from the data access layer 632 of the mobile device 630.
  • the data access layer 632 can be configured to selectively provide access to data stored in the data access layer to the remote device 640 using data requests as described with respect to the operation of the application layer 638. It should be understood that the data access layer can provide different data to applications in the application layer and remote device, or to any number of applications and remote devices.
  • the remote device 640 can be configured to perform storage and/or processing of the raw and/or processed physiological data.
  • the remote device 640 can be configured to apply additional (e.g., more complicated or sophisticated) processing to any of the data stored in the memory of the data access layer.
  • the remote device can be configured to perform a correction or calibration on any of the physiological data to obtain corrected physiological data 642.
  • the corrected physiological data 642 can then be optionally transmitted to the data access layer 632 and/or application layer 638.
  • FIG. 7 an example computer-implemented method of using a data access layer is shown, that can be implemented for example, using the system of FIG. 6. As described with reference to FIGS. 1A-3D, the computer implemented method shown in FIG.
  • the method can include storing raw physiological data in a first memory of a data access layer.
  • the method can include processing the raw physiological data into processed physiological data.
  • the method can further include storing the processed physiological data in a second memory of the data access layer.
  • the method can further include selectively providing access to a data structure comprising the raw physiological data and/or processed physiological data using the data access layer.
  • the method can include only providing access to the first memory and/or second memory of the data access layer in response to a data access function.
  • the data access function can include a code (e.g., predetermined data access function including a predetermined password or code), or other authentication system to determine that the request for the data structure is a valid request (e.g., that the request is from a pre-approved application and/or device).
  • the predetermined access function can include license information (e.g., a password or cryptographic code that indicates that the application is licensed to access the data structure that is requested at step 740).
  • selectively providing access to the data structure can include outputting a data structure comprising raw physiological data in response to receiving a data access function.
  • the data structure provided at step 740 can optionally include less than all the processed physiological data and/or raw physiological data than is stored in the memory (e.g., the first and second memories described with reference to FIG. 6). Moreover, it should be understood that providing the data structure at step 740 can be performed within one or more memories of a device, or, alternatively or additionally, by transmitting the data structure to a remote device.
  • Figs. 1A-4C include additional non-limiting examples of systems and methods that can be used to implement the present disclosure (e.g., the systems described with reference to in FIG. 6 and method shown in FIG. 7.
  • the present disclosure includes devices and systems of, and methods implemented by, a wearable and/or an implantable physiological sensing device 102 having sensors to acquire, capture, measure, sense, detect, analyze and/or assess physiological data or information (blood pressure, glucose level or fluid state of an animal (e.g., a human to which the wearable and/or implantable device is affixed)) wherein one or more data access layers 110, executed from/in the hardware/physical layer 114 of the device, may acquire, organize, manage and/or warehouse the physiological data/data sets and/or control or manage access to such physiological data/data sets by, for example, application(s), which, for example, use, assess and/or analyze such physiological data or information.
  • appl ication(s) execute from/in the application layer(s) 104 of the
  • a data access layer 110 is an organized data structure/warehouse of one or more sets of physiological data and includes one or more functions and features that (i) define, determine, organize and/or warehouse a type of physiological data/data sets (e.g., systolic related data, diastolic related data, guardrail related data, etc.), and/or (ii) control, manage and/or determine access to the physiological data/data sets (which may or may not be organized into one or more sets of organized data structures - each set including related physiological data).
  • a type of physiological data/data sets e.g., systolic related data, diastolic related data, guardrail related data, etc.
  • control, manage and/or determine access to the physiological data/data sets which may or may not be organized into one or more sets of organized data structures - each set including related physiological data.
  • the physiological data associated with the data access layer 110 may be raw" physiological data (i.e., physiological related data which has not undergone processing but is directly output from a sensor) and/or processed data (i.e., data, which is generated by and output from a sensor, which has undergone processing operation(s), e.g., filtering, limiting, error correction, etc. and/or more involved data processing such as derivation of related physiological data from the sensor data (e.g., heart rate data based on or determined from blood pressure related data detected by and output from a sensor).
  • processed data i.e., data, which is generated by and output from a sensor, which has undergone processing operation(s), e.g., filtering, limiting, error correction, etc.
  • more involved data processing such as derivation of related physiological data from the sensor data (e.g., heart rate data based on or determined from blood pressure related data detected by and output from a sensor).
  • the plurality of functions and features of a data access layer 110 may be fixed or programmable.
  • each function and feature of the plurality may be fixed (e.g., hardwired), one-time programmable (e.g., at manufacture or set-up/initialization, e.g., via a ROM and/or fuses), or more than one-time programmable (e.g., (i) at or via power-up, startup or performance/completion of the initialization sequence/process sequence, and/or (ii) in situ (i.e., during normal operation of the wearable physiological sensing device and/or an implantable physiological sensing device).
  • the functions and features associated with a data access layer 110 may be individually configurable/programmable (e.g., either one-time or more than one-time) - for example, (i) at/during an update sequence, and/or (ii) in situ.
  • certain functions and features associated with a data access layer 110 may be individually configurable/programmable (e.g., either one-time or more than one-time) -for example, (i) at/during an update sequence, and/or (ii) in situ, and other functions and features are configurable/programmable as a group or set.
  • all combinations and permutations of configurability and non-configurability functions and features associated with a data access layer 110 are intended to fall within the scope of the present disclosure.
  • the one or more data access layers 110 execute from the hardware/physical layer 114 of the sensing device 102.
  • one or more data access layers 110 preferably reside or are stored in the hardware/physical layer 114 (e.g., temporarily or permanently stored in memory of the hardware/physical layer 114 of the sensing device 102).
  • one or more functions and features of the data access layer 110 may control, manage and/or determine access to one or more subsets of data of a data access layer 110. In this way, access to the data of a data access layer 110 by one or more applications (e.g., application(s) that run in or execute from application layer 104 of the sensing device 102) may be managed or controlled (e.g., on a permissions or license/subscription basis).
  • the sensing device 102 may selectively control access of the data access layer 110, and data thereof, as well as additional security, performance and/or computational bandwidth to developers of applications of or residing in the application layer(s) 104 which, in turn, facilitates a sensing device 102 having greater security, higher performance and improved computational bandwidth.
  • data security is managed by one or more of the applications of the application layer(s) 104 (applications that executed in the application layer(s)) 104.
  • Executing the code of the data access layer 110, in the physical layer of the wearable or implantable physiological sensing device 102, to acquire or compile one or more data sets of the data access layer 110 provides additional security features via controlling, managing, limiting and/or restricting access to the sensor device and similarly controlling, managing, limiting and/or modulating the exposure or availability of data, via transmission of such data from the hardware layer to the application layer 104, that are acquired, captured, measured, detected, and/or sensed by one or more physiological sensors of the device to, for example, predetermined applications in the application layer 104.
  • access to and control of the code of data access layer(s) 110, and the data of such data access layers(s) 110 facilitates implementing access levels, privilege control and/or authentication control for application(s)/user(s).
  • executing such code of one or more data access layers 110 in the physical layer of the physiological sensing device 102 may further enhance security for the same reason(s) as set forth above.
  • locating the code of one or more data access layers 110 in the physical layer of the physiological sensing device 102 may provide even more security. Indeed, application developers may benefit from such an architecture by relying on faster feature development while also building upon or enhancing the security features of the device layer.
  • the data access layer 110 includes both data organization, storage/warehousing as well as one or more functions and features that (i) define and determine a type of physiological data of one or more data sets and/or (ii) access to and control of the data of such data sets.
  • the functions and features of the data access layers 110, and access thereto may be defined, modified and/or changed by, for example, the operator, device manufacturer and/or system manager (e.g., over the air (OTA) and/or via point-to-point communication).
  • OTA over the air
  • features of the data access layers(s) 110, and the access to the data of the data access layers(s) 110 may also be controlled or managed by the operator, device manufacturer and/or manager.
  • Each of the functions, features, and data access/control may be defined, modified, controlled and/or managed as a group (or one or more sub-groups) or individually/separately.
  • the hardware/physical layer 114 of such devices are abstracted as programming models for software applications (e.g., the device software 108 shown in FIGS. 1A-3D).
  • a programming model is an abstraction (usually a set of functions or a library of functions) provided by a hardware platform to enable or facilitate device access to software applications executing in the application layer 104.
  • firmware 112 e.g., software included in embedded systems.
  • applications residing/executing in the application layer 104 of conventional devices organize the data in local and remote data storage (e.g., memory residing in the wearable or implantable physiological sensing device 102) and computational functions are controlled, scheduled and/or driven by those applications which execute in the application layer 104.
  • local and remote data storage e.g., memory residing in the wearable or implantable physiological sensing device 102
  • an "application” is a program which resides and executes/runs in the application layer 104, for example, Windows, Android and iOS.
  • These programs are one or more layers above the hardware abstraction layer 106 and rely on elements such as device drivers or libraries or SDKs (or similar methods) to interact with or receive data from the hardware/physical layers (e.g., from the sensors of the hardware/physical layers).
  • the functions and features implemented by the data access layer 110 are not "applications” that execute/run in the application layer 104 of the sensing devices 102 of the present disclosure but are functions and features implemented/provided by the data access layer 110 which execute/run in the hardware/physical layer 114 of the sensing device 102 (and, e.g., are temporarily or permanently stored in memory of the hardware/physical layer).
  • the data access layer 110 acquires, organizes, manages and/or warehouses physiological data/data sets and/or, in one embodiment, controls or manages access to such physiological data by, for example, applications that execute/run in the application layer 104 of the device.
  • the applications that execute in the application layer 104 of the physiological sensing device 102 may, for example, assess and/or analyze such physiological data.
  • the functions provided by the data access layer 110 are not "applications” that execute/run in the application layer(s) 104 of the sensing devices 102 of the present disclosure but are functions performed or provided by the data access layer 110 which are stored in the hardware/physical layer 114 of the sensing device 102 (e.g., temporarily or permanently stored in memory of the hardware/physical layer) and, in one embodiment, available to and may be accessed by one or more applications of the application layer 104 of the device.
  • FIGURES 4A and 4B illustrate an exemplary programming model wherein the application is executed from the application layer 104 (FIGURE 4A) and an exemplary functions or operations (set forth in pseudo code) implemented with a data access layer 110 that is executed from and/or stored in the hardware/physical layer 114 (e.g., temporarily or permanently stored in memory of the hardware/physical layer) of the sensor device (FIGURE 4B).
  • FIGURE 4C illustrates exemplary functions or operations (set forth in pseudo code) implemented with a data access layer 110 associated with data acquired from sensor(s) employed to generate/detect data related to blood pressure sensors (e.g., pulse rate sensors based on photoplethysmogram (PPG) technology; such sensors are optically-based and can obtain plethysmograms that may be employed to detect/determine blood volume changes in the microvascular bed of tissue via illuminating the skin, via LED(s), and measuring changes in light absorption, via photodetector(s)).
  • blood pressure sensors e.g., pulse rate sensors based on photoplethysmogram (PPG) technology
  • PPG photoplethysmogram
  • a wearable sensing device 302 is an electronic device or apparatus that is and/or can be attached to and/or worn by a human including, but not limited to, a device that is and/or can be temporarily attached to and/or worn by a human as accessories (e.g., watch, bracelet, pendant, patch, and/or eye glasses) or is and/or can be embedded in clothing, a mechanism or an attachment that is configured to be disposed on or worn by a human.
  • an implantable device is an electronic device or apparatus that is introduced, inserted, implanted and/or embedded into or onto a human's body (e.g., an implantable cardioverter defibrillator or an implantable glucose sensor in a human).
  • a wearable sensing device 302 may interact, interface (e.g., by an interface 304) and/or communicate with, receive data from, and/or provide data to an implantable physiological sensing device (e.g., implanted or embedded in a human) or remote circuitry (circuitry which is remote from the wearable sensing device 302), and/or sense, detect, analyze and/or assess physiological data of an animal based on such communication and/or such data from the implantable physiological sensing device or remote circuitry.
  • an implantable physiological sensing device e.g., implanted or embedded in a human
  • remote circuitry circuitry which is remote from the wearable sensing device 302
  • FIGURES 1A and IB illustrate, in block diagram form, exemplary embodiments of physiological sensing device 102 (e.g., a wearable and/or an implantable physiological sensing device) to acquire, capture, measure, sense, detect, analyze and/or assess physiological data or information (blood pressure, glucose level or fluid state of an animal (e.g., a human)) wherein a data access layer 110, the code of which is executed from/in the hardware/physical layer 114 of the sensing device 102, organizes and/or warehouses data acquired, captured, measured, detected, and/or sensed by one or more physiological sensors of the device and may selectively control or manage access to the data access layer 110, and data/data sets thereof; here, the sensing device 102 (for example, via input from an operator, device manufacturer and/or system manager) may selectively control access to the data/data sets of the associated data access layer 110 by, for example, application(s) operating and/or executing in the application layer(s) 104 of the device which, for example,
  • FIGURES 1C and ID illustrate, in block diagram form, exemplary embodiments of physiological sensing device (e.g., a wearable and/or an implantable physiological sensing device) to acquire, capture, measure, sense, detect, analyze and/or assess physiological data or information (blood pressure, glucose level or fluid state of an animal (e.g., a human))
  • physiological data or information blood pressure, glucose level or fluid state of an animal (e.g., a human)
  • a data access layers 110 executed from the hardware/physical layer 114 of the device, organizes and/or warehouses data acquired, captured, measured, detected, and/or sensed by one or more physiological sensors of the device and may, in this embodiment, selectively control or manage access of the data/data sets associated with the data access layer 110 by application(s) operating and/or executing in the application layer(s) 104 of the sensing device 102 which, for example, assess or analyze physiological data or information;
  • the sensing device 102 (for example, via input from an operator, device manufacturer and/or
  • Application 2 122b may access physiological data/data set(s) ("DMx" 124a) of the data access layer, and Application x may access physiological data/data set(s) ("DMy" 124b) of the data access layer 110; as mentioned above, code to acquire data of the data access layers 110 executes from the hardware/physical layer 114 of the device and, in addition thereto, may be stored in the hardware/physical layer 114 of the device, for example, during manufacture or test such that code associated with the data access layers(s) 110 are preloaded prior to use by the user and/or during set-up by the user; in this illustrative embodiment, communication circuitry (not illustrated) in the sensing devices 102 facilitates communication (e.g., via an Intranet and/or Internet), with one or more remote servers/computers, storage systems and/or databases to, for example, receive one or and/or transmit one or more data access layers 110; notably, such communication circuitry may, in addition thereto or in lieu thereof, communicate (i.e., receive and/or
  • FIGURES 1E-1G illustrate, in block diagram form, exemplary embodiments of physiological sensing device (e.g., a wearable and/or an implantable physiological sensing device) including sensor circuitry 130 (which includes one or more sensors) to acquire, capture, measure, sense and/or detect physiological data or information of an animal (e.g., a human) wherein the data access layer 110, executed from the hardware/physical layer 114 of the device, may receive and organize "raw" physiological data and/or processed data based on the "raw" physiological data that are acquired, captured, measured, detected, and/or sensed by one or more physiological sensor(s) of the device; notably, Inset A illustrates, in block diagram form, exemplary physiological sensor(s) to determine, sense, detect, assess and/or obtain data/information which is representative of physiological condition of the user, according to at least certain embodiments of the present disclosure; in one embodiment, one or more physiological sensor(s) may be incorporated in and/or coupled to the exemplary physiological sensing device (for example, using the
  • the data access layer 110 may acquire, organize, manage and/or warehouse the physiological data (and/or data/data sets related thereto) and/or control or manage access to such physiological data (and/or related data/data sets), according to at least certain embodiments of the present disclosure.
  • FIGURES 2A and 2B illustrate, in block diagram form, exemplary embodiments of physiological sensing device (e.g., a wearable physiological sensing device and/or an implantable physiological sensing device) to acquire, capture, measure, sense, detect, analyze and/or assess physiological data or information (blood pressure, glucose level or fluid state of an animal (e.g., a human)) wherein, in addition to the hardware/physical layer 114 of the device acquiring and/or providing one or more data access layers 110 to the applications in the application layer(s) 104 of the device which, for example, assess or analyze physiological data or information, the sensing device 102 receives one or more data access layer extensions 202, having data associated therewith that may be imported, merged and/or integrated with data associated with data access layers(s) 110 of the sensing device 102 thereby forming or providing a composite or combined new data access layer (e.g., a continuous blood pressure monitor may import or merge data from a source such as an electro cardiogram and offer novel features) notwithstanding
  • FIGURES 3A-3D illustrate, in block diagram form, exemplary embodiments of communication to a physiological sensing device (labeled as a "wearable sensing device 302" - although the embodiment is applicable to an implantable physiological sensing device as well) that is capable of acquiring, capturing, measuring, sensing, detecting, analyzing and/or assessing physiological data or information (see, e.g., FIGURES 1A-1C, 2A and 2B) from the Internet or remote processing system (e.g., one or more servers in the "cloud” 306) and, in another embodiment, directly or more directly from another sensing device 312 (e.g., FIGURES 3C and 3D) which transmits one or more data access layer extensions 202 that may be employed by the wearable sensing device 302 to (i) generate, provide or present a composite or combined new data access layer 110 (see FIGURES 2A and 2B), and/or (ii) perform additional functions that are specific or particular to the user associated with the wearable sensing device
  • a dehydration alert may be issued to a person diagnosed with orthostatic hypotension; and/or, an alert may be issued to a person having a history or arrhythmias when that person is exposed to high pollution environments
  • a data access layer 110 which is "personalized" to or associated with the user that is an aggregate of multiple sources from, for example, multiple sensor devices (whether or not one, some or all of such sensor devices are (i) wearable or implantable and/or (ii) particularly associated with or acquiring data unique to the user);
  • the communication may be two- way wherein the wearable/implantable physiological sensing device 302may transmit, output and/or provide data (e.g., in real-time), via the Internet or other communication network (e.g., over the air (OTA)), corresponding to the state/status and/or change in state/status of one or more,
  • OTA over the air
  • FIGURES 4A and 4B illustrate an exemplary programming model wherein the application is executed from the application layer 104 (FIGURE 4A) and an exemplary function or an operation (set forth in pseudo code) implemented with a data access layer 110 that is executed from and/or stored in the hardware/physical layer 114 (e.g., temporarily or permanently stored in memory of the hardware/physical layer) of the sensor device (FIGURE 4B); a comparison of FIGURES 4A and 4B illustrates an exemplary difference between an exemplary application developed with a programming model versus an exemplary application developed with a data access layer 110 in pseudo code (e.g., which is stored and/or executed in the hardware/physical layer 114 of a physiological sensing device); and
  • FIGURE 4C illustrates exemplary functions/features that can be associated with a data access layer (e.g., the data access layers described with reference to FIGS. 1A-3D, 5B, 6, and 7) which generates data sets associated with the functions/features; the code associated with the data access layer 110 is executed from and/or stored in the hardware/physical layer 114 (e.g., temporarily or permanently stored in memory of the hardware/physical layer) of the sensor device.
  • a data access layer e.g., the data access layers described with reference to FIGS. 1A-3D, 5B, 6, and 7
  • the code associated with the data access layer 110 is executed from and/or stored in the hardware/physical layer 114 (e.g., temporarily or permanently stored in memory of the hardware/physical layer) of the sensor device.
  • the present disclosure are directed to devices and systems of, and methods implemented by, a wearable physiological sensing device and/or an implantable physiological sensing device having sensors to acquire, capture, measure, sense, detect, analyze and/or assess physiological data or information (blood pressure, glucose level or fluid state of an animal (e.g., a human to which the wearable and/or implantable device is affixed)) wherein a data access layer 110 , executed from/in the hardware/physical layer 114 of the device, may acquire, organize, manage and/or warehouse the physiological data (and/or data/data sets related thereto) and/or control or manage access to such physiological data (and/or related data/data sets) by, for example, application(s) that execute in/from the application layer(s) 104 of the device.
  • physiological data or information blood pressure, glucose level or fluid state of an animal (e.g., a human to which the wearable and/or implantable device is affixed)
  • a data access layer 110 executed from/in the hardware/physical layer 114
  • the application(s) may use, assess and/or analyze such physiological data or information.
  • the code corresponding to the application(s) execute from the application layer(s) 104 of the device whereas the code corresponding to the data access layer 110 executes from/in the hardware/physical layer 114 of the device.
  • a data access layer 110 can include an organized data structure/warehouse of one or more sets of physiological data and includes one or more functions and features that (i) warehouse, organize, define and determine a type of physiological data of one or more data sets (e.g., systolic related data, diastolic related data, guardrail related data, etc.), and/or (ii) control, manage and/or determine access to the data (which may or may not be organized into one or more sets of organized data structures - each set including related physiological data). (See, e.g., FIGURE 1A, Inset A).
  • the devices and systems of, and methods implemented by, a wearable or implantable physiological sensing device include one or more data access layers 110 having one or more functions and features that, in one embodiment, facilitate or enable communication and interaction with, for example, application(s) operating in the application layer 104 of the device. These functions and features are similar to "controls" of the programming model typically provided to application(s) of the application layers 104.
  • the data access layer in one embodiment, include one or more access functions and features that define, determine, facilitate and/or enable communication and interaction between data/data sets associated with the data access layer 110 and, for example, a ppi ication (s) operating or executing in the application layer 104 of the device. (See, e.g., FIGURE 1A).
  • the physiological data associated with the data access layer 110 can be "raw" physiological data (e.g., physiological related data which has not undergone processing but is directly output from a sensor).
  • the physiological data associated with the data access layer 110 may be processed data (i.e., data, generated by and output from a physiological sensor, which has undergone one or more processing operations, e.g., filtering, limiting, error correction, and/or more involved data processing such as derivation of related physiological data from the sensor data (e.g., heart rate data based on or determined from blood pressure related physiological data detected by and output from the sensor (e.g., a PPG sensor))).
  • processing operations e.g., filtering, limiting, error correction, and/or more involved data processing
  • derivation of related physiological data from the sensor data e.g., heart rate data based on or determined from blood pressure related physiological data detected by and output from the sensor (e.g., a PPG sensor)
  • the plurality of functions and features of a data access layer 110 can be fixed or programmable.
  • each function and feature of the plurality may be fixed (e.g., hardwired), one-time programmable (e.g., at manufacture or set-up/initialization, e.g., via a ROM and/or fuses), or more than one-time programmable (e.g., (i) at or via power-up, startup or performance/completion of the initialization sequence/process sequence, and/or (ii) in situ (i.e., during normal operation of the physiological sensing device).
  • one-time programmable e.g., at manufacture or set-up/initialization, e.g., via a ROM and/or fuses
  • more than one-time programmable e.g., (i) at or via power-up, startup or performance/completion of the initialization sequence/process sequence, and/or (ii) in situ (i.e., during normal operation
  • the functions and features associated with a data access layer 110 may be individually configurable/programmable (e.g., either one-time or more than one-time) -for example, (i) at/during an update sequence, and/or (ii) in situ.
  • certain functions and features associated with a data access layer 110 can be individually configurable/programmable (e.g., either one-time or more than one-time) - for example, (i) at/during an update sequence, and/or (ii) in situ, and other functions and features are configurable/programmable as a group or set.
  • the functions and features of the data access layer 110 can be defined, modified and/or changed by, for example, the operator, device manufacturer and/or system manager (e.g., over the air (OTA) and/or via point-to-point communication).
  • features of the data access layers, and the access to the data of the data access layers(s) 110 may also be controlled or managed by the operator, device manufacturer and/or manager.
  • Each of the functions, features, and data access/control may be defined, modified, controlled and/or managed as a group (or one or more sub-groups) or individua I ly/sepa rate ly.
  • all combinations and permutations of configurability and non-configurability functions and features associated with a data access layer 110 are intended to fall within the scope of the present disclosure.
  • the one or more data access layers 110 execute from the hardware/physical layer 114 of the sensing device.
  • the code of the data access layer 110 (which define the function(s) and feature(s) of the data access layer 110 and/or control, manage and/or determine access to the data/data sets associated with the data access layer 110) executes in the hardware/physical layer 114 of the wearable or implantable physiological sensing device and the data/data sets associated with the data access layer 110 are stored, managed and/or maintained in the hardware/physical layer.
  • the code of the data access layer 110 is preferably stored in the hardware/physical layer 114 of the sensing device (e.g., temporarily or permanently stored in memory of the hardware/physical layer).
  • executing the code of the data access layer 110 , in the physical layer of the physiological sensing device, to acquire, manage and/or store data/data sets of physiological related information associated with the data access layer 110 may provide additional security features via controlling, managing, limiting and/or restricting access to the physiological data/data sets (which are obtained from the sensors of the device) and similarly controlling, managing, limiting and/or modulating the exposure or availability of data, via transmission of such data from the hardware layer to the application layer 104, that are acquired, captured, measured, detected, and/or sensed by one or more physiological sensors of the device to, for example, predetermined applications in the application layer 104.
  • locating or storing the code of data access layer(s) 110 in the physical layer of the wearable or implantable physiological sensing device may provide even more security.
  • the data access layer 110 may be preloaded prior to normal operation (e.g., at manufacture, at or via power-up or start-up, and/or during an initialization sequence) and/or may be installed or enable in situ (i.e., during normal operation of the wearable sensing device 302 and/or an implantable physiological sensing device).
  • the physiological sensing device may receive new/updated data and/or data access layers 110 from the Internet or remote processing system (e.g., one or more servers in the "cloud” 306 or on the "edge" of the "cloud” 308 (i.e., edge computing) - over the air (OTA) and/or point-to-point communications) for use in the sensing device 102 during operation.
  • data/datasets and/or code of a data access layer 110 may be received and/or downloaded, by the sensing device 102, from an external server, storage and/or database, and stored in, for example, the device memory 116.
  • the code of the data access layer 110 may execute in/from the hardware/physical layer 114 and may be associated with new data/data sets to be generated by the sensing device 102 and/or data/data sets received/downloaded from, for example, the Internet or remote processing system for use in the sensing device 102 during operation.
  • the wearable or implantable physiological sensing device may transmit and/or upload data/data sets, which have been generated, organized, warehoused by data access layer 110 operating in the sensing device 102, from the sensing device 102 to remote circuitry.
  • the physiological sensing device may transmit new/updated data and/or modified data access layers 110 to the Internet or remote processing system (e.g., one or more servers in the "cloud” 306 or on the "edge” of the "cloud” 308 - over the air (OTA)) for use in, for example, assessing the physiological data or information of the user (e.g., blood pressure, glucose level or fluid state of an animal (e.g., a human user)) acquired, captured, measured, detected, and/or sensed by one or more physiological sensors of the sensing device 102 during operation.
  • the physiological data or information of the user e.g., blood pressure, glucose level or fluid state of an animal (e.g., a human user)
  • the data access layer 110 in addition to acquiring, organizing, managing and/or warehousing the physiological data (or data/data sets related thereto), or in lieu thereof, may control or manage access to such data by, for example, application(s) operating or executing in the wearable or implantable physiological sensing device.
  • the data access layer 110 may include functions and features that selectively (for example, via input from an operator, device manufacturer and/or system manager) control access to the data/data sets associated with the data access layer 110.
  • the data access layer 110 includes access level and privilege functionality that controls or limits access of the application(s), operating or executing in the physiological sensing device, to one or more (or all) data sets organized, managed and/or warehoused by the data access layer 110.
  • the data access layer 110 operating in a wearable or implantable physiological sensing device may be programmed/configured to control or manage access and/or use by Applications 1, 2 and x to selected data/data sets associated with the data access layer 110. That is, the functions and features of the data access layer 110 may restrict/limit access of Application 1 122a, which is executing or operating on/in the sensing device 102, to only the physiological data/data set DMx 124a of associated with the data access layer 110. Similarly, the access and/or use by Application 2 122b may be restricted/limited to the physiological data/data set DMy 124b of the data access layer 110.
  • the physiological data/data set DMx 124a may be different from the physiological data/data set DMy 124b.
  • Application x may be permitted to access and/or use the physiological data/data set DMz 124c associated with the data access layer 110.
  • the physiological data/data set DMz 124c may be different from the physiological data/data sets DMx 124a and DMy 124b.
  • the data access layer 110 operating in a wearable or implantable physiological sensing device may include functions and features that acquire, organize, manage and/or warehouse the physiological data/data sets (and/or data/data sets related thereto) of:
  • one or more of the functions and features of the data access layer 110 may manage, control or determine access by one or more (or all) applications (for example, operating in the sensing device 102) to data/data set(s) associated with the data access layer 110.
  • the data access layer 110 may limit/restrict Application 1 122a to access and/or use of only data/data sets of features 1-4 (i.e., DMx 124a in the illustrative embodiment), whereas Application 2 122b may access and/or use only data/data sets of features 3-6 (i.e., DMy 124b in the illustrative embodiment), and Application x may access and/or use data/data sets associated with all of the features of the data access layer 110 (i.e., features 1-8 - DMz 124c in the illustrative embodiment).
  • the functions and features of the data access layer 110 that manage, control or determine access by one or more (or all) applications/users to data/data set(s) associated with the data access layer 110 may be based on any criteria/criterion now known or later developed.
  • the criteria/criterion may be based on subscription, authentication, privilege, operator, device manufacturer and/or system manager.
  • the application operating in the application layer 104 may have access to the same or different data/data set(s) associated with the data access layer 110
  • the data access layer 110 may limit/restrict Application 1 122a and Application 2 122b to access and/or use of only data/data sets of features 1-4 (i.e., DMx 124a in the illustrative embodiment), whereas Application x may access and/or use only data/data sets of features 3-6 (i.e., DMy 124b in the illustrative embodiment).
  • the sensing device 102 may receive new/updated data access layers from the Internet or remote processing system (e.g., one or more servers in the "cloud” 306 or on the "edge" of the "cloud” 308 (i.e., edge computing) - over the air (OTA)) that modify access by one or more (or all) applications operating in the application layer 104 of the sensing device 102.
  • the manage and control of the access functions and features of the data access layer 110 may be modified, for example, in situ, whereby the data/data sets available or accessible to one or more applications operating on the sensing device 102 may change.
  • the subscription, authentication and/or privilege of a given application may change thereby allowing access to certain data/data sets or denying access to certain data/data sets.
  • Remote access to and/or use of data/data sets of a data access layer 110 operating in a given sensing device 102 may be controlled similarly. That is, access and/or use by remote circuitry (e.g., remote processing system such as one or more servers 118 in the "cloud” 306 or on the "edge" of the "cloud” 308 - over the air (OTA)) may be based on subscription, authentication, privilege, operator, device manufacturer and/or system manager - and may be modified in the same manner as described above with respect to applications operating on the sensing device 102. For the sake brevity, such discussion will not be repeated.
  • remote circuitry e.g., remote processing system such as one or more servers 118 in the "cloud” 306 or on the "edge" of the "cloud” 308 - over the air (OTA)
  • OTA over the air
  • the wearable/implantable physiological sensing device includes sensor circuitry 130, having one or more sensors, to acquire, capture, measure, sense and/or detect physiological data or information of the user (e.g., blood pressure, glucose level or fluid state of an animal (e.g., a human)) wherein such data is representative of a physiological condition (e.g., current or historical) of the user to which the device is affixed.
  • physiological data or information of the user e.g., blood pressure, glucose level or fluid state of an animal (e.g., a human)
  • the physiological sensor(s) determine, sense, detect, assess and/or obtain data/information which is representative of physiological condition of the user, according to at least certain embodiments of the present disclosure.
  • one or more physiological sensor(s) may be incorporated in and/or coupled to the exemplary wearable/implantable physiological sensing device (e.g., physically, electrically and/or optically coupled, including wired and/or wirelessly coupled), wherein the data access layer 110 may acquire, organize, manage and/or warehouse the physiological data (and/or data/data sets related thereto) and/or control or manage access to such physiological data (and/or related data/data sets), according to at least certain embodiments of the present disclosure.
  • the data access layer 110 may acquire, organize, manage and/or warehouse the physiological data (and/or data/data sets related thereto) and/or control or manage access to such physiological data (and/or related data/data sets), according to at least certain embodiments of the present disclosure.
  • wearable/implantable physiological sensing device including sensor circuitry 130 (which includes one or more physiological sensors) to acquire, capture, measure, sense and/or detect physiological data or information of an animal (e.g., a human).
  • sensor circuitry 130 which includes one or more physiological sensors
  • FIGURE IE illustrates, in block diagram form, exemplary physiological sensor(s) to determine, sense, detect, assess and/or obtain data/information which is representative of physiological condition of the user.
  • any physiological sensor, and data generated and output thereby, now known or later developed are intended to fall within the scope of the present disclosure wherein such physiological sensor may be incorporated in and/or coupled to the physiological sensing device (e.g., physically, electrically and/or optically coupled, including wired and/or wirelessly coupled), and the data access layer 110 operating in the device may acquire, organize, manage and/or warehouse the physiological data (and/or data/data sets related thereto) and/or control or manage access to such physiological data (and/or related data/data sets).
  • the physiological sensing device e.g., physically, electrically and/or optically coupled, including wired and/or wirelessly coupled
  • the data access layer 110 operating in the device may acquire, organize, manage and/or warehouse the physiological data (and/or data/data sets related thereto) and/or control or manage access to such physiological data (and/or related data/data sets).
  • the data access layer 110 executed from the hardware/physical layer 114 of the device, may receive and organize "raw" physiological data acquired, captured, measured, detected, and/or sensed by one or more physiological sensor(s) of the device. (See, e.g., FIGURE IE).
  • the data access layer 110 executed from the hardware/physical layer 114 of the device, may receive and organize processed physiological data which is based on the "raw" physiological data generated and/or output by the sensor circuitry 130 (e.g., one or more sensors). (See, e.g., FIGURE IF).
  • data processing circuitry 130 e.g., one or more sensors.
  • FIG. IF data processing circuitry
  • the data access layer 110 executed from the hardware/physical layer 114 of the physiological sensing device may be "raw" physiological data (i.e., physiological related data which has not undergone processing but is directly output from a sensor) and processed data (i.e., data, which is generated by and output from a sensor, which has undergone processing operation(s), e.g., filtering, limiting, error correction, etc.
  • the and/or more involved data processing such as correlating the physiological data from the sensor(s) to a physiological condition of the user and/or derivation of related physiological data from the sensor data (e.g., heart rate data based on or determined from blood pressure related data detected by and output from a sensor).
  • related physiological data e.g., heart rate data based on or determined from blood pressure related data detected by and output from a sensor.
  • the functions and features associated with a data access layer 110 may be individually configurable/programmable (one-time or more than onetime), or configurable/programmable as sub-groups (each sub-groups including one or more functions and features associated with a data access layer), or configurable/programmable as one set of functions and features associated with a data access layer 110.
  • Such configurable/programmable function(s) and feature(s) of the data access layer 110 may be programmable, configurable and/or reconfigurable in situ (i.e., during normal operation of the wearable physiological sensing device and/or an implantable physiological sensing device) by, for example, the device operator, device manufacturer and/or system manager.
  • functions of the data access layer 110 may be defined, modified and/or changed (e.g., updated) by, for example, the operator, device manufacturer and/or manager (e.g., over the air (OTA) and/or via point-to-point communication). (See, e.g., FIGURE IB).
  • features of the data access layers 110, and the access thereto may be controlled or managed by the operator, device manufacturer and/or manager.
  • Each of the set of functions and features, and access thereto may be modified, controlled and/or managed as a group (or one or more sub-groups) or individual ly/separately.
  • the data access layer(s) 110 may be replaced/augmented by distributed network storage elements or via a cloud computing device.
  • the one or more of the data access layers 110 are stored or reside in local/resident memory (i.e., memory of the sensing device 102) and code thereof is executed from the hardware/physical layer. (See, e.g., FIGURES 1A and IB).
  • the data access layer 110 stored in the wearable sensing device 302 and/or implantable sensing device may be supported by a set of functions and features via the manufacturer, operator and/or service provider which may include one, some or all of the following functions/features:
  • the device manufacturer, operator and/or service provider may control and/or modulate under what circumstance(s) access is provided, if at all, to each of the programming and data access layers or combination thereof.
  • the device manufacturer, operator and/or service provider may control and/or modulate when access is provided, if at all, to each of the programming and data access layers 110 or combination thereof.
  • the device manufacturer, operator and/or service provider may provision or provide this access control from time-to-time, from user-to-user and/or on an application basis.
  • Consistency and persistence across storage elements for the data access layer 110 may control consistency and persistence across storage elements for the data access layer 110.
  • the device manufacturer, operator and/or service provider may define, control and/or choose, for instance, the circumstances of access of the data of a data access layer 110 from the remote memory/storage (e.g., a cloud "copy") until completion of a transaction.
  • the device manufacturer, operator and/or service provider may implement a memory/data "flush” or clear operation of certain portions of local storage and maintain data of the data access layer 110 in remote memory/storage (e.g., the cloud) - thereby maintaining (e.g., storing and/or updating) a cloud version of the data access layer 110 only.
  • remote memory/storage e.g., the cloud
  • maintaining e.g., storing and/or updating
  • the output of the computational functions/operations may be stored in one or more new/other/different data access layers 110 that are stored in the sensing device 102.
  • the data of such data access layer 110 extensions may be accessed or employed, in one or more ways, operations, functions and/or techniques described above (see Items 1-7 immediately above), by one or more programming model(s) and/or application model(s) executed in the programming layer(s).
  • the data of the data access layer 110 generated via the output of the computational functions/operations may be stored in the wearable sensing device 302 and/or implantable sensing device and may also be supported by a set of policy features via the manufacturer or service provider which may include one, some or all of the immediately above policy features.
  • the set of policy features (including, e.g., Item 1 and/or Item 2) associated with a data access layer extension 202 may be the same as or different from the associated data access layer 110 (i.e., the data access layer of which the data access layer extension 202 relates to or is imported/merged with).
  • executing code of the data access layer 110, in the physical layer of the wearable or implantable sensing device, to organize, warehouse, define and determine data/data sets provides security advantages via controlling, managing, limiting and/or restricting access to critical features of the sensor device and similarly controlling, managing, limiting and/or modulating the exposure or availability of data/data sets, via transmission of such data from the hardware layer to the application layer 104, that are acquired, captured, measured, detected, and/or sensed by one or more physiological sensors of the device to, for example, predetermined applications in the application layer 104.
  • access to data access layer(s) 110 managed, stored, generated and/or accumulated via code, executed in the physical layer of the wearable or implantable sensing device facilitates implementing access levels, privilege control and/or authentication control for application(s)/user(s).
  • executing such code of the data access layer 110 in the physical layer of the wearable or implantable sensing device may further enhance security. Indeed, application developers may benefit from such an architecture by relying on faster feature development while also building upon or enhancing the security features of the device layer. (See, Item 4 above).
  • the functions and features of the data access layers 110, and access thereto may be defined, modified and/or changed by remotely, for example, via an operator, device manufacturer and/or manager (e.g., over the air (OTA) and/or via point-to-point communication, e.g., via wired communications).
  • OTA over the air
  • point-to-point communication e.g., via wired communications.
  • Each of the set of functions, features, and access thereto may be modified, controlled and/or managed as a group (or one or more sub-groups) or individually/separately.
  • the data/data sets of the data access layers 110, and the access thereto may be controlled or managed remotely, for example, by the operator, device manufacturer and/or manager.
  • the physiological sensing device may receive new/updated data and/or data access layers 110 remotely, for example, from the Internet or other remote processing system (e.g., one or more servers 118 in the "cloud” 306 or on the "edge" of the "cloud” 308 (i.e., edge computing) - over the air (OTA)) for use in the sensing device 102 during operation.
  • the Internet or other remote processing system e.g., one or more servers 118 in the "cloud” 306 or on the "edge” of the "cloud” 308 (i.e., edge computing) - over the air (OTA)
  • OTA over the air
  • the physiological sensing device may transmit new/updated data and/or modified data access layers 110 to remote processing circuitry, for example, via the Internet (e.g., one or more servers in the "cloud” 306 or on the “edge” of the "cloud” 308 - over the air (OTA)) for use in, for example, assessing the physiological data or information of the user (e.g., blood pressure, glucose level or fluid state of an animal (e.g., a human user)) acquired, captured, measured, detected, and/or sensed by one or more physiological sensors of the sensing device 102 during operation).
  • the Internet e.g., one or more servers in the "cloud” 306 or on the "edge” of the "cloud” 308 - over the air (OTA)
  • OTA over the air
  • the physiological sensing device in addition to executing code of a data access layer 110 in the hardware/physical layer 114 of the device to generate, organize and/or warehouse data/data sets, may receive one or more data access layer extensions 202, having data/data sets associated therewith that may be imported, merged and/or integrated with data/data sets associated with other data access layer(s) 110 thereby providing or presenting a composite and/or combined new data access layer 110 (e.g., a continuous blood pressure monitor may import/merge data from a source such as an electro cardiogram and offer novel features).
  • the programming model(s) associated with such data access layer extension 202 may be the same or different (e.g., a continuous blood pressure sensor/monitor having a data access layer 110 (and associated programming model).
  • the programming model(s) associated with the data access layer extension 202 may import/merge data associated with the data access layer extension 202 that originates from a physiological sensor that is different from the physiological sensor associated with the data access layer 110 that is/was "resident" in the physiological sensing device (i.e., the "original" data access layer executing in the hardware/physical layer).
  • data originating from a first sensor/monitor e.g., electrocardiogram
  • data associated with a second sensor/monitor e.g., blood pressure sensor/monitor
  • the programming model associated with the first sensor/monitor may be different from the programming model associated with the resident in the physiological sensing device (e.g., blood pressure sensor/monitor)
  • communication circuitry (not illustrated) in the physiological sensing device 102 facilitates communication (e.g., via an Intranet and/or Internet), with (i) one or more remote servers/computers, storage systems and/or databases and/or (ii) one or more other sensor devices (not illustrated) to, for example, transmit data/data sets of one or more data access layer extensions 202.
  • the sensing device may "personalize" or associate data from multiple physiological sensing devices (each having data access layer(s) 110 and associated programming model(s)) with, for example, a particular human/user of the physiological sensing device.
  • data associated with one or more data access layer extensions 202 may be stored in the memory of the physiological sensing device wherein the output of the data access layer extension(s) 202 may be available to the hardware/physical layer 114 and/or the application layer 104 of the device during start-up and/or operation.
  • the physiological sensing device may also (i) receive new/updated data access layer extension(s) 202 from the Internet or remote processing system (e.g., one or more servers in the "cloud” 306 or on the "edge” of the “cloud” 308 (i.e., edge computing) - over the air (OTA)) for use in the sensing device 102 during operation and/or (ii) transmit new/modified data access layer extension(s) 202 to the Internet or remote processing system (e.g., one or more servers in the "cloud” 306 or on the "edge” of the “cloud” 308 - over the air (OTA)) for use in, for example, assessing the physiological data or information of the user (e.g., blood pressure, glucose level or fluid state of an animal (e.g., a human user)) acquired, captured, measured, detected, and/or sensed by one or more physiological sensors of the sensing device 102 during operation.
  • the physiological data or information of the user e.g., blood pressure, glucose level or
  • the data of a particular user of the physiological sensing device may be aggregated into a personalized data access layer 110 wherein additional functions that are specific to that individual/user may be generated and implemented. For example, based on analysis of past or previous events/episodes, a dehydration alert may be issued to a person diagnosed with orthostatic hypotension. In another example, a person with history of arrhythmias may be alerted when exposed to high pollution environments. In current practice, these alerts require the activation of devices such as smartphones/cloud services and/or user intervention (e.g., automatic cardio defibrillators ("ICDs”)).
  • ICDs automatic cardio defibrillators
  • the alerts are often generated via an application executed in the application layer 104 of smartphones/cloud services.
  • generating an extension of a data access layer 110 that merges with data associated with a data access layer 110 of a physiological sensing device as described herein e.g., the code of the data access layer 110 executes in the hardware/physical layer of the device
  • the alert may be generated directly and/or autonomously from the physiological sensing device - thereby saving time and effort for the user while enhancing clinical benefit.
  • two, three, four or more devices generating and/or monitoring physiological data of a given individual may, via a plurality of data access layers 110 and/or data access layer extensions 202, and data associated therewith, may be imported or merged to form a data access layer, which generates data/data sets, that is personal or unique to a given individual or user of the device (e.g., importing/merging/aggregating physiological related data associated with an individual from multiple devices or sources).
  • a physiological sensing device may communicate with (transmit and/or receive) devices and circuitry that is/are external and/or remote to the sensing device.
  • a physiological sensing device is capable of acquiring, capturing, measuring, sensing, detecting, analyzing and/or assessing physiological data or information (see, e.g., FIGURES 1A-1C, 2A and 2B) from the Internet or remote processing system (e.g., one or more servers on the edge of the "cloud” 308 and/or in the "cloud” 306).
  • the wearable or implantable physiological sensing device may directly or more directly from another physiological sensing device (e.g., FIGURES 3C and 3D) which transmits one or more data access layer 110 extensions that may be employed by the wearable sensing device 302 to (i) generate, provide or present a composite, unified or combined new data access layer 110 (see FIGURES 2A and 2B).
  • another physiological sensing device e.g., FIGURES 3C and 3D
  • FIGURES 3C and 3D another physiological sensing device which transmits one or more data access layer 110 extensions that may be employed by the wearable sensing device 302 to (i) generate, provide or present a composite, unified or combined new data access layer 110 (see FIGURES 2A and 2B).
  • the wearable or implantable physiological sensing device may be configured to perform additional functions that are specific or particular to the user associated with the wearable sensing device 302 using data access layers 110 generated by the sensor device and data access layer extension(s) 202 (e.g., a dehydration alert may be issued to a person diagnosed with orthostatic hypotension; and/or, an alert may be issued to a person having a history or arrhythmias when that person is exposed to high pollution environments).
  • a dehydration alert may be issued to a person diagnosed with orthostatic hypotension; and/or, an alert may be issued to a person having a history or arrhythmias when that person is exposed to high pollution environments.
  • the wearable or implantable physiological sensing device in one embodiment may generate and/or implement a data access layer 110 which is "personalized" to or associated with the user that is, as described above, an aggregate of multiple sources from, for example, multiple sensor devices (whether or not one, some or all of such sensor devices are (i) wearable or implantable and/or (ii) particularly associated with or acquiring data unique to the user); notably, the communication may be two-way wherein the wearable/implantable physiological sensing device may transmit, output and/or provide data (e.g., in real-time), via the Internet or other communication network (e.g., over the air (OTA)), corresponding to the state/status and/or change in state/status of one or more, or all of the sensor data being monitored/acquired as well as the physiological characteristics of the user associated with the sensor device and/or the analysis/analyses thereof to one or more remote processing systems.
  • OTA over the air
  • the physiological sensing device may transmit updated data and/or data access layers 110 to Internet or remote processing system (e.g., one or more servers in the "cloud” 306 or on the “edge” of the “cloud” 308) for storage and/or additional processing.
  • Internet or remote processing system e.g., one or more servers in the "cloud” 306 or on the “edge” of the “cloud” 308 for storage and/or additional processing.
  • the physiological sensing device may (i) receive new/updated data, data access layers 110 and/or data access layer extensions 202 from the Internet or remote processing system (e.g., one or more servers in the "cloud” 306 - over the air (OTA)) for use in the sensing device 102 during operation and (ii) transmit new/updated data, modified data access layers 110 and/or data access layer extensions 202 to the Internet or remote processing system (e.g., one or more servers in the "cloud” 306 or on the "edge” of the "cloud” 308 - over the air (OTA)) for use in, for example, assessing the physiological data or information of the user (e.g., blood pressure, glucose level or fluid state of an animal (e.g., a human user)) acquired, captured, measured, detected, and/or sensed by one or more physiological sensors of the sensing device 102 during operation.
  • the physiological data or information of the user e.g., blood pressure, glucose level or fluid state of an animal (e.g.,
  • the present disclosure have been described and illustrated in the context a physiological sensing device, having a data access layer 110 which executes from/in the hardware/physical layer 114 of the device.
  • the data access layer 110 has largely/extensively described in the context of (i) acquiring, organizing, managing and/or warehousing the data/data sets associated physiological sensors and/or (ii) controlling or managing access to such data/data sets
  • the functions and features of the data access layers 110 of the present disclosure are configurable to employ or access other hardware resources of the sensing device 102 including for example, communication circuitry, as well as resources in the cloud 306.
  • the code associated with the data access layer 110 has often been described in the context of executing in the hardware/physical layer 114 of the sensing device 102, the code of the data access layer 110 may execute/run on any available/accessible processor resource (e.g., CPU plus memory resource).
  • the sensing device 102 of the present disclosure may be configurable to be distributed across a plurality of storage elements, and local and/or remote and implement policies for synchronization across them.
  • each device of the distribution includes a resident data access layer 110 that is suitable for that aspect of the distributed system.
  • the data access layer 110 of the present disclosure is encapsulated and/or separate from the applications that execute in the application layer 104 of the physiological sensing device.
  • the functions and features associated with a data access layer 110 may be individually configurable/programmable (for example, one time or more than one time), or configurable/programmable as groups or sub-groups (each group including one or more functions and features associated with a data access layer 110), or configurable/programmable as one set of functions and features associated with a data access layer 110.
  • Such configurable/programmable function(s) and feature(s) of the data access layer 110 for example, access to particular data or particular data set(s), may be programmable, configurable and/or reconfigurable in situ (i.e., during normal operation of the wearable physiological sensing device and/or an implantable physiological sensing device) by, for example, the device operator, device manufacturer and/or system manager.
  • access to particular data or one or more particular data sets by an application operating in the application layer 104 of the physiological sensing device may be controlled (enabled or disabled), in situ and wirelessly - that is, over the air (OTA).
  • functions and features of the data access layer 110 e.g., access to data/data sets
  • the one or more of the data access layers 110 are stored or reside in local/resident memory (i.e., memory of the physiological sensing device) and the code thereof is executed in/from the hardware/physical layer 114 of that sensing device 102.
  • the data access layers(s) 110 can be replaced/augmented by distributed network storage elements or via a cloud computing device.
  • control circuitry e.g., one or more processors (suitably programmed)
  • the control circuitry is employed to program the robust type memory cell during initialization or at start-up, and/or in situ such that the output of the robust type memory cell is employed to establish or implement a mode of operation or function in, for example, the logic tile.
  • circuits, circuitry and techniques disclosed herein may be described using computer aided design tools and expressed (or represented), as data and/or instructions embodied in various computer-readable media, in terms of their behavioral, register transfer, logic component, transistor, layout geometries, and/or other characteristics.
  • Formats of files and other objects in which such circuit, circuitry, layout and routing expressions may be implemented include, but are not limited to, formats supporting behavioral languages such as C, Verilog, and HLDL, formats supporting register level description languages like RTL, and formats supporting geometry description languages such as GDSII, GDSIII, GDSIV, CIF, MEBES and any other formats and/or languages now known or later developed.
  • Computer- readable media in which such formatted data and/or instructions may be embodied include, but are not limited to, non-volatile storage media in various forms (e.g., optical, magnetic or semiconductor storage media) and carrier waves that may be used to transfer such formatted data and/or instructions through wireless, optical, or wired signaling media or any combination thereof.
  • Examples of transfers of such formatted data and/or instructions by carrier waves include, but are not limited to, transfers (uploads, downloads, e-mail, etc.) over the Internet and/or other computer networks via one or more data transfer protocols (e.g., HTTP, FTP, SMTP, etc.).
  • circuits, circuitry and techniques disclosed herein may be represented via simulations using computer aided design and/or testing tools.
  • the simulation of the circuits, circuitry, layout and routing, and/or techniques implemented thereby may be implemented by a computer system wherein characteristics and operations of such circuits, circuitry, layout and techniques implemented thereby, are imitated, replicated and/or predicted via a computer system.
  • the present disclosure is also directed to such simulations of the inventive circuits, circuitry and/or techniques implemented thereby, and, as such, are intended to fall within the scope of the present disclosure.
  • the computer-readable media corresponding to such simulations and/or testing tools are also intended to fall within the scope of the present disclosure.
  • circuitry means, among other things, a circuit (whether integrated or otherwise), a group of such circuits, one or more processors, one or more state machines, one or more processors implementing software, one or more gate arrays, programmable gate arrays and/or field programmable gate arrays, or a combination of one or more circuits (whether integrated or otherwise), one or more state machines, one or more processors, one or more processors implementing software, one or more gate arrays, programmable gate arrays and/or field programmable gate arrays.
  • the present disclosure is neither limited to any single aspect nor embodiment thereof, nor to any combinations and/or permutations of such aspects and/or embodiments. Moreover, each of the aspects of the present disclosure, and/or embodiments thereof, may be employed alone or in combination with one or more of the other aspects of the present disclosure and/or embodiments thereof.
  • references herein to "one embodiment” or “an embodiment” (or the like) means that a particular feature, structure, or characteristic described in connection with the embodiment may be included, employed and/or incorporated in one, some or all of the embodiments of the present disclosure.
  • the usages or appearances of the phrase “in one embodiment” or “in another embodiment” (or the like) in the specification are not referring to the same embodiment, nor are separate or alternative embodiments necessarily mutually exclusive of one or more other embodiments, nor limited to a single exclusive embodiment.
  • the present disclosure is neither limited to any single aspect nor embodiment thereof, nor to any combinations and/or permutations of such aspects and/or embodiments.
  • a wearable sensing device 302 is an electronic device or apparatus that is and/or can be attached to and/or worn by a human including, but not limited to, a device that is and/or can be temporarily attached to and/or worn by a human as accessories (e.g., watch, bracelet, pendant, patch, and/or eye glasses) or is and/or can be embedded in clothing, a mechanism or an attachment that is configured to be disposed on or worn by a human.
  • an implantable device is an electronic device or apparatus that is introduced, inserted, implanted and/or embedded into or onto a human's body (e.g., an implantable cardioverter defibrillator or an implantable glucose sensor in a human).
  • a wearable sensing device 302 may interact, interface (e.g., by an interface 304) and/or communicate with, receive data from, and/or provide data to an implantable sensing device (e.g., implanted or embedded in a human) or remote circuitry (circuitry which is remote from the wearable sensing device 302), and/or sense, detect, analyze and/or assess physiological data of an animal based on such communication and/or such data from the implantable sensing device or remote circuitry.
  • an implantable sensing device e.g., implanted or embedded in a human
  • remote circuitry circuitry which is remote from the wearable sensing device 302
  • the present disclosure includes a physiological sensing device, and processes and/or operations implemented thereby, including a data access layer 110 having functions and features:
  • [00138] that is configurable to interact with program(s) and a programming model when applications (i.e., those programs which are in the application layers 104 of paradigms such as Windows, Android and iOS which are one or more layers above the hardware abstraction layer 106 and rely on elements such as device drivers or libraries or SDKs (or similar methods) to interact with or receive data from the hardware/physical layers) interact with hardware devices; and/or
  • applications i.e., those programs which are in the application layers 104 of paradigms such as Windows, Android and iOS which are one or more layers above the hardware abstraction layer 106 and rely on elements such as device drivers or libraries or SDKs (or similar methods) to interact with or receive data from the hardware/physical layers
  • applications i.e., those programs which are in the application layers 104 of paradigms such as Windows, Android and iOS which are one or more layers above the hardware abstraction layer 106 and rely on elements such as device drivers or libraries or SDKs (or similar methods) to interact with or receive data from the hardware/physical layers
  • each device of the distribution includes a resident data access layer 110 that is suitable for that aspect of the distributed system; and/or
  • connection should be broadly interpreted to include direct or indirect (e.g., via one or more conductors and/or intermediate devices/elements (active or passive) and/or via inductive or capacitive coupling)) unless intended otherwise (e.g., use of the terms “directly connect” or “directly connected”).
  • the terms “a” and “an” herein do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item.
  • first,” “second,” and the like, herein do not denote any order, quantity, or importance, but rather are used to distinguish one element/circuit/feature from another.
  • an example computing device 800 upon which the methods described herein may be implemented is illustrated. It should be understood that the example computing device 800 is only one example of a suitable computing environment upon which the methods described herein may be implemented.
  • the computing device 800 can be a well-known computing system including, but not limited to, personal computers, servers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network personal computers (PCs), minicomputers, mainframe computers, embedded systems, and/or distributed computing environments including a plurality of any of the above systems or devices.
  • Distributed computing environments enable remote computing devices, which are connected to a communication network or other data transmission medium, to perform various tasks.
  • computing device 800 In its most basic configuration, computing device 800 typically includes at least one processing unit 806 and system memory 804. Depending on the exact configuration and type of computing device, system memory 804 may be volatile (such as random access memory (RAM)), non-volatile (such as read-only memory (ROM), flash memory, etc.), or some combination of the two. This most basic configuration is illustrated in FIG. 8 by dashed line 802.
  • the processing unit 806 may be a standard programmable processor that performs arithmetic and logic operations necessary for operation of the computing device 800.
  • the computing device 800 may also include a bus or other communication mechanism for communicating information among various components of the computing device 800.
  • Computing device 800 may have additional features/functionality.
  • computing device 800 may include additional storage such as removable storage 808 and non-removable storage 810 including, but not limited to, magnetic or optical disks or tapes.
  • Computing device 800 may also contain network connection(s) 816 that allow the device to communicate with other devices.
  • Computing device 800 may also have input device(s) 814 such as a keyboard, mouse, touch screen, etc.
  • Output device(s) 812 such as a display, speakers, printer, etc. may also be included.
  • the additional devices may be connected to the bus in order to facilitate communication of data among the components of the computing device 800. All these devices are well known in the art and need not be discussed at length here.
  • the processing unit 806 may be configured to execute program code encoded in tangible, computer-readable media.
  • Tangible, computer-readable media refers to any media that is capable of providing data that causes the computing device 800 (i.e., a machine) to operate in a particular fashion.
  • Various computer-readable media may be utilized to provide instructions to the processing unit 806 for execution.
  • Example tangible, computer- readable media may include, but is not limited to, volatile media, non-volatile media, removable media 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.
  • System memory 804, removable storage 808, and non-removable storage 810 are all examples of tangible, computer storage media.
  • Example tangible, computer- readable recording media include, but are not limited to, an integrated circuit (e.g., field- programmable gate array or application-specific IC), a hard disk, an optical disk, a magnetooptical disk, a floppy disk, a magnetic tape, a holographic storage medium, a solid-state device, RAM, ROM, electrically erasable program 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.
  • an integrated circuit e.g., field- programmable gate array or application-specific IC
  • a hard disk e.g., an optical disk, a magnetooptical disk, a floppy disk, a magnetic tape, a holographic storage medium, a solid-state device, RAM, ROM, electrically erasable program read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks
  • the processing unit 806 may execute program code stored in the system memory 804.
  • the bus may carry data to the system memory 804, from which the processing unit 806 receives and executes instructions.
  • the data received by the system memory 804 may optionally be stored on the removable storage 808 or the non-removable storage 810 before or after execution by the processing unit 806.
  • the computing device In the case of program code execution on programmable computers, the computing device 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.
  • API application programming interface
  • Such programs may be implemented in a high level procedural or object- oriented programming language to communicate with a computer system.
  • 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 it may be combined with hardware implementations.

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Medical Informatics (AREA)
  • Public Health (AREA)
  • General Health & Medical Sciences (AREA)
  • Epidemiology (AREA)
  • Primary Health Care (AREA)
  • Data Mining & Analysis (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Pathology (AREA)
  • Databases & Information Systems (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)

Abstract

Un système donné à titre d'exemple comprend : un module de capteur physiologique et un dispositif mobile comprenant une couche d'application et une couche d'accès à des données, le dispositif mobile étant couplé de manière fonctionnelle au capteur physiologique ; un processeur connecté à une mémoire avec une instruction lisible par ordinateur stockée sur celui-ci, l'exécution des instructions lisibles par ordinateur amenant le processeur à recevoir des données physiologiques brutes provenant du capteur ; à stocker les données physiologiques brutes dans une première mémoire de la couche d'accès à des données ; et en réponse à une demande de données provenant de la couche d'application au niveau de la couche d'accès à des données, à fournir une réponse à la couche d'application comprenant une structure de données. Un procédé donné à titre d'exemple consiste à : stocker des données physiologiques brutes dans une première mémoire d'une couche d'accès à des données, traiter les données physiologiques brutes, stocker les données physiologiques traitées dans une seconde mémoire de la couche d'accès à des données, et fournir sélectivement un accès aux données physiologiques à l'aide d'une couche d'accès à des données.
PCT/US2024/041912 2023-08-10 2024-08-12 Dispositif de détection physiologique ayant une couche d'accès à des données, et ses procédés de fonctionnement Pending WO2025035147A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363518869P 2023-08-10 2023-08-10
US63/518,869 2023-08-10

Publications (2)

Publication Number Publication Date
WO2025035147A2 true WO2025035147A2 (fr) 2025-02-13
WO2025035147A3 WO2025035147A3 (fr) 2025-05-01

Family

ID=94535329

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/041912 Pending WO2025035147A2 (fr) 2023-08-10 2024-08-12 Dispositif de détection physiologique ayant une couche d'accès à des données, et ses procédés de fonctionnement

Country Status (1)

Country Link
WO (1) WO2025035147A2 (fr)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9877650B2 (en) * 2012-09-20 2018-01-30 Masimo Corporation Physiological monitor with mobile computing device connectivity
AU2014338867A1 (en) * 2013-10-25 2016-05-19 Ares Trading S.A. Patient care system reporting adherence to treatment regimen
WO2018218310A1 (fr) * 2017-06-01 2018-12-06 Alerte Digital Health Pte. Ltd. Système numérique de surveillance de la santé
CN112236788A (zh) * 2018-06-04 2021-01-15 3M创新有限公司 具有主动工人感测和评估的个人防护设备和安全管理系统
US11978555B2 (en) * 2020-04-08 2024-05-07 CareBand Inc. Wearable electronic device and system using low-power cellular telecommunication protocols
US20220395237A1 (en) * 2021-06-11 2022-12-15 Medtonic, Inc. Automatic ambulatory subject monitoring

Also Published As

Publication number Publication date
WO2025035147A3 (fr) 2025-05-01

Similar Documents

Publication Publication Date Title
US20240312620A1 (en) Dynamic report building
JP5410968B2 (ja) 医療測定機器のためのカスタマイズされたデータ収集プログラミング
US10733266B2 (en) Systems and methods of providing patient apps
US20100049006A1 (en) Medical signal processing system with distributed wireless sensors
Ungurean et al. An internet of things framework for remote monitoring of the healthcare parameters
WO2013012862A1 (fr) Analyse de données de santé en temps réel à l'aide de dispositif mobile
Janckulık et al. Personal Telemetric System–Guardian
US20210386360A1 (en) Detecting an ictal of a subject
WO2025035147A2 (fr) Dispositif de détection physiologique ayant une couche d'accès à des données, et ses procédés de fonctionnement
WO2026087929A1 (fr) Système de surveillance de patient à distance, amélioré par l'ia
BR102022005303A2 (pt) DISPOSITIVO E SISTEMA BASEADO EM INTERNET DAS COISAS (IoT) PARA COLETA, PROCESSAMENTO E ANÁLISE DE SINAIS VITAIS DE UM USUÁRIO
Cecilia-Valentina et al. Data collection from smartwatches and smartbands
Gurrapu et al. IoT based Medical Monitoring System using Node MCU
Oprea PHD THESIS SUMMARY
Zulkarnain et al. Monitoring System Heartbeat Detection Based on Internet of Things (IoT) IBM Bluemix
Xie Study of a Low-cost Heart rate Remote monitoring system using the Arduino platform
Manso et al. Real-Time Pervasive Monitoring System for Ambulatory Patients
Nagpal et al. Predicting Early Signs of Heart Attack by Implementing Smart Health Monitoring Using IoMT Devices
CN118717105A (zh) 血糖数据采集方法、装置、设备、存储介质及程序产品
Roy Heart Rate Monitoring System Using IoT: Hardware Implementation and Data Storage in Django
Krejcar et al. The real code migration on portable devices for personal biotelemetric systems
Ansari et al. The Smart Healthcare Initiative: Blood Glucose Prediction with Wireless Sensor Network
Jurik et al. Bidirectional ECG Monitoring with an Event Detection Policy Engine
Lee Framework and Algorithms for Wearable Medical Applications
Faustina et al. Study of a Low-cost Heart rate Remote monitoring system using the Arduino platform

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24852917

Country of ref document: EP

Kind code of ref document: A2

WWE Wipo information: entry into national phase

Ref document number: 2024852917

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24852917

Country of ref document: EP

Kind code of ref document: A2