Author Archives: Shripada Hebbar

Shripada Hebbar
Shripada Hebbar is our Principal Technical Architect. With 20+ years of experience, he has been instrumental in creating digital solutions for global clients across domains. He has expertise in multiple technologies and has a keen interest in Blockchain and its applications.
Blockchain Digital Health Digital Transformation Healthcare

How Hyperledger Fabric, a Blockchain Technology can revolutionize Clinical Trials

The approximate cost of drug discovery has reached $2.6 billion, which is a tenfolds increase in the last decade. Clinical trials are an important aspect of the drug discovery process and also adds to this cost. It has become extremely critical for the pharma companies and the CROs (Clinical Research Organizations) to adopt technologies that can optimize these costs and enable a faster and secure critical trial process.

The data generated in Clinical Trials is crucial in the preparation of peer-reviewed journal papers and approval applications for regulatory bodies. Therefore, data validation, data management, and data integrity play the most important role in Clinical Trials.

There are several impediments to the validity of Clinical Trials data. For instance, loss or alteration of data, redundant and non-transparent database management systems, data duplication and manipulation, etc.

There is a need for the industry to adopt technologies that can accelerate the pace of data validation, help in managing higher standards of data transparency, and maintain stricter fraud prevention practices. Blockchain and its Hyperledger Fabric framework, are now emerging as a technology that the industry has started to explore to solve for these issues.

In this article, we will outline how the open-source blockchain framework, Hyperledger Fabric can help in creating a more efficient, secure, and faster Clinical Trial process.

The Challenges of data management during the Clinical Trial process

The end-to-end Clinical trial process, including the preclinical phase, often can be lengthy and expensive taking 10-15 years to complete, with the median cost reaching approximately $19 million. Further, it requires communication between multiple stakeholders including academic researchers, journal editors and publishers, drug and device companies, government regulators, patients, etc. This increases the complexity of the clinical trial process, in terms of data collection, data management, data integrity, etc.

Sample clinical management workflow

Sample clinical management workflow – Data source

In this kind of Clinical Trials process, the different stages of Clinical Trials are conducted independently of each other. This is often due to the legacy technology and legacy approach to conducting Clinical Trials.

In this system:

  • Data is created at multiple channels – hospitals, Clinical Trials, smart devices, etc.
  • Data is then collected and stored in an organization-specific Centralized Database Management System (DBMS).
  • Different stakeholders like pharmaceutical companies, hospitals, CROs, Biotech, laboratories have their own decentralized databases.
  • Different organizations then collate and store data in their own preferred way and own preferred format in their own IT environments.
  • Data is then analyzed separately within each organization and results are presented to regulatory authorities.

In this model, collaboration is not only difficult between multiple parties involved in the process, but collaboration is also difficult within organizations.

Given the complexity of the ecosystem, the Clinical Trial process is faced by many challenges from data management to scalability. Some of these are:

Data validation and cleaning – Clinical trial professionals spend a huge amount of time in cleaning and preparing data to meet the demands of the evolving pharma and the life sciences industry. According to a study by Oracle, data completeness, data quality and data cleaning remain the topmost operational challenges for Clinical Trial professionals.

Clinical Trial data

Image source

The quality of the trial data can be affected by a number of factors like missing data, endpoint switching, data dredging, selective publication, etc.

Inconsistent data – During Clinical Trials multiple versions of data are created from sources like external labs, CROs, other vendors. This system gets increasingly complex with the globalization of Clinical Trials. The storage of data in siloed systems which leads to duplication and creates difficulties in accessing the required data.

No single platform of data aggregation – Clinical data is not easy to access, due to multiple sources of data collection. This leads to a huge amount of time spent by researchers in finding answers to research queries, which needs pulling data from a variety of sources and reports.

Manual Data Entry – The systems which have manual data entry do not allow for automatic integration with a broader record and thus investigators are not able to analyze data in real-time.

Adherence to regulatory norms: Clinical trial processes need to adhere to regulatory authority compliant system such as 21 CFR Part 11. Often necessary regulatory processes slowing research because timely approval is not given for data use.

