diff --git a/src/assets/images/EXR.png b/src/assets/images/EXR.png index 5ab091c..bfa2225 100644 Binary files a/src/assets/images/EXR.png and b/src/assets/images/EXR.png differ diff --git a/src/assets/images/bescom.png b/src/assets/images/bescom.png index cbff0d8..a0dc8a2 100644 Binary files a/src/assets/images/bescom.png and b/src/assets/images/bescom.png differ diff --git a/src/assets/images/chainx.png b/src/assets/images/chainx.png index 0358ede..9294399 100644 Binary files a/src/assets/images/chainx.png and b/src/assets/images/chainx.png differ diff --git a/src/assets/images/finalo.png b/src/assets/images/finalo.png index 78a2a82..0551d4e 100644 Binary files a/src/assets/images/finalo.png and b/src/assets/images/finalo.png differ diff --git a/src/assets/images/hdfc.png b/src/assets/images/hdfc.png index e9abff8..989b65b 100644 Binary files a/src/assets/images/hdfc.png and b/src/assets/images/hdfc.png differ diff --git a/src/assets/images/irctc.png b/src/assets/images/irctc.png index b6901a2..4f6c30f 100644 Binary files a/src/assets/images/irctc.png and b/src/assets/images/irctc.png differ diff --git a/src/assets/images/iskon.png b/src/assets/images/iskon.png index 357307e..1d1a3f2 100644 Binary files a/src/assets/images/iskon.png and b/src/assets/images/iskon.png differ diff --git a/src/assets/images/jupiter.png b/src/assets/images/jupiter.png index 7bcbf7e..2b44bbe 100644 Binary files a/src/assets/images/jupiter.png and b/src/assets/images/jupiter.png differ diff --git a/src/assets/images/ondc.png b/src/assets/images/ondc.png index ba0d53c..bb0b650 100644 Binary files a/src/assets/images/ondc.png and b/src/assets/images/ondc.png differ diff --git a/src/assets/images/smartcity.png b/src/assets/images/smartcity.png index eee760f..8b75f3f 100644 Binary files a/src/assets/images/smartcity.png and b/src/assets/images/smartcity.png differ diff --git a/src/assets/images/tzero.png b/src/assets/images/tzero.png index 6a42ba4..95a9448 100644 Binary files a/src/assets/images/tzero.png and b/src/assets/images/tzero.png differ diff --git a/src/assets/images/ymca.jpeg b/src/assets/images/ymca.jpeg new file mode 100644 index 0000000..aff0515 Binary files /dev/null and b/src/assets/images/ymca.jpeg differ diff --git a/src/assets/images/zing.png b/src/assets/images/zing.png index 4295e4a..bd47532 100644 Binary files a/src/assets/images/zing.png and b/src/assets/images/zing.png differ diff --git a/src/components/HomePage/Partner.jsx b/src/components/HomePage/Partner.jsx index 83217dc..caaa51a 100644 --- a/src/components/HomePage/Partner.jsx +++ b/src/components/HomePage/Partner.jsx @@ -37,10 +37,11 @@ import "swiper/css/navigation"; import { Navigation, Pagination, Autoplay } from "swiper/modules"; import { useState } from "react"; +import { Link } from "react-router-dom"; const imgWidth = { - width: "180px", - height: "82px", + width: "210px", + height: "140px", objectFit: "contain", filter: "grayscale(1)", transition: "0.5s", @@ -123,10 +124,19 @@ export default function Partner() { }} > - - - - + + + + + + + + + + + + + - - - - - + + + + + + + + + + + + + + + @@ -160,9 +186,18 @@ export default function Partner() { > - - - + + + + + + + + + - - - - - + + + + + + + + + + + + + + + diff --git a/src/components/UseCase/UseCase.jsx b/src/components/UseCase/UseCase.jsx index a199553..f55168d 100644 --- a/src/components/UseCase/UseCase.jsx +++ b/src/components/UseCase/UseCase.jsx @@ -3,7 +3,9 @@ /* eslint-disable no-unused-vars */ // eslint-disable-next-line no-unused-vars import React, { useEffect } from "react"; -import { Box, Text } from "@chakra-ui/react"; +import { Box, Button, Image, Text } from "@chakra-ui/react"; +import pdf from "../../assets/pdf/Rubix.pdf"; +import cardimg from "../../assets/images/CardImg.png"; // eslint-disable-next-line react/prop-types const UseCase = ({ useCase, bannerImage, bannerHeading, bannerSubHeading }) => { @@ -90,7 +92,12 @@ const UseCase = ({ useCase, bannerImage, bannerHeading, bannerSubHeading }) => { w={"100%"} > {useCase.map( - ({ useCaseHeading, useCaseSubHeading, useCaseDetails }) => ( + ({ + useCaseHeading, + useCaseSubHeading, + useCaseDetails, + documents, + }) => ( { - {useCaseDetails.map(({ title, description }, index) => ( + {useCaseDetails?.map(({ title, description }) => ( { ))} + + {documents?.map((item) => ( + + + + + + {item.title} + + + + + + + + + + + ))} ) )} diff --git a/src/data/useCase.jsx b/src/data/useCase.jsx index 4368572..5c69cad 100644 --- a/src/data/useCase.jsx +++ b/src/data/useCase.jsx @@ -270,3 +270,73 @@ export const healthTechContent = [ ], }, ]; + +export const IdentitySecurityContent = [ + { + useCaseHeading: "Identity and Security", + useCaseSubHeading: + "The HealthTech sector, while promising significant advancements in healthcare delivery and patient outcomes, faces several challenges that hinder its full potential. Some of the key issues include:", + useCaseDetails: [ + { + title: "Data Silos and Interoperability Challenges", + description: + "HealthTech solutions often operate in silos, with patient data fragmented across disparate systems and platforms. This lack of interoperability makes it difficult for healthcare providers to access comprehensive patient information, leading to inefficiencies in care delivery and decision-making.", + }, + { + title: "Data Fragmentation and Integration", + description: + "FinTech solutions often grapple with fragmented data sources, including bank accounts, investment portfolios, and retirement accounts. Integrating and aggregating these disparate data sets presents technical challenges, hindering the development of holistic financial management tools and insights.", + }, + { + title: "Integration with Legacy Systems", + description: + "Healthcare organizations often rely on legacy systems that may be outdated or incompatible with modern HealthTech solutions. Integrating new technologies with existing infrastructure poses technical challenges and requires substantial time, resources, and expertise, delaying the adoption and implementation of innovative solutions.", + }, + { + title: "Regulatory Compliance Burden", + description: + "HealthTech companies must navigate a complex regulatory landscape, including healthcare laws, privacy regulations (such as HIPAA in the United States), and industry standards (such as HL7 and DICOM). Achieving and maintaining regulatory compliance adds complexity and costs to product development and deployment, potentially slowing innovation and market entry.", + }, + { + title: "Complexity and Fragmentation", + description: + "The MarTech landscape is characterized by a multitude of disparate tools, platforms, and technologies, leading to fragmentation and interoperability challenges. Integrating and managing these diverse components often requires significant time, resources, and technical expertise.", + }, + ], + }, + { + useCaseHeading: "How Rubix solves them", + useCaseSubHeading: + "Rubix addresses the challenges faced by the healthcare industry while promoting data security, interoperability, and patient empowerment. Here's how Rubix based solutions can  revolutionise HealthTech:", + useCaseDetails: [ + { + title: "Patient Centric engagement platforms", + description: + "Rubix powered dAPPs can provide a privacy enhanced, user centric, unified health data service  that aggregates and standardises  health and wellness information from disparate sources, including electronic health records (EHRs), wearable devices, and telehealth platforms. By breaking down data silos and enhancing interoperability, these dAPPs can enable healthcare providers to access comprehensive patient insights and deliver personalized care without compromising on patient privacy", + }, + { + title: "Secure Data Sharing and Collaboration", + description: + "dAPPs built on Rubix can prioritize data security and privacy, implementing robust encryption, access controls, and audit trails to safeguard patient information throughout their lifecycle. With end-to-end encryption and secure collaboration features, Rubix facilitates safe and  privacy regulations compliant data sharing among healthcare stakeholders, including providers, patients, researchers, and insurers.", + }, + { + title: "Seamless Integration with Legacy Systems", + description: + "Rubix single composable stack with easy to implement smart contract framework can help seamless migration of existing  Web2 based healthcare infrastructure, including legacy EHR systems, medical devices, and administrative systems. By offering flexible APIs, standards-based interfaces, and modular architecture, Rubix simplifies the integration process, accelerates time to market, and minimizes disruption to healthcare operations.", + }, + { + title: "Regulatory Compliance Made Easy", + description: + "Rubix powered dAPPs can help healthcare organisations navigate complex regulatory requirements with built-in compliance features and tools. From HIPAA compliance to interoperability standards like HL7 and FHIR, dAPPs can ensure adherence to regulatory guidelines and industry best practices, reducing compliance burden and mitigating risk.", + }, + ], + }, + { + documents: [ + { + id: 1, + title: "Regulatory Compliance Made Easy", + }, + ], + }, +]; diff --git a/src/routes/_routes.jsx b/src/routes/_routes.jsx index 3f659d2..37c657b 100644 --- a/src/routes/_routes.jsx +++ b/src/routes/_routes.jsx @@ -5,6 +5,7 @@ import ArticleInternalThree from "../components/ArticleInternalThree/ArticleInte import ArticleInternalTwo from "../components/ArticleInternalTwo/ArticleInternalTwo"; import ArticleInternalfive from "../components/ArticleInternalfive/ArticleInternalfive"; import { + IdentitySecurityContent, adTechContent, healthTechContent, marTechContent, @@ -171,4 +172,17 @@ export const route = [ /> ), }, + { + path: "identity-security", + element: ( + + ), + }, ];