Patient with Lab and Referral Use Case - Revision history

Tomjones: /* Scenarios */

2019-05-03T17:21:30Z

Scenarios

← Older revision		Revision as of 17:21, 3 May 2019
Line 31:		Line 31:

	Primary Scenario:		Primary Scenario:
	#Patient schedules an appointment with primary care physician and is authenticated at the front desk. (This might involve re-affirmation of the consent with the practice.)		#Patient schedules an appointment with primary care physician (PCP) and is authenticated at the front desk. (This might involve re-affirmation of the consent with the practice.)
	#Patient sees the doctor, is reauthenticated (this reauth will be less onerous than that at the front desk) and explains symptoms.		#Patient sees the doctor, is reauthenticated (this reauth will be less onerous than that at the front desk) and explains symptoms.
	#Doctor schedules a lab test for a sensitive condition (for example sexually transmitted disease) in order to test patient consent to share such information with referral.		#Doctor schedules a lab test for a sensitive condition (for example sexually transmitted disease) in order to test patient consent to share such information with referral.
Line 45:		Line 45:

	Alternate Scenario:		Alternate Scenario:
	#The patient can sign onto the various practices' web sites and preform the actions from the comfort of her living room. In this case electronic consents are appropriate.		# The patient can sign onto the various practices' web sites and preform the actions from the comfort of her living room. In this case electronic consents are appropriate.
	# In this case the consent reciepts will be renderable to the user in understandable user experience.		# In this case the consent reciepts will be renderable to the user in understandable user experience.

			Alternate Scenario:
			# In the above scenario the lab delivers the patient results to the PCP for inclusion in their EHR, in some cases the patient will contract directly with the lab which will maintain an EHR for the patient.
			# In this scenario the patient needs to explicitly request the data be transfer to the PCP, or transfer it to the PCP themselves.

	==Results==		==Results==

Tomjones: /* Scenarios */

2019-02-05T17:47:19Z

Scenarios

← Older revision		Revision as of 17:47, 5 February 2019
Line 46:		Line 46:
	Alternate Scenario:		Alternate Scenario:
	#The patient can sign onto the various practices' web sites and preform the actions from the comfort of her living room. In this case electronic consents are appropriate.		#The patient can sign onto the various practices' web sites and preform the actions from the comfort of her living room. In this case electronic consents are appropriate.
			# In this case the consent reciepts will be renderable to the user in understandable user experience.

	==Results==		==Results==

Tomjones: /* Scenarios */

2019-02-05T17:44:31Z

Scenarios

← Older revision		Revision as of 17:44, 5 February 2019
Line 45:		Line 45:

	Alternate Scenario:		Alternate Scenario:
	#The patient can sign onto the various practices' web sites and preform the actions from the comfort of her living room.		#The patient can sign onto the various practices' web sites and preform the actions from the comfort of her living room. In this case electronic consents are appropriate.

	==Results==		==Results==

Tomjones: /* Preconditions */

2019-02-05T17:38:42Z

Preconditions

← Older revision		Revision as of 17:38, 5 February 2019
Line 23:		Line 23:
	# Different providers are unlikely to allow each other, or the patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient 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 patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient will have multiple repositories, each with their own [https://tcwiki.azurewebsites.net/index.php?title=Medical_Records_Identifier Medical Records Identifier].
	# Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants. The patient always has the right to revoke consent		# Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants. The patient always has the right to revoke consent
	# The patient has the right to eliminate some individuals in a practice from seeing their data.		# The patient has the right to eliminate some individuals in a practice from seeing their data even when the practice has access.

	An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.		An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.

Tomjones: /* Preconditions */

2019-02-05T17:38:00Z

Preconditions

← Older revision		Revision as of 17:38, 5 February 2019
Line 23:		Line 23:
	# Different providers are unlikely to allow each other, or the patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient 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 patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient will have multiple repositories, each with their own [https://tcwiki.azurewebsites.net/index.php?title=Medical_Records_Identifier Medical Records Identifier].
	# Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants. The patient always has the right to revoke consent		# Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants. The patient always has the right to revoke consent
			# The patient has the right to eliminate some individuals in a practice from seeing their data.

	An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.		An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.

Tomjones: /* Preconditions */

2019-02-05T17:35:50Z

Preconditions

← Older revision		Revision as of 17:35, 5 February 2019
Line 22:		Line 22:
	# The providers of health care and lab services present the patient 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 patient 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 patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient 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 patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient will have multiple repositories, each with their own [https://tcwiki.azurewebsites.net/index.php?title=Medical_Records_Identifier Medical Records Identifier].
	# Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants.		# Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants. The patient always has the right to revoke consent

	An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.		An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.

Tomjones: /* Preconditions */

2019-02-05T17:34:27Z

Preconditions

← Older revision		Revision as of 17:34, 5 February 2019
Line 22:		Line 22:
	# The providers of health care and lab services present the patient 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 patient 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 patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient 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 patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient will have multiple repositories, each with their own [https://tcwiki.azurewebsites.net/index.php?title=Medical_Records_Identifier Medical Records Identifier].
	# Patient can always get their own data, but only after strong authentication		# Patient can always get their own data, but only after strong authentication. This data will include a list of existing consent grants.

	An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.		An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.

Tomjones: /* Results */

2019-02-05T17:32:26Z

Results

← Older revision		Revision as of 17:32, 5 February 2019
Line 52:		Line 52:
	Post Condition:		Post Condition:
	#There are now two additional consents steps, lab with sensitive data and secondary provider with sensitive.		#There are now two additional consents steps, lab with sensitive data and secondary provider with sensitive.
			#No data is ever shared with any provider that has not been strongly identified to the patient.
	#The patient results are available it is assumed that the consent receipt acknowledged that the data would be sent back to the primary care doctor.		#The patient results are available it is assumed that the consent receipt acknowledged that the data would be sent back to the primary care doctor.

Tomjones: /* Results */

2019-02-05T17:30:23Z

Results

← Older revision		Revision as of 17:30, 5 February 2019
Line 51:		Line 51:

	Post Condition:		Post Condition:
			#There are now two additional consents steps, lab with sensitive data and secondary provider with sensitive.
	#The patient results are available it is assumed that the consent receipt acknowledged that the data would be sent back to the primary care doctor.		#The patient results are available it is assumed that the consent receipt acknowledged that the data would be sent back to the primary care doctor.

Tomjones: /* Preconditions */

2019-02-05T17:28:51Z

Preconditions

← Older revision		Revision as of 17:28, 5 February 2019
Line 22:		Line 22:
	# The providers of health care and lab services present the patient 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 patient 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 patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient 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 patient, to write into their [https://tcwiki.azurewebsites.net/index.php?title=EHR EHR], so it is expected that the patient will have multiple repositories, each with their own [https://tcwiki.azurewebsites.net/index.php?title=Medical_Records_Identifier Medical Records Identifier].
			# Patient can always get their own data, but only after strong authentication

	An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.		An optional condition would be for the patient to have a trusted identity in cyberspace that can be used to access their health records at any of their care providers.