Health data server device, hearing system and related methods

Abstract

The present disclosure provides a health data server device, which includes a memory, one or more interfaces, and one or more processors. The server device is configured to: obtain attachment data based on hearing data of a hearing device from an accessory device, obtain a first consent from the accessory device to share the attachment data with a healthcare platform, and share the attachment data with the healthcare platform according to the first consent.

Description

Technical Field

[0001] The present disclosure relates to health data server devices, hearing systems and related methods, including methods of operating a health data server device. Background Art

[0002] An individual's health status can be difficult to monitor, especially outside of a dedicated healthcare setting such as a hospital. For example, this can be difficult because some individuals may object to voluntarily sharing their data, such as health data. However, in the period between visits to a medical center, an individual's condition may develop and / or worsen without the healthcare professional being aware of this. Summary of the invention

[0003] Accordingly, there is a need for an improved health data server device, hearing system, and related methods for consent-based data sharing.

[0004] The present disclosure provides a health data server device. The health data server device includes a memory, one or more interfaces, and one or more processors. The server device is configured to obtain attachment data based on hearing data of a hearing device from an attachment device. The server device is configured to obtain a first consent from the attachment device to share the attachment data with a healthcare platform. The server device is configured to share the attachment data with the healthcare platform according to the first consent.

[0005] In addition, a method of operating a health data server device is disclosed. The method includes obtaining, from an accessory device, accessory data based on hearing data of a hearing device. The method includes obtaining, from the accessory device, a first consent to share the accessory data with a healthcare platform. The method includes sharing the accessory data with the healthcare platform based on the first consent.

[0006] A hearing system is also disclosed. The hearing system comprises a health data server device as disclosed herein, an accessory device as disclosed herein and a hearing device as disclosed herein.

[0007] The present disclosure can improve data privacy and improve data sharing security. The present disclosure enables hearing data of a hearing device (such as sensor data from a hearing device) to be shared to a healthcare platform via a health data server. The present disclosure enables users of hearing devices to share hearing data with healthcare professionals in a secure manner and while complying with personal data protection regulations (such as GDPR and HIPAA).

[0008] Furthermore, the present disclosure also enables users to give consent remotely and enables healthcare professionals to request permission for user data remotely in a secure manner.

[0009] An important advantage of such a health data server device is that a user can provide consent for a healthcare platform (e.g., used by a healthcare professional (e.g., a doctor)) to obtain the attachment data of the hearing device via the health data server device. This can enable 3 healthcare professionals to monitor the health status of the user, thereby enabling the healthcare professional to provide higher quality care for the user of the hearing device. For example, a healthcare professional (e.g., a doctor) can more accurately monitor the user's condition based on the attachment data shared with the healthcare platform. For example, when a new condition is diagnosed, a healthcare professional may want to be able to perform health monitoring to allow for optimal disease management. It is understandable that healthcare professionals can more accurately select relevant data by subscribing only to the types of data they think are relevant. This can, for example, address the increased information overload problem that exists within existing systems (including a large number of notifications and pop-ups that take up the time of healthcare professionals and cause them to be exhausted). In other words, it can give healthcare professionals the opportunity to use their time more purposefully while getting the best benefit from the data they want to see.

[0010] The present disclosure can improve the monitoring of a user's accessory data (eg, health data), thereby enabling healthcare professionals to diagnose patients with greater accuracy and robustness.

[0011] The present disclosure can integrate or present data (eg, attachment data) into existing healthcare platforms, thereby, for example, reducing the number of systems that need to be accessed by healthcare professionals and the number of systems that medical departments / hospitals need to maintain. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Those skilled in the art will readily appreciate the above and other features and advantages of the present invention through the following detailed description of exemplary embodiments of the present invention with reference to the accompanying drawings, in which:

[0013] Figure 1 schematically illustrates an exemplary hearing system according to the present disclosure and an exemplary health data server device according to the present disclosure, and

[0014] Figure 2A-2B A flow chart illustrating an exemplary method according to the present disclosure is shown. DETAILED DESCRIPTION

[0015] Various exemplary embodiments and details are described below with reference to the relevant drawings. It should be noted that the drawings may be drawn to scale or not to scale, and elements of similar structure or function are represented by the same reference numerals in all drawings. It should also be noted that the drawings are only for the convenience of describing the embodiments. The drawings are not intended to be an exhaustive description of the invention or a limitation on the scope of the invention. In addition, the illustrated embodiments do not need to have all aspects or all advantages shown. The aspects or advantages described in conjunction with a specific embodiment are not limited to that embodiment, but may be implemented in any other embodiment, even if not shown as such or not so clearly described.

[0016] The hearing system of the present disclosure includes, for example, a hearing device. The hearing device can be configured to be worn at the user's ear and can be a hearable device (e.g., earplugs, headphones, etc.) or a hearing aid, wherein the processor is configured to compensate for the user's hearing loss. In one or more examples or embodiments, the hearing device can be considered a hearing aid.

[0017] The hearing aid may be of the following type: behind-the-ear (BTE), in-the-ear (ITE), in-the-canal (ITC), receiver-in-the-canal (RIC) or receiver-in-the-ear (RITE). The hearing aid may be a binaural hearing aid. The hearing aid may include a first earpiece and a second earpiece, wherein the first earpiece and / or the second earpiece are earpieces as disclosed herein.

[0018] The hearing device can be configured to wirelessly communicate with one or more devices, such as with another hearing device (e.g., as part of a binaural hearing system) and / or with one or more accessory devices (such as a smartphone and / or a smartwatch). The hearing device optionally includes an antenna for converting one or more wireless input signals (e.g., a first wireless input signal and / or a second wireless input signal) into an antenna output signal. The wireless input signal can originate from an external signal source, such as a paired microphone device, a wireless television audio transmitter, and / or a distributed microphone array associated with a wireless transmitter. The wireless input signal can originate from, for example, another hearing device that is part of a binaural hearing system, and / or from one or more accessory devices.

[0019] The hearing device optionally comprises a radio transceiver coupled to the antenna to convert the antenna output signal into a transceiver input signal. Wireless signals from different external sources may be multiplexed in the radio transceiver as transceiver input signals, or provided as independent transceiver input signals at independent transceiver outputs of the radio transceiver. The hearing device may comprise multiple antennas and / or the antennas may be configured to operate in one or more antenna modes. The transceiver input signal optionally comprises a first transceiver input signal representing a first wireless signal from a first external source.

[0020] In one or more examples or embodiments, the hearing device includes a set of microphones. The set of microphones may include one or more microphones. The set of microphones includes a first microphone for providing a first microphone input signal and / or a second microphone for providing a second microphone input signal. The set of microphones may include N microphones for providing N microphone signals, where N is an integer in the range of 1 to 10. In one or more exemplary hearing devices, the number of microphones N is two, three, four, five or more. The set of microphones may include a third microphone for providing a third microphone input signal.

[0021] The hearing device optionally comprises a pre-processing unit. The pre-processing unit may be connected to the radio transceiver for pre-processing the transceiver input signal. The pre-processing unit may be connected to the first microphone for pre-processing the first microphone input signal. The pre-processing unit may be connected to the second microphone (if present) for pre-processing the second microphone input signal. The pre-processing unit may comprise one or more A / D converters for converting the analog microphone input signal into a digital pre-processed microphone input signal.

[0022] The hearing device includes a processor for processing an input signal (such as a preprocessed transceiver input signal and / or a preprocessed microphone input signal). The processor provides an electrical output signal based on the input signal entering the processor. The input terminal of the processor is optionally connected to the corresponding output terminal of the preprocessing unit. For example, the transceiver input terminal of the processor can be connected to the transceiver output terminal of the preprocessing unit. One or more microphone input terminals of the processor can be connected to corresponding one or more microphone output terminals of the preprocessing unit.

[0023] The hearing device includes a processor for processing an input signal (such as a pre-processed transceiver input signal and / or a pre-processed microphone input signal). The processor is optionally configured to compensate for the hearing loss of a user of the hearing device. The processor provides an electrical output signal based on the input signal entering the processor. The input terminal of the processor is optionally connected to the corresponding output terminal of the pre-processing unit. For example, the transceiver input terminal of the processor can be connected to the transceiver output terminal of the pre-processing unit. One or more microphone input terminals of the processor can be connected to the corresponding one or more microphone output terminals of the pre-processing unit.

[0024] The hearing system, hearing device, health data server device, healthcare platform and / or accessory device may be configured to communicate wirelessly via a wireless communication system, such as a short-range wireless communication system, such as Wi-Fi, Bluetooth (e.g., Auracast), Zigbee, IEEE 802.11, IEEE802.15, infrared, etc. The hearing system, hearing device, health data server device, healthcare platform and / or accessory device may be configured to communicate via a network, such as a global network, e.g., the Internet and / or a local area network.

[0025] The hearing system, hearing device and / or electronic device (e.g., accessory device) can be configured to communicate wirelessly via a wireless communication system, the wireless communication system being such as a 3GPP system, such as a 3GPP system supporting one or more of: New Radio (NR), Narrowband Internet of Things (NB-IoT) and Long Term Evolution - Enhanced Machine Type Communication (LTE-M), millimeter wave communication (such as millimeter wave communication within a licensed band, such as device-to-device millimeter wave communication within a licensed band).

