A Technical Deep-Dive into QR Codes and Their Multispectral Industrial Applications |
Chapter 10: Structured Append - Chaining Large Payloads |
Short Summary |
This chapter explains Structured Append, a powerful QR code feature that allows up to 16 individual QR codes to be linked together to store a single large payload exceeding 7 kilobytes of data. We describe how the mechanism works with headers containing position and parity information, enabling compliant scanners to stitch the pieces back together. The chapter then presents a wide range of American industry applications where Structured Append is essential: shipping manifests that require multiple pages of information, medical records that store comprehensive patient data across several codes, inventory management systems that track complex product details, and innovative security applications that use the feature to hide sensitive information. We also address the practical reality that not all scanner apps support this feature, and we provide guidance for system designers who must verify compatibility before deployment. Each example illustrates how breaking a large message into smaller, individually scannable codes solves real-world challenges. |
|
Introduction: When One Code Is Not Enough |
Throughout this book, we have explored the remarkable capacity of QR codes. A single Version 40 QR code with low error correction can hold nearly 3,000 bytes of data---enough for a short essay or a detailed product description. But what if you need to store more information than a single code can holdWhat if you need to encode an entire shipping manifest with hundreds of line items, or a comprehensive medical record with imaging reports and treatment histories |
This is the problem that Structured Append solves. |
Structured Append is a feature of the QR code standard that allows up to 16 individual QR codes to be chained together, forming a single logical data payload. Each code in the chain carries a small header that indicates its position in the sequence and the total number of codes in the chain. A compliant scanner reads all the codes in order and concatenates the data, reconstructing the complete message . |
The name is descriptive: you 'append' one QR code to another in a structured sequence. Think of it like chapters in a book. Each QR code is a chapter, and the header tells you which chapter you are reading and how many chapters there are in total. When a scanner reads all the chapters in the correct order, it has the complete book. |
Structured Append is not a different type of QR code; it is a mode of operation that any standard QR code can use. The individual codes look identical to ordinary QR codes to a casual observer. However, the header information at the beginning of the data payload tells a compliant decoder that this code is part of a sequence. |
This chapter explores how Structured Append works, why it is valuable in real-world applications, and how American industries leverage it to overcome the capacity limits of single QR codes. We will also look at emerging security applications that use Structured Append to hide sensitive information across multiple codes. |
|
The Anatomy of Structured Append |
To understand Structured Append, we must first understand the header that makes it work. The QR standard defines a specific structure at the beginning of the data payload for codes that are part of a sequence . |
The Structured Append header contains three pieces of information: |
Symbol Position. This indicates the position of this particular code within the sequence. For example, if a message is split across four codes, each code has a position from 1 to 4. The first code has position 1, the second has position 2, and so on. |
Total Number of Symbols. This indicates how many codes are in the entire sequence. A compliant scanner reads this number and knows how many codes to expect. |
Parity Data. This is a simple checksum calculated from the entire payload. The parity data is common to all codes in the sequence. When a scanner reads all the codes, it can verify the parity data to ensure that the pieces belong together and that no data has been corrupted . |
The header itself is encoded as part of the data stream, using the same encoding modes we discussed in the previous chapter (Numeric, Alphanumeric, Byte, or Kanji). A standard decoder that does not support Structured Append will simply decode the header as part of the data, displaying it as text. A compliant decoder, however, recognizes the header and uses it to reconstruct the complete message. |
It is important to note that Structured Append is not the same as simply putting multiple QR codes on a document. A true Structured Append sequence has the header information that allows the scanner to stitch the pieces together automatically. Without Structured Append, the user would have to scan each code manually and concatenate the data themselves. |
Technical Limits. The standard allows a maximum of 16 codes in a sequence . Each code can be up to Version 40, the largest size available. The theoretical maximum payload for a Structured Append sequence is therefore 16 times the capacity of a Version 40 code. With high error correction, that is about 16 times 1,852 alphanumeric characters, which is over 29,000 characters. With low error correction, it is even more---over 68,000 characters, or more than 7 kilobytes of data. This is enough for substantial documents. |
However, there is a practical consideration: the user must scan all 16 codes. If any code is missing or damaged, the complete message cannot be reconstructed. This is why Structured Append is typically used in controlled environments where the sequence of codes is physically organized and the scanner can read all codes systematically. |
|
Software Support for Structured Append |
The availability of Structured Append support varies significantly across QR code generation and scanning software. This is an important consideration for system designers. |
On the generation side, many QR code libraries support Structured Append. The Segno library, a popular Python QR code encoder, provides a `make_sequence()` function specifically for creating sequences of up to 16 QR codes . The Rust-based qrforge library also supports Structured Append through its `build_with_structual_append()` method, which splits input data across multiple codes . The Gleam-based qrkit library includes a `encode_split()` function that chains up to 16 symbols, and it provides the ISO/IEC 18004 compliant header with symbol position, total, and parity byte . |
On the scanning side, support is more variable. Many consumer-facing scanner apps decode each QR code individually and display the data as separate results, without stitching them back together . This is a critical limitation for any application that relies on Structured Append. The qrkit documentation explicitly warns: 'Structured Append reader support varies in practice --- some scanner apps decode each symbol independently rather than stitching the payload back together. Verify against the target reader before relying on it' . |
There are, however, specialized scanners that support Structured Append. The react-native-ios-qr-code-scanner package, for example, includes 'structured format support' and can 'seamlessly read 'Structured Append' QR codes, providing extended functionality' . This suggests that as the feature becomes more widely used, support is growing. |
For enterprise applications, system designers often use custom scanning software or specialized industrial scanners that can be configured to support Structured Append. In these environments, the lack of consumer app support is less of a concern because the scanning hardware and software are controlled by the organization. |
|
US Application Examples: Structured Append in Practice |
Now let us explore how American industries leverage Structured Append to solve real-world challenges that go beyond the capacity of a single QR code. |
Example 1: Shipping Manifests and Logistics |
The logistics industry deals with large amounts of data for every shipment. A single shipping manifest can include the consignor and consignee information, a list of items with quantities and weights, special handling instructions, hazardous materials declarations, and customs documentation. This data can easily exceed the capacity of a single QR code. |
Structured Append offers an elegant solution: split the manifest across several QR codes printed on the shipping label or on an accompanying document. Each code is a page of the manifest, and a compliant scanner reads all codes to reconstruct the complete document. |
The US healthcare supply chain provides a concrete example. The DHIS2 (District Health Information Software 2) platform, used in healthcare logistics, includes a 'Consignment receipt acknowledgement' feature where healthcare facilities acknowledge receipt of medical consignments by scanning barcodes on packing lists . These barcodes, which can be configured as QR codes, identify the consignment. For larger consignments with extensive documentation, Structured Append could be used to encode the complete packing list and receipt information across multiple codes, providing a paperless, scannable manifest. |
The benefit is clear: instead of manually entering data from a multi-page packing list, a warehouse worker scans a sequence of QR codes and the complete manifest is loaded into the inventory management system automatically. This reduces errors and speeds up the receiving process. |
Avery Dennison, a major US-based label manufacturer, provides QR code labeling solutions for logistics and supply chain applications, though their documentation primarily addresses standard QR codes . The extension to Structured Append for manifest encoding is a natural next step for high-volume shipping operations. |
|
Example 2: Medical Records and Healthcare Data |
Healthcare is one of the most promising fields for Structured Append. Patient records are complex, containing demographics, medical histories, medication lists, allergy alerts, test results, imaging reports, and treatment plans. While a single QR code on a patient wristband can hold critical identification and allergy information, a comprehensive record requires much more space. |
The Verifiable Health Link (VHL) specification, developed by the IHE (Integrating the Healthcare Enterprise) IT Infrastructure Technical Committee, provides a relevant example. VHL uses QR codes to encode secure links to health documents, including the manifest URL and decryption key . The payload is constructed as a JSON object containing the URL, encryption key, expiration time, and other parameters. This payload is minified, Base64url-encoded, and prefixed with 'vhlink:/' before being embedded in the QR code. |
While the current VHL specification does not explicitly mention Structured Append, the concept of encoding a 'full SHL payload' suggests that as medical data becomes more complex, the need for larger payloads will grow. Structured Append could allow a patient's complete medical record to be encoded across several QR codes, each representing a section of the record: the demographics code, the medication code, the allergy code, and so on. |
Another example is the OpenSpecimen platform, which supports creating specimen kits with barcode labels for tracking in biorepositories. The documentation notes that 'many labs now use pre-barcoded tubes (compatible with box scanners) as part of kits' and that 'these QR codes/barcodes needs to be associated with the kits' . For large kits with many specimens, Structured Append could allow the complete kit manifest to be encoded across multiple QR codes attached to the kit box. |
|
Example 3: Inventory Management and Asset Tracking |
Inventory management systems must track a vast number of items, each with its own unique identifier, location, status, and history. A single QR code on an item can encode a unique ID that references a database record, but in environments where database access is limited or where the item must be identifiable offline, storing more data directly in the code is valuable. |
Structured Append enables this by allowing an item's complete history to be stored across multiple QR codes. For example, a high-value asset like a piece of manufacturing equipment could have several QR codes attached to different parts. One code encodes the asset's basic identity and purchase date. A second code encodes the maintenance history. A third code encodes the warranty information. A compliant scanner reads all codes and presents the complete asset record. |
The US Department of Defense has explored QR codes for parts tracking, and the PolyCode program funded by DARPA has investigated advanced QR code generation techniques for defense applications. While the primary focus has been on security, the capacity and flexibility provided by Structured Append could be valuable for tracking complex defense systems with extensive documentation. |
|
Example 4: Construction and Engineering Documents |
Construction projects generate enormous amounts of documentation: blueprints, material specifications, safety certificates, inspection reports, and as-built drawings. These documents are often referenced on-site, where internet access may be limited. |
Structured Append offers a way to encode key documents directly onto QR codes that can be printed and attached to the physical structure. For example, a bridge could have QR codes on each major component. One code encodes the structural specifications. Another code encodes the concrete mix design. A third code encodes the inspection history. When an inspector scans the sequence of codes, they have instant access to the complete documentation for that component. |
The US construction industry has been slow to adopt QR codes for document management, but the benefits are clear. Structured Append makes it possible to store large documents without relying on a network connection. |
|
Example 5: Event Programs and Conference Materials |
Large conferences and events often provide attendees with printed programs that include schedules, speaker bios, session details, and exhibitor information. These programs can be dozens of pages long. Printing, distributing, and updating them is expensive and wasteful. |
Structured Append allows the entire program to be encoded as a sequence of QR codes printed on a single page or on a badge. An attendee scans the codes with their smartphone, and the complete program is loaded into their device. The program can be updated after printing because the QR codes link to a server that provides the latest content. |
This approach, described in the DHIS2 documentation as an 'Event program' for healthcare logistics, can be generalized to any event management scenario . The barcode field can be configured as a QR code, and the complete event program can be split across multiple codes for capacity. |
|
Example 6: Security and Information Hiding |
A fascinating application of Structured Append is in security, where it can be used to hide sensitive information across multiple QR codes. A patent from the US, US 10,062,023 B2, describes a method for concealing information within Structured Append QR codes . |
The patent describes a process where a message is split across two QR codes in a Structured Append sequence. One code contains the open information (the data that a standard decoder can read). The other code contains hidden information that is embedded by replacing part of a Reed-Solomon block with the secret data. A standard decoder reads the open information and ignores the hidden data. A specialized decoder, however, reads both codes, extracts the hidden information from the replaced block, and reconstructs the complete message . |
This approach is referred to as 'protection-encoding' or 'closed information' hiding. The parity data in the Structured Append header is common to both codes, allowing the specialized decoder to verify that the codes belong together. The error correction capability of the QR code (typically Level H for security applications) ensures that the hidden information can survive the replacement process . |
The practical applications of this technique are significant. It could be used to encode a digital signature that verifies the authenticity of a document. It could embed a watermark that identifies the owner of a product. It could store an encryption key that unlocks additional information when combined with the open data. |
The patent is careful to note that 'a plurality of protection-encoded Structured-Append enhanced QR codes may also be employed,' meaning that the technique can scale beyond two codes to a full sequence of up to 16 codes . |
|
Practical Considerations for System Designers |
If you are considering Structured Append for your application, there are several practical factors to consider. |
Scanner Support is Not Universal. The most important factor is that not all scanner apps support Structured Append. Many consumer apps decode each code individually. You must either use a specialized scanner or develop custom scanning software that can stitch the sequence together . |
Physical Organization of Codes. For a user to scan a sequence of codes, the codes must be physically organized and labeled. The user needs to know which order to scan them in, and the codes should be placed close together to make sequential scanning convenient. |
Error Correction Level. Since Structured Append sequences rely on multiple codes, each code's error correction level should be chosen based on the environment. If the codes will be exposed to damage, higher error correction levels (Q or H) are recommended. However, higher error correction reduces data capacity, so you may need more codes in the sequence. |
Version Selection. The version of each code in a Structured Append sequence can be the same or different. However, for simplicity and consistent scanning, most implementations use the same version for all codes . The Segno library, for example, allows you to specify either the version or the number of codes, and it automatically determines the other parameter . |
Parity Verification. The parity data in the Structured Append header allows a scanner to verify that all codes belong together. This is important for detecting if a code from a different sequence has been accidentally included. The scanner should check the parity and alert the user if there is a mismatch. |
Structured Append vs. Other Solutions. Before choosing Structured Append, consider whether a different approach might be better. For example, you could use a single code that encodes a URL pointing to a server where the full data is stored. This is the approach used by Verifiable Health Links . The advantage is that the scanner only needs to read one code. The disadvantage is that the device must have network access to retrieve the data. If offline operation is required, Structured Append may be the better choice. |
|
Structured Append in Software Libraries |
Several QR code generation libraries provide support for Structured Append, as we have noted. Let us look at these in more detail. |
Segno (Python). The Segno library provides a `make_sequence()` function that creates a sequence of up to 16 QR codes. You can specify either the version or the number of codes. If the content fits into one code, the sequence behaves like a single code . |
qrforge (Rust). The qrforge library includes a `build_with_structual_append()` method that splits input data across multiple codes. It requires specifying the version and error correction level . |
qrkit (Gleam). The qrkit library supports Structured Append and can encode a payload across up to 16 symbols. The header includes the mode indicator, symbol position, total minus one, and parity byte . |
qr_code (Rust). This library, forked from the original Rust QR code encoder, specifically added support for structured append because the original library lacked it . |
The availability of these libraries across multiple programming languages makes Structured Append accessible to developers building custom QR systems. |
|
Detailed Closing Summary |
Let us now consolidate everything we have covered in this chapter, reflecting on the significance of Structured Append in QR code technology and its applications in American industries. |
Structured Append is a powerful feature of the QR code standard that allows up to 16 individual QR codes to be chained together to form a single logical payload. Each code in the sequence carries a header containing the symbol position, the total number of symbols, and parity data. A compliant scanner reads all the codes in order, verifies the parity, and concatenates the data to reconstruct the complete message . |
The capacity of Structured Append is substantial. With up to 16 codes, each potentially at Version 40, the total payload can exceed 7 kilobytes of data, enough for substantial documents like shipping manifests, medical records, and technical specifications. |
Software support for Structured Append exists across multiple programming languages. The Segno library provides `make_sequence()` for Python . The qrforge and qr_code libraries provide Structured Append support for Rust . The qrkit library provides support for Gleam . However, scanner support is less universal. The qrkit documentation explicitly warns that 'Structured Append reader support varies in practice --- some scanner apps decode each symbol independently rather than stitching the payload back together' . |
|
In American industries, Structured Append is used or has potential in diverse applications: |
Shipping manifests and logistics: Encoding complete packing lists, including all line items, weights, and special handling instructions. |
Medical records: Encoding comprehensive patient data, medication lists, and treatment histories. |
Inventory management: Storing complete asset histories and maintenance records. |
Construction documentation: Encoding blueprints, specifications, and inspection reports. |
Event programs: Encoding schedules, speaker bios, and session details. |
Security applications: Hiding sensitive information across multiple codes using the 'closed information' technique described in US patent 10,062,023 B2 . |
|
The future of Structured Append is likely to see growing adoption as more scanner apps add support. The react-native-ios-qr-code-scanner package already includes 'structured format support' , suggesting that the trend is toward broader compatibility. As the Internet of Things (IoT) and offline-first applications become more common, the ability to store large amounts of data in scannable QR codes will become increasingly valuable. |
For the end user, Structured Append is invisible when it works correctly---you scan a sequence of codes and the complete data appears. But for the system designer, Structured Append is a tool that extends the QR code's capacity far beyond what a single symbol can hold. It enables applications that would otherwise require network connections or manual data entry, making QR codes even more versatile as a bridge between the physical and digital worlds. |
The US patent on security-enhanced Structured Append hints at even more sophisticated uses. By combining the chaining capability with error correction replacement techniques, it is possible to create QR codes that contain both public and private information, accessible only to specialized decoders. This could be the foundation for new authentication, anti-counterfeiting, and secure document verification systems. |
|
In summary, Structured Append is the QR code standard's answer to the question: 'What if one code is not enough' It allows you to break a large message into scannable pieces and reconstruct it automatically, without requiring the user to be a database administrator or a data entry specialist. It is a feature that deserves more attention and wider adoption, especially in industries that deal with complex, multi-part data. |
cs@easiersoft.com