Patient Registration with Distributed Attributes - Revision history

Tomjones: /* References */

2020-04-27T19:21:42Z

References

← Older revision		Revision as of 19:21, 27 April 2020
Line 100:		Line 100:

	==References==		==References==
			* [https://kantarainitiative.org/confluence/display/WT/Draft+Recommendations Distributed Identifier Assurance Specification]
	* The wiki page [[User Choice Pattern]] describes some of the challenges of user choice and the choice paradox.		* The wiki page [[User Choice Pattern]] describes some of the challenges of user choice and the choice paradox.
	* The wiki page [[Patient with Lab and Referral Use Case]] discusses subsequent visits with referral to outside providers.		* The wiki page [[Patient with Lab and Referral Use Case]] discusses subsequent visits with referral to outside providers.

Tomjones: /* Goal */

2020-03-20T00:48:24Z

Goal

← Older revision		Revision as of 00:48, 20 March 2020
Line 11:		Line 11:
	# Consent experience that gives the patient rightful ownership of their data and where it is to be shared.		# Consent experience that gives the patient rightful ownership of their data and where it is to be shared.
	# Collection of Attributes that can be validated by a health care provider to validate the patient.		# Collection of Attributes that can be validated by a health care provider to validate the patient.
	## This may be extended in the future to patient provided medical ~~record locators~~ for EHR data.		## This may be extended in the future to patient provided medical [[Record Locator Service]] for EHR data.
	* Out of scope are support for guardians that can legitimately address patient data or other providers, like lab services, that may use the same or different EHRs.		* Out of scope are support for guardians that can legitimately address patient data or other providers, like lab services, that may use the same or different EHRs.

Tomjones: /* Scenarios */

2019-09-28T23:36:15Z

Scenarios

← Older revision		Revision as of 23:36, 28 September 2019
Line 68:		Line 68:
	##Electronic consents are appropriate whenever additional consent is granted by the patient. Any consent receipts will be renderable to the user in plain language that they can understand.		##Electronic consents are appropriate whenever additional consent is granted by the patient. Any consent receipts will be renderable to the user in plain language that they can understand.
	##All sites that display patient data requires strong authentication of the patient and compliant protections of user information.		##All sites that display patient data requires strong authentication of the patient and compliant protections of user information.
	Following is one example of an online registration ceremony.		Following is one example of an online registration ceremony that has worked in the past to provide identity proofing of a patient at a web site.
	[[File:RegistrationCeremony.png]]		[[File:RegistrationCeremony.png]]

Tomjones: /* Scenarios */

2019-09-28T23:30:56Z

Scenarios

← Older revision		Revision as of 23:30, 28 September 2019
Line 60:		Line 60:
	#The provider may create diagnoses, health care plans, prescriptions or refer the patient to other providers during the visit.		#The provider may create diagnoses, health care plans, prescriptions or refer the patient to other providers during the visit.
	#At check-out additional actions, like payments or paperwork is provided. Re-authentication would apply at this step as needed by privacy concerns.		#At check-out additional actions, like payments or paperwork is provided. Re-authentication would apply at this step as needed by privacy concerns.
	# For new patients, the patient is given, or is mailed a form the the following pieces of information that can be used to establish an online presence.		# For new patients, the patient is given, or is mailed, a form the the following pieces of information that can be used to establish an online presence.
	## A URL to the patient chart on the web. This is the site of the EHR, which may, or may not, be the same as the provider, such as would be the case for a conglomerate of several providers.		## A URL to the patient chart on the web. This is the site of the EHR, which may, or may not, be the same as the provider, such as would be the case for a conglomerate of several providers.
	## An access code that allows them to create an identity proofed sign-in capability at the provider.		## An access code that allows them to create an identity proofed sign-in capability at the provider.
	Alternate Scenario:		Alternate Scenario:
			#Before accessing the EHR the patient will need to follow the instructions on the form provided above.
	#The patient can sign onto the various practices' web sites and perform the actions from the comfort of her living room.		#The patient can sign onto the various practices' web sites and perform the actions from the comfort of her living room.
	##Electronic consents are appropriate whenever additional consent is granted by the patient. Any consent receipts will be renderable to the user in plain language that they can understand.		##Electronic consents are appropriate whenever additional consent is granted by the patient. Any consent receipts will be renderable to the user in plain language that they can understand.
	##All sites that display patient data requires strong authentication of the patient and compliant protections of user information.		##All sites that display patient data requires strong authentication of the patient and compliant protections of user information.
			Following is one example of an online registration ceremony.
			[[File:RegistrationCeremony.png]]

	==Results==		==Results==

Tomjones: /* Scenarios */

2019-09-28T23:28:27Z

Scenarios

← Older revision		Revision as of 23:28, 28 September 2019
Line 60:		Line 60:
	#The provider may create diagnoses, health care plans, prescriptions or refer the patient to other providers during the visit.		#The provider may create diagnoses, health care plans, prescriptions or refer the patient to other providers during the visit.
	#At check-out additional actions, like payments or paperwork is provided. Re-authentication would apply at this step as needed by privacy concerns.		#At check-out additional actions, like payments or paperwork is provided. Re-authentication would apply at this step as needed by privacy concerns.
			# For new patients, the patient is given, or is mailed a form the the following pieces of information that can be used to establish an online presence.
			## A URL to the patient chart on the web. This is the site of the EHR, which may, or may not, be the same as the provider, such as would be the case for a conglomerate of several providers.
			## An access code that allows them to create an identity proofed sign-in capability at the provider.
	Alternate Scenario:		Alternate Scenario:
	#The patient can sign onto the various practices' web sites and perform the actions from the comfort of her living room.		#The patient can sign onto the various practices' web sites and perform the actions from the comfort of her living room.

Tomjones: /* Preconditions */

2019-09-28T23:02:16Z

Preconditions

← Older revision		Revision as of 23:02, 28 September 2019
Line 31:		Line 31:
	# The patient has self-selected to become "known to the practice" where general health care is provided.		# The patient has self-selected to become "known to the practice" where general health care is provided.
	# A trust registry of providers exists (based on [https://tcwiki.azurewebsites.net/index.php?title=TEFCA TEFCA]) which the patient knows and trusts.		# A trust registry of providers exists (based on [https://tcwiki.azurewebsites.net/index.php?title=TEFCA TEFCA]) which the patient knows and trusts.
	# ~~The~~ private care provider (PCP) presents the patient with a [[Entity Statement]] which confirms that they subscribe to the privacy regulations of [https://tcwiki.azurewebsites.net/index.php?title=TEFCA TEFCA] and other appropriate regulations.		# When accessed online, the private care provider (PCP) presents the user agent of the patient with a [[Entity Statement]] which confirms that they subscribe to the privacy regulations of [https://tcwiki.azurewebsites.net/index.php?title=TEFCA TEFCA] and other appropriate regulations to assure the patient that their health care data can be safely stored and accessed at their web site.
	# The PCP give the patient a list of documents to bring with them before the first appointment with the provider in order to initiate the creation of the EHR; for example:		# The PCP give the patient a list of documents to bring with them before the first appointment with the provider in order to initiate the creation of the EHR; for example:
	## Health Insurance card		## Health Insurance card

Tomjones: /* Context */

2019-05-01T01:30:28Z

Context

← Older revision		Revision as of 01:30, 1 May 2019
Line 3:		Line 3:

	==Context==		==Context==
	*To provide good assurance that a patient data records are as accurate as possible and relate to the real live person requesting services.		*To provide good assurance that a patient's data records are as accurate as possible and relate to the real live person requesting services.

	===Goal===		===Goal===

Tomjones: /* Context */

2019-04-30T22:51:43Z

Context

← Older revision		Revision as of 22:51, 30 April 2019
Line 3:		Line 3:

	==Context==		==Context==
	*To provide good assurance that a patient data records are as accurate as possible and relate to a real live person.		*To provide good assurance that a patient data records are as accurate as possible and relate to the real live person requesting services.

	===Goal===		===Goal===

Tomjones at 22:45, 30 April 2019

2019-04-30T22:45:34Z

← Older revision		Revision as of 22:45, 30 April 2019
Line 18:		Line 18:
	#The Provider of patient's general health care (the private care provider - PCP) that is creating the EHR which they control for its own and the patient's future reference.		#The Provider of patient's general health care (the private care provider - PCP) that is creating the EHR which they control for its own and the patient's future reference.
	#Digital Identifier or Attribute providers acting the some of the following roles:		#Digital Identifier or Attribute providers acting the some of the following roles:
	##Risk assessment evaluation which may be any insurance or financial provider		##Risk assessment evaluation which may be any insurance or financial provider,
	##Medical Records at some Qualified Health Information Network (QHIN) web site.		##Medical Records at some Qualified Health Information Network (QHIN) web site, (See appendix 3 of the of [https://tcwiki.azurewebsites.net/index.php?title=TEFCA TEFCA] spec for details on QHIN.)
	##Identity Authentication Provider to evaluate the rights and accuracy of the patient's link to any particular medical records		##Identity Authentication Provider to evaluate the rights and accuracy of the patient's link to any particular medical records,
	##Medical providers for consultation or referral. Specifically providers outside of the PCP that might need data interchange agreements.		##Medical providers for consultation or referral. Specifically providers outside of the PCP that might need data interchange agreements.

Tomjones: /* Results */

2019-04-30T22:33:27Z

Results

← Older revision		Revision as of 22:33, 30 April 2019
Line 88:		Line 88:
	#Standards (like TEFCA) exist to collect needed attributes where-ever they may be.		#Standards (like TEFCA) exist to collect needed attributes where-ever they may be.
	#Connections to related providers for financial settlements will need to be enabled. In many cases these will have patient private information that needs protection.		#Connections to related providers for financial settlements will need to be enabled. In many cases these will have patient private information that needs protection.
	#Most PCPs will depend on IT support from third party providers. It must be clear to the patient in all cases who holds their data (a data processor) and who controls their data (a PCP or data controller) and where the patient goes for redress. This is not true as of (2019-04-29).		#Most PCPs will depend on IT support from third party providers. It must be clear to the patient in all cases who holds their data (a data processor) and who controls their data (a PCP or data controller) and where the patient goes for redress. This is not generally true as of (2019-04-29).

	==Workflow Diagram==		==Workflow Diagram==