m Blockchain Healthcare
- jim mason
- jimm1
Key Points
- Some interesting blockchain solutions have been listed under Candidate Solutions below
- There are multiple blockchain frameworks and platforms available
- Some target enterprise, permissioned blockchain requirements like Hyperledger
References
EUBOF - Healthcare
https://www.linkedin.com/posts/drhichamnaim_healthcare-blockchain-ugcPost-6897496220873691136-0L4q
Key Groups
Hyperledger SIG - Healthcare
Steven Elliott
HIS is focused on how clinical artifacts can be stored on a blockchain in a semantically interoperable way and the policies, assets and consensus process needed to guarantee semantic interoperability. This means clinical artifacts stored in the ledger should have the same meaning for each of the consortium members including patients.
The goal of HIS is to build a working consortium of healthcare systems with peers executing episodes of care persisted to the distributed ledger which can then be retrieved in the future by different peers in different settings.
The means to achieve this goal is for the group to determine the tasks needed to develop and build the blockchain and members execute those tasks. Initial Epics and Stories can be found on the main HIS page as well as the agenda.
Who should participate?
Anyone who has the time and interest in blockchain in healthcare with a special interest in semantic interoperability. Individuals who have competencies as Clinicians, Clinical Informaticists, Engineers, Program Manager, Business Analysts/Technical Writers are some of the traits we feel can be especially helpful.
We welcome one and all and look forward to your participation and collaboration.
Monday, November 25 09:00 PT (16:00 UTC).
https://zoom.us/my/hyperledger.community.3
Healthcare SIG interop - m191209
- Steven Elliott
data stored in
ehr in icd10 and ??
icb10
semantic interoperability ???
learning mode
fhir to model data
used for analytics vs ehr / clinical use
cdm odessy
odhsi
chime
omop
https://www.hl7.org/implement/standards/
mdd mapper - master data directory
is vendor app certified as mdd ? which parts?
is data mapped ? to ?
odessy std data model
athena etl
mapping ndc for medications
snowman
icp4,
https://www.hl7.org/implement/standards/
https://www.hl7.org/fhir/overview.html
https://blog.drchrono.com/exporting-importing-data-electronic-health-record-vendor/
https://www.healthit.gov/sites/default/files/c-cda_and_meaningfulusecertification.pdf
https://archer-soft.com/en/blog/7-tools-healthcare-data-management
https://www.healthcatalyst.com/master-data-management-in-healthcare-3-approaches
free low-end fhir engine to share data
https://www.qvera.com/free-hl7-interface-engine/?gclid=Cj0KCQiA_rfvBRCPARIsANlV66M2e__nw9UcXVSg-1_4pGdzIg9aVAzp-IVGUQDolxP2kQ2oUdYDilkaAuueEALw_wcB
hl7 stds for data interop
hie xfer data exchanges
q> business perspective for investment in hl7 / hie implementation
q> infrastructure requirements for hl7 confidential data store, share
q> how is data signed, encrypted, locked, authorized,notified, sent,
unlocked, opened
consensus --- confidence level -- interop smart contract rules
patient - provider - pair
use case driven
scope from patient diagnosis to prescription to checkup
epic 1 what is semantic interoperability
epic 2 specs / reqmts
epic 3 mvp poc
assumptions
iam in place
small use case right place to start
ccda xml data export pair record - longitudinal
links to other reference data
cda uses hl7 rim
use cases ??
immunization
track flu shot notification to patients, fulfillment
ehr chain for patient, patient issues
Impriavata - security for healthcare - vendor
https://www.imprivata.com/what-we-do
VHS - Virtual Healthcare Services
https://jconnolly.substack.com/p/future-of-healthcare-virtual-first
Clinical Data Improvements with Blockchain
Wendy Charles, PHD, Burst IQ - Report improving data participation in clinical data with URMs
https://www.mdpi.com/2075-4426/12/5/713
Current best practices in tumor registries provide a glimpse into a limited time frame over the natural history of disease, usually a narrow window around diagnosis and biopsy. This creates challenges meeting public health and healthcare reimbursement policies that increasingly require robust documentation of long-term clinical trajectories, quality of life, and health economics outcomes. These challenges are amplified for underrepresented minority (URM) and other disadvantaged populations, who tend to view the institution of clinical research with skepticism. Participation gaps leave such populations underrepresented in clinical research and, importantly, in policy decisions about treatment choices and reimbursement, thus further augmenting health, social, and economic disparities. Cloud computing, mobile computing, digital ledgers, tokenization, and artificial intelligence technologies are powerful tools that promise to enhance longitudinal patient engagement across the natural history of disease. These tools also promise to enhance engagement by giving participants agency over their data and addressing a major impediment to research participation. This will only occur if these tools are available for use with all patients. Distributed ledger technologies (specifically blockchain) converge these tools and offer a significant element of trust that can be used to engage URM populations more substantively in clinical research. This is a crucial step toward linking composite cohorts for training and optimization of the artificial intelligence tools for enhancing public health in the future. The parameters of an idealized clinical genomic registry are presented
TIPPSS - Trust, Identity, Privacy, Protection, Safety, Security
https://sagroups.ieee.org/2933/
Standards for Clinical IOT
Title: Standard for Clinical Internet of Things (IoT) Data and Device Interoperability with TIPPSS – Trust, Identity, Privacy, Protection, Safety, Security
Scope: This standard establishes the framework with TIPPSS principles (Trust, Identity, Privacy, Protection, Safety, Security) for Clinical Internet of Things (IoT) data and device validation and interoperability. This includes wearable clinical IoT and interoperability with healthcare systems including Electronic Health Records (EHR), Electronic Medical Records (EMR), other clinical IoT devices, in hospital devices, and future devices and connected healthcare systems.
Key Concepts
"A big factor in moving from provider-centric to patient-centric health care is the use of self sovereign identity ( Decentralized digital Identity and verifiable credentials ). Without an automated, independent trust foundation, expanding health care for all is difficult. Many digital identity systems come up short."
Jim Mason
Healthcare Identity use cases
Decentralized identity - 6 key use cases in healthcare:
- Credentialing Providers, Business Associates
- Verification of Eligibility, Patient Claims
- Secure Communications
- Digital Credentials
- Health Information Exchange
- Privacy - Identity, Data
good health pass - digital credentials to manage covid
https://www.goodhealthpass.org/
The Good Health Pass Interoperability Blueprint addresses nine technical and interoperability challenges around which global consensus must be reached:
- Design principles
- Creating a consistent user experience
- Standard data models and elements
- Credential formats, signatures, and exchange protocols
- Security, privacy, and data protection
- Trust registries
- Rules engines
- Identity binding (ensuring the authenticity of the holder)
- Governance
chainyard blockchain id - digital credentials to manage covid
Blockchain and Digital Credentials for covid-19 era
covid-tracking-chainyard-Blockchain and Digital Credentials for covid-19 era.pdf file
It is clear on a daily basis that the economy is not yet fully up and running and businesses are struggling with how to safely proceed.
To avoid employee apprehensions and additional costs from workplace outbreaks, companies need a structured program that covers all bases by including testing, symptom tracking, and contact tracing of their employees.
When the pandemic initially hit, reactions included the implementation of lockdowns, sheltering in place, safe distancing and frequent personal sanitization, and focus on procuring PPEs , testing supplies and ventilators.
Then attention turned towards opening sections of the economy, improving the ease of getting tested, creating field hospitals, and stabilizing the virus spread.
Now governments and businesses are exploring solutions that leverage advances in information technology and science.
ChangeHealthcare
https://www.changehealthcare.com/
United Healthcare
Anthem Healthcare
CVS Health
drummond-group-hipaa-checklist2pdf.pdf - compliance checklist tracking and blockchain
HIPAA compliance is critical for healthcare organizations, as non-compliance can result in significant consequences, including enforcement actions and damage to reputation.
This checklist provides comprehensive guidance for health IT organizations to help them prepare for HIPAA compliance. The checklist covers a range of areas, including risk analysis, policies and procedures, technical and physical safeguards, breach response planning, ongoing monitoring, and documentation. We recommend you incorporate this checklist and the best practices mentioned throughout into your HIPAA compliance planning processes to ensure your plan is comprehensive and will address any issues that might prevent compliance or put patient data at risk.
PBMs - Pharmacy Benefit Managers - negotiate drug programs for organizations with Pharma firms
https://www.healthpartners.com/plan/blog/prescription-drug-rebates-and-pbms/
https://bipartisanpolicy.org/blog/are-pbms-the-right-target/
https://phrma.org/Blog/ICYMI-The-Opaque-Industry-Secretly-Inflating-Prices-for-Prescription-Drugs
why not change PBM incentives to benefit from lower rather than higher drug prices?
Auchincloss on PBM pricing
Tackling health insurers’ predatory Rx drug pricing: During the Oversight Committee hearing on prescription drug prices, I questioned executives from the Big 3 pharmacy benefit managers, the middlemen of drug pricing: CVS Caremark, UnitedHealthGroup’s OptumRx, and Cigna Express Scripts. Each are Fortune 20 companies.
CVS & the other big PBMs claim that the Federal Trade Commission, the Medicare Payment Advisory Commission, independent experts, the New York Times, and the Wall Street Journal are all wrong: they don't mark up drugs.
During my questioning, however, I laid out CVS's own data on percent mark-ups over NADAC (the actual acquisition cost) for specialty drugs. I drew the data from a big, sophisticated employer in Massachusetts.
Multiple sclerosis Rx – 38,352%
Prostate cancer Rx – 6,375%
Leukemia Rx – 13,591%
Chronic kidney disease Rx – 5,037%
HIV Rx – 4,124%
Heart failure Rx – 161%
Specialty drugs are used by less than 2% of the population but account for 50% of the drug spend, and this is why: the PBMs are massively marking up the drugs necessary to treat the sickest patients. The result is higher out-of-pocket costs for patients and higher premiums for everyone.
If the PBMs can get away with these markups after negotiations with benefits experts at a Fortune 100 employer, imagine how they treat the small-business pharmacists that have to do business with them.
Pharmacists Fight Back: I introduced the bipartisan Pharmacists Fight Back Act to tackle the manipulative practices of Pharmacy Benefit Managers (PBMs) – the middlemen of drug pricing,
Tackling health insurers’ predatory Rx drug pricing: During the Oversight Committee hearing on prescription drug prices, I questioned executives from the Big 3 pharmacy benefit managers, the middlemen of drug pricing: CVS Caremark, UnitedHealthGroup’s OptumRx, and Cigna Express Scripts. Each are Fortune 20 companies.
CVS & the other big PBMs claim that the Federal Trade Commission, the Medicare Payment Advisory Commission, independent experts, the New York Times, and the Wall Street Journal are all wrong: they don't mark up drugs.
During my questioning, however, I laid out CVS's own data on percent mark-ups over NADAC (the actual acquisition cost) for specialty drugs. I drew the data from a big, sophisticated employer in Massachusetts.
Multiple sclerosis Rx – 38,352%
Prostate cancer Rx – 6,375%
Leukemia Rx – 13,591%
Chronic kidney disease Rx – 5,037%
HIV Rx – 4,124%
Heart failure Rx – 161%
Specialty drugs are used by less than 2% of the population but account for 50% of the drug spend, and this is why: the PBMs are massively marking up the drugs necessary to treat the sickest patients. The result is higher out-of-pocket costs for patients and higher premiums for everyone.
If the PBMs can get away with these markups after negotiations with benefits experts at a Fortune 100 employer, imagine how they treat the small-business pharmacists that have to do business with them.
Pharmacists Fight Back: I introduced the bipartisan Pharmacists Fight Back Act to tackle the manipulative practices of Pharmacy Benefit Managers (PBMs) – the middlemen of drug pricing,
Bipartisan support already exists for PBM transparency. In 2022 (and again in 2023), Sens. Chuck Grassley (R-IA) and Maria Cantwell (D-WA) introduced the Pharmacy Benefit Manager Transparency Act of 2023 (S. 127), which would prohibit spread pricing, require full rebate pass-throughs, and require PBMs to file an annual report to HHS.
verified.me SecureKey design
Design overview for Fabric with proposed enhancements for DID, Indy support
https://docs.google.com/document/d/1ENMO-S7i0ef09IRx5teE-eJbRMFsaKSXEdatcufvjPM/edit
SecureKey Technologies is launching an interoperability initiative aimed at establishing common standards and development frameworks for next generation digital identity networks.
Contributions
We will support the efforts within the Hyperledger and Decentralized Identity Foundation (DIF) communities to help create innovative distributed ledger technologies and digital identity networks. We believe that creating cross-project and cross-network standardization and interop along with common development frameworks represents the next step in transforming the digital identity space. In particular we support, and look forward to contributing to, the efforts of Hyperledger Fabric, Indy and the newly proposed Aries project along with DIF’s Identity Hub efforts.
Contributions will be directed towards the community projects above as well as open project extensions within the TrustBloc initiative.
In particular, we will contribute:
- Hyperledger Fabric performance and customization improvements. We are excited to contribute improvements we learned while building and taking our network operational.
- Enable DIDs to be managed and exposed from Fabric, and more generically enabling document provenance.
- A model for digital identity exchange based on DIDs, Verifiable Credentials, and Hubs.
- Efforts towards interoperability with the newly proposed Hyperledger Aries project, in order to use a Fabric-based ledger and our digital identity model. We think it’s critical to allow variation on top of a common base.
- Tooling and demos to enhance developer experiences building digital identity networks.
About SecureKey
SecureKey builds identity networks like Verified.Me, the Canadian identity sharing Network supported by seven major banks, mobile operators, a major credit agency, and other providers in Canada. Verified.Me provides a user centric, privacy protecting identity platform for services that trust the individual’s identity established at their financial institution and other connected organizations. Users can link in account information across services for a convenient but highly reliable digital identity where information is delivered in real time.
Technical Brief
In the following diagram, we provide an overview of the components related to the TrustBloc initiative. We will follow-up with additional details and data exchange flows.
IBM Cross Border Carrier Payments solution coming
https://finance.yahoo.com/news/softbank-develop-cross-carrier-blockchain-050039037.html
SoftBank is teaming up with IBM to develop cross-carrier blockchain solutions, with the focus on technologies that will allow smartphone users to make local payments when traveling overseas and roaming.
first project being undertaken by the CBSG is the Cross-Carrier Payment System (CCPS), which is aimed to allow mobile-phone customers to pay locally using their devices when traveling outside their home countries.
TBCASoft will be using the IBM Blockchain Platform, IBM’s Hyperledger-powered enterprise blockchain solution.
TBCASoft technology helps “optimize” clearing between different carriers and transaction records, according to the announcement, and allows for the interoperability of mobile networks and the bolting on of networks of merchants to enable payments
TIPPSS - Trust Identity Privacy, Protection Safety & Security Standards
TIPPSS stands for Trust, Identity, Privacy, Protection, Safety, and Security. It's a framework of principles that's part of the IEEE 2933-2024 standard for Clinical Internet of Things (IoT) data and device interoperability. The standard aims to ensure that medical devices can communicate with each other and with healthcare systems, such as electronic health records (EHR) and electronic medical records (EMR), with trust, identity, privacy, safety, and security. The standard also includes wearable clinical IoT devices and in-hospital devices.
IEEE 2933-2024 - IEEE SA
IEEE Approved Draft Standard for Clinical Internet of Things (IoT) Data and Device Interop...
IEEE Standards Association
6:59
IEEE's new Clinical Internet of Things standard built on TIPPSS principles - Latest Videos - HIMSS TV Homepage
HIMSS.tv
Setting new standards for wireless medical devices
Feb 19, 2024 — The IEEE 2933 Working Group is moving through final stages to publish IEEE P29...
Med-Tech Innovation News
The IEEE P2733 Working Group, led by Florence Hudson, is developing the standard and also plans to incorporate artificial intelligence and machine learning (AI/ML). As the world becomes more connected and dependent on technology, the incorporation of universal human values like TIPPSS into new technologies is becoming increasingly important.
Generative AI is experimental.
HIPAA - Health Insurance Portability and Accountability Act (HIPAA)
The Health Insurance Portability and Accountability Act (HIPAA) of 1996 is a federal law that establishes standards to protect the confidentiality and security of patients' health information. HIPAA includes three rules:
Privacy Rule
Protects "individually identifiable health information" (PHI) in any form or media, including electronic, paper, or oral. This rule gives patients the right to request and receive copies of their health records, as well as to request corrections. It also requires organizations to verify the identity and authority of anyone requesting PHI, unless the organization already knows them.
Security Rule
Sets national standards to protect electronic PHI. This rule requires organizations to implement administrative, physical, and technical safeguards to ensure the confidentiality, integrity, and security of electronic PHI. For example, organizations must implement procedures to verify that anyone seeking access to electronic PHI is who they claim to be.
Enforcement Rule
Establishes civil financial penalties for violating HIPAA rules, as well as procedures for investigations and hearings. The US Department of Health and Human Resources has investigated over 20,000 cases, often requiring corrective action or changes to privacy practices.
video - Acronis - MSP compliance in AI w NIST 2.0, HIPAA
Potential Value Opportunities
Primary Care delivers the most value and best outcomes but gets little funding
TYX - Trust Your X
TYH - Trust Your Health
TYR - Trust Your Room
Just like a vehicle inspection sticker shows when your car was last inspected, we can help automate verifications that rooms are sanitized if you're interested
TYSU - Trust Your Support
TYC - Trust Your Compliance
TYCS - Trust Your Customer Service
TYSV - Trust Your Service
verification for ANY scheduled service using automated event workflows
- metadata context - multiple parties, asset for service, service type, service order, service tickets, assignment, schedule, contractor, work, materials used, inspection, approval, payment scheduled, payment completed
- create service order ( one time, on demand or repeat ) for an asset
- schedule work for all operations on service order
- assign resource ( worker or contractor )
- contractor accepts assignment
- materials allocated or ordered
- materials available
- contractor begins work ( logs in )
- contractor updates work status as required
- contractor updates materials consumed
- contractor stops work ( logs out )
- contractor validates work completed
- inspection scheduled
- inspection completed
DLT Services
| DLT Features | Impacts | |
| i | synchronized shared digital distributed ledger, replicated and distributed across participants | |
| ii | Mutually agreeable record and transaction formats that can be verified and validated by source systems | |
| iii | Strong cryptographic verification and cross‐validation of record entries to ensure immutability and prevent tampering or double‐entries | |
| iv | Processes for ensuring consensus and consistency of the ledger view by all participants utilizing strong cryptography, appropriate consensus mechanisms, and cryptographic hashing algorithms to link entries together | |
| v | Technologies that allow participants to utilize Application Programming Interfaces (APIs) or utilities to enable reading or writing to the distributed ledger and enable records and transactions to be transferred between the Distributed Ledger and authoritative data sources and/or systems |
Identities in Clinical Scenarios
| Identities | |
| i. | Patient identity |
| ii. | Patient identity related to the Clinical IoT device and software |
| iii. | Clinical IoT device identity and data transfer |
| iv. | Physician/Clinician/Organization identity related to patient data |
| v. | Patient and their data identity vi.Publisher‐subscriber identity |
Potential Challenges
Candidate Solutions
Google Health Data Engine
Google Cloud announced the private preview of Healthcare Data Engine, an end-to-end solution for healthcare and life sciences organizations that harmonizes data from multiple sources, including medical records, claims, clinical trials, and research data. Healthcare Data Engine helps operational leaders, researchers, and clinicians gain real-time, holistic views of patient longitudinal records, and enables advanced analytics and AI in a secure, compliant, and scalable cloud environment.
IBM Food Trust Network
| https://www.ibm.com/blockchain/solutions/food-trust | IBM Food Trust Network |
| https://www.ibm.com/downloads/cas/E9DBNDJG | Food Trust Overview ( view here ) |
| https://github.com/IBM/IFT-Developer-Zone/wiki/doc-Message-Types | Message Types |
| https://github.com/IBM/IFT-Developer-Zone/wiki/APIs | Food Trust API's |
| https://food.ibm.com/ift/api/connector/swagger-ui.html | Swagger Tests for API's |
| https://www.gs1.org/sites/default/files/docs/epc/EPCIS-Standard-1.2-r-2016-09-29.pdf | EPICS standard for trading partners |
Food Trust Value List
| Value | Features | Description |
|---|---|---|
| Safety | Transparency Traceability | Trace food instantly – with end-to-end supply chain data visibility – to help ensure food safety and regulatory compliance. |
| Supply chain efficiency | Shared immutable ledger | Access a shared and immutable digital ledger in real time – rather than ink on paper – to find choke points and uncover opportunities to speed your supply chain. |
| Food Freshness | Traceability Shared data | Gain instant and efficient food tracing from source to consumer to more accurately judge peak freshness and remaining shelf life – and reduce product loss. |
| Sustainability | Shared data Immutable ledger Smart contracts | Rely on shared data and an immutable ledger to help ensure the promised quality of products and that food comes from a sustainable source. Smart contracts improve data quality |
| Brand Trust | Transparency Traceability | Gain a competitive advantage as you add transparency and specificity about the sourcing of your food products. Build trust in the safety and quality of your brand. |
| Food waste | Shared data | Identify waste hot spots and speed responsiveness using better visibility into your food supply chain. Reduce costly food waste and boost your bottom line. |
| Food Fraud | Shared data Immutable ledger Smart contracts | Data-sharing across the food supply helps eliminate chances for fraud and errors – and can help preserve the integrity of raw materials, products, and packaging. |
Verified.me - a secure blockchain identity framework for Canadian banks on IBM Blockchain
Verified.Me, by SecureKey Technologies Inc., is the new and secure way to help you verify your identity, so you can quickly get access to the services and products you want online, in person and on the phone.
Verified.Me helps verify your identity using personal information that you consent to share from your Connections, like your financial institution, with service providers you want to transact with.
https://verified.me/wp-content/uploads/2019/04/VerifiedMe_General_Overview_Script_EN-1.pdf
The MediLedger Network pharmaceutical supply chain
https://www.mediledger.com/faq
What is the MediLedger Network?
The MediLedger Network is the leading life sciences industry network that runs solutions for data alignment, validation and transaction settlement between trading partners. The network actually utilizes transaction-related data like contracts, customers, and products that are shared through the network to enforce configurable business rules on transactions for each participant, enabling industry level automation and trust.
The MediLedger Network is powered by blockchain, which means it is decentralized so trading partners are doing business directly and rules are being enforced automatically, without any party sitting in the middle.
Chronicled is the technology company, based in San Francisco, CA, USA, that developed the MediLedger Network in collaboration with leading companies in the life sciences industry. Chronicled provides support to active participants, improvements to the network itself and develops the solutions run by participants on top of the network.
How is Blockchain used in MediLedger Network
Blockchain is a mechanism to enforce business rules automatically between participants.
Every participant in a blockchain network has a copy of the blockchain data and the rules being enforced on that data. No single party can change the data or the rules. This creates trust between trading partners that was never possible before now.
An example business rule enforced by the network might be:Manufacturer A requires that every chargeback submitted by wholesaler B has an active customer HIN that matches an eligible customer HIN on the contract
How is Data Privacy Maintained on the Network?
Contract and chargeback data is extremely sensitive, and is only meant to be shared between relevant trading partners. The MediLedger blockchain is unique in how it facilitates business rule enforcement while maintaining complete data privacy.
On the MediLedger Network, contract updates, chargebacks and other sensitive data are not published directly on the blockchain, instead business rules are enforced against cryptographic proofs (zero knowledge proofs) of the data, published on the blockchain instead of the data itself.
Every company in the network running a node has a copy of the blockchain to facilitate rule enforcement across the industry, but zero business intelligence is leaked through the blockchain. This is the true differentiator and strength of the MediLedger Network.
Priorities in MediLedger Solution Design
- Consensus, which leverages the Aura consensus plugin in Parity Ethereum and allows the network to authorize participants and block creators in a permissioned network environment whereby block creators stake their reputation instead of tokens.
- Privacy, which is paramount for any company to participate, clashes with the need to enforce industry-wide business rules. Chronicled solved this problem by coupling zk-SNARK technology with Parity Ethereum, making it possible to record proofs of transactions on-chain while ensuring that all of the participants in the network retain control over their raw transactional data.
- Performance, which is solved by using off-chain p2p communications and on-chain proofs of transactions only where needed to enforce cross-industry business rules. Such efficient design coupled with the use Aura consensus algorithm and the use of zk-SNARK for privacy has allowed the MediLedger Network to accomplish the full set of requirements defined by the industry with sub-second response times.
The pharmaceutical industry needed an end-to-end solution to a specific regulatory problem that all of the companies in the industry could easily integrate with their legacy enterprise systems.
In order to deliver the solution, Chronicled has built a platform using Parity’s tech stack that can deliver a complete enterprise solution via a single installation. The new Chronicled Platform is easily deployable by diverse industry participants with different levels of IT sophistication, as is now being demonstrated within the US pharmaceutical industry.
“The model of Parity Team is about delivering a toolkit and a modular underlying layer - i.e., Parity Substrate - that allows the professionals of each industry to build the most appealing solution for the targeted use case. At the same time, the network interoperability technology that Parity is creating - i.e. Polkadot - will allow us to integrate blockchain networks together.” - Chronicled CTO Maurizio Greco
Fetch.AI - smart blockchain tokenomics framework
Agents
Fetch.AI is a decentralised digital world in which useful economic activity takes place. This activity is performed by Autonomous Agents. These are digital entities that can transact independently of human intervention and can represent themselves, devices, services or individuals. Agents can work alone or together to construct solutions to today’s complex problems.
Open Economic Framework
The digital world in which agents live is called the Open Economic Framework (OEF). This world acts as the ultimate value exchange dating agency: each agent sees a space optimised in real-time just for them, where important things are clear and visible and less important things are simply removed. The OEF provides the senses for agents: their sight, touch and hearing to present to them a world unique to the viewer.
Smart Ledger
Underpinning the digital world is the smart ledger: a new generation of learning ledger that provides a collective super-intelligence to support agents’ individual intelligences. It provides market intelligence, previously locked up in centralised silos, to everyone so that any agent that wants something is assured of the shortest possible route to find another that has it. Fetch.AI’s smart ledger scales to support millions of transactions per second and is able to restructure itself to present the OEF’s digital world to the agents that use it.
EPIC vs AllScripts compare
https://www.slideshare.net/GinaDeGregorio/epic-systems-vs-allscripts
features
non-functional criteria
how google contract tracing api works
https://9to5mac.com/2020/05/23/apple-and-google-exposure-notification-api/
virus-contact-tracing-api-google-how-it-works-2020.pdf
How it works
When a user enables the feature and has an app from a public health authority installed, the device will regularly send out a beacon via Bluetooth that includes a random Bluetooth identifier. When two people are near each other, their phones will exchange and record these Bluetooth identifiers.
If someone tests positive for COVID-19, they can voluntarily report the positive test to the Exposure Notification application for their region. These screenshots show public health authority developers how to walk users through the process of reporting that they tested positive for coronavirus, including a unique test identifier:
The Exposure Notification API will also likewise download a list of the keys for the beacons that have been verified as belonging to people confirmed positive for COVID-19, and check against that list. If there is a match, the user may be notified and advised on the next steps. What constitutes as an exposure? This is up to the public health agencies to decide, but the API itself includes a minimum of 5 minutes of interaction for it to be considered a match.
Think of it like this: Person A and Person B spend more than 5 minutes together at a restaurant. During this time, their smartphones exchange the anonymous Bluetooth identifier. They go their separate ways, but Person A tests positive for COVID-19 a few days later and chooses to report that positive test via the Exposure Notification app. Person B will then receive a notification saying that someone they recently interacted with has tested positive for COVID-19.
Apple and Google have repeatedly emphasized that much of the control is in the hands of the public health authorities themselves. Apple and Google are providing the Exposure Notification API, and developers can adjust the details as-needed while preserving the privacy and requirements of the API.
With the release of iOS 13.5 this week, Apple and Google also said they had made further privacy enhancements to the Exposure Notification API:
- Temporary Exposure Keys are now generated randomly instead of being derived from a tracing key
- All metadata associated with Bluetooth is now encrypted to make it more difficult to identify a person
More details on the Exposure Notification API:
- The entire system is opt-in
- Other applications for contact tracing will be allowed in the App Stores; they can adopt Apple and Google’s API, but they must remove all Location Services features and adopt the privacy frameworks of the Apple and Google API
- Contact tracing data is only stored on a user’s device
- Contact tracing data is only processed on a user’s device
- Public health agencies can define what constitutes an exposure event
- Public health agencies can determine the number of exposure events a person has had
- Transmission risk of positive cases can be factored into the definition of an exposure event
- Public health agencies can contact exposed users based on a combination fo the API and data that users voluntarily choose to input into the app
Keyhole Virus Tracker app - open-source
https://github.com/in-the-keyhole/keyhole-virus-tracker
https://github.com/hyperledger-labs/keyhole-fabric-api-gateway
https://keyholesoftware.com/company/creations/white-papers/blockchain-virus-tracker/
There are many viable use cases for blockchain technology. In these strange and unsettling times, another one has unfortunately emerged: the tracking and dissemination of patient testing data amid the COVID-19 pandemic.
The healthcare industry has long struggled with the secure sharing of data. For a variety of reasons, healthcare leaders and experts agree that developing an integrated database to circulate health records and data is important to the future of the industry. However, as we see with the patient testing data, finding a way to securely store and share immutable, standardized data has proved to be a massive challenge.
As this white paper will discuss, blockchain technology offers a solution to the specific problem of sharing secure and up-to-date patient testing data. This paper describes a HIPAA-compliant blockchain solution and implementation for an efficient, near real-time single source of truth of lab results. The blockchain implementation will be compared to a traditional data-sharing model and analyzed for its features that directly benefit the virus lab result tracking use case.
Open-Source Implementation
The blockchain implementation discussed in this white paper has been released as open-source software, with all code available on Github. Learn more about the Keyhole Virus Tracker by visiting its product page here.
Step-by-step guide for Example
sample code block