[0026] In one or more examples or embodiments, the interface of the accessory device and / or the interface of the hearing device includes: one or more of a Bluetooth interface, a Bluetooth low energy interface, and a magnetic induction interface. For example, the interface of the accessory device and / or the interface of the hearing device may include a Bluetooth antenna and / or a magnetic induction antenna.

[0027] In one or more examples or embodiments, a hearing device as disclosed herein includes one or more sensors. One or more sensors may be configured to obtain sensor data. The sensor data may indicate a health condition of a user of the hearing device. It is understood that the hearing data may be based on the sensor data. The one or more sensors may include one or more of the following: a microphone, an optical sensor, a magnetic sensor, a galvanic sensor, a motion sensor, and a capacitive sensor. An example of an optical sensor is a photoplethysmography (PPG) sensor. An example of a galvanic sensor is an electrocardiogram (ECG) sensor and / or an electroencephalogram (EEG) sensor. A motion sensor may be considered an inertial measurement unit (IMU). A motion sensor may include an accelerometer and / or a gyroscope. A motion sensor may include a magnetic sensor such as a magnetometer. A capacitive sensor may include a capacitive microphone and / or a temperature sensor.

[0028] In one or more hearing systems, hearing devices and / or electronic devices, the one or more sensors include one or more of a physical condition sensor such as a heart rate sensor, a blood pressure sensor, a pulse sensor, a photoplethysmography (PPG) sensor, an electrocardiogram (ECG) sensor, an electroencephalogram (EEG) sensor, a bioimpedance sensor and / or a body temperature sensor. The one or more sensors of the hearing device may include a physical condition sensor such as a capacitance and / or conductivity sensor type for measuring and / or determining cognitive decline and / or atrial fibrillation.

[0029] Sensor data as disclosed herein may be obtained from one or more of the above sensors. In other words, the sensor data may be generated and / or provided by any one or more of the above sensors.

