Abstract: Disclosed are systems and techniques for wireless communications. For example, a wireless communication device can receive, from a network device, a signal indicating a plurality of slots of time within a subevent interval for transmission of data, wherein the subevent interval is associated with a group of wireless communication devices that includes the wireless communication device. The wireless communication device can transmit one or more data packets within the plurality of slots of time.

Abstract: Disclosed are systems and techniques for wireless communications. For example, a network device can divide a data package into a plurality of segments. The network device can transmit, to a plurality of wireless communication devices, a broadcast message indicating a first time to start receiving a plurality of subframes comprising the plurality of segments, a total number of the plurality of segments, and a total number of the plurality of subframes for the data package. The network device can transmit, to the plurality of wireless communication devices starting at the first time, the plurality of subframes comprising the plurality of segments.

Abstract: Aspects of the disclosure relate to providing improved optical character recognition (OCR). An OCR evaluation platform may generate a script for evaluating OCR performance. The platform may generate modified resources by executing OCR applications to modify original resources. Based on executing the script, the platform may generate comparative analysis information based on comparing the modified resources to the original resource. The platform may generate metric scores based on the comparative analysis information. The metric scores may be used to generate visual representations of the performance of different OCR applications. The platform may generate weighted scores representing the performance of different OCR applications. The platform may identify a preferred OCR application for performing a particular operation. The platform may store correlations between preferred OCR applications and corresponding operations.

Abstract: Techniques are disclosed for providing at least one proposed alternative plan of travel of a vehicle are disclosed based upon data of at least one geographic region about at least one of global navigation satellite system (GNSS) spoofing and GNSS jamming. If a current path of travel of the vehicle intersects at least one geographic region of at least one of GNSS spoofing and GNSS jamming, then determining the at least one proposed alternative plan of travel of the vehicle. At least one of the at least one proposed alternative plan of travel includes a path of travel that does not intersect at least one geographic region of the at least one geographic region of at least one of GNSS spoofing and GNSS jamming. The determined at least one proposed alternative plan of travel is sent to the vehicle.

Abstract: Techniques for storing health data can include a multi-node data structure. A data node, a category node, and an institution node of a multi-node data structure can be generated in accordance with a configuration file. The data node can include health data and can be identified by a first unique data identifier and encrypted using a first cryptographic key. The category node can include the first unique data identifier and the first cryptographic key. The category node can be identified by a second unique data identifier and encrypted using a second cryptographic key. The institution node can include the second unique data identifier and the second cryptographic key. The institution node can be identified by a third unique data identifier and encrypted using a third cryptographic key. The data node, the category node, and the institution node can be shared with a service provider.

Abstract: Techniques for storing health data can include a multi-node data structure. A data node, a category node, and an institution node of a multi-node data structure can be generated in accordance with a configuration file. The data node can include health data and can be identified by a first unique data identifier and encrypted using a first cryptographic key. The category node can include the first unique data identifier and the first cryptographic key. The category node can be identified by a second unique data identifier and encrypted using a second cryptographic key. The institution node can include the second unique data identifier and the second cryptographic key. The institution node can be identified by a third unique data identifier and encrypted using a third cryptographic key. The data node, the category node, and the institution node can be shared with a service provider.

Abstract: Systems and methods herein describe accessing a set of feature flags, a first feature flag in the set of feature flag describing vehicle navigation behavior on a routing graph, the routing graph representing the roadway, associating the set of feature flags with a vehicle, applying the associated set of feature flags to a graph traversal algorithm to generate a modified graph traversal algorithm, generating the route using the modified graph traversal algorithm; and transmitting instructions to the vehicle to begin executing the route.

Abstract: A device may receive multimodal content that includes two or more of text data, image data, or video data, and may process the two or more of the text data, the image data, or the video data, with a binary classifier model, to determine whether the two or more of the text data, the image data, or the video data is biased or unbiased. The device may process the two or more of the text data, the image data, or the video data, with a multilabel classifier model and based on the two or more of the text data, the image data, or the video data being biased, to determine an implicit bias in at least one of the two or more of the text data, the image data, or the video data, and may perform one or more actions based on the implicit bias.

Abstract: A schema is generated to establish a connection between user devices and one or more patient record servers. Generating a schema can include receiving configuration information associated with a patient record gateway, wherein the patient record gateway is associated with one or more patient record servers configured for storing electronic health records for a plurality of patients. Generating a schema can include defining, based at least in part on the configuration information, a schema configured to enable user devices to retrieve, via the patient record gateway, electronic health records from the one or more patient record servers. A schema can be requested by a user device. The schema can be sent to a user device to establish a connection with the one or more patient record servers.

Abstract: Techniques for storing health data can include a multi-node data structure. A data node, a category node, and an institution node of a multi-node data structure can be generated in accordance with a configuration file. The data node can include health data and can be identified by a first unique data identifier and encrypted using a first cryptographic key. The category node can include the first unique data identifier and the first cryptographic key. The category node can be identified by a second unique data identifier and encrypted using a second cryptographic key. The institution node can include the second unique data identifier and the second cryptographic key. The institution node can be identified by a third unique data identifier and encrypted using a third cryptographic key. The data node, the category node, and the institution node can be shared with a service provider.

