Code of Conduct - Revision history

Tomjones: /* Aerospace and Defense */

2020-05-20T23:32:31Z

Aerospace and Defense

← Older revision		Revision as of 23:32, 20 May 2020
Line 39:		Line 39:

	===Aerospace and Defense===		===Aerospace and Defense===
	Like the CA\|B rules for Certificate authorities, the Code of Conduct or the [http://www.tscp.org/common-operating-rules/ common operating rules] of the [https://www.tscp.org/ TSCP or Transglobal Secure Collaboration Program] has been very successful creating a federated or single siggon for employees of large A&D enterprises. Since employees sign away all of the rights heretofore, there has been no interest in any PKI federation to focus on user rights. Still their ~~documents~~ does give security guidance that is valuable for any site with valuable user information.		Like the CA\|B rules for Certificate authorities, the Code of Conduct or the [http://www.tscp.org/common-operating-rules/ common operating rules] of the [https://www.tscp.org/ TSCP or Transglobal Secure Collaboration Program] has been very successful creating a federated or single siggon for employees of large A&D enterprises. Since employees sign away all of the rights heretofore, there has been no interest in any PKI federation to focus on user rights. Still their common operating rules document does give security guidance that is valuable for any site with valuable user information.

	==References==		==References==
	[[Category:Trust]]		[[Category:Trust]]

Tomjones: /* Aerospace and Defense */

2020-05-20T23:31:31Z

Aerospace and Defense

← Older revision		Revision as of 23:31, 20 May 2020
Line 39:		Line 39:

	===Aerospace and Defense===		===Aerospace and Defense===
			Like the CA\|B rules for Certificate authorities, the Code of Conduct or the [http://www.tscp.org/common-operating-rules/ common operating rules] of the [https://www.tscp.org/ TSCP or Transglobal Secure Collaboration Program] has been very successful creating a federated or single siggon for employees of large A&D enterprises. Since employees sign away all of the rights heretofore, there has been no interest in any PKI federation to focus on user rights. Still their documents does give security guidance that is valuable for any site with valuable user information.

	==References==		==References==
	[[Category:Trust]]		[[Category:Trust]]

Tomjones: /* Healthcare */

2020-05-20T22:42:02Z

Healthcare

← Older revision		Revision as of 22:42, 20 May 2020
Line 24:		Line 24:
	This is a list of some of the codes listed by their intended audience.		This is a list of some of the codes listed by their intended audience.
	===Healthcare===		===Healthcare===
	The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare. As written is is wholly voluntary with ~~not~~ penalty for failure to ~~abid~~ by the terms. Any enforcement is directed to the FTC.		The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare. As written is is wholly voluntary with no penalty for failure to abide by the terms. Any enforcement is directed to the FTC which enforces a variety of consumer privacy and notification requirements.
	<blockquote>The CARIN Alliance believes that when an individual makes a request for their data to be sent to an application of their choice it should be treated as an individual “right of access” request pursuant to the HIPAA Privacy Rule. We also believe that when an application makes a request for a consumer’s data at the direction of, and on behalf of, an individual, it should also be treated as an individual “right of access” request when it does the [list of items including directed to a HIPAA EHR, the subject is IAL2 and AAL2 proofed and the destination of the data is well known].</blockquote>		<blockquote>The CARIN Alliance believes that when an individual makes a request for their data to be sent to an application of their choice it should be treated as an individual “right of access” request pursuant to the HIPAA Privacy Rule. We also believe that when an application makes a request for a consumer’s data at the direction of, and on behalf of, an individual, it should also be treated as an individual “right of access” request when it does the [list of items including directed to a HIPAA EHR, the subject is IAL2 and AAL2 proofed and the destination of the data is well known].</blockquote>
	The following sections are addressed (Notice is not mentioned other than the ONC’s Model Privacy Notice (MPN)) :		The following sections are addressed (Notice is not mentioned other than the ONC’s Model Privacy Notice (MPN)) :

Tomjones: /* Healthcare */

2020-05-20T22:37:11Z

Healthcare

← Older revision		Revision as of 22:37, 20 May 2020
Line 36:		Line 36:
	# Education		# Education
	# Advocacy		# Advocacy
	It is not clear how this intersects with the ONC rule that the app developer is "certified."		It is not clear how this intersects with the ONC rule that the app developer is "certified" but otherwise no limitations are placed on the app.

	===Aerospace and Defense===		===Aerospace and Defense===

Tomjones: /* Healthcare */

2020-05-20T22:36:02Z

Healthcare

← Older revision		Revision as of 22:36, 20 May 2020
Line 26:		Line 26:
	The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare. As written is is wholly voluntary with not penalty for failure to abid by the terms. Any enforcement is directed to the FTC.		The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare. As written is is wholly voluntary with not penalty for failure to abid by the terms. Any enforcement is directed to the FTC.
	<blockquote>The CARIN Alliance believes that when an individual makes a request for their data to be sent to an application of their choice it should be treated as an individual “right of access” request pursuant to the HIPAA Privacy Rule. We also believe that when an application makes a request for a consumer’s data at the direction of, and on behalf of, an individual, it should also be treated as an individual “right of access” request when it does the [list of items including directed to a HIPAA EHR, the subject is IAL2 and AAL2 proofed and the destination of the data is well known].</blockquote>		<blockquote>The CARIN Alliance believes that when an individual makes a request for their data to be sent to an application of their choice it should be treated as an individual “right of access” request pursuant to the HIPAA Privacy Rule. We also believe that when an application makes a request for a consumer’s data at the direction of, and on behalf of, an individual, it should also be treated as an individual “right of access” request when it does the [list of items including directed to a HIPAA EHR, the subject is IAL2 and AAL2 proofed and the destination of the data is well known].</blockquote>
	The following sections are addressed (Notice is not ~~mentions~~ other than the ONC’s Model Privacy Notice (MPN)) :		The following sections are addressed (Notice is not mentioned other than the ONC’s Model Privacy Notice (MPN)) :
	# Transparency		# Transparency
	# Consent (includes advance notice of privacy policy changes)		# Consent (includes advance notice of privacy policy changes)

Tomjones: /* Healthcare */

2020-05-20T22:35:41Z

Healthcare

← Older revision		Revision as of 22:35, 20 May 2020
Line 26:		Line 26:
	The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare. As written is is wholly voluntary with not penalty for failure to abid by the terms. Any enforcement is directed to the FTC.		The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare. As written is is wholly voluntary with not penalty for failure to abid by the terms. Any enforcement is directed to the FTC.
	<blockquote>The CARIN Alliance believes that when an individual makes a request for their data to be sent to an application of their choice it should be treated as an individual “right of access” request pursuant to the HIPAA Privacy Rule. We also believe that when an application makes a request for a consumer’s data at the direction of, and on behalf of, an individual, it should also be treated as an individual “right of access” request when it does the [list of items including directed to a HIPAA EHR, the subject is IAL2 and AAL2 proofed and the destination of the data is well known].</blockquote>		<blockquote>The CARIN Alliance believes that when an individual makes a request for their data to be sent to an application of their choice it should be treated as an individual “right of access” request pursuant to the HIPAA Privacy Rule. We also believe that when an application makes a request for a consumer’s data at the direction of, and on behalf of, an individual, it should also be treated as an individual “right of access” request when it does the [list of items including directed to a HIPAA EHR, the subject is IAL2 and AAL2 proofed and the destination of the data is well known].</blockquote>
	The following sections are addressed:		The following sections are addressed (Notice is not mentions other than the ONC’s Model Privacy Notice (MPN)) :
	# Transparency		# Transparency
	# Consent		# Consent (includes advance notice of privacy policy changes)
	# Use and DIsclosure		# Use and DIsclosure
	# Individual Access		# Individual Access

Tomjones: /* Healthcare */

2020-05-20T22:32:43Z

Healthcare

← Older revision		Revision as of 22:32, 20 May 2020
Line 24:		Line 24:
	This is a list of some of the codes listed by their intended audience.		This is a list of some of the codes listed by their intended audience.
	===Healthcare===		===Healthcare===
	* The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare. As written is is wholly voluntary with not penalty for failure to abid by the terms. Any enforcement is directed to the FTC.		The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare. As written is is wholly voluntary with not penalty for failure to abid by the terms. Any enforcement is directed to the FTC.
	<blockquote>The CARIN Alliance believes that when an individual makes a request for their data to be sent to an application of their choice it should be treated as an individual “right of access” request pursuant to the HIPAA Privacy Rule. We also believe that when an application makes a request for a consumer’s data at the direction of, and on behalf of, an individual, it should also be treated as an individual “right of access” request when it does the [list of items including directed to a HIPAA EHR, the subject is IAL2 and AAL2 proofed and the destination of the data is well known].</blockquote>		<blockquote>The CARIN Alliance believes that when an individual makes a request for their data to be sent to an application of their choice it should be treated as an individual “right of access” request pursuant to the HIPAA Privacy Rule. We also believe that when an application makes a request for a consumer’s data at the direction of, and on behalf of, an individual, it should also be treated as an individual “right of access” request when it does the [list of items including directed to a HIPAA EHR, the subject is IAL2 and AAL2 proofed and the destination of the data is well known].</blockquote>
			The following sections are addressed:
			# Transparency
			# Consent
			# Use and DIsclosure
			# Individual Access
			# Security
			# Provenance
			# Accountability
			# Education
			# Advocacy
	It is not clear how this intersects with the ONC rule that the app developer is "certified."		It is not clear how this intersects with the ONC rule that the app developer is "certified."

Tomjones: /* Healthcare */

2020-05-20T22:28:11Z

Healthcare

← Older revision		Revision as of 22:28, 20 May 2020
Line 24:		Line 24:
	This is a list of some of the codes listed by their intended audience.		This is a list of some of the codes listed by their intended audience.
	===Healthcare===		===Healthcare===
	* The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare.		* The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare. As written is is wholly voluntary with not penalty for failure to abid by the terms. Any enforcement is directed to the FTC.
			<blockquote>The CARIN Alliance believes that when an individual makes a request for their data to be sent to an application of their choice it should be treated as an individual “right of access” request pursuant to the HIPAA Privacy Rule. We also believe that when an application makes a request for a consumer’s data at the direction of, and on behalf of, an individual, it should also be treated as an individual “right of access” request when it does the [list of items including directed to a HIPAA EHR, the subject is IAL2 and AAL2 proofed and the destination of the data is well known].</blockquote>
			It is not clear how this intersects with the ONC rule that the app developer is "certified."

	===Aerospace and Defense===		===Aerospace and Defense===

Tomjones: /* Healthcare */

2020-05-20T22:20:50Z

Healthcare

← Older revision		Revision as of 22:20, 20 May 2020
Line 24:		Line 24:
	This is a list of some of the codes listed by their intended audience.		This is a list of some of the codes listed by their intended audience.
	===Healthcare===		===Healthcare===
	* The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address [[Native ~~Apps~~ in Healthcare]].		* The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address the [https://tcwiki.azurewebsites.net/index.php?title=Native_App Native App] in Healthcare.

	===Aerospace and Defense===		===Aerospace and Defense===

Tomjones: /* Healthcare */

2020-05-20T22:18:51Z

Healthcare

← Older revision		Revision as of 22:18, 20 May 2020
Line 24:		Line 24:
	This is a list of some of the codes listed by their intended audience.		This is a list of some of the codes listed by their intended audience.
	===Healthcare===		===Healthcare===
			* The CARIN Alliance [https://www.carinalliance.com/wp-content/uploads/2019/05/2019_CARIN_Code_of_Conduct_05082019.pdf Code of Conduct] was constructed specifically to address [[Native Apps in Healthcare]].

	===Aerospace and Defense===		===Aerospace and Defense===

	==References==		==References==
	[[Category:Trust]]		[[Category:Trust]]