mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2025-02-05 10:05:29 -05:00
916 lines
39 KiB
HTML
916 lines
39 KiB
HTML
<!doctype html>
|
||
<!--
|
||
Minimal Mistakes Jekyll Theme 4.24.0 by Michael Rose
|
||
Copyright 2013-2020 Michael Rose - mademistakes.com | @mmistakes
|
||
Free for personal and commercial use under the MIT license
|
||
https://github.com/mmistakes/minimal-mistakes/blob/master/LICENSE
|
||
-->
|
||
<html lang="en" class="no-js">
|
||
<head>
|
||
<meta charset="utf-8">
|
||
|
||
<!-- begin _includes/seo.html --><title>Healthcare and Self Sovereign Identity | Verifiable Credentials and Self Sovereign Identity Web Directory</title>
|
||
<meta name="description" content="This workflow doesn’t involve any third-party to store your medical data">
|
||
|
||
|
||
<meta name="author" content="DIDecentral">
|
||
|
||
<meta property="article:author" content="DIDecentral">
|
||
|
||
|
||
|
||
<meta property="og:type" content="article">
|
||
<meta property="og:locale" content="en_US">
|
||
<meta property="og:site_name" content="Verifiable Credentials and Self Sovereign Identity Web Directory">
|
||
<meta property="og:title" content="Healthcare and Self Sovereign Identity">
|
||
<meta property="og:url" content="https://decentralized-id.com/application/healthcare/">
|
||
|
||
|
||
<meta property="og:description" content="This workflow doesn’t involve any third-party to store your medical data">
|
||
|
||
|
||
|
||
<meta property="og:image" content="https://decentralized-id.com/images/DID_og.webp">
|
||
|
||
|
||
|
||
<meta name="twitter:site" content="@infominer33">
|
||
<meta name="twitter:title" content="Healthcare and Self Sovereign Identity">
|
||
<meta name="twitter:description" content="This workflow doesn’t involve any third-party to store your medical data">
|
||
<meta name="twitter:url" content="https://decentralized-id.com/application/healthcare/">
|
||
|
||
|
||
<meta name="twitter:card" content="summary_large_image">
|
||
<meta name="twitter:image" content="https://decentralized-id.com/images/DID_og.webp">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<meta property="article:published_time" content="2023-06-15T00:00:00+13:00">
|
||
|
||
|
||
|
||
<meta property="article:modified_time" content="2023-06-16T00:00:00+13:00">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<link rel="canonical" href="https://decentralized-id.com/application/healthcare/">
|
||
|
||
|
||
|
||
|
||
<script type="application/ld+json">
|
||
{
|
||
"@context": "https://schema.org",
|
||
|
||
"@type": "Person",
|
||
"name": "Infominer",
|
||
"url": "https://decentralized-id.com/"
|
||
|
||
}
|
||
</script>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<!-- end _includes/seo.html -->
|
||
|
||
|
||
|
||
<link href="/feed.xml" type="application/atom+xml" rel="alternate" title="Verifiable Credentials and Self Sovereign Identity Web Directory Feed">
|
||
|
||
|
||
<!-- https://t.co/dKP3o1e -->
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
|
||
<script>
|
||
document.documentElement.className = document.documentElement.className.replace(/\bno-js\b/g, '') + ' js ';
|
||
</script>
|
||
|
||
<!-- For all browsers -->
|
||
<link rel="stylesheet" href="/assets/css/main.css">
|
||
<link rel="preload" href="https://cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5/css/all.min.css" as="style" onload="this.onload=null;this.rel='stylesheet'">
|
||
<noscript><link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5/css/all.min.css"></noscript>
|
||
|
||
|
||
|
||
|
||
<meta name="yandex-verification" content="876ea269be433d62" />
|
||
<!-- Favicons -->
|
||
<link rel="apple-touch-icon" sizes="180x180" href="https://decentralized-id.com/assets/icons/apple-touch-icon.png">
|
||
<link rel="icon" type="image/png" sizes="32x32" href="https://decentralized-id.com/assets/icons/favicon-32x32.png">
|
||
<link rel="icon" type="image/png" sizes="16x16" href="https://decentralized-id.com/assets/icons/favicon-16x16.png">
|
||
<link rel="manifest" href="https://decentralized-id.com/assets/icons/site.webmanifest">
|
||
<link rel="mask-icon" href="https://decentralized-id.com/assets/icons/safari-pinned-tab.svg" color="#eeeeef">
|
||
<link rel="shortcut icon" href="https://decentralized-id.com/assets/icons/favicon.ico">
|
||
<meta name="msapplication-TileColor" content="#eeeeef">
|
||
<meta name="msapplication-config" content="https://decentralized-id.com/assets/icons/browserconfig.xml">
|
||
<meta name="theme-color" content="#eeeeef">
|
||
|
||
<!-- start custom head snippets -->
|
||
|
||
<!-- insert favicons. use https://realfavicongenerator.net/ -->
|
||
|
||
<!-- end custom head snippets -->
|
||
|
||
</head>
|
||
|
||
<body class="layout--single wide">
|
||
<nav class="skip-links">
|
||
<ul>
|
||
<li><a href="#site-nav" class="screen-reader-shortcut">Skip to primary navigation</a></li>
|
||
<li><a href="#main" class="screen-reader-shortcut">Skip to content</a></li>
|
||
<li><a href="#footer" class="screen-reader-shortcut">Skip to footer</a></li>
|
||
</ul>
|
||
</nav>
|
||
|
||
|
||
|
||
<div class="masthead">
|
||
<div class="masthead__inner-wrap">
|
||
<div class="masthead__menu">
|
||
<nav id="site-nav" class="greedy-nav">
|
||
|
||
<a class="site-logo" href="/"><img src="/images/DID.webp" alt="Decentralized Identity"></a>
|
||
|
||
<a class="site-title" href="/">
|
||
Decentralized Identity
|
||
|
||
</a>
|
||
<ul class="visible-links"><li class="masthead__menu-item">
|
||
<a href="/introduction/">Introduction</a>
|
||
</li><li class="masthead__menu-item">
|
||
<a href="/ecosystem/">Ecosystem</a>
|
||
</li><li class="masthead__menu-item">
|
||
<a href="/posts/">New</a>
|
||
</li><li class="masthead__menu-item">
|
||
<a href="/recent/">Updated</a>
|
||
</li><li class="masthead__menu-item">
|
||
<a href="/categories/">Categories</a>
|
||
</li><li class="masthead__menu-item">
|
||
<a href="/about/">Welcome</a>
|
||
</li><li class="masthead__menu-item">
|
||
<a href="/aim/">Aim</a>
|
||
</li></ul>
|
||
|
||
<button class="greedy-nav__toggle hidden" type="button">
|
||
<span class="visually-hidden">Toggle menu</span>
|
||
<div class="navicon"></div>
|
||
</button>
|
||
<ul class="hidden-links hidden"></ul>
|
||
</nav>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<div class="initial-content">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<div id="main" role="main">
|
||
|
||
<div class="sidebar sticky">
|
||
|
||
|
||
|
||
|
||
<img src="/images/the-world-map-from-a-binary-code.webp"
|
||
alt="Binary Globe by GDj">
|
||
|
||
<h3>Identity Decentralized</h3>
|
||
|
||
|
||
|
||
<nav class="nav__list">
|
||
|
||
<input id="ac-toc" name="accordion-toc" type="checkbox" />
|
||
<label for="ac-toc">Toggle menu</label>
|
||
<ul class="nav__items">
|
||
|
||
<li>
|
||
|
||
<a href="/"><span class="nav__sub-title">Home</span></a>
|
||
|
||
|
||
|
||
<ul>
|
||
|
||
<li><a href="/history/">• Resources & Pre-History</a></li>
|
||
|
||
<li><a href="/history/2000-2009/">• 2000-2009</a></li>
|
||
|
||
<li><a href="/history/2010-2014/">• 2010-2014</a></li>
|
||
|
||
<li><a href="/history/2015-2019/">• 2015-2019</a></li>
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li>
|
||
|
||
<a href="/categories/#companies"><span class="nav__sub-title">New Pages New Structure</span></a>
|
||
|
||
|
||
|
||
<ul>
|
||
|
||
<li><a href="/companies/ValidatedID/">• ValidatedID</a></li>
|
||
|
||
<li><a href="/companies/ValidatedID/">• SpruceID</a></li>
|
||
|
||
<li><a href="/companies/Spherity/">• Spherity</a></li>
|
||
|
||
<li><a href="/companies/MyDEX/">• MyDEX</a></li>
|
||
|
||
<li><a href="/companies/Mattereum/">• Mattereum</a></li>
|
||
|
||
<li><a href="/companies/MagicLabs/">• Magic Labs</a></li>
|
||
|
||
<li><a href="/companies/Lissi/">• Lissi</a></li>
|
||
|
||
<li><a href="/companies/Indicio/">• Indicio</a></li>
|
||
|
||
<li><a href="/companies/IDramp/">• IDRamp</a></li>
|
||
|
||
<li><a href="/companies/GlobalID/">• GlobalID</a></li>
|
||
|
||
<li><a href="/companies/Gataca/">• Gataca</a></li>
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li>
|
||
|
||
<span class="nav__sub-title">Literature</span>
|
||
|
||
|
||
|
||
<ul>
|
||
|
||
<li><a href="https://identosphere.net/">• Identosphere Blog Catcher</a></li>
|
||
|
||
<li><a href="https://newsletter.identosphere.net/">• Identosphere Newsletter</a></li>
|
||
|
||
<li><a href="/literature/self-sovereign-identity/">• SSI Literature</a></li>
|
||
|
||
<li><a href="/workshops/internet-identity-workshop/">• IIW Session Topics</a></li>
|
||
|
||
<li><a href="/workshops/rebooting-web-of-trust/">• RWoT Papers Index</a></li>
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li>
|
||
|
||
<a href="/web-standards/"><span class="nav__sub-title">Web Standards</span></a>
|
||
|
||
|
||
|
||
<ul>
|
||
|
||
<li><a href="/web-standards/w3c/">• W3C</a></li>
|
||
|
||
<li><a href="/web-standards/w3c/wg/vc/verifiable-credentials/">• Verifiable Credentials</a></li>
|
||
|
||
<li><a href="/web-standards/linked-data/JSON-LD/">• JSON-LD</a></li>
|
||
|
||
<li><a href="/web-standards/gs1/">• GS1</a></li>
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li>
|
||
|
||
<span class="nav__sub-title">Regulation</span>
|
||
|
||
|
||
|
||
<ul>
|
||
|
||
<li><a href="/government/europe/regulation/eidas/">• eIDAS</a></li>
|
||
|
||
<li><a href="/government/europe/regulation/gdpr/">• GDPR</a></li>
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li>
|
||
|
||
<a href="/organizations/"><span class="nav__sub-title">Organizations</span></a>
|
||
|
||
|
||
|
||
<ul>
|
||
|
||
<li><a href="/organizations/decentralized-identity-foundation/">• Identity Foundation</a></li>
|
||
|
||
<li><a href="/organizations/mydata/">• My Data</a></li>
|
||
|
||
<li><a href="/blockchain/hyperledger/">• Hyperledger Foundation</a></li>
|
||
|
||
<li><a href="/organizations/sovrin-foundation/">• Sovrin Foundation</a></li>
|
||
|
||
<li><a href="/organizations/ssi-meetup/">• SSI Meetup</a></li>
|
||
|
||
<li><a href="/organizations/women-in-identity/">• Women in Identity</a></li>
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
<li>
|
||
|
||
<span class="nav__sub-title">Infominer</span>
|
||
|
||
|
||
|
||
<ul>
|
||
|
||
<li><a href="https://infominer.xyz/">• InfoHub</a></li>
|
||
|
||
<li><a href="https://identosphere.net/">• Identosphere Newsletter</a></li>
|
||
|
||
<li><a href="https://identosphere.net/">• Identosphere BlogCatcher</a></li>
|
||
|
||
<li><a href="https://bitcoinfo.github.io/history/">• Bitcoin Histories</a></li>
|
||
|
||
<li><a href="https://sourcecrypto.github.io/decentralized-web/">• Decentralized Web Histories</a></li>
|
||
|
||
<li><a href="https://sourcecrypto.github.io">• Source⧉Crypto</a></li>
|
||
|
||
</ul>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
|
||
|
||
|
||
</div>
|
||
|
||
|
||
|
||
<article class="page h-entry" itemscope itemtype="https://schema.org/CreativeWork">
|
||
<meta itemprop="headline" content="Healthcare and Self Sovereign Identity">
|
||
<meta itemprop="description" content="Most healthcare organizations are and should be, focused on their core business pursuits, such as patient care or processing insurance claims. Information security and identity management is not their core business, yet is a critical factor in compliant, secure business operations.">
|
||
<meta itemprop="datePublished" content="2023-06-15T00:00:00+13:00">
|
||
<meta itemprop="dateModified" content="2023-06-16T00:00:00+13:00">
|
||
|
||
<div class="page__inner-wrap">
|
||
|
||
<header>
|
||
<h1 id="page-title" class="page__title p-name" itemprop="headline">
|
||
<a href="https://decentralized-id.com/application/healthcare/" class="u-url" itemprop="url">Healthcare and Self Sovereign Identity
|
||
</a>
|
||
</h1>
|
||
|
||
|
||
<p class="page__meta">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<span class="page__meta-readtime">
|
||
<i class="far fa-clock" aria-hidden="true"></i>
|
||
|
||
8 minute read
|
||
|
||
</span>
|
||
|
||
</p>
|
||
|
||
|
||
</header>
|
||
|
||
|
||
<section class="page__content e-content" itemprop="text">
|
||
|
||
<aside class="sidebar__right ">
|
||
<nav class="toc">
|
||
<header><h4 class="nav__title"><i class="fas fa-link"></i> Contents</h4></header>
|
||
<ul class="toc__menu"><li><a href="#explainer">Explainer</a></li><li><a href="#project">Project</a></li><li><a href="#business">Business</a></li><li><a href="#policy">Policy</a></li><li><a href="#standards">Standards</a></li><li><a href="#development">Development</a></li><li><a href="#literature">Literature</a></li><li><a href="#devices">Devices</a></li><li><a href="#mychart-thierchart">MyChart ThierChart</a></li></ul>
|
||
|
||
</nav>
|
||
</aside>
|
||
|
||
<h2 id="explainer">Explainer</h2>
|
||
<ul>
|
||
<li><a href="https://www.youtube.com/watch?v=gimrMbcj91A">Webinar: The Future of Self Sovereign Identity</a> 2021-12-21 Patientory Association, with Michael Merchant, Health Information Exchange; Jim Clair, LFPH; Kapil Bareja, Technical Governance Board
|
||
<blockquote>
|
||
<p>Self-sovereign identity (SSI) is a movement that claims digital identity should be just as legitimate and nuanced as a person’s human identity, while being accessible to all, privacy-preserving, and not reliant on a single government or corporation.</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://blog.dock.io/verifiable-credentials-set-to-revolutionize-health-and-safety-compliance/">Verifiable Credentials set to Revolutionize Health and Safety Compliance</a> 2021-11-05 Dock
|
||
<blockquote>
|
||
<p>By integrating with Dock and utilizing verifiable credentials, the process of verifying a workers qualifications goes from analysing paper-based certificates and calling each educational body to certify the legitimacy of it, to having the accreditations sitting in a tamper-proof digital wallet, with a digital signature signature from the issuing body certifying the legitimacy.</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://www.htworld.co.uk/insight/decentralized-identity-verifiable-credentials-healthcare/">How decentralised identity & verifiable credentials will transform the world of healthcare</a> 2021-08-20 HealthTech World
|
||
<blockquote>
|
||
<p>When a medical accrediting agency provides a digitally signed certificate, the healthcare practitioner and owner of that certificate holds the credential in a digital wallet. The details of the credential such as the time stamp in which the certificate was given and how long it is valid for, can be optionally held within a blockchain network, digitally linked to the certificate, this process is called ‘anchoring’.</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://academy.affinidi.com/accessing-medical-records-anywhere-a-use-case-for-verifiable-credentials-81a248f9b746">Accessing Medical Records Anywhere</a> 2021-04-02 Affinidi
|
||
<blockquote>
|
||
<p>this workflow doesn’t involve any third-party to store your medical data and this also means no worry about medical data storage policies and the laws associated with it. The holder completely owns his or her medical data and stores it exclusively in his or her digital wallet, thereby making it secure and hassle-free.</p>
|
||
</blockquote>
|
||
</li>
|
||
<li>[Literature] <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7013398/">Distributed Ledger Technology for eHealth Identity Privacy: State of The Art and Future Perspective</a> 2020-01 NLM
|
||
<blockquote>
|
||
<p>In the decentralized trusted identity model, the identity provider still centralized and performs the user’s identity proofing based on trusted credentials like passports or driver licenses while uses the DLT to store the identity attestation for later validation by third parties services and trusted organizations as is shown in Figure 1b [46]. The decentralized trusted identity doesn’t use the concept of identity repository which is the slight difference from the SSI model, and the identity provider will provide the receiving entity a testimony on the validity of the data while all the credentials are encrypted and stored locally in the user phone.</p>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="project">Project</h2>
|
||
<ul>
|
||
<li><a href="https://medium.com/gravity-earth/case-study-gravity-digital-id-solution-enables-vulnerable-migrants-in-kenya-to-receive-consistent-713a78f9e0d8">Case study: Gravity digital ID solution enables vulnerable migrants in Kenya to receive consistent healthcare services</a> 2022-04-27 Shiyao Zhang
|
||
<blockquote>
|
||
<p>For patients who have a smartphone, they can directly view and manage their medical credentials on their wallet application; for patients who are equipped with feature phones, they can interact with their credentials via a dedicated USSD menu; for those who don’t have a phone, the medical credentials will be stored in a printed QR code.</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://www.brightlands.com/en/brightlands-smart-services-campus/brightlands-techruption-SSI-simplifies-medical-supply-orders">Simplify medical supply orders with SSI: Techruption innovation project</a> 2021-12-21 Brightlands
|
||
<blockquote>
|
||
<p>Participants in this co-creation use case were TNO, CZ, Rabobank and Accenture. The developed solution can be applied in other industries as well. For example in public services, which are often offered by a network of organisations that are all required to comply with high administrative standards.</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://knowledge.wealize.digital/en/blog/blog/ssi-at-healthcare-industry">Self-Sovereign Identity and Blockchain in the Healthcare Industry</a> 2021-12-14 Wealize Digital
|
||
<blockquote>
|
||
<p>Healthcare is a key case-use of the SSI model employing blockchain given the significance and scalability of this sectoral. In this article, we give you details about a pilot project developed for the Andalusian Health Service in Spain to evidence the feasibility of a vaccination card according to the Alastria Self-Sovereign Identity system based on Blockchain technology.</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://northernblock.io/patient-centric-identity-management-for-healthcare/">Patient-Centric Identity Management for Healthcare with Jim St-Clair</a> 2021-04-13 Northern Block
|
||
<blockquote>
|
||
<p>I began working with Lumedic in January of this year, specifically focused on digital identity standards, especially in self-sovereign identity, and also continuing to work in HL7. Lumedic is part of Providence Health Systems, and we play a very active role in several HL7 initiatives for health IT and data exchange. It’s very complementary to the work we’re doing with groups like Sovrin, the Trust over IP Foundation, and so on.</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://ssimeetup.org/self-sovereign-identity-healthcare-dr-manreet-nijjar-webinar-21/">Self-Sovereign Identity in Healthcare by Manny Nijjar from truu.id</a> 2019-02-19 SSIMeetup <a href="https://www.slideshare.net/SSIMeetup/selfsovereign-identity-in-healthcare-by-manny-nijjar-from-truuid">presentation</a>
|
||
<blockquote>
|
||
<p>Dr Manreet Nijjar MB ChB MRCP (London) is the Co-founder & CEO of truu.id Manny’s talk will cover the work his team has been doing on decentralised digital identity for medical professionals in the United Kingdom. He will take you through his personal journey that led him to break from being a doctor to focus fully on SSI and how it will solve healthcare problems not only at the individual level, but also nationally and globally.</p>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="business">Business</h2>
|
||
<ul>
|
||
<li><a href="https://auth0.com/blog/the-future-of-healthcare-relies-on-adaptation/">The Future of Healthcare Relies on Adaptation</a> 2021-10-14 auth0
|
||
<blockquote>
|
||
<p>Most healthcare organizations are and should be, focused on their core business pursuits, such as patient care or processing insurance claims. Information security and identity management is not their core business, yet is a critical factor in compliant, secure business operations.</p>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="policy">Policy</h2>
|
||
<ul>
|
||
<li><a href="https://www.pocketcred.com/post/member-as-api-the-interoperability-and-patient-access-final-rule-and-verifiable-credentials">“Member as API” - The Interoperability and Patient Access final rule and Verifiable Credentials</a> 2021-07-26 PocketCred
|
||
<blockquote>
|
||
<p>The Interoperability and Patient Access final rule (CMS-9115-F) delivers on the government’s promise to put patients first, giving them access to their health information when they need it most and in a way they can best use it. As part of the MyHealthEData initiative, this final rule is focused on driving interoperability and patient access to health information by liberating patient data using CMS authority to regulate Medicare Advantage (MA), Medicaid, CHIP, and Qualified Health Plan (QHP) issuers on the Federally-facilitated Exchanges (FFEs).</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://www.federalregister.gov/documents/2020/05/01/2020-07419/21st-century-cures-act-interoperability-information-blocking-and-the-onc-health-it-certification">21st Century Cures Act</a> 2020-05-01
|
||
<blockquote>
|
||
<p>This final rule implements certain provisions of the 21st Century Cures Act, including Conditions and Maintenance of Certification requirements for health information technology (health IT) developers under the ONC Health IT Certification Program (Program), the voluntary certification of health IT for use by pediatric health care providers, and reasonable and necessary activities that do not constitute information blocking. The implementation of these provisions will advance interoperability and support the access, exchange, and use of electronic health information. The rule also finalizes certain modifications to the 2015 Edition health IT certification criteria and Program in additional ways to advance interoperability, enhance health IT certification, and reduce burden and costs.</p>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="standards">Standards</h2>
|
||
<ul>
|
||
<li><a href="https://auth0.com/blog/what-smart-on-fhir-means-for-the-future-of-healthcare/">What SMART on FHIR Means for the Future of Healthcare</a> 2021-09-07 Auth0
|
||
<blockquote>
|
||
<p>The Substitutable Medical Applications and Reusable Technologies (SMART) platform promises to solve these data fragmentation challenges by standardizing how patient data is accessed and shared. And given SMART’s inclusion in the <a href="https://www.federalregister.gov/documents/2020/05/01/2020-07419/21st-century-cures-act-interoperability-information-blocking-and-the-onc-health-it-certification">21st Century Cures Act</a>, the platform will become the standard protocol for accessing electronic health records (EHRs) in the near future.</p>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="development">Development</h2>
|
||
<ul>
|
||
<li><a href="https://iiw.idcommons.net/21C/_Solving_Identity_Challenges_at_the_Intersection_of_Education_and_Healthcare">Solving Identity Challenges at the Intersection of Education and Healthcare</a> 2021-05-06 Kimberly Linson
|
||
<blockquote>
|
||
<ul>
|
||
<li>We have to get to protocol/standards like we did with email</li>
|
||
<li>It will be messy and competitive with new players who emerge and offer more freedom</li>
|
||
<li>Those who can’t adapt will lose ground - need to be willing to let go</li>
|
||
<li>Messaging apps: Signal/What’s APp - PRESSURE…eventually someone will make it so that they work together and scoop up everyone’s business</li>
|
||
</ul>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://www.blockchainhealthcaretoday.com/index.php/journal/article/view/196">Technical Design and Development of a Self-Sovereign Identity Management Platform for Patient-Centric Healthcare Using Blockchain Technology</a> 2022-04-22 Blockchain Healthcare
|
||
<blockquote>
|
||
<p>Results: MediLinker allows users to store their personal data on digital wallets, which they control. It uses a decentralized trusted identity using Hyperledger Indy and Hyperledger Aries. Patients use MediLinker to register and share their information securely and in a trusted system with healthcare and other service providers. Results: MediLinker allows users to store their personal data on digital wallets, which they control. It uses a decentralized trusted identity using Hyperledger Indy and Hyperledger Aries. Patients use MediLinker to register and share their information securely and in a trusted system with healthcare and other service providers.</p>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="literature">Literature</h2>
|
||
|
||
<ul>
|
||
<li><a href="https://blockchainhealthcaretoday.com/index.php/journal/article/view/196/363">Technical Design and Development of a Self-Sovereign Identity Management Platform for Patient-Centric Health Care using Blockchain Technology</a> 2022-03-25 Daniel Toshio Harrell, Muhammad Usman, Ladd Hanson, Mustafa Abdul-Moheeth, Ishav Desai, Jahnavi Shriram, Eliel de Oliveira, John Robert Bautista, Eric T. Meyer, Anjum Khurshid Blockchain Healthcare Today
|
||
<blockquote>
|
||
<p>we leveraged the Hyperledger Indy blockchain framework to store patient’s decentralized identifiers (DIDs) and the schemas or format for each credential type. In contrast, the credentials containing patient data are stored ‘off-ledger’ in each person’s wallet and accessible via a computer or smartphone. We used Hyperledger Aries as a middleware layer (API: Application Programming Interface) to connect Hyperledger Indy with the front-end,</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://blockchainhealthcaretoday.com/index.php/journal/article/view/122/144">Blockchain, Interoperability, and Self-Sovereign Identity: Trust Me, It’s My Data</a> 2020-01-03 Jim St. Clair, Ann Ingraham, Dominic King, Michael B. Marchant, Fletcher Cotesworth McCraw, David Metcalf, John Squeo
|
||
<blockquote>
|
||
<p>The current interoperability processes for data exchange result in fragmentation and lack of aggregation, impacting patient identity, consent management, and access management across stakeholders. Patients lack the ability to administer and transfer consent in managing their own data. Payers risk sharing data with partners without consent. And, providers have identified “pain points” in data sharing in consent management and care coordination.</p>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="devices">Devices</h2>
|
||
<ul>
|
||
<li><a href="https://iiw.idcommons.net/11C/_Rugged_Identity:_resilience_for_Identity_of_Things_to_bad_latency,_signal,_power,_physical_integrity.">Rugged Identity: resilience for Identity of Things to bad latency, signal, power, physical integrity. Mars, war zones, bad neighbors, Great Firewalls.</a> 2021-05-06 Phil Wolff
|
||
<blockquote>
|
||
<p>Problem: So, what happens when you can’t call home to conduct an identity conversation? You’re on Mars and the latency is long. You’re in Haiti and the bandwidth is very limited during a storm. You’re in a war zone and your signal is noisy due to interference.</p>
|
||
|
||
<p>Rugged Identity is hoped-for resilience from very long latency, noisy signal, low bandwidth, interrupted connections, very low power computing and radio, power outages, and attacks on physical integrity like device tampering.</p>
|
||
</blockquote>
|
||
</li>
|
||
<li><a href="https://wider.team/2020/12/23/2021ruggediomd/">In 2021, #RuggedIoMD becomes an #IIoT category</a> 2020-12-23 Wider Team
|
||
<blockquote>
|
||
<p>So there’s demand for a new category of IoT and #IoMD that survives and thrives despite these challenges. Very low power consumption. Lots of storage and caching to hold on through power outages. Ruggedized for use outside clinics. Easy and cheap to field-repair. Lots of smarts inside so they work without an internet tap. Many flavors of connectivity to exploit opportunities as they knock. Open sourced, the better to adapt to new and unplanned problems.</p>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="mychart-thierchart"><del>MyChart</del> ThierChart</h2>
|
||
<ul>
|
||
<li><a href="https://blogs.harvard.edu/doc/2022/01/15/theircharts/">TheirCharts</a> 2022-01-15 Doc Searls
|
||
<blockquote>
|
||
<p>If you’re getting health care in the U.S., chances are your providers are now trying to give you a better <a href="https://www.epic.com/software#PatientEngagement">patient experience</a> through a website called MyChart.</p>
|
||
|
||
<p>This is supposed to be yours, as the first person singular pronoun My implies. Problem is, it’s TheirChart.</p>
|
||
</blockquote>
|
||
</li>
|
||
</ul>
|
||
|
||
|
||
</section>
|
||
|
||
<footer class="page__meta">
|
||
|
||
<h4 class="page__meta-title">Meta</h4>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<p class="page__taxonomy">
|
||
<strong><i class="fas fa-fw fa-tags" aria-hidden="true"></i> Tags </strong>
|
||
<span itemprop="keywords">
|
||
|
||
<a href="/tags/#affinidi" class="page__taxonomy-item p-category" rel="tag">Affinidi</a><span class="sep">, </span>
|
||
|
||
<a href="/tags/#dizme" class="page__taxonomy-item p-category" rel="tag">DIZME</a><span class="sep">, </span>
|
||
|
||
<a href="/tags/#dock" class="page__taxonomy-item p-category" rel="tag">Dock</a><span class="sep">, </span>
|
||
|
||
<a href="/tags/#evernym" class="page__taxonomy-item p-category" rel="tag">Evernym</a><span class="sep">, </span>
|
||
|
||
<a href="/tags/#gravity-earth" class="page__taxonomy-item p-category" rel="tag">Gravity Earth</a><span class="sep">, </span>
|
||
|
||
<a href="/tags/#healthcare" class="page__taxonomy-item p-category" rel="tag">Healthcare</a><span class="sep">, </span>
|
||
|
||
<a href="/tags/#lfph" class="page__taxonomy-item p-category" rel="tag">LFPH</a><span class="sep">, </span>
|
||
|
||
<a href="/tags/#real-world" class="page__taxonomy-item p-category" rel="tag">Real World</a><span class="sep">, </span>
|
||
|
||
<a href="/tags/#smart" class="page__taxonomy-item p-category" rel="tag">SMART</a>
|
||
|
||
</span>
|
||
</p>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<p class="page__taxonomy">
|
||
<strong><i class="fas fa-fw fa-folder-open" aria-hidden="true"></i> Categories: </strong>
|
||
<span itemprop="keywords">
|
||
|
||
<a href="/categories/#uses" class="page__taxonomy-item p-category" rel="tag">Uses</a>
|
||
|
||
</span>
|
||
</p>
|
||
|
||
|
||
|
||
|
||
<p class="page__date"><strong><i class="fas fa-fw fa-calendar-alt" aria-hidden="true"></i> Updated:</strong> <time class="dt-published" datetime="2023-06-16">June 16, 2023</time></p>
|
||
|
||
</footer>
|
||
|
||
<section class="page__share">
|
||
|
||
<h3 class="page__share-title">Share on</h3>
|
||
|
||
|
||
<a href="https://twitter.com/intent/tweet?via=infominer33&text=Healthcare+and+Self+Sovereign+Identity%20https%3A%2F%2Fdecentralized-id.com%2Fapplication%2Fhealthcare%2F" class="btn btn--twitter" onclick="window.open(this.href, 'window', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;" title="Share on Twitter"><i class="fab fa-fw fa-twitter" aria-hidden="true"></i><span> Twitter</span></a>
|
||
<a href="https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fdecentralized-id.com%2Fapplication%2Fhealthcare%2F" class="btn btn--facebook" onclick="window.open(this.href, 'window', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;" title="Share on Facebook"><i class="fab fa-fw fa-facebook" aria-hidden="true"></i><span> Facebook</span></a>
|
||
<a href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdecentralized-id.com%2Fapplication%2Fhealthcare%2F" class="btn btn--linkedin" onclick="window.open(this.href, 'window', 'left=20,top=20,width=500,height=500,toolbar=1,resizable=0'); return false;" title="Share on LinkedIn"><i class="fab fa-fw fa-linkedin" aria-hidden="true"></i><span> LinkedIn</span></a>
|
||
<a href="https://www.reddit.com/submit?url=https%3A%2F%2Fdecentralized-id.com%2Fapplication%2Fhealthcare%2F&title=Healthcare+and+Self+Sovereign+Identity" class="btn btn--reddit" title="Share on Reddit"><i class="fab fa-fw fa-reddit" aria-hidden="true"></i><span> Reddit</span></a>
|
||
</section>
|
||
|
||
|
||
|
||
<nav class="pagination">
|
||
|
||
<a href="/application/education/" class="pagination--pager" title="Education and Self Sovereign Identity
|
||
">Previous</a>
|
||
|
||
|
||
<a href="/application/kyc/" class="pagination--pager" title="KYC\AML and Self Sovereign Identity
|
||
">Next</a>
|
||
|
||
</nav>
|
||
|
||
</div>
|
||
|
||
|
||
<div class="page__comments">
|
||
|
||
|
||
<section id="static-comments">
|
||
|
||
</section>
|
||
|
||
</div>
|
||
|
||
|
||
</article>
|
||
|
||
|
||
|
||
<div class="page__related">
|
||
<h2 class="page__related-title">See Also</h2>
|
||
<div class="grid__wrapper">
|
||
|
||
|
||
|
||
|
||
|
||
<div class="grid__item">
|
||
<article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
|
||
|
||
<div class="archive__item-teaser">
|
||
<img src="/images/did-square.webp" alt="">
|
||
</div>
|
||
|
||
<br><strong><a href="/ecosystem/" rel="permalink">Ecosystem Overview
|
||
</a></strong>
|
||
<p class="archive__item-excerpt" itemprop="description">This page includes a breakdown of the Web Standards, Protocols,Open Source Projects, Organizations, Companies, Regions, Government and Policy surrounding Verifiable Credentials and Self Sovereign Identity.
|
||
</p>
|
||
<p class="page__meta"><strong>Updated:</strong> 2024-02-26 <i class="far fa-clock" aria-hidden="true"></i>
|
||
|
||
|
||
|
||
|
||
4 minute read
|
||
</p>
|
||
|
||
<small><strong>Tags:</strong></small>
|
||
|
||
</article>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
<div class="grid__item">
|
||
<article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
|
||
|
||
<div class="archive__item-teaser">
|
||
<img src="/images/Verifiable-Credentials-Flavors-Explained_jsonld-lds-teaser.webp" alt="">
|
||
</div>
|
||
|
||
<br><strong><a href="/web-standards/w3c/verifiable-credentials/data-integrity-bbs+/" rel="permalink">Verifiable Credentials with JSON-LD and BBS+ Signatures
|
||
</a></strong>
|
||
<p class="archive__item-excerpt" itemprop="description">BBS signatures were implicitly proposed by Boneh, Boyen, and Shacham (CRYPTO ’04) as part of their group signature scheme, and explicitly cast as stand-alone signatures by Camenisch and Lysyanskaya (CRYPTO ’04). A provably secure version, called BBS+, was then devised by Au, Susilo, and Mu (SCN ’...</p>
|
||
<p class="page__meta"><strong>Updated:</strong> 2023-09-29 <i class="far fa-clock" aria-hidden="true"></i>
|
||
|
||
|
||
|
||
|
||
8 minute read
|
||
</p>
|
||
|
||
<small><strong>Tags:</strong></small>
|
||
|
||
<div class="tags">BBS</div>
|
||
|
||
<div class="tags">Data Integrity</div>
|
||
|
||
<div class="tags">JSON-LD</div>
|
||
|
||
<div class="tags">Verifiable Credentials</div>
|
||
|
||
<div class="tags">W3C</div>
|
||
|
||
</article>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
<div class="grid__item">
|
||
<article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
|
||
|
||
<div class="archive__item-teaser">
|
||
<img src="/images/Verifiable-Credentials-Flavors-Explained_jwt-teaser.webp" alt="">
|
||
</div>
|
||
|
||
<br><strong><a href="/web-standards/w3c/verifiable-credentials/jose-jwt+cose-cbor/" rel="permalink">Verifiable Credentials with JOSE (JWT) / COSE (CBOR)
|
||
</a></strong>
|
||
<p class="archive__item-excerpt" itemprop="description">Digital proof mechanisms, a subset of which are digital signatures, are required to ensure the protection of a verifiable credential. Having and validating proofs, which may be dependent on the syntax of the proof (for example, using the JSON Web Signature of a JSON Web Token for proofing a key h...</p>
|
||
<p class="page__meta"><strong>Updated:</strong> 2023-09-09 <i class="far fa-clock" aria-hidden="true"></i>
|
||
|
||
|
||
|
||
|
||
12 minute read
|
||
</p>
|
||
|
||
<small><strong>Tags:</strong></small>
|
||
|
||
<div class="tags">COSE</div>
|
||
|
||
<div class="tags">IANA</div>
|
||
|
||
<div class="tags">JOSE</div>
|
||
|
||
<div class="tags">JWT</div>
|
||
|
||
<div class="tags">Verifiable Credentials</div>
|
||
|
||
<div class="tags">W3C</div>
|
||
|
||
</article>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
<div class="grid__item">
|
||
<article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
|
||
|
||
<div class="archive__item-teaser">
|
||
<img src="/images/Verifiable-Credentials-Flavors-Explained_zkp-cl-teaser.webp" alt="">
|
||
</div>
|
||
|
||
<br><strong><a href="/web-standards/w3c/verifiable-credentials/zkp-cl_anoncreds/" rel="permalink">Verifiable Credentials (ZKP-CL) Anoncreds
|
||
</a></strong>
|
||
<p class="archive__item-excerpt" itemprop="description">This credential format was created specifically to leverage the CL Signatures. JSON-JWT and JSON-LD Signatures each have their own way of representing the meaning of the attributes within a VC. JSON-JWT references an IANA registry and assumes a “closed world” authority model based on that authori...</p>
|
||
<p class="page__meta"><strong>Updated:</strong> 2023-09-29 <i class="far fa-clock" aria-hidden="true"></i>
|
||
|
||
|
||
|
||
|
||
6 minute read
|
||
</p>
|
||
|
||
<small><strong>Tags:</strong></small>
|
||
|
||
<div class="tags">Anoncreds</div>
|
||
|
||
<div class="tags">Evernym</div>
|
||
|
||
<div class="tags">Hyperledger Foundation</div>
|
||
|
||
<div class="tags">IBM</div>
|
||
|
||
<div class="tags">IDEMIX</div>
|
||
|
||
<div class="tags">Sovrin Foundation</div>
|
||
|
||
<div class="tags">Verifiable Credentials</div>
|
||
|
||
<div class="tags">W3C</div>
|
||
|
||
<div class="tags">ZKP-CL</div>
|
||
|
||
</article>
|
||
</div>
|
||
|
||
</div>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
|
||
</div>
|
||
|
||
|
||
|
||
<div id="footer" class="page__footer">
|
||
<footer>
|
||
<!-- start custom footer snippets -->
|
||
|
||
<!-- end custom footer snippets -->
|
||
<div class="page__footer-follow">
|
||
<ul class="social-icons">
|
||
|
||
<li><strong>Follow:</strong></li>
|
||
|
||
|
||
|
||
|
||
|
||
<li><a href="mailto:nfo@infominer.xyz" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-envelope-square" aria-hidden="true"></i> Email</a></li>
|
||
|
||
|
||
|
||
<li><a href="https://decentralized-id.com" rel="nofollow noopener noreferrer"><i class="fas fa-fw fa-link" aria-hidden="true"></i> Website</a></li>
|
||
|
||
|
||
|
||
<li><a href="https://twitter.com/DecentralizeID" rel="nofollow noopener noreferrer"><i class="fab fa-fw fa-twitter-square" aria-hidden="true"></i> Twitter</a></li>
|
||
|
||
|
||
|
||
<li><a href="https://github.com/Decentralized-ID" rel="nofollow noopener noreferrer"><i class="fab fa-fw fa-github" aria-hidden="true"></i> GitHub</a></li>
|
||
|
||
|
||
|
||
|
||
|
||
<li><a href="/feed.xml"><i class="fas fa-fw fa-rss-square" aria-hidden="true"></i> Feed</a></li>
|
||
|
||
</ul>
|
||
</div>
|
||
|
||
<script data-goatcounter="https://didecentral.goatcounter.com/count" async src="//gc.zgo.at/count.js"></script>
|
||
|
||
|
||
<div class="page__footer-copyright">⧉ <a href="https://infominer.xyz">infominer</a> • <a href="https://creativecommons.org/publicdomain/zero/1.0/">Creative Commons (CC0 1.0) Public Domain</a> • Powered by <a href="https://mademistakes.com/work/minimal-mistakes-jekyll-theme/" rel="nofollow">Minimal Mistakes</a> via <a href="https://web-work.tools/jamstack/github-pages-starter-pack/">Github Pages</a>. ⧉</div>
|
||
|
||
</footer>
|
||
</div>
|
||
|
||
|
||
<script src="/assets/js/main.min.js"></script>
|
||
<script src="https://kit.fontawesome.com/4eee35f757.js"></script>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<!-- start custom analytics snippet -->
|
||
|
||
|
||
|
||
|
||
<!-- end custom analytics snippet -->
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</body>
|
||
</html>
|