Definition
Electronic Supervision Code (drug traceability code) is a unique identification code assigned to each box/bottle/injectable of medicine. It usually uses GS1 coding or a unified drug regulatory code and is used for full-chain traceability of drug production, circulation, and use. Scanning the code allows checking information such as drug authenticity, circulation, batch number, expiration date, and storage conditions, meeting the regulatory requirements for drug traceability and supporting GSP (Good Supply Practice) and GDP (Good Distribution Practice), among others.
China's drug traceability system adopts a 'one item, one code; same code follows the item' approach, requiring drug marketing authorization holders, manufacturers, distributors, and users to upload traceability data to the national drug regulatory platform or a third-party traceability platform as specified.
Technical Features
The electronic supervision code uses barcode or QR code formats and is associated with drug packaging. Codes are assigned and linked during production, scanned in and out during circulation while uploading data, and scanned for sales or usage during retail/use. Devices such as barcode scanners, PDAs, smart medicine cabinets, and automatic dispensing machines upload scanning data in real time to the traceability platform via IoT SIM cards, ensuring data integrity and timeliness.
Use Cases
Electronic supervision codes are widely used in drug production, wholesale, retail, medical institutions, and pharmacies. Typical scenarios include code assignment and association during production, scanning for in-and-out inventory, sales scanning, prescription drug traceability, and cold chain drug temperature control traceability. SimtoLink provides traceability equipment with stable networking, dedicated APN, and MLPS compliance solutions to ensure real-time reporting of traceability data.
A wrong step time breaks the traceability chain
On an IoT SIM, an electronic supervision code means each manufacturing, distribution, or use step reports when this code passed from which party to which party. It does not only mean the scanner beeped. Coding at production, wholesale in and out, retail sale, and split-pack sale happen at different times and under different responsible parties. The SIM connects a scanner, a handheld, a smart cabinet, or a vending machine. A usable record can string the code, the batch, the step, and the party. Without the step time, the code still exists on the platform and the chain breaks at that hop. If a delayed batch upload writes an afternoon outbound as happening after an evening inbound, first-expiry handling and the recall scope are both wrong.
The terminal must be able to store unscanned-up scans locally in a pharmacy back room, a cold store, and a basement, and catch up in scan order after recovery, not reorder them by the moment the network returned. Bind the SIM to the store or warehouse and the device id. Stop it when the device goes for repair, so the repair point cannot keep uploading that party’s movements. Split-pack, case assembly, and returns need transaction types different from a full-box sale. Do not reuse a sale message. If a cold-chain medicine also carries temperature, the temperature record and the code’s movement should be able to cite each other, but do not stuff the temperature curve into every scan and cause failed retries. If the receiving address is the drug regulator or a named traceability platform, limit access to those addresses. The clock must match the platform, or a count that crosses midnight puts today’s sales into yesterday.
A common error is to upload the cache in reverse order when the network returns. A code sold later leaves inventory first, and the system judges the earlier sale illegal. Another is a repeated scan counted as two sales, so stock and traceability are both overstated. A third is allowing a scan only when online, then switching to handwriting when the link drops, and backfilling later with no original time, so a recall cannot prove that segment. Several stores sharing one upload account and no store id concentrate the code’s movement on the wrong party. Acceptance should drop cellular in the middle of one receipt, keep scanning, and after recovery check that those codes have one receipt each and that the time is still the scan time. The general practice for item identity is described under one item, one code. Storage and transport conditions are described under GDP.
Keep one effective movement per code at each hop. A repeated scan returns the original record and does not create a new one. Returns, damage, and split-pack each use their own transaction. Do not substitute a reverse sale, or the recall scope miscounts quantity already split. Catch up scans from an outage in local order. The platform refuses an out-of-order overwrite. Rate-limit a store’s bulk upload on stock-count day so it does not block live sales from other stores in the same city. Stop the SIM and export unsent codes before a device goes for repair. The repair point should not keep that store’s right to upload. Associate a cold-chain temperature record with the code by batch or case id. A batch that failed temperature stays visible in the movement, but do not put the whole temperature curve into every retail scan. A terminal whose clock is outside the allowed skew should be blocked from upload first, then corrected, then catch up at the original scan time. At a regulatory check, follow a retail code to the receipt time and the supplier. If a hop is missing, mark where the gap is. Do not fill the earlier hop with the later hop’s time.
Cap a batch catch-up and send it in scan order. Pushing three days of a store’s sales the moment the network returns can look to the platform like abnormal scanning. Send the relationship between a split-pack code and the full-box code at upload time. Filling that relationship in later collides with records already sold. If someone set the terminal clock by hand, restore time sync before upload is allowed, and mark the altered interval as time-untrusted. Time-untrusted records do not take part in recall ordering until they have been reordered by the original scan sequence.