Patient Web Experience - Revision history

Tomjones: /* Problems */

2020-09-08T20:39:10Z

Problems

← Older revision		Revision as of 20:39, 8 September 2020
Line 24:		Line 24:
	* The users have no simple way to tell the smartphone which apps are actually critical to their safety and well-being so that these apps can be given priority whenever the user really needs them to work on the user's behalf.		* The users have no simple way to tell the smartphone which apps are actually critical to their safety and well-being so that these apps can be given priority whenever the user really needs them to work on the user's behalf.
	* At some level they grant a small amount of effort to assure [[Usable Req 7\|Accessibility]] for users with some physical impairment, but there has been little attention given to the long term use of patient identifiers and devices.		* At some level they grant a small amount of effort to assure [[Usable Req 7\|Accessibility]] for users with some physical impairment, but there has been little attention given to the long term use of patient identifiers and devices.
	* The smartphone development environment even uses the language of intention to describe the choices it makes on behalf of the user as to the specific piece of code to invoke to achieve those ~~intensions~~.		* The smartphone development environment even uses the language of intention to describe the choices it makes on behalf of the user as to the specific piece of code to invoke to achieve those intentions.
	* The browser and the web apps do not currently provide access to a key store and if they did, that the keys in the store would become available to all javascript ~~down loaded~~ from a web site.		* The browser and the web apps do not currently provide access to a key store and if they did, that the keys in the store would become available to all javascript downloaded from a web site.
			===Access to Telemedicine===
			* [https://www.wired.com/story/access-telemedicine-is-hardest-those-who-need-it-most/?bxid=5c5b250d24c17c67f8640083&cndid=45183233&esrc=AUTO_PRINT&source=EDT_WIR_NEWSLETTER_0_DAILY_ZZ Access to Telemedicine Is Hardest for Those Who Need It Most]
			* Older patients and other vulnerable populations tend to need more medical care, but it’s often difficult for them to get online for remote visits.

	==Solutions==		==Solutions==

Tomjones: /* The User Imperative */

2020-09-08T20:18:42Z

The User Imperative

← Older revision		Revision as of 20:18, 8 September 2020
Line 3:		Line 3:

	===The User Imperative===		===The User Imperative===
	The web must be available for all healthcare patients; not just those with the latest whizzbang phone.		# The web must be available for all healthcare patients; not just those with the latest whizzbang phone.
			# The Patient view of portability is that healthcare services are available when and where the patient needs them.
	Patient view of portability.

	===Success Metrics===		===Success Metrics===

Tomjones: /* The User Imperative */

2020-09-08T17:16:40Z

The User Imperative

← Older revision		Revision as of 17:16, 8 September 2020
Line 4:		Line 4:
	===The User Imperative===		===The User Imperative===
	The web must be available for all healthcare patients; not just those with the latest whizzbang phone.		The web must be available for all healthcare patients; not just those with the latest whizzbang phone.

			Patient view of portability.

	===Success Metrics===		===Success Metrics===

Tomjones at 23:06, 6 September 2020

2020-09-06T23:06:04Z

← Older revision		Revision as of 23:06, 6 September 2020
Line 34:		Line 34:

	For healthcare apps it has been proposed to required [[Software Compliance Attestation]] before any PHI is release to the patient.		For healthcare apps it has been proposed to required [[Software Compliance Attestation]] before any PHI is release to the patient.

			===Reach out the the Blink-Dev teams===
			The browser developers ask for use cases that they can test their new features. That requires resources to rnteract with that team. Funding would be required to make this work.

	===Proposed Tests of the Patient Web Experience===		===Proposed Tests of the Patient Web Experience===

Tomjones: /* Proposed Tests of the Patient Web Experience */

2020-09-06T22:58:47Z

Proposed Tests of the Patient Web Experience

← Older revision		Revision as of 22:58, 6 September 2020
Line 42:		Line 42:
	# Test the performance of the app on the earliest supported version of a smart phone from each os.		# Test the performance of the app on the earliest supported version of a smart phone from each os.
	# Load the native browser on the test smartphone with at least 3 complex web sites (perhaps crafted just for the purpose). And retest the performance of the app.		# Load the native browser on the test smartphone with at least 3 complex web sites (perhaps crafted just for the purpose). And retest the performance of the app.
	# Run user ~~test~~ of the app with a diverse population of users with their existing smartphones.		# Run user tests of the app with a diverse population of users with their existing smartphones.

	==References==		==References==

Tomjones: /* Trusted Native Apps */

2020-09-06T22:58:05Z

Trusted Native Apps

← Older revision		Revision as of 22:58, 6 September 2020
Line 31:		Line 31:
	* For web sites to know that the code is validated the code needs the capability to report on its own provenance. See the wiki page on [[Native Apps for US Healthcare]]'		* For web sites to know that the code is validated the code needs the capability to report on its own provenance. See the wiki page on [[Native Apps for US Healthcare]]'
	===Trusted Native Apps===		===Trusted Native Apps===
	A variety of methods have been proposed to signal trust if apps provided to users, for example trust~~-marks~~.		A variety of methods have been proposed to signal trust if apps provided to users, for example see the wiki page [[Trustmark]]s. There is [https://tcwiki.azurewebsites.net/index.php?title=Privacy#User_and_Web_Site_Acceptance_for_Privacy_Seals ample evidence] that trust wrks do not provide the intend indication of trust to the user. So some more active proposal is required.

			For healthcare apps it has been proposed to required [[Software Compliance Attestation]] before any PHI is release to the patient.

	===Proposed Tests of the Patient Web Experience===		===Proposed Tests of the Patient Web Experience===
	# Create a Service Acceptance Criteria (SAC) and test any app (native or web) that wants to access Patient Health Information (PHI) from an Electronic Health Record (EHR).		# Create a Service Acceptance Criteria (SAC) and test any app (native or web) that wants to access Patient Health Information (PHI) from an Electronic Health Record (EHR).

Tomjones: /* Proposed Tests of the Patient Web Experience */

2020-09-06T22:44:18Z

Proposed Tests of the Patient Web Experience

← Older revision		Revision as of 22:44, 6 September 2020
Line 39:		Line 39:
	# Test the performance of the app on the earliest supported version of a smart phone from each os.		# Test the performance of the app on the earliest supported version of a smart phone from each os.
	# Load the native browser on the test smartphone with at least 3 complex web sites (perhaps crafted just for the purpose). And retest the performance of the app.		# Load the native browser on the test smartphone with at least 3 complex web sites (perhaps crafted just for the purpose). And retest the performance of the app.
			# Run user test of the app with a diverse population of users with their existing smartphones.

	==References==		==References==

Tomjones: /* Proposed Tests of the Patient Web Experience */

2020-09-06T22:42:45Z

Proposed Tests of the Patient Web Experience

← Older revision		Revision as of 22:42, 6 September 2020
Line 37:		Line 37:
	# Ensure that part fo the EHR criteria is to validate the MAAS before releasing PHI to an app.		# Ensure that part fo the EHR criteria is to validate the MAAS before releasing PHI to an app.
	# Validate the user experience of the Mobile App		# Validate the user experience of the Mobile App
	$ Test the performance of the app on the earliest supported version of a smart phone from each os.		# Test the performance of the app on the earliest supported version of a smart phone from each os.
	# Load the native browser on the smartphone with at least 3 complex web sites (perhaps crafted just for the purpose). And retest the performance of the app.		# Load the native browser on the test smartphone with at least 3 complex web sites (perhaps crafted just for the purpose). And retest the performance of the app.

	==References==		==References==

Tomjones: /* Proposed Tests of the Patient Web Experience */

2020-09-06T22:42:11Z

Proposed Tests of the Patient Web Experience

← Older revision		Revision as of 22:42, 6 September 2020
Line 33:		Line 33:
	A variety of methods have been proposed to signal trust if apps provided to users, for example trust-marks.		A variety of methods have been proposed to signal trust if apps provided to users, for example trust-marks.
	===Proposed Tests of the Patient Web Experience===		===Proposed Tests of the Patient Web Experience===
			# Create a Service Acceptance Criteria (SAC) and test any app (native or web) that wants to access Patient Health Information (PHI) from an Electronic Health Record (EHR).
			# Provide any certified app with a Mobile Authentication Assurance Statement (MAAS).
			# Ensure that part fo the EHR criteria is to validate the MAAS before releasing PHI to an app.
			# Validate the user experience of the Mobile App
			$ Test the performance of the app on the earliest supported version of a smart phone from each os.
			# Load the native browser on the smartphone with at least 3 complex web sites (perhaps crafted just for the purpose). And retest the performance of the app.

	==References==		==References==

Tomjones: /* Full Title or Meme */

2020-09-06T21:14:05Z

Full Title or Meme

← Older revision		Revision as of 21:14, 6 September 2020
Line 1:		Line 1:
	==Full Title or Meme==		==Full Title or Meme==
	The [[Patient Web Experience]] needs to be created in such a way that improves long-term patient out-comes for the entire duration of their life.		The [[Patient Web Experience]] needs to be created in such a way that improves long-term patient out-comes for the entire duration of their life.

			===The User Imperative===
			The web must be available for all healthcare patients; not just those with the latest whizzbang phone.

	===Success Metrics===		===Success Metrics===