Health Care Native App Example - Revision history

Tom: /* Distribution by Epic in US */

2025-04-25T01:04:46Z

‎Distribution by Epic in US

Tom: /* Protected Data Store */

2025-04-25T01:04:00Z

‎Protected Data Store

Tom: /* Solutions */

2025-04-12T00:14:11Z

‎Solutions

Tom: /* Solutions */

2025-04-12T00:13:32Z

‎Solutions

Tom: /* Deployed Apps */

2024-01-22T18:08:51Z

‎Deployed Apps

Tom: /* Details of Implementation */

2024-01-22T06:38:06Z

‎Details of Implementation

Tom: /* Other References */

2021-12-06T18:23:42Z

‎Other References

Tom: /* Next Steps */

2021-11-02T14:46:55Z

‎Next Steps

Tom: /* Solutions */

2021-07-15T13:13:12Z

‎Solutions

Tom: /* Patient's Rights */

2021-07-15T13:11:20Z

‎Patient's Rights

@@ Line 100: / Line 100: @@
 *Microsoft [https://docs.microsoft.com/en-us/dotnet/standard/io/types-of-isolation types of isolation] for UWP apps.
 ===Distribution by Epic in US===
-A little-known fact: Epic doesn’t make it easy to distribute your app across its network of hospitals.
+A little-known fact: Epic doesn’t make it easy to distribute your app across its network of hospitals. But there’s a loophole, and it’s completely legit.
-But there’s a loophole, and it’s completely legit.
+If you’re building a patient-facing app, Epic offers something called Automatic Client ID Distribution. Epic powers over 50% of inpatient beds in the US. If your app qualifies for this automatic distribution, you can get instantly deployed to ALL of Epic’s partner hospitals without needing to sign individual agreements.
 Here's how to qualify:

@@ Line 99: / Line 99: @@
 *There are a variety of data stores associated with a native app. This store contains the user personal information that binds the user to the various [[Web Site]]s where the user has an account and is not for any [[PHI]]. Note that the private key is NOT stored in the data store, but in the [[Trusted Execution Environment]] where it can be used for signing, but is not exposed to the [[Native App]].
 *Microsoft [https://docs.microsoft.com/en-us/dotnet/standard/io/types-of-isolation types of isolation] for UWP apps.
 ===Deployed Apps===

@@ Line 34: / Line 34: @@
 ==Solutions==
 Several trends have been seen that can enable such a Patient-empowered solution:
 # Matching of patient records to the patient is a recognized problem that requires some solution to prevent unwanted patient outcomes. Efforts at a universal health care identifier for patients seems to be as far in the future as ever and no other solution has appeared on the horizon.
 # The CARIN Alliance has published a code of ethics for health care information that moves beyond the control of HIPAA covered entities.

@@ Line 35: / Line 35: @@
 ==Solutions==
 Several trends have been seen that can enable such a Patient-empowered solution:
 # Matching of patient records to the patient is a recognized problem that requires some solution to prevent unwanted patient outcomes. Efforts at a universal health care identifier for patients seems to be as far in the future as ever and no other solution has appeared on the horizon.
 # The CARIN Alliance has published a code of ethics for health care information that moves beyond the control of HIPAA covered entities.

@@ Line 100: / Line 100: @@
 ===Deployed Apps===
-There are a [https://apps.smarthealthit.org/apps/featured/page/2 fair number of apps deployed] that support
+There are a [https://apps.smarthealthit.org/apps/featured/page/2 fair number of apps deployed] that support [[FHIR]] formatted data on smart phones, nearly 50 at the end of 2023. Usage data is not available, but assumed to be low accept for the case of Smart Health Cards (SHC:) which includes wallet apps like Apple and the LA state driver's license app. There was a spurt of support during the COVID pandemic as evidence for vaccination peaked and then died out.
 ==Details of Implementation==

@@ Line 117: / Line 117: @@
 *[https://www.hl7.org/fhir/http.html#capabilities MetaData] or capabilities from FHIR - might not survive till next versions.
 *The [https://nhisac.org/ H-ISAC] Healthcare Information Sharing and Analysis Center provides a forum for coordinating, collaborating and sharing vital Physical and Cyber Threat Intelligence and best practices with each other.
-*[http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2a.pdf#nameddest=3_19_Authenticate_Node__ITI_19_ Authenticate Node] section 19 of (2018-07-24) IHE IT Infrastructure Technical Framework primarily relies on mutual authentication with no specific trust anchor other than X.509 certificate chains.
+*[http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2a.pdf#nameddest=3_19_Authenticate_Node__ITI_19_ Authenticate Node] section 19 of (2018-07-24) IHE IT Infrastructure Technical Framework primarily relies on [[Mutual Authentication]] with no specific trust anchor other than X.509 certificate chains.
 *[https://wiki.idesg.org/wiki/index.php/Category:Health IDEF health wiki pages.]
@@ Line 123: / Line 123: @@
 [[Category:User Experience]]
 [[Category:Best Practice]]
-[[Category:Health]]
+[[Category: Health]]

@@ Line 107: / Line 107: @@
 ==Next Steps==
 #Create pilot test code for validation of ideas with all participants in a live setting.
-#Test APIs for getting data (like Blue Button)
+#Test APIs for getting data (like [[Blue Button]])
 #Start a directed pilot test with a specific health care provider to get real-world feedback.
 #Test APIs for transmitting data to [[EHR]]s.

@@ Line 37: / Line 37: @@
 # Matching of patient records to the patient is a recognized problem that requires some solution to prevent unwanted patient outcomes. Efforts at a universal health care identifier for patients seems to be as far in the future as ever and no other solution has appeared on the horizon.
 # The CARIN Alliance has published a code of ethics for health care information that moves beyond the control of HIPAA covered entities.
-# The [[Smart_Phone#Smart_Phone_role_in_Authentication|role of Smart Phones in Authentication]] has been expanding (see that wiki page for specific examples.)
+# The [[Smart_Phone#Smart_Phone_role_in_Authentication|role of Smart Phones in Authentication]] has been expanding (see that wiki page for specific examples.) See section below on Patient Rights.
 # Microsoft has just introduced<ref>Microsoft, ''Microsoft unveils decentralized identity protocol that works atop the Bitcoin blockchain.'' (2019-05-13) https://www.geekwire.com/2019/microsoft-unveils-decentralized-identity-protocol-works-atop-bitcoin-blockchain/</ref> a open-source protocol to address performance issues with [[Blockchain]]. ION, or Identify Overlay Network, is based on an earlier blockchain project built by Microsoft and others called Sidetree.

@@ Line 59: / Line 59: @@
 ===Patient's Rights===
-Deborah C. Peel, MD Founder and President Patient Privacy Rights
+* Deborah C. Peel, MD Founder and President Patient Privacy Rights www.patientprivacyrights.org https://patientprivacyrights.org/health-privacy-summit/
+* [https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Forange.hosting.lsoft.com%2Ftrk%2Fclick%3Fref%3Dznwrbbrs9_6-2be2bx32c520x081583%26&data=04%7C01%7C%7C1b0cfc8a7db9484bb50308d946e0a1e9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637618752869025374%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=PaRyaYQadjyHbH5wP%2FruYlnD0B5rftISxc8a9dfAJeQ%3D&reserved=0 WHO Releases AI Guidelines for Health Government Technology] 2021-07-12 <blockquote>A new report from the World Health Organization (WHO) offers guidance for the ethical use of artificial intelligence (AI) in the health sector. The six primary principles for the use of AI as set forth in the report are to protect autonomy; promote human well-being, safety, and the public interest; ensure transparency, explainability, and intelligibility; foster responsibility and accountability; ensure inclusiveness and equity; and promote responsive and sustainable AI. These principles are intended as a foundation for AI stakeholders, including governments, developers, and society. The report, Ethics and Governance of Artificial Intelligence for Health, finds public- and private-sector collaboration necessary to ensure AI’s accountability.<blockquote>
 ===Patient Experience===