Another issue faced by the US Food and Drug Administration is updating of data by the publicly-funded Clinical Trial labs. According to the FDA, all the publicly-funded Clinical Trial labs should submit the data done on human subjects to the designated public repositories. While portals like clinicaltrials.gov allow the depositing of research data with the help of services like Fighare, only a few research groups follow this. And even if they do follow they seldom to it consistently over a long-term, leading to missing information.

According to a report on Forbes, it is estimated that 50% of Clinical Trials go unreported, and investigators often fail to share their study results (e.g. nearly 90% of trials on ClinicalTrials.gov lack results). This may result in crucial safety issues for patients and create an information gap for healthcare stakeholders and health policymakers.

Data security: The Clinical Trial data is sensitive and preventing data leakage, fraud and misuse of confidential data are of prime importance. Hence, data verification through multi-party channels is required. Further, ensuring that data sharing is consistent with federal and local regulations is also one of the challenges that the industry faces.

Cost implications: Due to the complexity of the Clinical Trials process and the above issues, the cost of conducting Clinical Trials is high. Further, the tight delivery timelines put additional pressure on the Clinical research professionals and CROs

How Blockchain Technology can help to solve these issues

The BFSI sector has been long facing the issue of data attrition and data fraud, and Blockchain Technology has been one of the solutions that the sector has been looking forward to. In a digital era, technologies are no longer limited to one industry and the healthcare sector too is starting to explore the benefits of blockchain in various areas and Clinical Trials are one of them.

Blockchain technology is a peer-to-peer distributed ledger-based system where the information is stored in a distributed shared ledger, which can only be manipulated by something called transactions. Transactions are digitally signed and encrypted form of communication between the client and the blockchain app.

There are various Blockchain frameworks available like Entehreum, Hyperledger Fabric, R3 Corda, Ripple, Quorum, Multichain, BigChainDB, and Chain. Ethereum and Hyperledger Fabric are the two most popular frameworks.

In our recent webinar – Introduction to Hyperledger Sawtooth: An open-source enterprise blockchain platform, we simplified the concept of blockchain and helped participants understand how Hyperledger Sawtooth can be implemented for businesses – with a live demo. You can watch the replay of this webinar here.

Ethereum vs Hyperledger Fabric and why Hyperledger Fabric is better suited for Clinical Trials

What is Ethereum?

Ethereum is an open-source blockchain platform where decentralized applications can be built using Smart Contracts. As the Smart Contracts on which Ethereum runs are decentralized, they are open to everyone in the network.  This aspect is not favorable for privacy-conscious data that the Clinical trial ecosystem deals with.

The Clinical Trial ecosystem is complex with multiple stakeholders requiring time-sensitive inputs. And, a secured framework consisting of multiple private blockchains with different properties and shared data accessed by various stakeholders,  can help streamline the Clinical Trial process.

This is where a Hyperledger framework comes into the picture.

What is Hyperledger Fabric?

Hyperledger is a collaborative project supported by the Linux foundation. It is modular and pluggable and consists of open-source blockchain and related tools with a number of frameworks and distributed ledgers.

Hyperledger Fabric is a permissioned blockchain framework. A permissioned blockchain (also called a consortium or federated blockchain) is a hybrid of public and private blockchain frameworks. On a permissioned blockchain, transactions or data is visible only to the parties with permission to view them — not the whole network.

Why Hyperledger Fabric is better than Ethereum

The key difference between Ethereum and Hyperledger Fabric is that the former is a public or permissionless blockchain where anyone with an open source software can be a participant. While advantages are anonymity and transparency, but the tradeoff is privacy and scalability. This is why Ethereum is more suited for B2C environments.

Hyperledger Fabric’s private or permissioned blockchain protocol allows for authentication, authorization, and permission of actions. That makes Hyperledger Fabric more suitable for businesses in industries like healthcare, which demands collaboration with multiple stakeholders in a secure ecosystem. Further, the modular architecture allows Hyperledger to be more flexible and enables customization.

