We use cookies to keep the site working, understand how it’s used, and measure our marketing. You can accept everything, reject non-essentials, or pick what’s on.
Published: May 4, 2026 | Category: Blockchain & Healthcare Technology | Reading Time: ~18 min
By aquicksoft
Hyperledger Fabric for Pharmaceutical Supply Chain: A Technical Deep Dive into Blockchain-Enabled Drug Traceability
Published: May 4, 2026 | Category: Blockchain & Healthcare Technology | Reading Time: ~18 min
1. The Counterfeit Drugs Crisis and Blockchain as a Solution
The World Health Organization estimates that counterfeit pharmaceuticals account for approximately 10% of the global drug supply, a figure that rises to as much as 30% in low- and middle-income countries. These falsified medicines cause an estimated one million deaths annually and cost the pharmaceutical industry over $200 billion per year. The problem is not merely financial; counterfeit drugs containing incorrect active ingredients, insufficient dosages, or toxic contaminants directly threaten patient safety on a massive scale. In 2023 alone, Interpol seized more than 21 million units of illicit pharmaceuticals across 89 countries during Operation Pangea XVI, underscoring the relentless scale of this global threat.
Traditional pharmaceutical supply chains are inherently vulnerable to infiltration. A typical drug passes through four to seven intermediaries—manufacturers, repackagers, wholesale distributors, third-party logistics providers, and pharmacies—before reaching the patient. Each handoff represents a potential point of entry for counterfeit products. Legacy track-and-trace systems rely on centralized databases that can be tampered with, lack interoperability between trading partners, and provide limited real-time visibility into product movement. Paper-based documentation remains common in many jurisdictions, further eroding the reliability of provenance records.
Distributed ledger technology (DLT), and Hyperledger Fabric in particular, offers a fundamentally different approach to pharmaceutical supply chain integrity. By providing an immutable, shared, and cryptographically secured record of every transaction across the entire supply chain, blockchain enables real-time verification of drug authenticity at each point of custody transfer. Unlike public blockchains such as Ethereum or Bitcoin, Hyperledger Fabric is a permissioned, enterprise-grade blockchain framework that addresses the specific requirements of pharmaceutical supply chains: data privacy, regulatory compliance, high throughput, and governance flexibility. This article provides a comprehensive technical analysis of how Hyperledger Fabric can be architected, deployed, and integrated to meet the stringent requirements of pharmaceutical drug traceability systems.
2. Regulatory Landscape and Blockchain Fundamentals
2.1 DSCSA Requirements and Supply Chain Challenges
The Drug Supply Chain Security Act (DSCSA), enacted by the U.S. Congress in 2013, establishes a comprehensive framework for building an interoperable, electronic system to identify and trace prescription drugs as they move through the U.S. pharmaceutical distribution supply chain. The legislation was implemented in phases, culminating in the final interoperability requirements originally targeted for November 2023 (with the enforcement deadline extended to November 2024). Under the enhanced requirements, manufacturers must serialize every unit-level package with a unique product identifier, wholesale distributors and dispensers must verify and electronically share transaction information (TI), transaction history (TH), and transaction statements (TS) at the package level, and all trading partners must participate in an interoperable electronic system for product verification and tracing.
The GS1 Standards system forms the backbone of DSCSA compliance. Each serialized product receives a GS1 DataMatrix 2D barcode containing the product’s National Drug Code (NDC), unique serial number, lot number, and expiration date. GS1’s Electronic Product Code Information Services (EPCIS) standard provides the event-based data format for capturing and sharing traceability events—such as “commissioning,” “shipping,” “receiving,” and “dispensing”—across trading partners. However, the interoperability mandate requires not merely electronic data exchange, but a trusted, tamper-proof mechanism for verifying that serialization data has not been altered, that transaction histories are complete and authentic, and that suspect or illegitimate products can be rapidly identified and quarantined across the entire supply chain.
These requirements expose critical weaknesses in existing supply chain infrastructure. Most trading partners operate proprietary track-and-trace systems that are siloed and incompatible. Point-to-point integration between systems is expensive, fragile, and difficult to maintain across hundreds of trading relationships. Reconciliation of transaction data between partners is often a manual, error-prone process. When a recall or suspect product investigation is initiated, assembling the complete chain of custody from manufacturer to pharmacy can take weeks, during which potentially dangerous products may continue to reach patients. Blockchain technology directly addresses these challenges by providing a shared, append-only ledger that all authorized participants can trust without relying on a central authority.
2.2 Why Hyperledger Fabric Over Other Blockchain Platforms
While multiple blockchain platforms exist, Hyperledger Fabric is uniquely suited for pharmaceutical supply chain applications. Several critical differentiators set it apart. First, Fabric is a permissioned network, meaning all participants are identified and authenticated through a Membership Service Provider (MSP). This is essential for regulated industries where anonymous participation (as on public blockchains) is incompatible with Know Your Customer (KYC) and Good Distribution Practice (GDP) requirements. Second, Fabric’s execute-order-validate architecture enables high transaction throughput, achieving 3,000 to 20,000 transactions per second (TPS) depending on configuration—far exceeding the capabilities of Ethereum’s proof-of-work consensus. For pharmaceutical supply chains processing millions of serialized transactions daily, this performance margin is critical.
Third, Fabric’s modular consensus mechanism allows networks to use pluggable ordering services (Raft, Kafka, BFT) optimized for specific trust assumptions and performance requirements. Unlike Ethereum or Bitcoin, where all transactions are visible to all participants, Fabric provides fine-grained privacy controls through channels and private data collections (PDCs), enabling trading partners to share only the data necessary for verification while keeping commercially sensitive information—such as pricing, quantities, and supplier relationships—confidential. Fourth, Fabric supports smart contracts (called “chaincode”) written in Go, Java, and Node.js, allowing pharmaceutical companies to leverage existing developer expertise and integrate chaincode logic with their enterprise Java and Go microservices architectures.
3. Hyperledger Fabric Architecture for Pharma Traceability
3.1 Network Topology and Organizational Roles
A production-grade Hyperledger Fabric network for pharmaceutical supply chain management typically involves multiple organizations representing the key stakeholders in the drug distribution lifecycle. The network topology must be designed to balance data sharing requirements with privacy constraints. In a reference architecture, the primary channel—referred to as “pharma-trace-channel”—includes peer nodes from manufacturing organizations, wholesale distributor organizations, third-party logistics (3PL) providers, retail pharmacy chains, and potentially a regulatory authority node for oversight and audit purposes. Each organization operates one or more peer nodes that maintain a copy of the distributed ledger and endorse transactions according to the chaincode endorsement policy.
The ordering service is a critical infrastructure component that determines transaction ordering and block creation. For pharmaceutical supply chains, the Raft consensus protocol is the recommended ordering service implementation, providing crash fault tolerance with a leader-based approach that delivers deterministic ordering with low latency (typically under 1 second for transaction confirmation). The ordering service nodes are typically operated by a consortium of major supply chain participants or by a neutral trusted third party. Channel configuration defines the endorsement policies that specify which organizations must approve a transaction before it is committed to the ledger—for example, a drug transfer transaction might require endorsement from both the shipping and receiving organizations.
The Membership Service Provider (MSP) manages identity and access control for the network. Each organization operates its own MSP using Certificate Authorities (CAs) based on the Fabric CA component. Identity certificates issued by the MSP are embedded in every transaction proposal, creating a cryptographically verifiable audit trail that links each ledger entry to the specific organization and user that submitted it. This identity framework is essential for regulatory compliance, as it enables investigation authorities to trace any transaction back to its originating party. Certificate Revocation Lists (CRLs) and Fabric’s Attribute-Based Access Control (ABAC) further enable granular permission management—for instance, restricting serialization operations to manufacturer identities and verification operations to distributor and pharmacy identities.
3.2 Smart Contract (Chaincode) Design for Pharma Tracking
The chaincode layer implements the business logic for pharmaceutical tracking. A well-designed pharma chaincode typically defines key data models and transaction functions. The core data model centers on a DrugAsset, which captures the serialization information mandated by DSCSA: product identifier (GTIN+serial), lot number, expiration date, current owner, custody status, and a chain of provenance events. Additional data structures may include TransactionRecords (TI/TH/TS equivalents), VerificationRequests, and RecallNotices. Below is a representative Go chaincode implementation for drug asset creation and transfer:
This chaincode demonstrates several key design patterns for pharmaceutical tracking. The CreateDrugAsset function implements serialization commissioning, creating an immutable record of the drug’s identity at the point of manufacture. The TransferDrugOwnership function implements custody transfer, appending provenance events to form a complete chain of custody. The VerifyDrug function enables point-of-dispensing verification, allowing pharmacies to authenticate products before distribution to patients. Each transaction automatically captures the caller’s MSP identity, transaction ID, and timestamp, creating a comprehensive audit trail.
3.3 Drug Serialization and Verification Workflow
The end-to-end drug serialization and verification workflow on Hyperledger Fabric follows a well-defined sequence of operations that maps directly to DSCSA-mandated processes. The workflow begins at the manufacturing facility, where a serialization system generates unique serial numbers and encodes them into GS1 DataMatrix 2D barcodes on each unit-level package. The manufacturing application invokes the CreateDrugAsset chaincode function, writing the initial drug asset record to the ledger with the product’s GTIN, serial number, lot number, and expiration date. The ledger record is endorsed by the manufacturer’s peer nodes and committed to the channel ledger, creating the immutable origin record for that specific drug package.
When the manufacturer ships products to a wholesale distributor, a TransferDrugOwnership transaction is invoked. The manufacturer’s application submits a transaction proposal that includes the list of GTIN-serial combinations being shipped, the recipient organization’s identifier, and the shipping location. The endorsement policy requires both the manufacturer’s and the distributor’s peer nodes to endorse the transaction, ensuring that both parties agree on the transfer details. Once endorsed and ordered, the transaction is committed to the ledger, updating the CurrentOwner field for each drug asset and appending a provenance event to the custody chain. The distributor’s receiving application can then reconcile the physical product received against the ledger records, verifying that all expected serial numbers match and flagging any discrepancies.
The verification workflow is triggered at the point of dispensing. When a pharmacy receives a drug shipment from a distributor, the pharmacy’s dispensing system scans the GS1 DataMatrix barcode and invokes the VerifyDrug chaincode function. The chaincode performs a series of checks: it confirms that the drug asset exists on the ledger, verifies that the current ownership chain is unbroken, checks that the product has not expired, and confirms that the product is not flagged as recalled or suspect. If all checks pass, the drug is verified as authentic and can be dispensed to the patient. If any check fails—such as a gap in the provenance chain, an expired product, or a recalled serial number—the verification returns an alert, and the pharmacy’s system can automatically quarantine the suspect product and notify the relevant authorities.
For recall scenarios, the chaincode can implement a RecallDrug function that updates the CustodyStatus field for affected serial numbers (either by specific serial, lot number, or GTIN range) to “RECALLED.” Because the ledger is shared across all participating organizations, this status change is immediately visible to all trading partners, enabling rapid identification and quarantine of recalled products regardless of where they currently reside in the supply chain. This is a significant improvement over traditional recall processes, which often rely on phone calls, emails, and manual record searches that can take days or weeks to complete.
3.4 Multi-Organization Network Setup
Setting up a multi-organization Hyperledger Fabric network for a pharmaceutical supply chain involves several carefully orchestrated steps. The network bootstrapping process typically uses Hyperledger Fabric’s configuration transaction (configtx) mechanism to define the channel configuration, organizational memberships, and policies. Below is a simplified example of a configtx.yaml configuration for a pharma supply chain network:
The chaincode endorsement policy is a critical configuration parameter that enforces the business rules for transaction approval. For pharmaceutical supply chains, the endorsement policy for drug transfer transactions should require endorsement from both the sending and receiving organizations. This is defined when instantiating or upgrading chaincode on the channel:
3.5 Private Data Collections for Sensitive Business Data
One of the most significant advantages of Hyperledger Fabric for pharmaceutical supply chains is its support for private data collections (PDCs). In a typical supply chain, trading partners need to share product provenance data for verification purposes but want to keep commercially sensitive information—such as purchase prices, order quantities, supplier relationships, and contract terms—confidential. Private data collections enable precisely this: a subset of channel organizations can share sensitive data among themselves while the broader channel sees only a hash of that data, which is sufficient for verification without revealing the underlying content.
In the pharmaceutical context, a manufacturer and a distributor might share a private data collection for their bilateral transactions, including pricing and volume data, while publishing only the serialized product identifiers and custody transfer events to the channel ledger. A pharmacy performing verification can query the channel ledger to confirm that a product has a valid provenance chain without seeing the commercial terms of any upstream transaction. This architecture is essential for pharmaceutical industry adoption, as companies are strongly resistant to sharing pricing and contract data with competitors or downstream parties.
The collections_config.json above defines three private data collections. The “mfrDistributorPrivateData” collection enables bilateral data sharing between manufacturers and distributors, including pricing and volume information that remains invisible to pharmacies and other parties. The “distributorPharmacyPrivateData” collection similarly enables confidential data sharing between distributors and pharmacies. The “regulatorAuditData” collection allows regulatory authorities to access aggregated audit data from all trading partners. The blockToLive parameter controls data purge; setting it to 43800 (approximately 5 years at one block per hour) for regulator data ensures compliance with record retention requirements while automatically purging stale operational data.
3.6 Integration with Existing ERP/WMS Systems
For pharmaceutical companies, a blockchain traceability system is only valuable if it integrates seamlessly with existing enterprise systems. Most large pharmaceutical manufacturers and distributors operate Enterprise Resource Planning (ERP) systems (such as SAP S/4HANA or Oracle ERP Cloud) and Warehouse Management Systems (WMS) that already manage serialization, inventory, and order fulfillment. The integration architecture typically follows a middleware pattern, where a blockchain integration layer acts as a bridge between the ERP/WMS systems and the Hyperledger Fabric network.
The Fabric SDK (available for Node.js, Java, and Go) provides the client libraries for connecting enterprise applications to the blockchain network. A typical integration architecture includes the following components: an event-driven message broker (Apache Kafka or RabbitMQ) that receives serialization and transfer events from the ERP system, a blockchain adapter service that transforms ERP events into chaincode invocations and submits transactions to the Fabric network, a listener service that subscribes to block events from the Fabric network and updates the ERP system with confirmed transaction statuses, and a reconciliation engine that periodically compares ERP inventory records with on-chain asset states to identify and resolve discrepancies.
The GS1 EPCIS standard plays a critical role in this integration. Most pharmaceutical serialization systems already generate EPCIS events—such as ObjectEvent (shipping/receiving), AggregationEvent (case/pallet aggregation), and TransactionEvent (sale/transfer)—in XML or JSON format. The blockchain adapter can consume these standard EPCIS events, map them to chaincode function calls, and record the corresponding provenance events on the ledger. This approach minimizes changes to existing serialization infrastructure and leverages the significant investment that pharmaceutical companies have already made in GS1-compliant systems.
API gateway integration is also essential for enabling trading partner onboarding. A RESTful API layer (implemented using frameworks such as Spring Boot, Express.js, or Go Gin) exposes blockchain query and transaction functions as standard web services, allowing trading partners with different technology stacks to participate in the network. The API layer handles authentication (using OAuth 2.0 or API keys), request validation, rate limiting, and transaction submission to the Fabric SDK. For high-volume operations—such as batch serialization of millions of packages during a production run—the API should support asynchronous batch processing to avoid blocking the caller while transactions are being endorsed and committed.
4. Real-World Deployments and Case Studies
4.1 The MediLedger Project
The MediLedger Project is the most significant real-world deployment of blockchain technology for pharmaceutical supply chain management. Initiated in 2017 by the company Chronicled (now part of sourcingstudio), MediLedger brought together 24 leading pharmaceutical companies and supply chain stakeholders—including Pfizer, Gilead Sciences, AmerisourceBergen, McKesson, Cardinal Health, and Walgreens—to pilot a blockchain-based solution for DSCSA compliance. The project was formally submitted to the FDA as a DSCSA Pilot Project and published its final report in January 2020, demonstrating the feasibility of blockchain as the interoperable system mandated by the DSCSA.
The MediLedger network operates on a permissioned blockchain (initially built on the Parity Ethereum client and later migrated to a custom network) and focuses specifically on two use cases: verifiable unit-level drug serialization and verification, and returns processing for expired or unwanted pharmaceutical products. In the serialization pilot, participating companies demonstrated that a shared blockchain ledger could provide near-real-time (approximately 50-millisecond latency) verification of drug authenticity, with immutable, time-stamped records that create an auditable chain of custody. The returns processing pilot showed that blockchain could reduce the time required to verify and authorize pharmaceutical returns from days to minutes, while preventing the reintroduction of recalled or expired products into the supply chain.
The FDA’s summary of the MediLedger pilot concluded that “it is feasible to use a blockchain-based solution for compliance with DSCSA requirements related to product verification and the exchange of transaction information.” The project demonstrated that blockchain could serve as the trust layer for interoperable data exchange between trading partners without requiring a central authority. Importantly, the pilot also revealed practical challenges: achieving consensus among competitors on network governance, managing the complexity of onboarding hundreds of small pharmacies and distributors, and ensuring that blockchain-based verification integrates reliably with existing serialization and verification systems.
4.2 PharmaPortal and Other Initiatives
Beyond MediLedger, several other blockchain-based pharmaceutical supply chain initiatives have emerged. PharmaPortal, a consortium project led by European pharmaceutical companies, explores blockchain for compliance with the European Union’s Falsified Medicines Directive (FMD), which requires serialization and verification of prescription medicines across the EU. The project uses Hyperledger Fabric to create a decentralized system for sharing serialization data between national verification systems, addressing the challenge of cross-border pharmaceutical traceability within the European Economic Area.
In India, the Apollo Hospitals Group and other healthcare organizations have explored blockchain-based solutions for drug traceability to combat the country’s significant counterfeit drug problem. India’s drug regulatory authority, the Central Drugs Standard Control Organisation (CDSCO), has expressed interest in blockchain as a complement to its existing track-and-trace system, particularly for high-risk pharmaceutical categories such as oncology drugs and vaccines. Academic research has produced frameworks such as PharmaChain (a Hyperledger Fabric-based provenance verification system published in Heliyon), TrackChain (a pharmaceutical supply chain system based on Hyperledger Fabric published in IEEE/PMC), and PHTrack (a Hyperledger Sawtooth-based traceability framework published in Computers & Industrial Engineering). These research prototypes demonstrate the technical viability of blockchain for pharma traceability and provide reference architectures for production deployments.
5. Challenges, Limitations, and Adoption Barriers
5.1 Scalability Challenges
While Hyperledger Fabric offers significantly better performance than public blockchain alternatives, scalability remains a challenge for pharmaceutical supply chain applications at the scale required by the DSCSA. The U.S. pharmaceutical distribution system processes approximately 4 billion prescription drug packages annually, translating to tens of millions of serialization events per week. Even at Fabric’s upper throughput range of 20,000 TPS, handling peak loads during mass serialization campaigns (such as product launches or recall events that require verification of millions of packages simultaneously) requires careful capacity planning, horizontal scaling of peer nodes, and optimization of endorsement policies.
The state database size is another scalability concern. Hyperledger Fabric uses CouchDB or LevelDB as the state database for storing current world state, while historical data is stored in the blockchain’s append-only log. For a network tracking billions of serialized drug packages, the state database can grow to terabytes in size, requiring robust storage infrastructure and periodic compaction strategies. Rich queries against CouchDB (which support complex queries using MongoDB-style selectors) are essential for pharmaceutical use cases—such as querying all drugs in a specific lot or from a specific manufacturer—but these queries must be carefully optimized to avoid performance degradation as the database grows.
5.2 Adoption Barriers
The adoption of blockchain technology in pharmaceutical supply chains faces several significant barriers. First, the governance challenge: establishing a blockchain consortium requires competing pharmaceutical companies and distributors to agree on shared governance structures, data sharing policies, and operational procedures. These negotiations are complex and time-consuming, as each participant has different business models, regulatory obligations, and risk tolerances. The MediLedger project took nearly three years from inception to FDA report submission, and the broader industry has been slow to follow its lead.
Second, the cost of implementation is substantial. Pharmaceutical companies must invest in blockchain infrastructure (peer nodes, ordering service, certificate authorities), integration development (connecting ERP and WMS systems to the blockchain network), and ongoing operational management (network monitoring, certificate management, software upgrades). For small and medium-sized pharmacies and distributors, these costs can be prohibitive. Third, the skills gap is significant: blockchain development requires specialized expertise in distributed systems, cryptography, and the Hyperledger Fabric framework that is not readily available in most pharmaceutical IT organizations.
Fourth, regulatory uncertainty persists. While the FDA has acknowledged the feasibility of blockchain for DSCSA compliance through the MediLedger pilot, the agency has not formally endorsed blockchain as a compliance mechanism, and the regulatory framework for blockchain-based pharmaceutical traceability remains undefined. Questions about data residency, privacy (particularly under HIPAA and state privacy laws), legal admissibility of blockchain records, and liability for smart contract errors remain unresolved. Fifth, interoperability between different blockchain networks and between blockchain and non-blockchain traceability systems is an ongoing challenge. The pharmaceutical supply chain is global, and a solution that works in the United States must interoperate with systems in the EU, Japan, and other markets that may use different blockchain platforms or no blockchain at all.
6. Conclusion and Future Implications
Hyperledger Fabric represents the most technically mature and architecturally appropriate blockchain platform for pharmaceutical supply chain traceability. Its permissioned network model, fine-grained privacy controls through channels and private data collections, high transaction throughput, pluggable consensus mechanisms, and support for enterprise programming languages make it uniquely suited to the regulatory, commercial, and operational requirements of the pharmaceutical industry. The MediLedger pilot project has demonstrated that blockchain-based solutions can achieve near-real-time drug verification, create immutable audit trails for regulatory compliance, and enable efficient interoperable data exchange between trading partners—all critical requirements of the DSCSA.
However, the path from pilot to production at industry scale remains challenging. Scalability optimization, governance standardization, cost reduction for small participants, regulatory clarification, and interoperability framework development are all essential prerequisites for widespread adoption. The pharmaceutical industry’s conservative approach to technology adoption, combined with the complexity of multi-stakeholder coordination, suggests that full blockchain-based traceability will be achieved incrementally rather than through a single transformative deployment.
Looking forward, several trends are likely to accelerate blockchain adoption in pharmaceutical supply chains. The DSCSA’s interoperability mandate creates regulatory urgency that was absent in earlier years. The growing maturity of Hyperledger Fabric—particularly Fabric 2.x and beyond, with its improved lifecycle management and enhanced private data capabilities—reduces technical risk. The emergence of blockchain-as-a-service offerings from major cloud providers (IBM Blockchain Platform, AWS Managed Blockchain, Azure Blockchain Service) lowers the barrier to entry for organizations that lack the infrastructure to operate their own peer nodes. And the increasing use of AI and machine learning for supply chain analytics creates demand for the high-quality, trusted data that blockchain-based traceability systems can provide.
For pharmaceutical companies, distributors, and technology providers evaluating blockchain for supply chain traceability, the recommendation is to begin with a focused pilot program—modeled on the MediLedger approach—that addresses a specific, high-value use case (such as high-risk drug verification or returns processing), involves a small consortium of willing trading partners, and integrates with existing serialization infrastructure through GS1 EPCIS-compliant interfaces. Success at this stage creates the organizational knowledge, governance precedents, and technical foundation for incremental expansion to broader use cases and a larger network of participants.
7. References
[1] U.S. Food and Drug Administration (FDA). “MediLedger DSCSA Pilot Project Final Report.” FDA Pilot Project Report, January 2020. Available at: https://www.fda.gov/media/168283/download
[2] U.S. Congress. Drug Supply Chain Security Act (DSCSA), Title II of the Drug Quality and Security Act, Public Law 113-54, enacted November 27, 2013.
[11] PHTrack. “Hyperledger Sawtooth Based Supply Chain Traceability System for Pharmaceuticals.” Computers & Industrial Engineering, Elsevier, 2024. DOI: 10.1016/j.cie.2024.110021
[12] Kshetri, N. “Blockchain and Drug Traceability in Pharmaceutical Supply Chains.” Journal of Business Research, Elsevier, 2025. DOI: 10.1016/j.jbusres.2023.01.001
[13] Springer. “Hyperledger Fabric-Based Secure and Privacy-Preserved Medicine Supply Chain.” Journal of Supercomputing, Springer, 2025. DOI: 10.1007/s12083-025-02092-8
[14] Sage Journals. “Blockchain for Drug Traceability: Architectures and Open Challenges.” Health Informatics Journal, 2022. DOI: 10.1177/14604582211011228
[15] Tracelink. “DSCSA 2023: Requirements, Necessary Capabilities, and Implementation Considerations.” Whitepaper, 2023. Available at: https://www.tracelink.com/node/23646/pdf
[16] Tiwari, S. et al. “Blockchain-Enabled Drug Traceability Systems: Implications for Pharmacy Supply Chain Transparency.” IJRMP, 2025.
[17] Emerald Publishing. “Pharmaceutical Supply Chain Blockchain Adoption Barriers and Drivers in Developing Countries.” Business Information Review, 2026. DOI: 10.1108/BIJ-02-2025-0130
