Phase III IDEF Registry - Revision history

Tomjones: /* Technology Short Comings */

2019-04-16T16:34:06Z

Technology Short Comings

← Older revision		Revision as of 16:34, 16 April 2019
Line 40:		Line 40:
	There are at least two identity challenges that need to be resolved before secure communications can be undertaken with web sites that have important personal information like health or financial information:		There are at least two identity challenges that need to be resolved before secure communications can be undertaken with web sites that have important personal information like health or financial information:
	# The identity of the web site itself is seldom clear. Some sites have urls that are easy to recognize, but many do not and even those that do are subject to spoofing by sites that deliberately try to confuse the user, often with alphabets that are very close to the Latin one we are familiar with. What the user needs is clear indication of who is responsible for the web site in a way that is easy for them to understand.		# The identity of the web site itself is seldom clear. Some sites have urls that are easy to recognize, but many do not and even those that do are subject to spoofing by sites that deliberately try to confuse the user, often with alphabets that are very close to the Latin one we are familiar with. What the user needs is clear indication of who is responsible for the web site in a way that is easy for them to understand.
	# Documents that are delivered from health and financial sites very often is delivered by some site other that the one that created the information as is responsible for it. So it is important to package the information and display the owner of the information in a way that is easy for the user to understand. For example; in health care a variety of health care providers (primary care physician, lab) and data controllers (Epic, etc.) are involved in provisioning patient information. When data is displayed to the user, it is seldom clear where the data originated and who controls access to the data. These need to be clear if the patient is a exercise their right to ultimate control of the information.		# Documents that are delivered from health and financial sites very often is delivered by some site other that the one that created the information as is responsible for it. So it is important to package the information and display the owner of the information in a way that is easy for the user to understand. For example; in health care a variety of health care providers (primary care physician, lab) and data controllers (Epic, Cerner, AllScripts, etc.) are involved in provisioning patient information. When data is displayed to the user, it is seldom clear where the data originated and who controls access to the data. These need to be clear if the patient is a exercise their right to ultimate control of the information.
	Both of these issues are known and solutions are being explored. These use case are built with the understanding that these problems will be fixed in the near term.		Both of these issues are known and solutions are being explored. These use case are built with the understanding that these problems will be fixed in the near term.

Tomjones: /* Minuets of meetings */

2019-04-16T16:27:10Z

Minuets of meetings