Why Hyperledger Fabric is better than Ethereum

Image source

Blockchain taking a leap in digital health with Hyperledger Fabric

Hyperledger Fabric, released in 2017, is the first publicly available version of the Hyperledger consortium’s open-source blockchain framework. It is a framework based on a plug-and-play environment for building blockchain applications. Some of its features are modularity, container technology to host smart contracts called chain code, which comprises the application logic of the framework.

Last year, Change Healthcare launched Change Healthcare Intelligent Healthcare Network using Hyperledger Fabric 1.0. It is the first blockchain solution for enterprise-scale use in healthcare, enabling payers and providers to boost revenue cycle efficiency, improve real-time analytics, cut costs, and create innovative new services.

Medicalchain a decentralized platform aims to create a platform for different healthcare agents to request permission to access and interact with medical records. Each interaction on the platform is auditable, transparent, and secure, and will be recorded as a transaction on a distributed ledger. The project will guarantee privacy since it will be built on the permission-based Hyperledger Fabric architecture providing for varying access levels

It has some key properties that make it an ideal distributed ledger which makes it easier for the CRO’s and pharma companies to adopt blockchain.

The key features of the Hyperledger fabric are

Assets: Asset definitions enable the exchange of data.

Chaincode: It is a ‘smart contract’ which allows users to create transactions in the shared ledger network of Hyperledger Fabric.

The immutable shared ledger: this can encode the data history of each channel, a include a SQL-like query capability for efficient auditing and dispute resolution.

High level of privacy through Channels: Channels allows multilateral transactions with high levels of privacy and confidentiality required to maintain the strict standards of regulations for the pharma and life sciences industries when assets are exchanged on a common network.

Security & Membership Services: The Fabric platform allows for a permissioned membership provides a trusted blockchain network.

Consensus: A flexible and scalable approach to consensus.

Advantages of using Hyperledger Fabric for Clinical Trials

Data security and privacy

Using permissioned blockchains like Hyperledger Fabric ensures that only authorized organizations/entities with designated permissions as defined by a set protocol can join the network(s) and perform only certain activities on the network. In Hyperledger Fabric HSM (Hardware Security Module) provides a way to keep private keys secured. These private keys are not outside of the HSM thus ensuring greater security. This approach can provide sources guaranteed anonymity required for PHI (Protected Health Information) and a fully audited verification of the data.

Regulatory compliance

Permissioned blockchains can achieve data privacy and security compliance such as HIPAA or PIPEDA as data is stored only on authorized “nodes”. Hyperledger Fabric is a framework where all participants have known identities. The healthcare, pharmaceuticals, and life sciences industry, is subject to data protection laws that require knowing the identity of the members of the network and who is accessing specific data. Creates a Private Permission structure for the patients, allowing them to use SSO  (Single sign-on) to hide and maintain their anonymous status in all data exchanges.

Optimized costs and faster process

With a private and permissioned blockchain framework like Hyperledger Fabric, computationally inexpensive protocols can be used for verifying transactions. Leading to faster and significantly cheaper processes. It enables the analysis of data from multiple trials, as well as leveraging data stored by different sources, in different locations. Creating a cost-effective virtual data universe (Data Lake).

Increased performance, scalability, and levels of trust

Due to the modular architecture of Hyperledger Fabric data processing is distributed into three phases: distributed logic processing and agreement (“chaincode”), transaction ordering, and transaction validation and commitment. This distribution needs fewer levels of trust and verification across node types, and thus network scalability and performance are optimized.

As IBM describes it, Fabric “is designed to provide a framework for building enterprise-grade blockchain networks that can quickly scale as new network members join and transact at rates of more than 1,000 transactions per second among large ecosystems of users.”

In conclusion:

Clinical trials are one of the most crucial parts of the drug discovery process. As the time and the cost of the clinical trials rise, it hinders the drug discovery process.

