Emergency Contact Information Use Case - Revision history

Tomjones: /* Results */

2019-12-04T20:08:22Z

Results

← Older revision		Revision as of 20:08, 4 December 2019
Line 72:		Line 72:
	#No data is ever shared with any provider that has not been strongly identified to FirstNet (which would include emergency rooms).		#No data is ever shared with any provider that has not been strongly identified to FirstNet (which would include emergency rooms).
	#The user results are available it is assumed that the consent receipt acknowledged that the access information would be sent back to the primary care doctor as well as to the user for later reference.		#The user results are available it is assumed that the consent receipt acknowledged that the access information would be sent back to the primary care doctor as well as to the user for later reference.
	# Access by the emergency medical technician or physician is covered by sovereign immunity and not privacy law.		# Access by the emergency medical technician or physician is covered by sovereign immunity and not privacy law. (Break-the-glass access.)
	Examples:		Examples:
	#In operation whenever a user's EHR is accessed by "breaking the glass" that protects the user data, the user will be notified of the access.		#In operation whenever a user's EHR is accessed by "breaking the glass" that protects the user data, the user will be notified of the access.

Tomjones: /* Results */

2019-12-04T18:38:08Z

Results

← Older revision		Revision as of 18:38, 4 December 2019
Line 72:		Line 72:
	#No data is ever shared with any provider that has not been strongly identified to FirstNet (which would include emergency rooms).		#No data is ever shared with any provider that has not been strongly identified to FirstNet (which would include emergency rooms).
	#The user results are available it is assumed that the consent receipt acknowledged that the access information would be sent back to the primary care doctor as well as to the user for later reference.		#The user results are available it is assumed that the consent receipt acknowledged that the access information would be sent back to the primary care doctor as well as to the user for later reference.
	* Access by the emergency medical technician or physician is covered by sovereign immunity and not privacy law.		# Access by the emergency medical technician or physician is covered by sovereign immunity and not privacy law.
	Examples:		Examples:
	#In operation whenever a user's EHR is accessed by "breaking the glass" that protects the user data, the user will be notified of the access.		#In operation whenever a user's EHR is accessed by "breaking the glass" that protects the user data, the user will be notified of the access.

Tomjones: /* Results */

2019-12-04T18:37:48Z

Results

← Older revision		Revision as of 18:37, 4 December 2019
Line 70:		Line 70:
	Post Condition:		Post Condition:
	#There are now two additional consent steps, both of which provide a consent receipt to the user.		#There are now two additional consent steps, both of which provide a consent receipt to the user.
	#No data is ever shared with any provider that has not been strongly identified to FirstNet.		#No data is ever shared with any provider that has not been strongly identified to FirstNet (which would include emergency rooms).
	#The user results are available it is assumed that the consent receipt acknowledged that the access information would be sent back to the primary care doctor as well as to the user for later reference.		#The user results are available it is assumed that the consent receipt acknowledged that the access information would be sent back to the primary care doctor as well as to the user for later reference.
			* Access by the emergency medical technician or physician is covered by sovereign immunity and not privacy law.
	Examples:		Examples:
	#In operation whenever a user's EHR is accessed by "breaking the glass" that protects the user data, the user will be notified of the access.		#In operation whenever a user's EHR is accessed by "breaking the glass" that protects the user data, the user will be notified of the access.

Tomjones: /* Context */

2019-09-19T21:15:01Z

Context

← Older revision		Revision as of 21:15, 19 September 2019
Line 5:		Line 5:
	* To provide good assurance that a user contact data is kept as private as possible consistent with emergency access.		* To provide good assurance that a user contact data is kept as private as possible consistent with emergency access.
	* First responder or other emergency access of patient health information (PHI) in an Electronic Health Repository (EHR) is call a "brake-the-glass" emergency in the sense of the common fire alarm or heart defibrillator in the hallway that cannot be used without some destructive act, like breaking a glass seal, that can clearly be seen and heard and cannot be repaired by the perpetrator.		* First responder or other emergency access of patient health information (PHI) in an Electronic Health Repository (EHR) is call a "brake-the-glass" emergency in the sense of the common fire alarm or heart defibrillator in the hallway that cannot be used without some destructive act, like breaking a glass seal, that can clearly be seen and heard and cannot be repaired by the perpetrator.
			* This use can can easily be extended to other sources of user-provided information, but it is likely that the solution would not change much.

	===Goal===		===Goal===
	* The user has full capability to exercise their right to participate in the selecting the people that are notified in an emergency.		* The user has full capability to exercise their right to participate in the selecting the people that are notified in an emergency.

Tomjones: /* Results */

2019-09-19T19:50:08Z

Results

← Older revision		Revision as of 19:50, 19 September 2019
Line 73:		Line 73:
	Examples:		Examples:
	#In operation whenever a user's EHR is accessed by "breaking the glass" that protects the user data, the user will be notified of the access.		#In operation whenever a user's EHR is accessed by "breaking the glass" that protects the user data, the user will be notified of the access.
			#A reasonable extension of this use case is for all people on the emergency contact list getting notification whenever emergency access is requested.

	Dependencies::		Dependencies::

Tomjones: /* Context */

2019-09-19T19:48:00Z

Context