← Older revision		Revision as of 16:27, 16 April 2019
Line 28:		Line 28:
	* Wiki page [[Privacy Profile]] is in development		* Wiki page [[Privacy Profile]] is in development

	===~~Minuets~~ of meetings===		===Minutes of meetings===
	* [https://docs.google.com/document/d/1tGTqhOSl4ZGsahfLPnx3D-xBkaok3oNe_0KnRXV1yQQ/edit?ts=5c34e445 Collected mins starting on 2018-01-08]		* [https://docs.google.com/document/d/1tGTqhOSl4ZGsahfLPnx3D-xBkaok3oNe_0KnRXV1yQQ/edit?ts=5c34e445 Collected mins starting on 2018-01-08]

Tomjones: /* Technology Short Comings */

2019-04-16T16:25:57Z

Technology Short Comings

← Older revision		Revision as of 16:25, 16 April 2019
Line 39:		Line 39:
	==Technology Short Comings==		==Technology Short Comings==
	There are at least two identity challenges that need to be resolved before secure communications can be undertaken with web sites that have important personal information like health or financial information:		There are at least two identity challenges that need to be resolved before secure communications can be undertaken with web sites that have important personal information like health or financial information:
	# The identity of the web site itself is seldom clear. Some sites have urls that are easy to ~~recognized~~, but many do not and even those that do are subject to spoofing by sites that deliberately try to confuse the user, often with alphabets that are very close to the Latin one we are familiar with. What the user needs is clear indication of who is responsible for the web site in a way that is easy for them to understand.		# The identity of the web site itself is seldom clear. Some sites have urls that are easy to recognize, but many do not and even those that do are subject to spoofing by sites that deliberately try to confuse the user, often with alphabets that are very close to the Latin one we are familiar with. What the user needs is clear indication of who is responsible for the web site in a way that is easy for them to understand.
	# Documents that are delivered from health and financial sites very often is delivered by some site other that the one that created the information as is responsible for it. So it is important to package the information and display the owner of the information in a way that is easy for the user to understand. For example; in health care a variety of health care providers (primary care physician, lab) and data controllers (Epic, etc.) are involved in provisioning patient information. When data is displayed to the user, it is seldom clear where the data originated and who controls access to the data. These need to be clear if the patient is a exercise their right to ultimate control of the information.		# Documents that are delivered from health and financial sites very often is delivered by some site other that the one that created the information as is responsible for it. So it is important to package the information and display the owner of the information in a way that is easy for the user to understand. For example; in health care a variety of health care providers (primary care physician, lab) and data controllers (Epic, etc.) are involved in provisioning patient information. When data is displayed to the user, it is seldom clear where the data originated and who controls access to the data. These need to be clear if the patient is a exercise their right to ultimate control of the information.
	Both of these issues are known and solutions are being explored. These use case are built with the understanding that these problems will be fixed in the near term.		Both of these issues are known and solutions are being explored. These use case are built with the understanding that these problems will be fixed in the near term.

Tomjones: /* Open Issues */

2019-04-16T15:45:55Z

Open Issues

← Older revision		Revision as of 15:45, 16 April 2019
Line 54:		Line 54:

	# There will be multiple identifier frameworks (aka methods or profiles) which have their own set of identity requirements.		# There will be multiple identifier frameworks (aka methods or profiles) which have their own set of identity requirements.
	# ~~our~~ focus will be on the frameworks will be IDEF compliant.		# Our focus will be on the frameworks will be IDEF compliant.
	# All IDEF compliant frameworks will provide a machine-readable method to determine if a web site is a member of the framework		# All IDEF compliant frameworks will provide a machine-readable method to determine if a web site is a member of the framework
	# Especially at the start, most frameworks will not be IDEF compliant.		# Especially at the start, most frameworks will not be IDEF compliant.

Tomjones: /* Open Issues */

2019-04-16T15:45:37Z

Open Issues

← Older revision		Revision as of 15:45, 16 April 2019
Line 54:		Line 54:

	# There will be multiple identifier frameworks (aka methods or profiles) which have their own set of identity requirements.		# There will be multiple identifier frameworks (aka methods or profiles) which have their own set of identity requirements.
	# ~~Some of~~ the frameworks will be IDEF compliant.		# our focus will be on the frameworks will be IDEF compliant.
	# All IDEF compliant frameworks will provide a machine-readable method to determine if a web site is a member of the framework		# All IDEF compliant frameworks will provide a machine-readable method to determine if a web site is a member of the framework
	# Especially at the start, most frameworks will not be IDEF compliant.		# Especially at the start, most frameworks will not be IDEF compliant.

Tomjones: /* Use Cases */

2019-04-16T15:44:10Z

Use Cases

← Older revision		Revision as of 15:44, 16 April 2019
Line 20:		Line 20:

	===Use Cases===		===Use Cases===
			*[[Emergency Contact Information Use Case]]
	* [[Patient with Lab and Referral Use Case]]		* [[Patient with Lab and Referral Use Case]]
	* [https://docs.google.com/document/d/1taCE6I8tcx5zLQ9PYcDfk6ThB3WlcISIMBfIhKKC_Bg/edit Over 21 claim]		* [https://docs.google.com/document/d/1taCE6I8tcx5zLQ9PYcDfk6ThB3WlcISIMBfIhKKC_Bg/edit Over 21 claim]

Tomjones: /* Open Issues */

2019-04-15T17:55:15Z

Open Issues

← Older revision		Revision as of 17:55, 15 April 2019
Line 54:		Line 54:
	# There will be multiple identifier frameworks (aka methods or profiles) which have their own set of identity requirements.		# There will be multiple identifier frameworks (aka methods or profiles) which have their own set of identity requirements.
	# Some of the frameworks will be IDEF compliant.		# Some of the frameworks will be IDEF compliant.
	# All ~~IDESG~~ compliant frameworks will provide a machine-readable method to determine if a web site is a member of the framework		# All IDEF compliant frameworks will provide a machine-readable method to determine if a web site is a member of the framework
	# Especially at the start, most frameworks will not be IDEF compliant.		# Especially at the start, most frameworks will not be IDEF compliant.
	# How should an IDEF compliant entity deal with identifiers that are:		# How should an IDEF compliant entity deal with identifiers that are:

Tomjones: /* Updates completed in Phase II */

2019-04-15T16:55:02Z

Updates completed in Phase II

← Older revision		Revision as of 16:55, 15 April 2019
Line 36:		Line 36:
	* Security [[file:Secure_Requirements_Update.docx]]		* Security [[file:Secure_Requirements_Update.docx]]
	* Usable [[file:Usable_Requirments_Update.docx]]		* Usable [[file:Usable_Requirments_Update.docx]]
			==Technology Short Comings==
			There are at least two identity challenges that need to be resolved before secure communications can be undertaken with web sites that have important personal information like health or financial information:
			# The identity of the web site itself is seldom clear. Some sites have urls that are easy to recognized, but many do not and even those that do are subject to spoofing by sites that deliberately try to confuse the user, often with alphabets that are very close to the Latin one we are familiar with. What the user needs is clear indication of who is responsible for the web site in a way that is easy for them to understand.
			# Documents that are delivered from health and financial sites very often is delivered by some site other that the one that created the information as is responsible for it. So it is important to package the information and display the owner of the information in a way that is easy for the user to understand. For example; in health care a variety of health care providers (primary care physician, lab) and data controllers (Epic, etc.) are involved in provisioning patient information. When data is displayed to the user, it is seldom clear where the data originated and who controls access to the data. These need to be clear if the patient is a exercise their right to ultimate control of the information.
			Both of these issues are known and solutions are being explored. These use case are built with the understanding that these problems will be fixed in the near term.

	==Work Product==		==Work Product==

Tomjones: /* Requirements Documents */

2019-04-15T16:49:05Z

Requirements Documents

← Older revision		Revision as of 16:49, 15 April 2019
Line 15:		Line 15:

	*[https://tcwiki.azurewebsites.net/index.php?title=Framework_Profile Framework Profile]		*[https://tcwiki.azurewebsites.net/index.php?title=Framework_Profile Framework Profile]
	* [https://docs.google.com/presentation/d/1sYqjqnarKBMGMT-3dJuA6QE4EWYhD3pvtbQZvn9Xz3w Consumer Ratings System]		*[[Health Care Profile]]
			*[[Financial Profile]]
			*[https://docs.google.com/presentation/d/1sYqjqnarKBMGMT-3dJuA6QE4EWYhD3pvtbQZvn9Xz3w Consumer Ratings System]

	===Use Cases===		===Use Cases===

Tomjones: /* Work Product */

2019-04-15T16:46:44Z

Work Product

← Older revision		Revision as of 16:46, 15 April 2019
Line 37:		Line 37:

	==Work Product==		==Work Product==
			# Build example use case and sandbox for emergency contact information
	# Obtain funding to move forward with Web Site ratings		# Obtain funding to move forward with Web Site ratings
	# Obtain funding to build out a sandbox for the Trust Registry		# Obtain funding to build out a sandbox for the Trust Registry