The distributed ledger and permissioned framework of the Hyperledger Fabric based blockchain app can help in creating a more efficient Clinical Trial process by maintaining Clinical Trial integrity, manage data efficiently, manage data transparency and security, and achieve data compliance. It can lead to the structuration of community-driven health data, decentralization of the process, and manage higher security and with transparent interactions to ensure an easier and more transparent process.

Read More
Mobile Opinion

Why is the world of app development in love with React Native?

Ever since mobile phones have become more powerful in terms of their battery capacity, their processing power and the OSes that they run on them, mobiles have been running more and more versatile apps. This has been fuelled by the open source community of Android developers, helped partly by the iOS development community as well. As of October 2018, there are 2.1 million apps in the Google Play Store and around 2 million apps in the App Store. This is an unprecedented number of apps, and this number is only set to grow in the next few years.

For many years now, there has been a huge push to code android apps in Java, and iOS apps in either Swift or Objective-C. This led to having different development teams and software stacks for all these different app ecosystems. This meant having different CI/CD pipelines, different change cycles, and different development teams for each of these platforms. With the possible advent of other devices and operating systems like smartwatches, smart TVs, smart kitchenware, this app ecosystem was about to explode and be rendered unmanageable. Cross-platform app development became a problem to be solved.

Thankfully, Facebook recognized this predicament and came up with a fantastic solution which was based on the powerful React Web development framework. React is a framework created by Facebook for data-driven web interfaces. React provides a component-driven architecture which uses a declarative syntax and is easily extensible.

In 2012 Mark Zuckerberg commented,

“The biggest mistake we made as a company was betting too much on HTML5 as opposed to Native”.

Facebook was running an internal hackathon project, that used React’s core, and javascript language, using which, one could write apps for mobile devices. Which was later named as React Native and was announced at Facebook’s React.js conference in February 2015. In March of 2015, Facebook announced at F8 conference that React Native is open and available on GitHub.

And then suddenly, the IT world was abuzz with excitement around React Native. Everyone wanted to build an application in React Native, and React Native developers started getting hired in huge numbers.

The React Native is rapidly gaining popularity over other frameworks

Image Source

To understand why this buzz is justified, and why we should develop applications in React Native, let’s take a step back and understand some basics.

What exactly is React Native?

React Native is an open source framework which transfers the concepts of web development into mobile development. The apps you build with React Native aren’t just mobile web apps though. This is because React Native uses the exact fundamental UI building blocks that regular iOS and Android apps use. Instead of using Swift, Kotlin or Java, you can put the building blocks together using JavaScript. In contrast, frameworks like Ionic would end up creating just web apps for mobile, and you won’t get the native experience in the apps created by them.

Why is React Native so Useful?

React Native was created with“Learn Once, Write Anywhere”. With Javascript being the medium of development, the developers, don’t need to know multiple languages such as Swift, Kotlin, or Java. Neither they need to be adept at native iOS or Android development. Anyone with good Javascript knowledge can be easily on-boarded to React Native development with a little learning curve.

Facebook’s objective has been:

“To be able to develop a consistent set of goals and technologies that let us build applications using the same set of principles across whatever platform we want.”

Given this overarching objective, they set out to apply the same set of principles such as the virtual dom, layout engine, stateful components and many others of their React framework, to the iOS and Android platforms. The benefit of React Native is that if you understand how to build a React Native app for Android, you understand how to build a React Native app for iOS.

It’s truly – learn once, write anywhere!

Some of the Most Popular Apps in the Market Today Are Running on React Native partially or fully:

  • Facebook:

React Native in production at Facebook

Image Source

  • Bloomberg:

Bloomberg Used React Native

Image Source

  • Myntra:

Myntra exemplifies how an online shopping portal on mobile be like

Image Source

Some Major Benefits of Coding Apps with React Native

