Phone as Health Care Credential - Revision history

Tomjones: /* Liabilities */

2021-03-20T20:23:56Z

Liabilities

← Older revision		Revision as of 20:23, 20 March 2021
Line 45:		Line 45:
	*In any case liability insurance is RECOMMENDED for app vendors.		*In any case liability insurance is RECOMMENDED for app vendors.
	* If an attacker learns either your subject identifier or medical record locator, they can claim ownership. In a well-designed system such a fraudulent claim will fail.		* If an attacker learns either your subject identifier or medical record locator, they can claim ownership. In a well-designed system such a fraudulent claim will fail.
			===Connection Establishment===
			# The app is started by the user, it connects to the portal of the EHR. (Example is the Apple Health App.) The portal will get user consent to communicate with the app.
			# The user is on the portal of the EHR. The EHR will need to understand what app is being started. If there are multiple apps that are applicable, this [[User Experience]] may be challenging.

	==Solution==		==Solution==

Tomjones: /* Context */

2021-03-20T20:15:31Z

Context

← Older revision		Revision as of 20:15, 20 March 2021
Line 12:		Line 12:

	==Context==		==Context==
	* ~~Only~~ smart phones running iOS or Android operating systems in use by the patient or their guardian.		* Primary use case is smart phones running iOS or Android operating systems in use by the patient or their guardian.
	*The wiki page [[Trustworthy Healthcare Ecosystem]] contains more context information for the patient's view of trusted identifiers in cyberspace.		*The wiki page [[Trustworthy Healthcare Ecosystem]] contains more context information for the patient's view of trusted identifiers in cyberspace.
	*Some of the benefits of simple cell phone use can be included in a comprehensive plan for patient matching and authentication, but since 84% of patients in early 2020 have smart phones, that is the focus of this wiki page.		*Some of the benefits of simple cell phone use can be included in a comprehensive plan for patient matching and authentication, but since 84% of patients in early 2020 have smart phones, that is the focus of this wiki page.

Tomjones: /* Context */

2021-03-20T20:11:36Z

Context

← Older revision		Revision as of 20:11, 20 March 2021
Line 12:		Line 12:

	==Context==		==Context==
	* Only smart phones running iOS or Android operating systems.		* Only smart phones running iOS or Android operating systems in use by the patient or their guardian.
	*The wiki page [[Trustworthy Healthcare Ecosystem]] contains more context information for the patient's view of trusted identifiers in cyberspace.		*The wiki page [[Trustworthy Healthcare Ecosystem]] contains more context information for the patient's view of trusted identifiers in cyberspace.
	*Some of the benefits of simple cell phone use can be included in a comprehensive plan for patient matching and authentication, but since 84% of patients in early 2020 have smart phones, that is the focus of this wiki page.		*Some of the benefits of simple cell phone use can be included in a comprehensive plan for patient matching and authentication, but since 84% of patients in early 2020 have smart phones, that is the focus of this wiki page.

Tomjones: /* Liabilities */

2021-03-20T20:10:54Z

Liabilities

← Older revision		Revision as of 20:10, 20 March 2021
Line 44:		Line 44:
	*But judicial review will win in the end, and that process has hardly begun.		*But judicial review will win in the end, and that process has hardly begun.
	*In any case liability insurance is RECOMMENDED for app vendors.		*In any case liability insurance is RECOMMENDED for app vendors.
	* If an attacker learns either your subject identifier or medical record locator, they can claim ownership.		* If an attacker learns either your subject identifier or medical record locator, they can claim ownership. In a well-designed system such a fraudulent claim will fail.

	==Solution==		==Solution==

Tomjones: /* References */

2021-03-20T20:07:09Z

References