[0030] The present disclosure provides a health data server device. Such a health data server device includes a memory, one or more interfaces and one or more processors. The health data server device as disclosed herein can be regarded as, for example, an electronic device configured to provide health data services. The health data server device can be regarded as a server device for processing health data (such as health data of multiple users (e.g., hearing device users)). The health data server device as disclosed herein can be regarded as a secure interface for sharing data between the user's accessory device and the healthcare platform. For example, the health data server device can be regarded as a secure interface for sharing data between the user's hearing device (e.g., via the user's accessory device) and the healthcare platform. The health data server device can be a dedicated server device for processing the health data of the hearing device and processing the access and sharing of health data by a third party (such as, as disclosed herein The healthcare platform). The health data server device can be configured to store, manage and / or securely send and / or receive health-related information. The health data server device can be configured to deal with the sensitivity of health data and the need to comply with data protection regulations. The health data server device can take into account medically recognized algorithms to analyze data. For example, the health data server device can allow configuration of external integration through an API while maintaining a secure connection.

[0031] For example, the memory of the health data server device may be configured to store one or more of the attachment data, the hearing data, and the consent as disclosed herein.

[0032] For example, a health data server device may be considered a health data server. The terms "health data server device" and "server device" may be used interchangeably.

[0033] The server device is configured to obtain accessory data based on the hearing data of the hearing device from the accessory device, for example via an interface of the server device and / or an interface of the accessory device. Obtaining the accessory data from the accessory device may include obtaining, receiving and / or searching for the accessory data from the accessory device, for example via an interface of the accessory device and / or one or more interfaces of the health data server device.

[0034] The accessory device may be considered a primary accessory device, such as a primary accessory device of a user. For example, the accessory device may be considered an accessory electronic device. In some examples, the accessory device may include storage circuitry, processor circuitry, and / or an interface (e.g., a touch screen, one or more wireless interfaces). For example, the accessory device may be an accessory device of a user. For example, the accessory device may be a mobile phone, such as a smart phone. In some examples, the accessory device may be configured to run one or more applications. The accessory device may be configured to communicate with the hearing device, for example, via a wireless interface of the accessory device. The accessory device may be configured to collect and / or aggregate data, such as hearing data, from the hearing device. The accessory device may be configured to obtain hearing data from the hearing device. Obtaining hearing data from the hearing device may include, for example, obtaining, receiving, and / or searching for hearing data from the hearing device via an interface of the accessory device and / or an interface of the hearing device. Obtaining accessory data from the accessory device may include obtaining, receiving, and / or searching for accessory data from the accessory device.

[0035] Hearing data as disclosed herein may be considered as data obtained by a hearing device. For example, the hearing data comprises data associated with a hearing device of a user. The hearing data may be considered as user data, sensor data, health data and / or usage data of a user of the hearing device. The hearing data may include or be based on one or more of the following: hearing device settings, audio input data entering the hearing device, audio output data from the hearing device and sensor data of the hearing device. The hearing data may be associated with or indicate a hearing state and / or health state of the user. In general, the hearing data may be considered as data obtained from a hearing device, sent from a hearing device and / or generated at a hearing device.

[0036] The attachment data may, for example, include and / or be based on hearing data obtained (e.g., received and / or searched) by the accessory device, for example, from a hearing device. The attachment data may, for example, include processed hearing data (e.g., processed by the accessory device). The processed hearing data is, for example, based on hearing data of the hearing device. For example, the attachment data may include one or more health indicators indicating the health status of the user. In some examples, the attachment data includes, for example, sensor data obtained via a sensor of the hearing device. The attachment data may be derived from the hearing data. For example, the accessory device may be configured to determine or derive health data based on the hearing data. Before communicating with the health data server device, the attachment data may be stored on the accessory device for a period of time. In one or more examples or embodiments, after communicating with the health data server device, the attachment data may be deleted from the attachment device. In general, the attachment data may be regarded as data obtained from the attachment device, sent from the attachment device, and / or generated at the attachment device.

[0037] In one or more example server devices, the hearing data includes health data associated with a user of the hearing device. In one or more example server devices, the attachment data is based on the health data.

[0038] For example, a user of a hearing device may be considered as a person wearing the hearing device. In other words, the hearing data may indicate health data associated with the user of the hearing device. The hearing data may include health data, which includes information indicating the health status of the user of the hearing device. For example, the hearing device is configured to determine or derive health data based on one or more of the following: hearing device settings, audio input data entering the hearing device, audio output data from the hearing device, and sensor data of the hearing device. The health data may indicate the health status of the user of the hearing device. For example, the health data may include data indicating the following items: heart rate, body temperature, blood oxygen, blood pressure, blood sugar level, breathing rate, and brain activity, etc. The hearing data may be obtained, for example, by one or more sensors of the hearing device.

[0039] In one or more example server devices, the hearing data includes usage data of the hearing device. In one or more example server devices, the attachment data is based on the usage data.

[0040] The usage data, for example, includes information indicating the use of the hearing device by the user. For example, the hearing device is configured to obtain (such as, receive, search and / or determine) usage data indicating the use of the hearing device. The usage data can be regarded as information collected and / or recorded by the hearing device about how the user or wearer of the hearing device uses the hearing device. The usage data can provide information about the performance of the hearing device and / or the user's hearing experience. For example, the usage data can include one or more of the following: average wearing time, usage duration, volume settings and / or adjustments, program usage, battery life, voice data, and usage data associated with sensor data (e.g., accelerometer data). For example, the hearing device is configured to determine or derive usage data based on one or more of the following: hearing device settings and / or settings adjustments, audio input data entering the hearing device, audio output data from the hearing device, and sensor data of the hearing device. It is understood that the usage data can provide an indication of the health status of the user of the hearing device. It is understood that the usage data can be related to health data. In other words, additional data (such as health data) can be determined based on hearing data including usage data and sensor data and / or health data. For example, sensor data can be associated with usage data in the time domain. This can enable a determination of how trustworthy the sensor data is. The usage data can, for example, be used to set a threshold to determine how long a hearing device needs to be used before the health data server device has an indicative data sample that is worth sharing with a healthcare platform and healthcare professionals.

[0041] In one or more examples or embodiments, the accessory device is configured to obtain hearing data, for example, via an application of the accessory device and / or a wireless interface of the accessory device and / or a wireless device of the hearing device. In some examples, in order for the accessory device to obtain (e.g., receive and / or search for) hearing data, the user may need to activate an application (app) of the accessory device. In other words, the hearing device may provide (e.g., send) hearing data to the accessory device, for example, via an application of the accessory device.

[0042] For example, the accessory data may include post-processed hearing data. In other words, in some examples, obtaining the accessory data from the accessory device may include obtaining processed hearing data, such as post-processed hearing data. For example, the hearing device, the accessory device, and / or the health data server device may, for example, be configured to process (e.g., post-process) the hearing data.

[0043] In one or more examples, the accessory device can be configured to obtain (e.g., receive and / or search for) raw (e.g., unprocessed) hearing data from the hearing device. In one or more examples, the health data server device can be configured to obtain (e.g., receive and / or search for) raw (e.g., unprocessed) hearing data from the hearing device (e.g., via the accessory device).

[0044] The accessory device may, for example, post-process the raw hearing data to obtain processed hearing data, thereby obtaining the accessory data. Then, the server device may obtain the post-processed hearing data from the accessory device.

[0045] In one or more examples or embodiments, the health data server device may be configured to post-process the raw hearing data and / or the attachment data to obtain processed hearing data and / or processed attachment data, thereby obtaining health data server device data. Then, the healthcare platform may obtain the post-processed attachment data from the health data server device.

[0046] In one or more examples, the accessory data includes processed data, such as analyzed data. In other words, the accessory data may include one or more insights (e.g., conclusions) determined based on the hearing data. For example, the accessory device may be configured to process the hearing data.

[0047] In some examples, the accessory device (e.g., via an application and utilizing a processor of the accessory device) can be configured to determine one or more analyses based on the hearing data. In some examples, the hearing device can be configured to determine one or more analyses based on the hearing data. In some examples, the server device can be configured to determine one or more analyses based on the hearing data and / or the accessory data. For example, one or more analyses based on the hearing data can be provided to a healthcare platform, for example, via a server device. The one or more analyses can be viewed as analyses of a health condition of a user of the hearing device, such as analyses of health data.

[0048] In some examples, the accessory device can provide (e.g., to a user) the attachment data, for example, via an application of the accessory device. For example, a user can request (e.g., subscribe to) obtain (e.g., receive and / or search for) the attachment data via the application of the accessory device. In one or more examples or embodiments, a healthcare professional can request (e.g., subscribe to) obtain (e.g., receive and / or search for) the attachment data via the healthcare platform.

[0049] The health data server device is configured to obtain, from the accessory device and, for example, via an interface of the accessory device and / or one or more interfaces of the health data server device, a first consent to share the accessory data with the healthcare platform.

[0050] The first consent may be provided, for example, by a user of the accessory device and / or the hearing device. The first consent may be obtained, for example, by the accessory device via an application of the accessory device and forwarded to the health data server device and / or the healthcare platform. In one or more examples or embodiments, obtaining the first consent includes obtaining an indication of a first consent to share the attachment data with the healthcare platform. In other words, the health data server device may not need to obtain the first consent itself, but may receive a message indicating that the user of the hearing device has given consent to share the attachment data with the healthcare platform via the accessory device. The health data server device may then share the attachment data with the healthcare platform based on the message. The first consent may be provided by the user of the hearing device via the accessory device. Sharing the attachment data may include sharing the health data server device with the healthcare platform. The health data server device may be viewed as data generated and / or communicated by the health data server device.

[0051] In the following, an example of how a user gives consent for sharing attachment data is described. The user can provide a first consent by agreeing to share a data sharing token in an application of an attachment device. Then, the attachment device and / or the health data server device can send the data sharing token to the healthcare platform. The data sharing token can be in the form of a digital code, etc. Then, the healthcare professional can enter the data sharing token into the healthcare platform. After that, the user can be prompted on the attachment device to accept or refuse to share the attachment data with the healthcare platform, for example, the attachment device is configured to output a user interface via a display screen of the attachment device to prompt the user to accept or refuse to share the attachment data with the healthcare platform. When the user accepts sharing the attachment data with the healthcare platform on the attachment device, the attachment device can provide a first consent or a message indicating the first consent to the health data server device. Then, the health data server device is configured to share the attachment data with the healthcare platform according to the first consent. In other words, a data link can be established between the health data server device and the healthcare platform according to the first consent. In one or more examples or embodiments, the sharing of the attachment data is performed such as via a data link until the first consent is revoked and / or the healthcare platform stops the data subscription.

[0052] As disclosed herein, consent, such as first consent, second consent, third consent and / or fourth consent, may include different types of consent. For example, consent may be full consent or partial consent. For example, partial consent may be considered as time-limited consent.

[0053] The accessory device is, for example, configured to obtain the user's consent by providing the user with a selectable option indicating consent, for example, via an application of the accessory device. In some examples, the accessory device may provide a "yes" option and a "no" option, for example, via a selectable check box, a selectable option in a drop-down menu, etc. For example, if the "yes" option is selected, it may be deemed that consent is granted. For example, if the "no" option is selected, it may be deemed that consent is not granted. In other words, the health data server device may be configured to obtain a first consent from the user via the accessory device.

[0054] For example, the healthcare platform includes one or more electronic devices. For example, the healthcare platform includes one or more databases that store information associated with one or more users of hearing devices (e.g., patients). The healthcare platform, for example, includes one or more electronic devices associated with one or more healthcare professionals (e.g., doctors, general practitioners, physicians, etc.). For example, the electronic device of the healthcare platform can be a doctor's computer, where the electronic device can be configured to obtain user input from the healthcare professional (e.g., doctor). The healthcare platform can be viewed as an electronic health record system used by hospitals and / or general practitioners for routine tasks related to healthcare.

[0055] The health data server device is configured to share the attachment data with the healthcare platform according to the first consent, for example via one or more interfaces of the health data server device and / or via an interface of the healthcare platform.

[0056] In one or more examples, sharing the attachment data with the healthcare platform includes providing (eg, sending) the attachment data to the healthcare platform. In other words, the health data server device can be configured to share the attachment data in response to obtaining the first consent.

[0057] For example, a healthcare professional (e.g., a doctor) may be able to monitor a user's condition with greater accuracy based on the attached data shared with the healthcare platform.

[0058] Due to the access to the shared attachment data, the present disclosure can enable healthcare experts to see treatment responses and / or intervene in a timely manner. In some examples, based on the attachment data shared with the healthcare platform, healthcare experts can be enabled to diagnose (e.g., for medical conditions) with higher accuracy.

[0059] In one or more example server devices, the server device is configured to obtain, from the healthcare platform and, for example, via one or more interfaces of the health data server device and / or via an interface of the healthcare platform, a first request for a first permission to share attachment data with the healthcare platform.

[0060] The first request can, for example, be considered a request for a first permission to which the user can provide (such as, give) a first consent. The first request can, for example, be considered information provided or communicated, for example, by the accessory device to the user of the accessory device. For example, the first request includes a message indicating a first request for a first permission to share the attachment data with the healthcare platform. In some examples, the first request includes a message indicating a request for permission for the server device to share the attachment data with the healthcare platform. The first request can, for example, be provided by a healthcare professional (such as a doctor) associated with the healthcare platform.

[0061] For example, a healthcare professional (e.g., a doctor) may have diagnosed that a user (e.g., a patient) of a hearing device has a certain disease, or that the user is showing signs of a certain disease. The healthcare platform may obtain, for example, a first request for attachment data of a hearing device of the user from the doctor. The attachment data requested in the first request, for example, is related to a medical condition. For example, the attachment data requested in the first request may help monitor a medical condition (e.g., a health condition) of the user. In other words, the healthcare professional (e.g., a doctor) may request (e.g., require) to receive attachment data of a hearing device (e.g., subscribe to an attachment data stream).

[0062] In one or more example server devices, the server device is configured to send a first request to the accessory device.

[0063] In some examples, after the server device obtains the first request from the healthcare platform, the health data server device can provide the first request to the accessory device, such as forwarding the first request to the accessory device. In other words, the first request can be sent from the healthcare platform to the accessory device via the health data server device.

[0064] In some examples, after the accessory device obtains the first request from the server device, the accessory device can provide the first request to a user (e.g., a user of the accessory device and / or the hearing device). For example, the accessory device can display the first request as a notification (e.g., a pop-up notification, a push notification, etc.). After providing the first request to the user, the accessory device can obtain a first consent from the user, for example, in response to the first request.

[0065] For example, when the user provides a response indicating a first consent to the first request, the server device has a first permission (such as may be allowed) to share the attachment data with the healthcare platform. In other words, when the server device obtains the first consent in response to the first request, it may be deemed that the first permission has been granted (e.g., granted based on the first consent).

[0066] The first permission may be regarded as permission for the server device to share the attachment data, for example. For example, based on the first permission, the server device may share the attachment data with the healthcare platform.

[0067] In one or more example server devices, obtaining the first consent to share the attachment data with the healthcare platform includes obtaining, in response to the sent first request, from the accessory device the first consent to share the attachment data with the healthcare platform.

[0068] In one or more examples, when the server device does not obtain the first consent from the accessory device in response to the first request sent, the server device can avoid sharing the attachment data with the healthcare platform. In other words, when the first consent is not obtained or the first disapproval or the first refusal to share the attachment data is obtained instead of the first consent, it can be considered that the server device is not granted the first permission.

[0069] In some examples, the healthcare platform can obtain the hearing data via the accessory device. In some examples, the healthcare platform obtains the hearing data via the server device. In other words, sharing the accessory data can include forwarding the hearing data from the hearing device to the healthcare platform via the accessory device and the health data server device.

[0070] In one or more example server devices, the first request includes a device identifier.

[0071] In other words, obtaining the first request may include obtaining a device identifier, such as a device identifier associated with a hearing device, a user of the hearing device, and / or an accessory device of the user of the hearing device. For example, the user of the hearing device may have shared its device identifier with a healthcare practitioner (e.g., a doctor). The healthcare practitioner may then enter the device identifier into the healthcare platform. The healthcare platform may be configured to send the device identifier along with the first request to the health data server device. For example, the doctor has a label for device data and access on a user interface of the healthcare platform. The doctor may enter a device identifier found on a user's mobile application on the accessory device to identify the device to be subscribed to. The doctor may then check which data streams to receive. For example, when the device identifier is entered by the doctor, the user may see a pop-up window for confirming sharing data with the doctor, thereby allowing data to be automatically streamed from the health data server device. In one or more example server devices, the server device is configured to obtain attachment data associated with the device identifier. In one or more example server devices, the server device is configured to share attachment data with the healthcare platform. In other words, the server device may be configured to share attachment data associated with the device identifier.

[0072] The device identifier may for example be regarded as a unique identifier indicating a device, for example a hearing device. The device identifier for example comprises a code, for example a unique code for a given hearing device. For example, the device identifier may comprise a numeric code, an alphabetic code and / or an alphanumeric code.

[0073] In some examples, the device identifier is associated with a hearing device. In some examples, the device identifier is associated with and / or indicates a user of the hearing device. In some examples, the device identifier is associated with an accessory device of the user. For example, the device identifier may indicate an accessory device.

[0074] In one or more example server devices, prior to obtaining the attachment data, the server device is configured to obtain a second consent from the attachment device to obtain the attachment data. In one or more example server devices, the server device is configured to obtain the attachment data based on the second consent.

[0075] The second consent may for example be regarded as a general consent for the server device to obtain the accessory data. The second consent may for example be provided by a user of the accessory device and / or the hearing device. The second consent may for example be obtained by the accessory device via an application of the accessory device.

[0076] In one or more examples, when the server device obtains the second consent, for example, in response to the second request, the second permission can be considered to have been granted (eg, based on the second consent).

[0077] In some examples, the second consent can be provided by a user (e.g., a user of the accessory device and / or the hearing device). For example, when the user provides user input indicating the second consent to the accessory device, the server device can be considered to have the second permission (e.g., can be allowed) to obtain the accessory data (e.g., from the accessory device).

[0078] In some examples, the user of the hearing device can provide the second consent when using the hearing device for the first time (e.g., initial use of the hearing device). In one or more examples, the user of the hearing device can provide the second consent before using the hearing device for the first time (e.g., during and / or after a transfer of ownership of the hearing device, such as during and / or after purchasing the hearing device). The first consent and the second consent do not have any temporal order, they are just labels. Thus, the second consent can be provided before the first consent, and vice versa.

[0079] In one or more example server devices, the server device is configured to obtain a third consent from the healthcare platform to obtain the healthcare platform data from the healthcare platform. In one or more example server devices, the server device is configured to obtain the healthcare platform data from the healthcare platform based on the third consent.

[0080] The third consent may be provided to the healthcare platform, for example, by a healthcare expert or practitioner (e.g., a physician, doctor, etc.) or via the healthcare platform. For example, the healthcare platform may be configured to provide (e.g., send) the healthcare platform data to the server device after obtaining the third consent. In other words, when the server device obtains the third consent, it may be deemed that the third permission has been granted (e.g., granted based on the third consent).

[0081] The third permission may be, for example, considered as permission for the server device to share the healthcare platform data. For example, based on the third permission, the server device may share the healthcare platform data with the healthcare platform. In one or more examples or implementations, the third consent may be obtained in response to a third request, such as a third request from a user of the accessory device. The third request may be considered as a request from the user of the accessory device to receive the healthcare platform data.

[0082] The healthcare platform data includes, for example, data for activating one or more sensors of the hearing device. Generally speaking, the healthcare platform data can be considered as data obtained from, sent from, and / or generated at the healthcare platform. For example, the healthcare platform data can include a healthcare professional's analysis of the accessory data, such as a report and / or information to a user of the hearing device and / or the accessory device. In other words, the health data server device can enable consent-based secure two-way communication between the healthcare platform and the accessory device (such as between a user of the accessory device and a healthcare practitioner).

[0083] In one or more example server devices, the server device is configured to send the healthcare platform data to the accessory device. In other words, the health data server device can be configured to send the healthcare platform data to the accessory device in response to obtaining the third consent and / or based on the third consent.

[0084] In one or more example server devices, the healthcare platform data includes a sensor activation request for activating a sensor of a hearing device.

[0085] The hearing device, for example, comprises one or more sensors. The one or more sensors of the hearing device may, for example, be configured to obtain hearing data, such as health data. In some examples, the one or more sensors of the hearing device may be configured to obtain heart rate, body temperature, blood oxygen, blood pressure, blood sugar level, breathing rate, etc. The sensor of the hearing device may, for example, be an internal or external device of the hearing device. The hearing data (e.g., usage data and / or health data) may, for example, be considered to be generated by one or more sensors of the hearing device. In other words, the hearing data may include sensor data.

[0086] The sensor activation request may be, for example, considered as a request for activating a sensor (e.g., a sensor of a hearing device). For example, when the accessory device obtains the sensor activation request, the accessory device may be configured to activate the sensor of the hearing device. In other words, after obtaining (e.g., receiving and / or searching for) the sensor activation request from the health data server device, the accessory device may obtain data from the activated sensor of the one or more sensors of the hearing device. Activating a sensor of the one or more sensors of the hearing device based on the sensor activation request may, for example, be considered as initiating a data flow including hearing data into, for example, the accessory device. In this case, the activation of the sensor may be considered as activating the sharing of sensor data from the hearing device to the health data server device (e.g., via the accessory device) and vice versa from the health data server device to the healthcare platform. For example, the activation of the sensor may be considered as activating the recording of sensor data at the hearing device. When the sensor is activated, the hearing device may be configured to include the sensor data in the hearing data. It is understood that the sensor activation request may enable a healthcare professional to remotely and securely activate the sensor of the hearing device and / or share sensory data from the hearing device using the healthcare platform. It is understood that the user of the hearing device may have agreed to activate the sensor through the sensor activation request. For example, the user of the hearing device may provide consent in response to the sensor activation request, eg, provide sensor activation permission to the health data server device.

[0087] In one or more example server devices, sending the healthcare platform data includes sending a sensor activation request to the accessory device. In other words, the healthcare platform data may include or indicate the sensor activation request. It is understood that the health data server device may transmit the sensor activation request from the healthcare platform to the accessory device.

[0088] In some examples, after the accessory device obtains / receives the sensor activation request from the server device, the accessory device can provide the sensor activation request to a user (e.g., a user of the accessory device and / or the hearing device). For example, the accessory device can display the sensor activation request as a notification (e.g., a pop-up notification, a push notification, etc.). After providing the sensor activation request to the user, for example, the accessory device can obtain sensor activation consent from the user, for example, in response to the sensor activation request.

[0089] In one or more example server devices, the server device is configured to obtain a fourth consent to share the healthcare platform data with the accessory device. In one or more example server devices, the server device is configured to share the healthcare platform data with the accessory device based on the fourth consent.

[0090] The fourth consent can, for example, be considered as consent for the server device to share the healthcare platform data with the accessory device (e.g., provided by a user of the accessory device). For example, when the server device obtains the fourth consent, e.g., from the accessory device, the server device can be considered to have permission to share the healthcare platform data with the accessory device. For example, the user can provide user input indicating the fourth consent to the accessory device.

[0091] In one or more example server devices, the server device is configured to obtain auxiliary accessory data from an auxiliary accessory device.

[0092] In some examples, the server device can be configured to obtain (eg, receive and / or search for) auxiliary accessory data from the auxiliary accessory device, such as via an API.

[0093] An auxiliary accessory device may be considered an auxiliary accessory electronic device. In some examples, the auxiliary accessory device may include memory circuitry, processor circuitry, an interface (e.g., a touch screen), and / or one or more sensors. For example, the auxiliary accessory device may be an accessory device of a user. For example, the auxiliary accessory device may be a smart device and / or a wearable device (such as a smart watch). In some examples, the auxiliary accessory device may be configured to run one or more applications.

[0094] For example, one or more sensors of the auxiliary accessory device can be configured to obtain auxiliary accessory data. The auxiliary accessory data, for example, includes health data. The auxiliary accessory device, for example, is configured to obtain health data of a user (e.g., a user of the auxiliary accessory device, such as a user wearing a smart watch) via one or more sensors.

[0095] In some examples, the auxiliary accessory device is configured to provide the auxiliary accessory data to the healthcare platform, such as via a server device.

[0096] In one or more examples or embodiments, the auxiliary accessory device consent may be provided by a user of the accessory device for the server device to share the auxiliary accessory device data with the accessory device. For example, when the server device obtains the auxiliary accessory device consent, for example from the accessory device, the server device may be deemed to have permission (permitted) to share the auxiliary accessory device data with the accessory device. For example, the user may provide user input to the accessory device indicating the auxiliary accessory device consent. In one or more examples or embodiments, the user may provide consent on the auxiliary accessory device to allow the auxiliary accessory device to share the auxiliary accessory device data with the accessory device and / or the health data server device.

[0097] The present disclosure provides a hearing system. The hearing system includes a health data server device, such as the health data server device disclosed herein. The hearing system includes an accessory device (such as the accessory device disclosed herein) and a hearing device (such as the hearing device disclosed herein).

[0098] In one or more example hearing systems, the hearing device comprises one or more sensors for providing sensor data. In one or more example hearing systems, the hearing device is configured to send hearing data comprising the sensor data to the accessory device.

[0099] Sensor data may for example be regarded as data obtained by one or more sensors of the hearing device.In some examples, the sensor data is associated with a user of the hearing device.

[0100] In one or more examples, sending the hearing data from the hearing device to the accessory device includes sending the hearing data from the hearing device to the accessory device via a wireless and / or wired connection. In some examples, the hearing data can be sent wirelessly from the hearing device to the accessory device using near field communication, Bluetooth, etc.

[0101] In one or more example hearing systems, the hearing system includes a hearing device data server configured to store hearing data associated with a user of a hearing device.

[0102] In one or more examples, the hearing device data server is configured to obtain consent (eg, consent of a user) from the accessory device to obtain hearing data from the hearing device, eg, via the accessory device.

[0103] In some examples, the accessory device is configured to share hearing data associated with a user of the hearing device with a hearing device data server (e.g., after obtaining the user's consent). In some examples, the hearing device data server can be considered a hearing device data storage server. In some examples, the hearing device data server can be part of a data storage device that includes, for example, one or more servers configured to store hearing data.

[0104] It is to be understood that any definitions and terms used in the description regarding the health data server device also apply to the corresponding functions in the hearing system and the operating method of the health data server device as disclosed herein.

[0105] The present disclosure also discloses a method of operating a health data server device. The method includes obtaining, from an accessory device, accessory data based on hearing data of a hearing device. The method includes obtaining, from the accessory device, a first consent for sharing the accessory data with a healthcare platform. The method includes sharing the accessory data with the healthcare platform based on the first consent.

[0106] In one or more example methods, the method includes obtaining a first request from a healthcare platform for a first permission to share attachment data with the healthcare platform. In one or more example methods, the method includes sending the first request to an accessory device. In one or more example methods, obtaining the first consent to share the attachment data with the healthcare platform includes obtaining, in response to the sent first request, from the accessory device the first consent to share the attachment data with the healthcare platform.

[0107] In one or more example methods, the first request includes a device identifier. In one or more example methods, the method includes obtaining attachment data associated with the device identifier. In one or more example methods, the method includes sharing the attachment data with a healthcare platform.

[0108] In one or more example methods, prior to obtaining the attachment data, the method includes obtaining a second consent from the accessory device to obtain the attachment data. In one or more example methods, the method includes obtaining the attachment data based on the second consent.

[0109] In one or more example methods, the method includes obtaining a third consent from the healthcare platform to obtain the healthcare platform data from the healthcare platform. In one or more example methods, the method includes obtaining the healthcare platform data from the healthcare platform based on the third consent.

[0110] In one or more example methods, the method includes sending the healthcare platform data to an accessory device.

[0111] In one or more example methods, the healthcare platform data includes a sensor activation request for activating a sensor of the hearing device. In one or more example methods, sending the healthcare platform data includes sending the sensor activation request to the accessory device.

[0112] In one or more example methods, the method includes obtaining a fourth consent to share the healthcare platform data with the accessory device. In one or more example methods, the method includes sharing the healthcare platform data with the accessory device in accordance with the fourth consent.

[0113] In one or more example methods, the hearing data includes health data associated with a user of the hearing device. In one or more example methods, the attachment data is based on the health data.

[0114] In one or more example methods, the hearing data comprises usage data of the hearing device. In one or more example methods, the attachment data is based on the usage data.

[0115] In one or more example methods, the method includes obtaining auxiliary accessory data from an auxiliary accessory device.

[0116] It is noted that descriptions and features of the functionality of the health data server device (such as the functionality that the health data server device is configured for) also apply to the method, and vice versa. For example, a description of a health data server device configured for determining also applies to, for example, a method of operating the health data server device, where the method includes a determining step, and vice versa.

[0117] Figure 1 An example hearing system according to the present disclosure is schematically shown, such as a hearing system 2. The hearing system 2 comprises a health data server device 30 according to the present disclosure. The health data server device 30 comprises a memory 30A, one or more interfaces 30B, and one or more processors 30C. The hearing system 2 comprises a hearing device, such as a hearing device 40 as disclosed herein. The hearing device 40 may comprise a memory 40A, an interface 40A, a processor 40C, and one or more sensors 40D. The system 2 comprises an accessory device, such as an accessory device 10 as disclosed herein. The accessory device 10 may comprise a memory 10A, an interface 10B, a processor 10C, and one or more sensors 10D. Figure 1 A healthcare platform is shown, such as a healthcare platform 20 as disclosed herein. It is understood that the healthcare platform 20 may not be part of the system 2. The healthcare platform 20 includes a memory 20A, an interface 20A (such as one or more interfaces), and a processor 20C.

[0118] Optionally, the one or more sensors 40D and / or the one or more sensors 10D include one or more of the following: a microphone, an optical sensor, a magnetic sensor, a galvanic sensor, a motion sensor, and a capacitive sensor. In one or more example hearing systems, the hearing device 40 is configured to send 42 hearing data including sensor data to the accessory device 10.

[0119] Optionally, the interface 10B of the accessory device 10 and / or the interface 40B of the hearing device 40 includes one or more of the following: a Bluetooth interface, a Bluetooth low energy interface, and a magnetic induction interface. For example, the interface 10B of the accessory device 10 and / or the interface 40B of the hearing device 40 may include a Bluetooth antenna and / or a magnetic induction antenna.

[0120] The server device 30 is configured to obtain accessory data based on hearing data of the hearing device 40 from the accessory device 10, for example via the interface 30B and / or the interface 10B. Obtaining hearing data from the hearing device 40 may include, for example, obtaining, receiving and / or searching hearing data from the hearing device 40 via the interface 40B and / or the interface 10B. Obtaining accessory data from the accessory device 10 may include, for example, obtaining, receiving and / or searching accessory data from the accessory device 10 via the interface 30B and / or the interface 10B. In one or more examples or embodiments, obtaining accessory data from the accessory device 10 may include, for example, obtaining 13, 24 the accessory data from the accessory device 10 via a network 50 (such as a global network, such as the Internet and / or a local area network). In one or more examples or embodiments, obtaining accessory data from the accessory device 10 may include obtaining 34 the accessory data directly from the accessory device 10.

[0121] In one or more examples or embodiments, the accessory device 10 is configured to obtain hearing data 42, for example, via an application of the accessory device 10 and / or an interface 10B (such as a wireless interface of the accessory device 10) and / or an interface 40B (such as a wireless interface of the hearing device 40). In some examples, the user needs to activate the application of the accessory device 10 in order for the accessory device 10 to obtain (such as, receive and / or search for) hearing data. In other words, the hearing device 40 can provide 42 (e.g., send) hearing data to the accessory device 10, for example, via the application of the accessory device 10.

[0122] In one or more examples, the accessory device 10 can be configured to obtain 42 (eg, receive and / or search for) raw (eg, unprocessed) hearing data from the hearing device 40. In one or more examples or implementations, the accessory device 10 is configured to send 44 data to the hearing device 40.

[0123] Optionally, the user 1, 1A may provide input 7 (e.g., user input) to the hearing device 40, such as via the interface 40B. The input 7 may be, for example, considered as sound input from the user 1, 1A, such as speech input. The input 7 may include measurement data (such as measurements made on the user 1, 1A) made with one or more sensors 40D. The hearing data may be based on the input 7 from the user 1, 1A.

[0124] Optionally, the hearing device 40 may provide an output 8 (such as a user output) to the user 1 , 1A, such as via the interface 40B. The output 8 may for example be considered as an acoustic output, such as a processed output of the hearing device 40 in one or more ears of the user 1 , 1A.

[0125] Hearing data as disclosed herein may be considered as data obtained by a hearing device 40. For example, the hearing data comprises data associated with a hearing device 40 of a user 1, 1A. The hearing data may be considered as user data and / or usage data of the user 1, 1A of the hearing device 40. The hearing data may comprise or be based on one or more of the following, for example from one or more sensors 40D: hearing device settings, audio input data into the hearing device 40, audio output data from the hearing device 40, and sensor data of the hearing device 40. The hearing data may be associated with or indicate a hearing state of the user 1, 1A. In general, the hearing data may be considered as data obtained from, sent to, and / or generated at the hearing device 40.

[0126] The accessory data may, for example, include and / or be based on hearing data obtained (such as received and / or searched) by the accessory device 10, for example, from the hearing device 40. The accessory data may, for example, include processed hearing data (such as processed by the accessory device 10). The processed hearing data is, for example, based on the hearing data of the hearing device 40. For example, the accessory data may include one or more health indicators indicating the health status of the user 1, 1A. In some examples, the accessory data includes sensor data obtained, for example, via one or more sensors 40D of the hearing device 40 and / or via one or more sensors 10D of the accessory device 10. The accessory data may be derived from the hearing data. The accessory data may be stored on the accessory device 10 (such as on the memory 10A) for a period of time before being transmitted to the health data server device 30. In one or more examples or embodiments, the accessory data may be deleted from the accessory device 10 after being transmitted to the health data server device 30. In general, the accessory data may be considered as data obtained, sent, and / or generated from the accessory device 10.

[0127] In one or more examples or embodiments, the hearing data comprises health data associated with the user 1 , 1A of the hearing device 40. In one or more examples, the accessory data is based on the health data.

[0128] For example, the user 1, 1A of the hearing device 40 may be considered as a person wearing the hearing device 40. In other words, the hearing data indicates health data associated with the user 1, 1A of the hearing device 40. The hearing data may include health data, which includes information indicating a health condition of the user 1, 1A of the hearing device 40. For example, the hearing device 40 is configured to determine or derive health data based on one or more of: hearing device settings, audio input data entering the hearing device, audio output data from the hearing device 40, and sensor data of the hearing device 40. The health data may indicate a health condition of the user 1, 1A of the hearing device 40. For example, the health data may include data indicating items such as heart rate, body temperature, blood oxygen, blood pressure, blood sugar level, respiratory rate, and brain activity.

[0129] In one or more examples or embodiments, the hearing data includes usage data of the hearing device 40. In one or more examples or embodiments, the accessory data is based on the usage data.

[0130] The server device 30 is configured to obtain a first consent from the accessory device 10 (e.g., via interface 30B and / or interface 10B) to share the attachment data with a healthcare platform, such as healthcare platform 20. The server device 30 is configured to share the attachment data with the healthcare platform 20 in accordance with the first consent. In one or more examples or implementations, the server device 30 is configured to share the attachment data with the healthcare platform 20 in accordance with the first consent, e.g., via interface 30B and / or interface 20B.

[0131] The first consent may be provided, for example, by a user 1, 1A of the accessory device 10 and / or the hearing device 40. The first consent may be obtained 5 by the accessory device 10 via an application of the accessory device and forwarded to the health data server device 30 and / or the healthcare platform 20, for example. In one or more examples or embodiments, obtaining the first consent comprises obtaining an indication of a first consent for sharing the accessory data with the healthcare platform 20. In other words, the health data server device 30 may not need to obtain the first consent itself, but may receive a message indicating that the user 1, 1A of the hearing device 40 has given 5 consent for sharing the accessory data with the healthcare platform 20 via the accessory device 10. The health data server device 30 may then share the accessory data with the healthcare platform 20 according to the message. The first consent may be provided, for example, by a user 1, 1A of the hearing device 40 via the accessory device 10 by a user input 5. In other words, the health data server device 30 may be configured to obtain the first consent from the user 1, 1A via the accessory device 10. In one or more examples or implementations, obtaining the first consent from the accessory device 10 can include obtaining 13, 24 the first consent from the accessory device 10, for example, via a network 50 (such as a global network, such as the Internet and / or a local area network). In one or more examples or implementations, obtaining the first consent from the accessory device 10 can include obtaining 34 the first consent directly from the accessory device 10.

[0132] The healthcare platform 20 includes, for example, one or more electronic devices. For example, the healthcare platform 20 includes one or more databases that store information associated with one or more users (e.g., patients) of the hearing device. The healthcare platform includes, for example, one or more electronic devices associated with one or more healthcare professionals (e.g., doctors, general practitioners, internists, etc.). For example, the electronic device of the healthcare platform can be a doctor's computer, where the electronic device can be configured to obtain user input from the healthcare professional (e.g., doctor). Figure 1 In the example of , the healthcare platform 20 is associated with a user 1, 1B (e.g., a healthcare professional). The healthcare platform 20 may be configured to provide an output 36 to the user 1, 1B of the healthcare platform 20. For example, the healthcare platform 20 may be configured to output 36 to the user 1, 1B the attachment data and / or a representation based on the attachment data.

[0133] In one or more examples, sharing the attachment data with the healthcare platform 20 includes providing 22, 16 the attachment data to the healthcare platform 20 (e.g., via a network 50 (such as a global network, such as the Internet and / or a local area network) and / or sending through interface 30B and / or interface 20B). In other words, the health data server device 30 can be configured to share 22, 16 the attachment data in response to obtaining the first consent.

[0134] For example, a healthcare professional 1 , 1B (eg, a doctor) may be able to monitor the user's condition with greater accuracy based on the attached data shared with the healthcare platform 20 .

[0135] In some examples, the healthcare professional 1 , 1B may be able to make a diagnosis (eg, for a medical condition) with greater accuracy based on the attached data shared with the healthcare platform 20 .

[0136] In one or more example server devices, the server device 30 is configured to obtain 24 a first request from the healthcare platform 20 for a first permission to share the attachment data with the healthcare platform 20. In one or more example server devices, the server device 30 is configured to send 22 the first request to the accessory device 10. In one or more example server devices, the server device 30 is configured to obtain 24 from the accessory device 10 the first consent to share the attachment data with the healthcare platform 20 in response to the sent first request.

[0137] The first request can be viewed, for example, as a message provided or communicated 6 by the accessory device 10 to the user 1, 1A of the accessory device 10. For example, the first request includes a message indicating a request for a first permission to share the attachment data with the healthcare platform 20. In some examples, the first request includes a message indicating a request for permission for the server device 30 to share the attachment data with the healthcare platform 20. The first request can be provided 38, for example, by a healthcare professional 1, 1B (e.g., a doctor) associated with the healthcare platform 20.

[0138] In one or more example server devices, the first request includes a device identifier. In one or more example server devices, the server device 30 is configured to obtain 34, 24 attachment data associated with the device identifier. In one or more example server devices, the server device 30 is configured to share the attachment data with the healthcare platform 20.

[0139] In other words, obtaining the first request may include obtaining a device identifier, such as a device identifier associated with the hearing device 40, the user 1, 1A of the hearing device 40, and / or an accessory device 10 of the user 1, 1A of the hearing device 40. For example, the user 1, 1A of the hearing device 40 may share its device identifier with a healthcare practitioner 1, 1B (e.g., a doctor). The healthcare practitioner 1, 1B may then enter 38 the device identifier into the healthcare platform 20. The healthcare platform 20 may be configured to send the device identifier 18 to the health data server device 30 along with the first request.

[0140] In one or more example server devices, prior to obtaining the attachment data, the server device 30 is configured to obtain 24, 34 a second consent to obtain the attachment data from the accessory device 10. In one or more example server devices, the server device 30 is configured to obtain 24, 34 the attachment data in accordance with the second consent.

[0141] In one or more examples or implementations, obtaining the second consent from the accessory device 10 can include obtaining 13, 24 the second consent from the accessory device 10, for example, via a network 50 (such as a global network, such as the Internet and / or a local area network). In one or more examples or implementations, obtaining the second consent from the accessory device 10 can include obtaining 34 the second consent directly from the accessory device 10.

[0142] In some examples, the second consent can be provided by user 1, 1 A. For example, when the user provides 5 user input indicating the second consent to accessory device 10, server device 30 can be considered to have the second permission to (e.g., be permitted to) obtain the accessory data (e.g., from accessory device 10).

[0143] In one or more example server devices, the server device 30 is configured to obtain 18, 24 a third consent from the healthcare platform 20 to obtain the healthcare platform data from the healthcare platform 20. In one or more example server devices, the server device 30 is configured to obtain 18, 24 the healthcare platform data from the healthcare platform 20 based on the third consent.

[0144] In one or more examples or embodiments, obtaining the third consent from the healthcare platform 20 may include obtaining 18 , 24 the third consent from the healthcare platform 20 , for example via a network 50 , such as a global network, eg, the Internet and / or a local area network.

[0145] In one or more example server devices, the server device 30 is configured to send 22, 32 the healthcare platform data to the accessory device 10. In other words, the health data server device 30 can be configured to send 22, 32 the healthcare platform data to the accessory device 10 in response to obtaining the third consent and / or according to the third consent. In one or more examples or implementations, sending the healthcare platform data to the accessory device 10 can include, for example, sending 14, 22 the healthcare platform data to the accessory device 10 via a network 50 (such as a global network, such as the Internet and / or a local area network). In one or more examples or implementations, sending the healthcare platform data to the accessory device 10 can include sending the healthcare platform data 32 directly to the accessory device 10.

[0146] In one or more example server devices, the healthcare platform data includes a sensor activation request for activating a sensor (e.g., sensor 40D) of the hearing device 40. In one or more example server devices, sending 22, 32 the healthcare platform data includes sending 22, 32 the sensor activation request to the accessory device 10. In one or more examples or embodiments, the accessory device 10 is configured to send 44 an instruction to the hearing device 40 indicating the sensor activation.

[0147] In one or more example server devices, the server device 30 is configured to obtain 24, 34 a fourth consent to share the healthcare platform data with the accessory device 10. In one or more example server devices, the server device 30 is configured to share 22, 32 the healthcare platform data with the accessory device 10 in accordance with the fourth consent. The fourth consent may, for example, be considered as a consent provided, for example, by a user 1, 1A of the accessory device 10, for the server device 30 to share the healthcare platform data with the accessory device 10. For example, when the server device 30 obtains 24, 34 the fourth consent, for example from the accessory device 10, the server device 30 may be considered to have permission (be permitted) to share the healthcare platform data with the accessory device 10. For example, the user 1, 1A may provide a user input 5 to the accessory device 10 indicating the fourth consent.

[0148] In one or more example server devices, the hearing data comprises health data associated with a user 1, 1A of the hearing device 40. In one or more example server devices, the attachment data is based on the health data.

[0149] In one or more example server devices, the hearing data comprises usage data of the hearing device 40. In one or more example server devices, the attachment data is based on the usage data.

[0150] In one or more example server devices, the server device 30 is configured to obtain auxiliary accessory data 74 from the auxiliary accessory device 70. In one or more examples or embodiments, the server device 30 is configured to output or send 72 data to the auxiliary accessory device 70. In one or more examples or embodiments, the server device 30 obtains 24, 34 auxiliary accessory device consent, for example, from the accessory device 10. For example, the server device 30 can be considered to have permission (permission) to share the auxiliary accessory device data from the auxiliary accessory device 70 with the accessory device 10. For example, the user 1, 1A can provide user input indicating the auxiliary accessory device consent to the accessory device 10 and / or the auxiliary accessory device 70. In one or more examples or embodiments, the user 1, 1A can provide consent on the auxiliary accessory device 70 to allow the auxiliary accessory device 70 to share 74 the auxiliary accessory device data with the accessory device 10 and / or the health data server device 30. In one or more examples or embodiments, obtaining the auxiliary accessory data from the auxiliary accessory device 70 can include, for example, obtaining the auxiliary accessory data from the auxiliary accessory device 70 via a network 50 (such as a global network, such as the Internet and / or a local area network). In one or more examples or implementations, the auxiliary accessory device 70 may be configured to communicate directly with the electronic device 10 , the health data server device 30 , and / or the hearing device 40 .

[0151] In one or more example hearing systems, the hearing system 2 comprises a hearing device data server 60 configured to store hearing data associated with a user 1, 1A of a hearing device 40. In one or more examples, the hearing device data server 60 is configured to obtain 62 a consent (such as a consent of the user 1, 1A) from the accessory device 10 to obtain the hearing data from the hearing device 40, for example via the accessory device 10. In one or more examples or embodiments, the hearing device data server 60 is configured to obtain the hearing data 62 via the accessory device 10, for example via a network 50 (such as a global network, such as the Internet and / or a local area network). In one or more examples or embodiments, the hearing device data server 60 is configured to obtain 65 the hearing data directly from the hearing device 40.

[0152] In some examples, the accessory device 10 is configured to share 64 hearing data associated with the user 1, 1A of the hearing device 40 with a hearing device data server 60 (e.g., after obtaining consent from the user 1, 1A). In some examples, the hearing device data server 60 may be considered a hearing device data storage server. In some examples, the hearing device data server 60 may be part of a data storage device, e.g., comprising one or more servers configured to store hearing data.

[0153] In one or more examples or embodiments, the hearing device data server 60 is configured to output or send 68 data to the health data server device 30. In one or more examples or embodiments, the health data server device 30 is configured to output or send 67 data to the hearing device data server 60. In one or more examples or embodiments, the hearing device data server 60 is configured to output or send 66 data to the hearing device 40.

[0154] Figure 2A-2B is a flow chart of an example method, such as method 100 , according to the present disclosure.

[0155] The present disclosure provides a method of operating a health data server device. The method 100 may be performed by a health data server device (such as Figure 1 The health data server device 30) is executed.

[0156] The method 100 comprises obtaining, from the accessory device, accessory data based on the hearing data of the hearing device ( S116 ).

[0157] The method 100 includes obtaining a first consent from the accessory device to share the accessory data with the healthcare platform (S122).

[0158] The method 100 includes sharing the attachment data with the healthcare platform according to the first consent ( S126 ).

[0159] In one or more example methods, method 100 includes obtaining a first request from a healthcare platform for a first permission to share attachment data with the healthcare platform (S118). In one or more example methods, method 100 includes sending the first request to an accessory device (S120). In one or more example methods, obtaining the first consent to share attachment data with the healthcare platform (S122) includes: obtaining, in response to the sending first request, from the accessory device the first consent to share attachment data with the healthcare platform (S122A).

[0160] In one or more example methods, the first request includes a device identifier. In one or more example methods, the method 100 includes obtaining attachment data associated with the device identifier (S124). In one or more example methods, the method 100 includes sharing the attachment data with the healthcare platform (S126).

[0161] In one or more example methods, before obtaining the attachment data, the method 100 includes obtaining a second consent from the accessory device to obtain the attachment data (S112). In one or more example methods, the method 100 includes obtaining the attachment data according to the second consent (S114).

[0162] In one or more example methods, the method 100 includes obtaining a third consent from the healthcare platform to obtain healthcare platform data from the healthcare platform (S102). In one or more example methods, the method 100 includes obtaining healthcare platform data from the healthcare platform according to the third consent (S104).

[0163] In one or more example methods, the method 100 includes sending healthcare platform data to an accessory device ( S110 ).

[0164] In one or more example methods, the healthcare platform data includes a sensor activation request for activating a sensor of the hearing device. In one or more example methods, sending the healthcare platform data (S110) includes sending the sensor activation request (S110A) to the accessory device.

[0165] In one or more example methods, the method 100 includes obtaining a fourth consent for sharing the healthcare platform data with the accessory device (S106). In one or more example methods, the method 100 includes sharing the healthcare platform data with the accessory device in accordance with the fourth consent (S108).

[0166] In one or more example methods, the hearing data includes health data associated with a hearing device user. In one or more example methods, the attachment data is based on the health data.

[0167] In one or more example methods, the hearing data comprises usage data of the hearing device. In one or more example methods, the accessory data is based on the usage data.

[0168] In one or more example methods, method 100 includes obtaining auxiliary accessory data from an auxiliary accessory device (S128).

[0169] Examples of health data server devices, hearing systems and methods according to the present disclosure are listed in the following items:

[0170] Item 1. A health data server device, comprising a memory, one or more interfaces, and one or more processors, wherein the server device is configured to:

[0171] obtaining, from the accessory device and such as via the one or more interfaces, accessory data based on the hearing data of the hearing device;

[0172] obtaining, from the accessory device and such as via the one or more interfaces, a first consent to share the accessory data with a healthcare platform; and

[0173] Based on the first consent, the attachment data is shared with the healthcare platform, such as via the one or more interfaces.

[0174] Item 2. The server device according to Item 1, wherein the server device is configured as follows:

[0175] obtaining, from the healthcare platform and such as via the one or more interfaces, a first request for a first permission to share the attachment data with the healthcare platform;

[0176] sending the first request to the accessory device, such as via the one or more interfaces; and

[0177] Wherein obtaining the first consent for sharing the attachment data with the healthcare platform comprises: obtaining, from the accessory device, the first consent for sharing the attachment data with the healthcare platform in response to the sent first request.

[0178] Item 3. A server device according to Item 2, wherein the first request includes a device identifier, and wherein the server device is configured to: obtain attachment data associated with the device identifier, and share the attachment data associated with the device identifier with the healthcare platform.

[0179] Item 4. The server device according to any one of the preceding items, wherein, before obtaining the attachment data, the server device is configured to: obtain a second consent for obtaining the attachment data from the attachment device, and obtain the attachment data based on the second consent.

[0180] Item 5. A server device according to any one of the preceding items, wherein the server device is configured to: obtain a third consent from the healthcare platform to obtain healthcare platform data from the healthcare platform, and obtain the healthcare platform data from the healthcare platform based on the third consent.

[0181] Item 6. The server device of Item 5, wherein the server device is configured to: send the healthcare platform data to the accessory device.

[0182] Item 7. A server device according to Item 6, wherein the healthcare platform data includes: a sensor activation request for activating a sensor of the hearing device, and wherein sending the healthcare platform data includes: sending the sensor activation request to the accessory device.

[0183] Item 8. A server device according to any one of Items 6-7, wherein the server device is configured to: obtain a fourth consent from an accessory device to share the healthcare platform data with the accessory device, and share the healthcare platform data with the accessory device based on the fourth consent.

[0184] Item 9. A server device according to any of the preceding items, wherein the hearing data includes health data associated with a user of the hearing device, and wherein the attachment data is based on the health data.

[0185] Item 10. The server device according to any of the preceding items, wherein the hearing data comprises usage data of the hearing device, and wherein the attachment data is based on the usage data.

[0186] Item 11. The server device of any of the preceding items, wherein the server device is configured to obtain auxiliary accessory data from an auxiliary accessory device.

[0187] Item 12. A hearing system comprising a health data server device, an accessory device, and a hearing device according to any one of Items 1-11.

[0188] Item 13. A hearing system according to Item 12, wherein the hearing device comprises one or more sensors for providing sensor data, and wherein the hearing device is configured to send hearing data including the sensor data to the accessory device.

[0189] Item 14. A hearing system according to any one of Items 12-13, wherein the hearing system comprises a hearing device data server configured to store hearing data associated with a user of the hearing device.

[0190] Item 15. A method for operating a health data server device, the method comprising:

[0191] Obtaining accessory data based on hearing data of the hearing device from the accessory device (S116);

[0192] obtaining a first consent from the accessory device to share the accessory data with the healthcare platform (S122); and

[0193] The attachment data is shared with the healthcare platform according to the first consent ( S126 ).

[0194] Item 16. The method for operating health data server data according to Item 15, wherein the method comprises:

[0195] obtaining, from the healthcare platform, a first request for a first permission to share the attachment data with the healthcare platform (S118);

[0196] sending the first request to the accessory device (S120); and

[0197] Wherein, obtaining a first consent for sharing the attachment data with the healthcare platform (S122) includes: obtaining, from the accessory device, the first consent for sharing the attachment data with the healthcare platform in response to the sent first request (S122A).

[0198] Item 17. A method for operating a health data server device according to Item 16, wherein the first request includes a device identifier, and wherein the method includes obtaining attachment data associated with the device identifier (S124), and sharing the attachment data with the healthcare platform (S126).

[0199] Item 18. A method for operating a health data server device according to any one of Items 15-17, wherein, before obtaining attachment data, the method includes obtaining a second consent for obtaining the attachment data from the attachment device (S112), and obtaining the attachment data based on the second consent (S114).

[0200] Item 19. A method for operating a health data server device according to any one of Items 15-18, wherein the method includes obtaining a third consent from the healthcare platform to obtain healthcare platform data from the healthcare platform (S102), and obtaining the healthcare platform data from the healthcare platform based on the third consent (S104).

[0201] Item 20. The method for operating a health data server device according to Item 19, wherein the method includes sending the healthcare platform data to the accessory device (S110).

[0202] Item 21. A method for operating a health data server device according to Item 20, wherein the healthcare platform data includes a sensor activation request for activating a sensor of the hearing device, and wherein sending the healthcare platform data (S110) includes sending (S110A) the sensor activation request to the accessory device.

[0203] Item 22. A method for operating a health data server device according to any one of Items 19-20, wherein the method includes obtaining a fourth consent for sharing the healthcare platform data with the accessory device (S106), and sharing the healthcare platform data with the accessory device based on the fourth consent (S108).

[0204] Item 23. A method of operating a health data server device according to any one of the preceding Items 15-22, wherein the hearing data includes health data associated with a user of the hearing device, and wherein the attachment data is based on the health data.

[0205] Item 24. A method of operating a health data server device according to any one of the preceding Items 15-23, wherein the hearing data includes usage data of the hearing device, and wherein the attachment data is based on the usage data.

[0206] Item 25. A method of operating a health data server device according to any one of the preceding Items 15-24, wherein the method includes obtaining auxiliary accessory data from an auxiliary accessory device (S128).

[0207] The use of the terms "first", "second", "third" and "fourth", "primary", "auxiliary", "tertiary", etc. does not imply any particular order, but is intended to identify individual elements. Furthermore, the use of the terms "first", "second", "third" and "fourth", "primary", "auxiliary", "tertiary", etc. does not indicate any order or importance. The terms "first", "second", "third" and "fourth", "primary", "auxiliary", "tertiary", etc. are used to distinguish one element from another. It should be noted that the terms "first", "second", "third" and "fourth", "primary", "auxiliary", "tertiary", etc. are used here and elsewhere for labeling purposes only and are not intended to indicate any particular spatial or temporal order.

[0208] Furthermore, the marking of a first element does not imply the presence of a second element, and vice versa.

[0209] It is understood that the accompanying drawings include some circuits or operations shown with solid lines, and some circuits, components, features or operations shown with dotted lines. The circuits or operations included in the solid lines are the circuits, components, features or operations included in the most extensive examples. The circuits, components, features or operations included in the dotted lines are examples, which may be included in the circuits, components, features or operations in the solid line examples, or are part thereof, or are other circuits, components, features or operations that may be included in addition to the circuits, components, features or operations in the solid line examples. It should be understood that these operations do not have to be performed in the order presented. In addition, it should be understood that not all operations need to be performed. The example operations can be performed in any order and combination. It should be understood that these operations do not need to be performed in order. The circuits, components, features or operations included in the dotted lines can be considered optional.

[0210] Other operations not described herein may also be combined in the exemplary operations. For example, one or more additional operations may be performed before, after, simultaneously, or between any of the operations.

[0211] Features discussed above as separate implementations may also be implemented in combination as a single implementation. Conversely, features described as separate implementations may also be implemented separately in multiple implementations or in any suitable subcombination. In addition, although the above features may be described as functioning in a particular combination, in some cases one or more features in a claimed combination may be deleted from the combination, and the combination may be claimed as any subcombination or variation of any subcombination.

[0212] It should be noted that the word "comprising" does not exclude the presence of other elements or steps than the listed elements or steps. It should be noted that the word "a / an" before an element does not exclude the presence of a plurality of such elements.

[0213] It should be noted that the term "indicating" may be viewed as "associated with," "related to," "describing," "characterizing," and "defining." The terms "indicating," "associated with," "related to," "describing," "characterizing," and "defining" may be used interchangeably. The term "indicating" may be viewed as indicating a relationship. For example, weight data indicating weight may include one or more weight parameters.

[0214] Note that the wording "based on" may be viewed as "as a function of" and / or "derived from". The terms "based on" and "as a function of" may be used interchangeably. For example, a parameter determined "based on" a data set may be viewed as a parameter determined "as a function of" the data set. In other words, a parameter may be the output of one or more functions that have a data set as input.

[0215] A function may be characterized as a relationship between inputs and outputs, such as a mathematical relationship, a database relationship, a hardware relationship, a logical relationship, and / or other suitable relationship.

[0216] It should be noted that the word "comprising" does not exclude the presence of other elements or steps than the listed elements or steps.

[0217] It should be noted that the word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements.

[0218] It should also be noted that any reference signs do not limit the scope of the claims, that exemplary embodiments may be implemented at least partially by hardware and software, and that multiple "means," "units," or "devices" may be represented by the same item of hardware.

[0219] The various exemplary methods, apparatuses, and systems described herein are described in the general context of method step processes, which in one aspect can be implemented by a computer program product (embodied in a computer-readable medium) comprising computer-executable instructions (such as program code) executed by a computer in a network environment. Computer-readable media may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), compact disks (CD), digital versatile disks (DVD), etc. In general, program modules may include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of program codes for performing steps of methods as disclosed herein. A specific sequence of such executable instructions or associated data structures represents an example of corresponding actions for implementing the functions described in such steps or processes.

[0220] Although features have been shown and described, it should be understood that these features are not intended to limit the claimed invention, and it will be apparent to those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention. Therefore, the description and drawings should be regarded as illustrative rather than restrictive. The claimed invention is intended to cover all alternatives, modifications and equivalents.

[0221] Reference to Figures:

[0222] 1.1A, 1B users

[0223] 2 Hearing System

[0224] 5 Input

[0225] 6 Output

[0226] 7 Input

[0227] 8 Output

[0228] 10 Accessories

[0229] 10A Memory

[0230] 10B One or more interfaces

[0231] 10C Processor

[0232] 10D One or more sensors

[0233] 13Get and send

[0234] 14Get and send

[0235] 16Get and send

[0236] 18Get and send

[0237] 20 Healthcare Platform

[0238] 20A Memory

[0239] 20B One or more interfaces

[0240] 20C Processor

[0241] 22Get and send

[0242] 24Get and send

[0243] 30 Electronic equipment, health data server equipment

[0244] 30A One or more interfaces

[0245] 30B memory

[0246] 30C Processor

[0247] 32Get, send

[0248] 34Get and send

[0249] 36Get, send

[0250] 38Get, send

[0251] 40 Hearing equipment

[0252] 40A Memory

[0253] 40B One or more interfaces

[0254] 40C Processor

[0255] 40D One or more sensors

[0256] 42Get, send

[0257] 44Get, send

[0258] 50 Network

[0259] 60 Hearing Device Data Server

[0260] 62Get, send

[0261] 64Get, send

[0262] 65Get, send

[0263] 66Get, send

[0264] 67Get, send

[0265] 68Get, send

[0266] 70 auxiliary equipment

[0267] 72Get, send

[0268] 74Get and send.

Claims

1. A health data server device, comprising a memory, one or more interfaces and one or more processors, wherein: The server device is configured as follows: obtaining, from the accessory device, accessory data based on the hearing data of the hearing device; obtaining a first consent from the accessory device to share the accessory data with a healthcare platform; as well as The attachment data is shared with the healthcare platform according to the first consent.

2. The server device according to claim 1, wherein: The server device is configured as follows: obtaining a first request from the healthcare platform for a first permission to share the attachment data with the healthcare platform; sending the first request to the accessory device; and Wherein obtaining the first consent for sharing the attachment data with the healthcare platform comprises: obtaining, from the accessory device, the first consent for sharing the attachment data with the healthcare platform in response to the sent first request.

3. The health data server device according to claim 2, wherein: The first request includes a device identifier, and The health data server device is configured to obtain attachment data associated with the device identifier and share the attachment data associated with the device identifier with the healthcare platform.

4. A health data server device according to any one of the preceding claims, wherein: Before obtaining the attachment data, the health data server device is configured to obtain a second consent for obtaining the attachment data from the attachment device, and obtain the attachment data according to the second consent.

5. A health data server device according to any one of the preceding claims, wherein: The health data server device is configured to obtain a third consent from the health care platform to obtain health care platform data from the health care platform, and obtain the health care platform data from the health care platform according to the third consent.

6. The health data server device according to claim 5, wherein: The health data server device is configured to send the healthcare platform data to the accessory device.

7. The health data server device according to claim 6, wherein: The healthcare platform data comprises: a sensor activation request for activating a sensor of the hearing device, and Wherein, sending the healthcare platform data includes: sending the sensor activation request to the accessory device.

8. The health data server device according to any one of claims 6 to 7, wherein: The health data server device is configured to obtain a fourth consent to share the health care platform data with the accessory device, and to share the health care platform data with the accessory device according to the fourth consent.

9. A health data server device according to any one of the preceding claims, wherein: The hearing data comprises health data associated with a user of the hearing device, and wherein the accessory data is based on the health data.

10. A health data server device according to any one of the preceding claims, wherein: The hearing data comprises usage data of the hearing device, and wherein the accessory data is based on the usage data.

11. A health data server device according to any one of the preceding claims, wherein: The health data server device is configured to obtain auxiliary accessory data from an auxiliary accessory device.

12. A hearing system comprising the health data server device, an accessory device and a hearing device according to any one of claims 1-11.

13. The hearing system according to claim 12, wherein: The hearing device comprises one or more sensors for providing sensor data, and wherein the hearing device is configured to send hearing data comprising the sensor data to the accessory device.

14. The hearing system according to any one of claims 12-13, wherein: The hearing system comprises a hearing device data server configured to store hearing data associated with a user of the hearing device.

15. A method of operating a health data server device, the method comprising the steps of: Obtaining accessory data based on hearing data of the hearing device from the accessory device (S116); obtaining a first consent from the accessory device to share the accessory data with the healthcare platform (S122); and The attachment data is shared with the healthcare platform according to the first consent ( S126 ).

Images