Some Major Benefits of Coding Apps with React Native

  • Reusable code: You need to now manage only one code base for both platforms. You can easily reuse code for across platforms during development.
  • Universal: Covers both iOS and Android.
  • Native development: React Native’s components which are reusable can compile directly to native. This will ensure that you get a more natural and native look and feel along with consistency.
  • Easy Integration: Incorporate React Native components into your existing app’s native code base. This means your app can still reuse a huge portion of native code, along with few modules written in React Native. Apps such as Facebook are known to Mix Native and React Native modules in their app.
  • Native UI Centric: It provides a rich set of UI components that map with that of native UI components. This is in stark contrast to the other JS frameworks such as Ionic, or Cordova.
  • Constant support by vibrant OSS community: React Native thrives because of a powerful open source community around it. This ensures React Native gets support for the latest iOS and Android advancements as soon as possible.

UI Stands Out with React Native

React Native is famous for empowering its developers with unmatched speed during coding and efficiency. React UI library for web applications is present for all UI elements. The DOM abstraction only adds to the technical superiority of the library.

You will get speed and agility.

How do we choose between React Native/Native app development/ Flutter/ Cordova based frameworks?

Some of the most critical questions that are plaguing the heads of technology divisions at most companies are –

Is React Native the right solution for us? Is it better than native development?

There is no easy way to answer this question. It depends, to a large extent, on your use case. Both React to Native development and Native app development serve different purposes.

  • Native over React Native: When you want OS-specific native experiences, and when you have the resources to work on two simultaneous builds, you should choose native development. Currently, React Native does not support all native APIs. This means that complex requirements in terms of either the UI, the API flows or even streaming of media on the app, will give a better experience if the app is developed natively on Swift or Kotlin.
  • React Native over Native: If your use case is UI and the flows aren’t wildly complex and remain mostly the same for both iOS and Android, then you can definitely think of developing using React Native. React Native makes it possible to have one focussed team solving the problems for both the platforms using a single code base. Should it require to bridge any native specific experience, that is not yet there in React Native, you can still write a native module and expose it to your React Native app.
  • React Native over Cordova based frameworks: We have already observed that React Native has the immense advantage of providing native experience over a web experience in mobile. This one strength itself is super enough to decide over using Cordova based framework for your cross-platform development requirements. No need to fiddle with frameworks such as Ionic, Cordova, or PhoneGap. Their days are over.
  • React Native over Google’s Flutter: While google’s flutter is a promising competitor, it comes with a steep learning curve. Unlike React Native’s use of Javascript, Flutter requires developers to know a different programming language called Dart. This means you might not be able to onboard your javascript developers into it directly. Also, React Native is quite mature and has much more support libraries compared to Flutter. At this point of time, React Native still has edge over Flutter.

Can We Use React Native All the Time?

The short answer is “NO”. There some pitfalls of using React Native as well.

Some of the disadvantages are:

  • React Native does not have a very good upgrade cycle: Every new update has a lot of changes, so developers need to update their apps regularly. Going more than a few months without updating an app can have an unfortunate result. For example, Airbnb developers faced a problem with React Native for their mobile app development in 2017. They found it impossible to use React Native version 0.43 to React Native version 0.49 as they used React 16 alpha and beta.
  • JS is a weakly typed language: Some mobile engineers might face a lack of type safety, which makes it difficult to scale. As a result, engineers have to adopt other integrations like TypeScript and Flow to the existing infrastructure.
  • API coverage: Community wise React Native Development lags a lot behind Native development. Ergo, there is a severe lack of third-party libraries. To make use of the native libraries, the teams would have to create in-native modules which only increases the development efforts.
  • Complex user interfaces: If your use case is to have many interactions, animations or complex gestures in your app, then you will face some difficulties while coding with React Native. Sometimes the differences between the behavior of Android and iOS can be too complicated for a unified API.
  • Apps Designed for single OS: If your use case involves supporting only one OS such as iOS or Android, there is little reason to go for React Native. Going for native development would be ideal in this case.

The Way Ahead for React Native

Maybe React Native is not meant to be for all your needs and use cases.

But the key thing about React Native is that it’s still in development and we are yet to see its full potential. In the future, it may be more powerful and efficient and allow for even more use cases, but for now, it cannot fully replace native mobile app development. However, it’s written once, use everywhere paradigm can be a tremendous time and money saver if used on the right projects.

Read More