← Older revision		Revision as of 20:07, 20 March 2021
Line 109:		Line 109:
	* [https://www.nccoe.nist.gov/projects/use-cases/mobile-sso NIST use cases for mobile SSO - Single SignOn]		* [https://www.nccoe.nist.gov/projects/use-cases/mobile-sso NIST use cases for mobile SSO - Single SignOn]
	* [https://www.evernym.com/blog/claims-verification-healthcares-496b-problem/ Evernym described the benefits of a decentralized Identity.] This solution provides all of those benefits without taking a dependency on the DID. It is still possible to use a DID or any other source of an [[Identifier]].		* [https://www.evernym.com/blog/claims-verification-healthcares-496b-problem/ Evernym described the benefits of a decentralized Identity.] This solution provides all of those benefits without taking a dependency on the DID. It is still possible to use a DID or any other source of an [[Identifier]].
	* [https://www.youtube.com/watch?v=N0PXAxBA-J8&t=1064s Smart on FHIR] presentation by Josh Mandel in 2019 ~~focus~~ on the following KLAS report.		* [https://www.youtube.com/watch?v=N0PXAxBA-J8&t=1064s Smart on FHIR] presentation by Josh Mandel in 2019 focuses on the following KLAS report.
	* [https://smarthealthit.org/2017/02/connected-apps-report/ KLAS application report] is directed to healthcare providers.		* [https://smarthealthit.org/2017/02/connected-apps-report/ KLAS application report] is directed to healthcare providers.

	[[Category:Profile]]		[[Category:Profile]]
	[[Category:Health]]		[[Category:Health]]

Tomjones: /* References */

2021-03-20T20:06:49Z

References

← Older revision		Revision as of 20:06, 20 March 2021
Line 109:		Line 109:
	* [https://www.nccoe.nist.gov/projects/use-cases/mobile-sso NIST use cases for mobile SSO - Single SignOn]		* [https://www.nccoe.nist.gov/projects/use-cases/mobile-sso NIST use cases for mobile SSO - Single SignOn]
	* [https://www.evernym.com/blog/claims-verification-healthcares-496b-problem/ Evernym described the benefits of a decentralized Identity.] This solution provides all of those benefits without taking a dependency on the DID. It is still possible to use a DID or any other source of an [[Identifier]].		* [https://www.evernym.com/blog/claims-verification-healthcares-496b-problem/ Evernym described the benefits of a decentralized Identity.] This solution provides all of those benefits without taking a dependency on the DID. It is still possible to use a DID or any other source of an [[Identifier]].
			* [https://www.youtube.com/watch?v=N0PXAxBA-J8&t=1064s Smart on FHIR] presentation by Josh Mandel in 2019 focus on the following KLAS report.
	* [https://smarthealthit.org/2017/02/connected-apps-report/ KLAS application report] is directed to healthcare providers.		* [https://smarthealthit.org/2017/02/connected-apps-report/ KLAS application report] is directed to healthcare providers.

	[[Category:Profile]]		[[Category:Profile]]
	[[Category:Health]]		[[Category:Health]]

Tomjones: /* References */

2021-03-20T20:05:22Z

References

← Older revision		Revision as of 20:05, 20 March 2021
Line 109:		Line 109:
	* [https://www.nccoe.nist.gov/projects/use-cases/mobile-sso NIST use cases for mobile SSO - Single SignOn]		* [https://www.nccoe.nist.gov/projects/use-cases/mobile-sso NIST use cases for mobile SSO - Single SignOn]
	* [https://www.evernym.com/blog/claims-verification-healthcares-496b-problem/ Evernym described the benefits of a decentralized Identity.] This solution provides all of those benefits without taking a dependency on the DID. It is still possible to use a DID or any other source of an [[Identifier]].		* [https://www.evernym.com/blog/claims-verification-healthcares-496b-problem/ Evernym described the benefits of a decentralized Identity.] This solution provides all of those benefits without taking a dependency on the DID. It is still possible to use a DID or any other source of an [[Identifier]].
			* [https://smarthealthit.org/2017/02/connected-apps-report/ KLAS application report] is directed to healthcare providers.

	[[Category:Profile]]		[[Category:Profile]]
	[[Category:Health]]		[[Category:Health]]

Tomjones: /* References */

2021-01-24T00:39:03Z

References

← Older revision		Revision as of 00:39, 24 January 2021
Line 102:		Line 102:
	==References==		==References==
	* This wiki page is derived, in part, from the [[Privacy Enhanced by User Agent]] use case created by Tom Jones in September 2013.		* This wiki page is derived, in part, from the [[Privacy Enhanced by User Agent]] use case created by Tom Jones in September 2013.
			* The wiki page [[Digital Travel Credentials]] has a Health credential use case.
	* Robert S. Rudin et al., ''Defining and Evaluating Patient-Empowered Approaches to Improving Record Matching.'' RAND Corp., accessed Aug. 27, 2018, https://www.rand.org/pubs/research_reports/RR2275.html.		* Robert S. Rudin et al., ''Defining and Evaluating Patient-Empowered Approaches to Improving Record Matching.'' RAND Corp., accessed Aug. 27, 2018, https://www.rand.org/pubs/research_reports/RR2275.html.
	* NIST ''Electronic Health Records on Mobile Devices'' NIST Cybersecurity Practice Guide, Special Publication 1800-1: (2018-08-29) https://www.nccoe.nist.gov/projects/use-cases/health-it/ehr-on-mobile-devices		* NIST ''Electronic Health Records on Mobile Devices'' NIST Cybersecurity Practice Guide, Special Publication 1800-1: (2018-08-29) https://www.nccoe.nist.gov/projects/use-cases/health-it/ehr-on-mobile-devices

Tomjones: /* Context */

2021-01-16T00:34:37Z

Context

← Older revision		Revision as of 00:34, 16 January 2021
Line 15:		Line 15:
	*The wiki page [[Trustworthy Healthcare Ecosystem]] contains more context information for the patient's view of trusted identifiers in cyberspace.		*The wiki page [[Trustworthy Healthcare Ecosystem]] contains more context information for the patient's view of trusted identifiers in cyberspace.
	*Some of the benefits of simple cell phone use can be included in a comprehensive plan for patient matching and authentication, but since 84% of patients in early 2020 have smart phones, that is the focus of this wiki page.		*Some of the benefits of simple cell phone use can be included in a comprehensive plan for patient matching and authentication, but since 84% of patients in early 2020 have smart phones, that is the focus of this wiki page.
	* [https://healthwallet.cards ~~smart~~ Health Cards Framework] is focused on COVID-19 certificates.		* [https://healthwallet.cards Smart Health Cards Framework] is focused on COVID-19 certificates.
	*[https://www.pewtrusts.org/-/media/assets/2018/09/healthit_enhancedpatientmatching_report_final.pdf Pew research reports] that Enhanced Patient Matching Is Critical to Achieving Full Promise of Digital Health Records, and to prevent harm through faulty health history information. The report is oriented towards healthcare provider issues. When they did ask patients what they wanted it was consistently shown that patients want all of the purported benefit of matching, but with no loss of privacy. They also found that Republican voters tended to favor less government involvement in the process.		*[https://www.pewtrusts.org/-/media/assets/2018/09/healthit_enhancedpatientmatching_report_final.pdf Pew research reports] that Enhanced Patient Matching Is Critical to Achieving Full Promise of Digital Health Records, and to prevent harm through faulty health history information. The report is oriented towards healthcare provider issues. When they did ask patients what they wanted it was consistently shown that patients want all of the purported benefit of matching, but with no loss of privacy. They also found that Republican voters tended to favor less government involvement in the process.
	# System oriented solution needs unique patient identifiers - but what they really mean is mandatory patient IDs for life.		# System oriented solution needs unique patient identifiers - but what they really mean is mandatory patient IDs for life.

Tomjones: /* Context */

2021-01-16T00:34:09Z

Context

← Older revision		Revision as of 00:34, 16 January 2021
Line 15:		Line 15:
	*The wiki page [[Trustworthy Healthcare Ecosystem]] contains more context information for the patient's view of trusted identifiers in cyberspace.		*The wiki page [[Trustworthy Healthcare Ecosystem]] contains more context information for the patient's view of trusted identifiers in cyberspace.
	*Some of the benefits of simple cell phone use can be included in a comprehensive plan for patient matching and authentication, but since 84% of patients in early 2020 have smart phones, that is the focus of this wiki page.		*Some of the benefits of simple cell phone use can be included in a comprehensive plan for patient matching and authentication, but since 84% of patients in early 2020 have smart phones, that is the focus of this wiki page.
			* [https://healthwallet.cards smart Health Cards Framework] is focused on COVID-19 certificates.
	*[https://www.pewtrusts.org/-/media/assets/2018/09/healthit_enhancedpatientmatching_report_final.pdf Pew research reports] that Enhanced Patient Matching Is Critical to Achieving Full Promise of Digital Health Records, and to prevent harm through faulty health history information. The report is oriented towards healthcare provider issues. When they did ask patients what they wanted it was consistently shown that patients want all of the purported benefit of matching, but with no loss of privacy. They also found that Republican voters tended to favor less government involvement in the process.		*[https://www.pewtrusts.org/-/media/assets/2018/09/healthit_enhancedpatientmatching_report_final.pdf Pew research reports] that Enhanced Patient Matching Is Critical to Achieving Full Promise of Digital Health Records, and to prevent harm through faulty health history information. The report is oriented towards healthcare provider issues. When they did ask patients what they wanted it was consistently shown that patients want all of the purported benefit of matching, but with no loss of privacy. They also found that Republican voters tended to favor less government involvement in the process.
	# System oriented solution needs unique patient identifiers - but what they really mean is mandatory patient IDs for life.		# System oriented solution needs unique patient identifiers - but what they really mean is mandatory patient IDs for life.