Learn more >
Get the code
by Ashutosh Nath Agarwal | Published March 18, 2019
This code pattern shows you how to use Blockchain Solution Manager and Blockchain Document Store, connected with the IBM Blockchain Platform, to build an application for the healthcare industry. This app uses these services to manage user access and patient medical records data, and create a well-defined hierarchical structure of all the stakeholders. The pattern showcases the flow of the application from the point of view of the solution admin, hospital admin, doctor, and patient.
Electronic medical records and data is an area in serious need of innovation. The methods that are currently used for storing and securing patient health records do not reflect the technological advancements in this area over the past decade, and hospitals continue to use age-old data management systems for patient data. This is partly due to strict regulations around the privacy and security of medical data, which has stifled the use of current technologies that can make medical data management more transparent and useful for both patients and doctors.
This code pattern showcases a medical data/access management platform that’s built using blockchain. The application shows the platform from the perspective of four different stakeholders:
This code pattern is for developers who want to integrate with the Blockchain Solution Manager, Blockchain Document Store, and the IBM Blockchain Platform. When you have completed it, you will understand how to:
The login portal uses OpenAPI Connect and allows the user the login through any onboarded identity provider (IDP). (In this example, we have onboarded IBMID and GoogleID.) Successful authentication leads to the JWT credentials for the user.
The solution admin flow begins at the admin component, and requires the user to authenticate themselves through the login flow described above.
The Blockchain Solution Manager connects with the IBM Blockchain Platform and updates the ledger appropriately.
The hospital admin flow begins at the organization component, and requires the user to authenticate themselves through the login flow described above.
The doctor flow begins at the doctor component, and requires the user to authenticate themselves through the login flow described above.
The Blockchain Document Store connects with the IBM Blockchain Platform and updates the ledger appropriately.
The patient flow begins at the patient component, and requires the user to authenticate themselves through the login flow described above.
Document access control list (ACL) flow
The doctor and patient components are connected with the Redis APIs that invoke methods to manage document-level access control across hospitals.
Ready to get started? Please see the README for detailed instructions.
Get the Code »
Back to top