Abstract: A client device collects immunization data includes a type of immunization given to an individual and a date that the immunization was provided to the individual. The client device converts immunization data into a numeric string, where the numeric string as converted comprises an encrypted payload portion and a mode indicator portion. The client device generates a two-dimensional machine-readable identifier using the numeric string. A reader device reads the two-dimensional machine-readable identifier and accesses the numeric string. The reader device converts at least a portion of the numeric string comprising the immunization data into a predetermined format for importing into an electronic health record (EHR).

Abstract: Disclosed are various embodiments for forming spinal rod members for use in pedicle screw systems for spinal fixation surgery and systems. A system can include a pedicle screw having a pedicle screw head and a pedicle screw shaft, the pedicle screw head comprising an aperture for receiving and retaining a spinal rod member relative to the pedicle screw. The spinal rod member can include an elongated tubular membrane having a flexible body and a spinal rod body formed of a compound, where the spinal rod body is formed by insertion of a liquid compound into the elongated tubular membrane and a hardening of the liquid compound or other similar process for conversion of the flexible rod to a rigid rod. The pedicle screw head can include a channel configured to receive and retain the spinal rod member.

Abstract: A client device collects immunization data includes a type of immunization given to an individual and a date that the immunization was provided to the individual. The client device converts immunization data into a numeric string, where the numeric string as converted comprises an encrypted payload portion and a mode indicator portion. The client device generates a two-dimensional machine-readable identifier using the numeric string. A reader device reads the two-dimensional machine-readable identifier and accesses the numeric string. The reader device converts at least a portion of the numeric string comprising the immunization data into a predetermined format for importing into an electronic health record (EHR).

Abstract: Disclosed are various embodiments for providing access control to the underlying data of a single machine-readable identifier when read by various reader devices. A client device may receive a first cryptographic key associated with a first device profile and a second cryptographic key associated with a second device profile. Data provided through an ingestion process is formatted into at least a first portion of data and a second portion of data, where the first portion of data is intended for a first reader device and the second portion of data is intended for a second reader device. The first portion of data may be encrypted using the first cryptographic key while the second portion of data is encrypted using the second cryptographic key. A machine-readable identifier may be generated using the first portion of data as encrypted and the second portion of data as encrypted.

Abstract: Disclosed are various embodiments for providing secure data translation using machine-readable identifiers, such as barcodes or quick response (QR) codes. A client device may be configured to translate input data stored in a first data format to data in a universal data format and encrypt the data in the universal data format using the cryptographic key such that the data in the universal data format is only accessible by the reader device having the cryptographic key. The client device may further generate a machine-readable identifier using the data as encrypted for rendering in a display accessible by the client device. A reader device may be configured to decrypt the data as encrypted to access the data in the universal data format, and translate the input data from the universal data format to a second data format in accordance with a second format setting.

Abstract: Disclosed are various embodiments for selectively encrypting and display machine-readable identifiers in a lock screen of a client device. In one embodiment, a client device may be configured to access input data from a data store and identify a first portion of the input data having a first sensitivity level and a second portion of the input data having a second sensitivity level, where the second sensitivity level is more sensitive than the first sensitivity level. The client device may encrypt at least the second portion of the input data using a cryptographic key and generate a machine-readable identifier using the first portion of the input data and the second portion of the input data as encrypted. The machine-readable identifier may be shown in a lock screen of the client device.

Abstract: Disclosed are various embodiments for providing access control to the underlying data of a single machine-readable identifier when read by various reader devices. A client device may receive a first cryptographic key associated with a first device profile and a second cryptographic key associated with a second device profile. Data provided through an ingestion process is formatted into at least a first portion of data and a second portion of data, where the first portion of data is intended for a first reader device and the second portion of data is intended for a second reader device. The first portion of data may be encrypted using the first cryptographic key while the second portion of data is encrypted using the second cryptographic key. A machine-readable identifier may be generated using the first portion of data as encrypted and the second portion of data as encrypted.

Abstract: Disclosed are various embodiments for augmenting and updating content data using encrypted machine-readable identifiers. A client application may be employed to transfer a first amount of data to a reader device using a first machine-readable identifier, where the reader device has access to at least one cryptographic key capable of decrypting the data. If the first amount of data is modified or augmented on the reader device, the client application may capture an image of a second machine-readable identifier generated by the reader device, decode and decrypt the machine-readable identifier to identify a second amount of data, and reconcile differences between the first amount of data and the second amount of data.