Abstract: A hearing device may include an earpiece, and ear-tip suspension element disposed in the earpiece, a solenoid actuator, and a controller. The earpiece and the ear-tip suspension element may include passageways that connect to form a vent through the earpiece. The solenoid actuator may include a solenoid and a core. The core may be movable between an open position and a closed position to open and close the vent. The controller may include one or more processors and may be operably coupled to the solenoid actuator to control movement of the core between the open and closed position. The controller may be configured to move the core using the solenoid based on at least a listening environment of the hearing device.

Abstract: A hearing device may include a housing, a microphone, and an acoustic element. The housing may include a shell and a microphone port disposed between an outer surface of the shell and an inner surface of the shell that defines a cavity within the shell. The microphone may be disposed within the cavity of the shell and acoustically connected to the microphone port. The acoustic element may be disposed on the outer surface of the shell or at least partially within the microphone port. The acoustic element may include a substrate and fibers extending from the substrate. At least a portion of acoustic energy incident upon the acoustic element may be received by the microphone.

Abstract: A system includes a hearing device comprising a rechargeable power source, power management circuitry, and a first charging interface comprising a first cathode contact and a first anode contact spaced apart from the first cathode contact. A charging module comprises a second charging interface configured to detachably couple with the first charging interface of the hearing device. The second charging interface comprises a second anode contact having a contact surface and a displaceable second cathode contact. An arrangement is configured to displace at least a portion of the second cathode contact above the contact surface to facilitate electrical contact between the first and second cathode contacts prior to electrical contact between the first and second anode contacts. Charging circuitry of the charging module is coupled to the second charging interface and configured to charge the rechargeable power source of the hearing device.

Abstract: Systems and methods are disclosed that receive data at an electronic computing device. The data can include phrases that can be transformed according to an algorithm to generate a masked version of the phrases. The masked version can be transmitted to a third party system for securing. The secured version can be received from the third party system. A secured filter representative of the received data can be generated based on the received secured version.

Abstract: Systems and methods are disclosed for generation of secure indexes that permit the querying or searching of encrypted data in a cryptographically-secure manner. In various embodiments, a filter gradient comprises a node identifier, a set membership filter, and an ordered genealogy (such that it comprises a filter that encodes a subset of the items encoded by its parent), and a FiG tree is a rooted tree with filter gradients (and, optionally, one or more dictionaries) as nodes such that each filter gradient uses a different hash. A HiiT data structure, in various embodiments, comprises a hash table that points to the rows of an inverted index table. In various embodiments, an oblivious pseudorandom function may be employed to mask, secure, and prepare the phrases for insertion into the secure indexes.

Abstract: Systems and methods are disclosed for, without access to the original set of data elements from which the online filter was originally constructed, converting online filters to other types of filters. To convert a particular type of online filter to either an offline filter or a different type of online filter, the system, in various embodiments, first determines the types/formats of each of the relevant filters. Then, in various embodiments, the system extracts the appropriate data representations from the original online filter. In various embodiments, the system converts the extracted data representations into the data representation format of the new filter. The system, in various embodiments, then constructs the new filter from the converted data representations.

Abstract: A radio assembly is provided. The radio assembly includes at least one radio module and a radome. The radio module has a heatsink disposed on one side and a radio module base on the other side thereof. The radio module base is disposed between the heatsink and the radome. The heatsink defines a cable channel for routing at least one power cable and at least one data cable.

Abstract: A radio assembly is provided. The radio assembly includes at least one radio module and a radome. The radio module has a heatsink disposed on one side and a radio module base on the other side thereof. The radio module base is disposed between the heatsink and the radome. The heatsink defines a cable channel for routing at least one power cable and at least one data cable.

Abstract: A clinical data management system (1) has databases (20), processors in servers (2-4) which are programmed to process clinical data and communicate with user interfaces and external systems interfaces, and at least one database. The system imports source data from disparate clinical site sources into staging databases at refresh intervals, maintains data models, and maps data from the staging databases into the data models, and feeds data from the data models into data delivery databases. There is a uniform refresh frequency for the staging databases. The system output is regularly updated data for clinical site performance, quality and risk metrics to a clinical study team. The data mapper servers identify each of a plurality of source data stages, and transform data from each stage to one or more data models according to one or more mapsets, each mapset defining a transformation.

Abstract: A clinical data management system has databases, processors in servers which are programmed to process clinical data and communicate with user interfaces and external systems interfaces, and at least one database. The system imports source data from disparate clinical site sources into staging databases at refresh intervals, maintains data models, and maps data from the staging databases into the data models, and feeds data from the data models into data delivery databases. There is a uniform refresh frequency for the staging databases. The system output is regularly updated data for clinical site performance, quality and risk metrics to a clinical study team. The data mapper servers identify each of a plurality of source data stages, and transform data from each stage to one or more data models according to one or more mapsets, each mapset defining a transformation.