Abstract: A schema is generated to establish a connection between user devices and one or more patient record servers. Generating a schema can include receiving configuration information associated with a patient record gateway, wherein the patient record gateway is associated with one or more patient record servers configured for storing electronic health records for a plurality of patients. Generating a schema can include defining, based at least in part on the configuration information, a schema configured to enable user devices to retrieve, via the patient record gateway, electronic health records from the one or more patient record servers. A schema can be requested by a user device. The schema can be sent to a user device to establish a connection with the one or more patient record servers.

Abstract: A user device may share encrypted health data with an electronic health record (EHR) system associated with a health institution. A unique data identifier that identifies a portion of the health data and a cryptographic key may be shared with the EHR system. The encrypted health may be shared with a service provider and a unique data identifier. To access the health data, the EHR system may query the service provider with the unique data identifier.

Abstract: Techniques are disclosed for providing at least one proposed alternative plan of travel of a vehicle are disclosed based upon data of at least one geographic region about at least one of global navigation satellite system (GNSS) spoofing and GNSS jamming. If a current path of travel of the vehicle intersects at least one geographic region of at least one of GNSS spoofing and GNSS jamming, then determining the at least one proposed alternative plan of travel of the vehicle. At least one of the at least one proposed alternative plan of travel includes a path of travel that does not intersect at least one geographic region of the at least one geographic region of at least one of GNSS spoofing and GNSS jamming. The determined at least one proposed alternative plan of travel is sent to the vehicle.

Abstract: A schema is generated to establish a connection between user devices and one or more patient record servers. Generating a schema can include receiving configuration information associated with a patient record gateway, wherein the patient record gateway is associated with one or more patient record servers configured for storing electronic health records for a plurality of patients. Generating a schema can include defining, based at least in part on the configuration information, a schema configured to enable user devices to retrieve, via the patient record gateway, electronic health records from the one or more patient record servers. A schema can be requested by a user device. The schema can be sent to a user device to establish a connection with the one or more patient record servers.

Abstract: Information about a medical provider's locations, brands, and gateways can be received (e.g., via an online portal). This information can be used to generate a data object that represents relationships between the locations, the brands, and the gateways. This data object can be maintained in a database base that is searchable by a user device. For example, a user of the user device may search the database to identify a medical provider where the user obtains care. Once identified, other systems can be used to connect the user device to a gateway associated with the medical provider in order to download electronic health record data associated with the user.

Abstract: A patient record gateway of an electronic health record system can be validated using a conformance statement that defines capabilities and characteristics of patient record servers associated with the gateway. Part of validating the patient record gateway includes performing a configuration test of the patient record gateway using the conformance statement.

Abstract: Cross-domain integration within product lifecycle management can include providing a plurality of finite state machines (FSMs), wherein each FSM is associated with one business object of an integration flow between a first enterprise information system and a second enterprise information system. Each FSM defines a plurality of lifecycle states of the associated business object. A business rule can be associated with each lifecycle state of each FSM. For each FSM, the associated business rules are independent of the FSM. For a selected lifecycle state of each FSM, the associated business rule defines a condition causing a transition from the selected lifecycle state to a next lifecycle state of the FSM. A network of the plurality of FSMs is established by providing communication links among individual ones of the plurality of FSMs according to the business rules. The communication links define the integration flow.

Abstract: Cross-domain integration within product lifecycle management can include providing a plurality of finite state machines (FSMs), wherein each FSM is associated with one business object of an integration flow between a first enterprise information system and a second enterprise information system. Each FSM defines a plurality of lifecycle states of the associated business object. A business rule can be associated with each lifecycle state of each FSM. For each FSM, the associated business rules are independent of the FSM. For a selected lifecycle state of each FSM, the associated business rule defines a condition causing a transition from the selected lifecycle state to a next lifecycle state of the FSM. A network of the plurality of FSMs is established by providing communication links among individual ones of the plurality of FSMs according to the business rules. The communication links define the integration flow.

Abstract: A posterior knee guard is coupled to a shin guard which includes a front shell, padding, and an elastic mounting strap. The posterior knee guard includes a hard outer layer and an resilient inner pad. The inner pad has a strap channel extending laterally therethrough which is configured to receive the mounting strap of the shin guard. The outer layer may be overlaid with a strong covering material. The outer layer has a vertical column of horizontally extending guard strips. The guard strips are separated from each other to form a space between adjacent guard strips.

Abstract: A user device may share encrypted health data with an electronic health record (EHR) system associated with a health institution. A unique data identifier that identifies a portion of the health data and a cryptographic key may be shared with the EHR system. The encrypted health may be shared with a service provider and a unique data identifier. To access the health data, the EHR system may query the service provider with the unique data identifier.