← Older revision		Revision as of 19:48, 19 September 2019
Line 4:		Line 4:
	==Context==		==Context==
	* To provide good assurance that a user contact data is kept as private as possible consistent with emergency access.		* To provide good assurance that a user contact data is kept as private as possible consistent with emergency access.
	* First responder or other emergency access of patient health information (PHI) in an Electronic Health Repository (EHR) is call a "brake-the-glass" emergency in the sense of the common fire alarm or heart defibrillator in the hallway that cannot be used without some destructive act, like breaking a glass seal, that can clearly be seen and heard.		* First responder or other emergency access of patient health information (PHI) in an Electronic Health Repository (EHR) is call a "brake-the-glass" emergency in the sense of the common fire alarm or heart defibrillator in the hallway that cannot be used without some destructive act, like breaking a glass seal, that can clearly be seen and heard and cannot be repaired by the perpetrator.
	===Goal===		===Goal===
	* The user has full capability to exercise their right to participate in the selecting the people that are notified in an emergency.		* The user has full capability to exercise their right to participate in the selecting the people that are notified in an emergency.

Tomjones: /* Results */

2019-09-19T19:46:37Z

Results

← Older revision		Revision as of 19:46, 19 September 2019
Line 72:		Line 72:

	Examples:		Examples:
	#In operation whenever a user's EHR is accessed by		#In operation whenever a user's EHR is accessed by "breaking the glass" that protects the user data, the user will be notified of the access.

	Dependencies::		Dependencies::

Tomjones: /* Context */

2019-09-19T19:45:50Z

Context

← Older revision		Revision as of 19:45, 19 September 2019
Line 3:		Line 3:

	==Context==		==Context==
	To provide good assurance that a user contact data is kept as private as possible consistent with emergency access.		* To provide good assurance that a user contact data is kept as private as possible consistent with emergency access.
			* First responder or other emergency access of patient health information (PHI) in an Electronic Health Repository (EHR) is call a "brake-the-glass" emergency in the sense of the common fire alarm or heart defibrillator in the hallway that cannot be used without some destructive act, like breaking a glass seal, that can clearly be seen and heard.
	===Goal===		===Goal===
	* The user has full capability to exercise their right to participate in the selecting the people that are notified in an emergency.		* The user has full capability to exercise their right to participate in the selecting the people that are notified in an emergency.
	* ~~Extendibility~~ to provide access to user care stipulations that would help First Responders provide care.		* Extensibility to provide access to user care stipulations that would help First Responders provide care.
	* Provide the privacy and other considerations as described in the [[Health Care Profile]].		* Provide the privacy and other considerations as described in the [[Health Care Profile]].
	# Give the contact person ability to impact the record about their own data and availability as a contact.		# Give the contact person ability to impact the record about their own data and availability as a contact.

Tomjones: /* Results */

2019-09-19T19:41:20Z

Results

← Older revision		Revision as of 19:41, 19 September 2019
Line 67:		Line 67:

	Post Condition:		Post Condition:
	#There are now two additional consent steps,		#There are now two additional consent steps, both of which provide a consent receipt to the user.
	#No data is ever shared with any provider that has not been strongly identified to FirstNet.		#No data is ever shared with any provider that has not been strongly identified to FirstNet.
	#The user results are available it is assumed that the consent receipt acknowledged that the access information would be sent back to the primary care doctor as well as to the user for later reference.		#The user results are available it is assumed that the consent receipt acknowledged that the access information would be sent back to the primary care doctor as well as to the user for later reference.

	Examples:		Examples:
	#~~tbd~~		#In operation whenever a user's EHR is accessed by

	Dependencies::		Dependencies::

Tomjones: /* Preconditions */

2019-09-19T19:38:01Z

Preconditions

← Older revision		Revision as of 19:38, 19 September 2019
Line 28:		Line 28:
	==Preconditions==		==Preconditions==
	# The user has learned that it is possible to store their contact information which leads them to the site.		# The user has learned that it is possible to store their contact information which leads them to the site.
	# A trust registry exists which the user knows and trusts.		# A trust registry exists which the user knows and trusts to tell her whether any healthcare web site can be trusted with her data.
	# The providers of health care and lab services present the user with a trusted identity which confirms that they subscribe to the privacy regulations of the trust provider.		# The providers of health care and lab services present the user with a trusted identity which confirms that they subscribe to the privacy regulations of the trust provider.
	# Different providers are unlikely to allow each other, or the user, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the user will have multiple repositories, each with their own [https://tcwiki.azurewebsites.net/index.php?title=Medical_Records_Identifier Medical Records Identifier].		# Different providers are unlikely to allow each other, or the user, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the user will have multiple repositories, each with their own [https://tcwiki.azurewebsites.net/index.php?title=Medical_Records_Identifier Medical Records Identifier].
Line 34:		Line 34:
	# Contact has right to know that they are in an emergency contract list and can update their own contact information.		# Contact has right to know that they are in an emergency contract list and can update their own contact information.

	An optional condition would be for the user to have a trusted identity in cyberspace that can be directly targeted to provide needed information to the First Resonders.		An optional condition would be for the user to have a trusted (AAL2) identity in cyberspace that can be directly targeted to provide needed information to the First Resonders.

	==Scenarios / User Journeys==		==Scenarios / User Journeys==