Health Care Profile - Revision history

Tomjones: /* Goals */

2020-12-07T18:52:49Z

Goals

← Older revision		Revision as of 18:52, 7 December 2020
Line 6:		Line 6:
	#Improve [[Patient Choice]] in acquiring and releasing of their Personal Healthcare Information (PHI).		#Improve [[Patient Choice]] in acquiring and releasing of their Personal Healthcare Information (PHI).
	# Solution to the TEFCA requirement for Level 2 identifier assurance based on NIST 800-63-3 (A) for IAL2 and (B) for AAL2.		# Solution to the TEFCA requirement for Level 2 identifier assurance based on NIST 800-63-3 (A) for IAL2 and (B) for AAL2.
	# ~~Patient~~ oriented solution ~~will~~ provide a corresponding level of trust in the covered health care providers.		# That a patient oriented solution must provide a corresponding level of trust in the covered health care providers (aka the [[Electronic Health Record]] service).

	===Assumptions===		===Assumptions===

Tomjones at 18:50, 7 December 2020

2020-12-07T18:50:23Z

← Older revision		Revision as of 18:50, 7 December 2020
Line 3:		Line 3:

	===Goals===		===Goals===
	# Creation of a profile for the use of the [[~~IDEF Registry~~]] in the US Healthcare community.		# Creation of a profile for the use of the [[UXC NSTIC Principles]] in the US Healthcare community.
	#Improve [[Patient Choice]] in acquiring and releasing of their Personal Healthcare Information (PHI).		#Improve [[Patient Choice]] in acquiring and releasing of their Personal Healthcare Information (PHI).
	# Solution to the TEFCA requirement for Level 2 identifier assurance based on NIST 800-63-3 (A) for IAL2 and (B) for AAL2.		# Solution to the TEFCA requirement for Level 2 identifier assurance based on NIST 800-63-3 (A) for IAL2 and (B) for AAL2.

Tomjones: /* Use Cases */

2020-10-29T00:00:53Z

Use Cases

← Older revision		Revision as of 00:00, 29 October 2020
Line 63:		Line 63:
	* [https://kantarainitiative.org/confluence/display/uma/UMA+Scenarios+and+Use+Cases#UMAScenariosandUseCases-scenario-hdataScenario:ControllingAccesstoHealthData(Pending) Controlling Access to Health Data] from the UMA use cases.		* [https://kantarainitiative.org/confluence/display/uma/UMA+Scenarios+and+Use+Cases#UMAScenariosandUseCases-scenario-hdataScenario:ControllingAccesstoHealthData(Pending) Controlling Access to Health Data] from the UMA use cases.
	* Coordinated chronic disease management for a patient having several modalities using telemedicine and 3rd party business associates vendors as part of the remote monitoring solution. (Not yet started)		* Coordinated chronic disease management for a patient having several modalities using telemedicine and 3rd party business associates vendors as part of the remote monitoring solution. (Not yet started)
			* [[Mobile Driver's License in Healthcare]] how it can be used to register a patient in telemedicine.
	* [[Trustworthy Healthcare Ecosystem]] contains the patient trust experience in a healthcare ecosystem.		* [[Trustworthy Healthcare Ecosystem]] contains the patient trust experience in a healthcare ecosystem.
	* Patient from US travels to Northern Ireland where she contracts salmonella. She is diagnosed in the Republic of Ireland that tries to track the source of infrection.		* Patient from US travels to Northern Ireland where she contracts salmonella. She is diagnosed in the Republic of Ireland that tries to track the source of infrection.

Tomjones: /* Use Cases */

2020-09-23T16:33:30Z

Use Cases

← Older revision		Revision as of 16:33, 23 September 2020
Line 64:		Line 64:
	* Coordinated chronic disease management for a patient having several modalities using telemedicine and 3rd party business associates vendors as part of the remote monitoring solution. (Not yet started)		* Coordinated chronic disease management for a patient having several modalities using telemedicine and 3rd party business associates vendors as part of the remote monitoring solution. (Not yet started)
	* [[Trustworthy Healthcare Ecosystem]] contains the patient trust experience in a healthcare ecosystem.		* [[Trustworthy Healthcare Ecosystem]] contains the patient trust experience in a healthcare ecosystem.
			* Patient from US travels to Northern Ireland where she contracts salmonella. She is diagnosed in the Republic of Ireland that tries to track the source of infrection.
	* [[FHIR Use Case]]		* [[FHIR Use Case]]

Tomjones: /* Use Cases */

2020-09-09T16:27:23Z

Use Cases

← Older revision		Revision as of 16:27, 9 September 2020
Line 64:		Line 64:
	* Coordinated chronic disease management for a patient having several modalities using telemedicine and 3rd party business associates vendors as part of the remote monitoring solution. (Not yet started)		* Coordinated chronic disease management for a patient having several modalities using telemedicine and 3rd party business associates vendors as part of the remote monitoring solution. (Not yet started)
	* [[Trustworthy Healthcare Ecosystem]] contains the patient trust experience in a healthcare ecosystem.		* [[Trustworthy Healthcare Ecosystem]] contains the patient trust experience in a healthcare ecosystem.
			* [[FHIR Use Case]]

	==References==		==References==

Tomjones: /* Goals */

2020-02-01T00:42:31Z

Goals

← Older revision		Revision as of 00:42, 1 February 2020
Line 4:		Line 4:
	===Goals===		===Goals===
	# Creation of a profile for the use of the [[IDEF Registry]] in the US Healthcare community.		# Creation of a profile for the use of the [[IDEF Registry]] in the US Healthcare community.
			#Improve [[Patient Choice]] in acquiring and releasing of their Personal Healthcare Information (PHI).
	# Solution to the TEFCA requirement for Level 2 identifier assurance based on NIST 800-63-3 (A) for IAL2 and (B) for AAL2.		# Solution to the TEFCA requirement for Level 2 identifier assurance based on NIST 800-63-3 (A) for IAL2 and (B) for AAL2.
	# Patient oriented solution will provide a corresponding level of trust in the covered health care providers.		# Patient oriented solution will provide a corresponding level of trust in the covered health care providers.

Tomjones: /* References */

2019-09-27T03:42:31Z

References

← Older revision		Revision as of 03:42, 27 September 2019
Line 80:		Line 80:
	* [http://www.hipaasurvivalguide.com/hipaa-regulations/part-164.php HIPPA - Legislation] - § 164.414(b) Burden of proof. In the event of a use or disclosure in violation of subpart E, the covered entity or business associate, as applicable, shall have the burden of demonstrating that all notifications were made as required by this subpart or that the use or disclosure did not constitute a breach, as defined at § 164.402.		* [http://www.hipaasurvivalguide.com/hipaa-regulations/part-164.php HIPPA - Legislation] - § 164.414(b) Burden of proof. In the event of a use or disclosure in violation of subpart E, the covered entity or business associate, as applicable, shall have the burden of demonstrating that all notifications were made as required by this subpart or that the use or disclosure did not constitute a breach, as defined at § 164.402.
	* [https://www.directtrust.org/about-directtrust/ Direct Trust]<blockquote>DirectTrust is a collaborative non-profit association of 121 health IT and health care provider organizations to support secure, interoperable health information exchange via the Direct message protocols. DirectTrust has created a “trust framework” that extends use of Direct exchange to over 106,000 health care organizations and 1,582,373 Direct addresses/accounts. Over 300 EHR and PHR vendors’ products, and over 50 HIEs, participate in the DirectTrust network, ensuring interoperability and security via Direct for exchange of health information to more than half the professionals in the U.S. health care system.</blockquote>		* [https://www.directtrust.org/about-directtrust/ Direct Trust]<blockquote>DirectTrust is a collaborative non-profit association of 121 health IT and health care provider organizations to support secure, interoperable health information exchange via the Direct message protocols. DirectTrust has created a “trust framework” that extends use of Direct exchange to over 106,000 health care organizations and 1,582,373 Direct addresses/accounts. Over 300 EHR and PHR vendors’ products, and over 50 HIEs, participate in the DirectTrust network, ensuring interoperability and security via Direct for exchange of health information to more than half the professionals in the U.S. health care system.</blockquote>
	* [https://sequoiaproject.org/ehealthexchange-manager-policy-governance-2-2/ The Sequoia Project] ONC selects nonprofit Sequoia Project to coordinate TEFCA (2019-09-06) <blockquote>		* [https://sequoiaproject.org/ehealthexchange-manager-policy-governance-2-2/ The Sequoia Project] ONC selects nonprofit Sequoia Project to coordinate TEFCA (2019-09-06) <blockquote>The government’s health IT agency has selected nonprofit Sequoia Project to serve as the recognized coordinating entity (RCE) overseeing the implementation of the Trusted Exchange Framework and Common Agreement (TEFCA). The Sequoia Project, a public-private partnership that advocates for nationwide health IT exchange, will start work on its responsibilities this week. The RCE is mostly responsible for developing and implementing the Common Agreement portion of the interoperability guidelines: creating baseline technical and legal requirements for different health IT systems, companies and groups to communicate with each another and share electronic information. In its new role, the Sequoia Project will also choose and monitor qualified health information networks (QHINs). The four-year agreement with the Office of the National Coordinator for Health IT is funded for $900,000 for the first year.</blockquote>
	The government’s health IT agency has selected nonprofit Sequoia Project to serve as the recognized coordinating entity (RCE) overseeing the implementation of the Trusted Exchange Framework and Common Agreement (TEFCA). The Sequoia Project, a public-private partnership that advocates for nationwide health IT exchange, will start work on its responsibilities this week.
	The RCE is mostly responsible for developing and implementing the Common Agreement portion of the interoperability guidelines: creating baseline technical and legal requirements for different health IT systems, companies and groups to communicate with each another and share electronic information. In its new role, the Sequoia Project will also choose and monitor qualified health information networks (QHINs). The four-year agreement with the Office of the National Coordinator for Health IT is funded for $900,000 for the first year.</blockquote>
	* [https://kantarainitiative.org/groups/healthcare-identity-assurance-work-group/ Kantara Healthcare Identity Assurance Work Group] <blockquote>The Kantara Healthcare Identity Assurance WG (HIAWG) exists to be the primary source of Healthcare Industry expert input into the Kantara IAF; to promote the use of Trust Frameworks in the Healthcare Industry for meeting the Trusted Identity interoperability requirements of the industry; and, to foster collaboration with regional, national and international Healthcare IT organizations.</blockquote>		* [https://kantarainitiative.org/groups/healthcare-identity-assurance-work-group/ Kantara Healthcare Identity Assurance Work Group] <blockquote>The Kantara Healthcare Identity Assurance WG (HIAWG) exists to be the primary source of Healthcare Industry expert input into the Kantara IAF; to promote the use of Trust Frameworks in the Healthcare Industry for meeting the Trusted Identity interoperability requirements of the industry; and, to foster collaboration with regional, national and international Healthcare IT organizations.</blockquote>
	* [https://kantarainitiative.org/groups/identity-assurance-work-group/ Kantara Identity Assurance Work Group]<blockquote>The IAWG is an active discussion forum that maintains the Kantara Identity Assurance Framework (IAF) and supports Kantara Initiative Inc. governance and assurance programs. The IAF includes the standards, processes, practices, guidance and methods by which participants in identity federations gain assurance of the reliability, security, thoroughness and degree of assurance of each others’ processes for identity and credential information verification, validation and exchange.</blockquote>		* [https://kantarainitiative.org/groups/identity-assurance-work-group/ Kantara Identity Assurance Work Group]<blockquote>The IAWG is an active discussion forum that maintains the Kantara Identity Assurance Framework (IAF) and supports Kantara Initiative Inc. governance and assurance programs. The IAF includes the standards, processes, practices, guidance and methods by which participants in identity federations gain assurance of the reliability, security, thoroughness and degree of assurance of each others’ processes for identity and credential information verification, validation and exchange.</blockquote>

Tomjones: /* References */

2019-09-27T03:41:46Z

References

← Older revision		Revision as of 03:41, 27 September 2019
Line 80:		Line 80:
	* [http://www.hipaasurvivalguide.com/hipaa-regulations/part-164.php HIPPA - Legislation] - § 164.414(b) Burden of proof. In the event of a use or disclosure in violation of subpart E, the covered entity or business associate, as applicable, shall have the burden of demonstrating that all notifications were made as required by this subpart or that the use or disclosure did not constitute a breach, as defined at § 164.402.		* [http://www.hipaasurvivalguide.com/hipaa-regulations/part-164.php HIPPA - Legislation] - § 164.414(b) Burden of proof. In the event of a use or disclosure in violation of subpart E, the covered entity or business associate, as applicable, shall have the burden of demonstrating that all notifications were made as required by this subpart or that the use or disclosure did not constitute a breach, as defined at § 164.402.
	* [https://www.directtrust.org/about-directtrust/ Direct Trust]<blockquote>DirectTrust is a collaborative non-profit association of 121 health IT and health care provider organizations to support secure, interoperable health information exchange via the Direct message protocols. DirectTrust has created a “trust framework” that extends use of Direct exchange to over 106,000 health care organizations and 1,582,373 Direct addresses/accounts. Over 300 EHR and PHR vendors’ products, and over 50 HIEs, participate in the DirectTrust network, ensuring interoperability and security via Direct for exchange of health information to more than half the professionals in the U.S. health care system.</blockquote>		* [https://www.directtrust.org/about-directtrust/ Direct Trust]<blockquote>DirectTrust is a collaborative non-profit association of 121 health IT and health care provider organizations to support secure, interoperable health information exchange via the Direct message protocols. DirectTrust has created a “trust framework” that extends use of Direct exchange to over 106,000 health care organizations and 1,582,373 Direct addresses/accounts. Over 300 EHR and PHR vendors’ products, and over 50 HIEs, participate in the DirectTrust network, ensuring interoperability and security via Direct for exchange of health information to more than half the professionals in the U.S. health care system.</blockquote>
			* [https://sequoiaproject.org/ehealthexchange-manager-policy-governance-2-2/ The Sequoia Project] ONC selects nonprofit Sequoia Project to coordinate TEFCA (2019-09-06) <blockquote>
			The government’s health IT agency has selected nonprofit Sequoia Project to serve as the recognized coordinating entity (RCE) overseeing the implementation of the Trusted Exchange Framework and Common Agreement (TEFCA). The Sequoia Project, a public-private partnership that advocates for nationwide health IT exchange, will start work on its responsibilities this week.
			The RCE is mostly responsible for developing and implementing the Common Agreement portion of the interoperability guidelines: creating baseline technical and legal requirements for different health IT systems, companies and groups to communicate with each another and share electronic information. In its new role, the Sequoia Project will also choose and monitor qualified health information networks (QHINs). The four-year agreement with the Office of the National Coordinator for Health IT is funded for $900,000 for the first year.</blockquote>
	* [https://kantarainitiative.org/groups/healthcare-identity-assurance-work-group/ Kantara Healthcare Identity Assurance Work Group] <blockquote>The Kantara Healthcare Identity Assurance WG (HIAWG) exists to be the primary source of Healthcare Industry expert input into the Kantara IAF; to promote the use of Trust Frameworks in the Healthcare Industry for meeting the Trusted Identity interoperability requirements of the industry; and, to foster collaboration with regional, national and international Healthcare IT organizations.</blockquote>		* [https://kantarainitiative.org/groups/healthcare-identity-assurance-work-group/ Kantara Healthcare Identity Assurance Work Group] <blockquote>The Kantara Healthcare Identity Assurance WG (HIAWG) exists to be the primary source of Healthcare Industry expert input into the Kantara IAF; to promote the use of Trust Frameworks in the Healthcare Industry for meeting the Trusted Identity interoperability requirements of the industry; and, to foster collaboration with regional, national and international Healthcare IT organizations.</blockquote>
	* [https://kantarainitiative.org/groups/identity-assurance-work-group/ Kantara Identity Assurance Work Group]<blockquote>The IAWG is an active discussion forum that maintains the Kantara Identity Assurance Framework (IAF) and supports Kantara Initiative Inc. governance and assurance programs. The IAF includes the standards, processes, practices, guidance and methods by which participants in identity federations gain assurance of the reliability, security, thoroughness and degree of assurance of each others’ processes for identity and credential information verification, validation and exchange.</blockquote>		* [https://kantarainitiative.org/groups/identity-assurance-work-group/ Kantara Identity Assurance Work Group]<blockquote>The IAWG is an active discussion forum that maintains the Kantara Identity Assurance Framework (IAF) and supports Kantara Initiative Inc. governance and assurance programs. The IAF includes the standards, processes, practices, guidance and methods by which participants in identity federations gain assurance of the reliability, security, thoroughness and degree of assurance of each others’ processes for identity and credential information verification, validation and exchange.</blockquote>

Tomjones: /* References */

2019-09-27T03:32:02Z

References

← Older revision		Revision as of 03:32, 27 September 2019
Line 84:		Line 84:
	* [https://openid.net/wg/heart/ OpenID HEART WG]<blockquote>HEART (Health Relationship Trust) is a set of profiles that enables patients to control how, when, and with whom their clinical data is shared. The HEART model builds on existing state-of-the-art security and adds additional components to ensure that patient clinical data is securely exchanged. In addition to giving patients control over how their own data is shared, HEART defines the interoperable process for systems to exchange patient-authorized healthcare data consistent with open standards, specifically FHIR (Fast Healthcare Interoperability Resources), OAuth, OpenID Connect, and UMA (User-Managed Access).</blockquote>		* [https://openid.net/wg/heart/ OpenID HEART WG]<blockquote>HEART (Health Relationship Trust) is a set of profiles that enables patients to control how, when, and with whom their clinical data is shared. The HEART model builds on existing state-of-the-art security and adds additional components to ensure that patient clinical data is securely exchanged. In addition to giving patients control over how their own data is shared, HEART defines the interoperable process for systems to exchange patient-authorized healthcare data consistent with open standards, specifically FHIR (Fast Healthcare Interoperability Resources), OAuth, OpenID Connect, and UMA (User-Managed Access).</blockquote>
	* [https://strategichie.com/ The Strategic Health Information Exchange Collaborative (SHIEC)] is the national collaborative representing health information exchanges (HIEs) and their strategic business and technology partners.<blockquote>SHIEC strives to enable the secure exchange of patient information to improve the quality, coordination, and cost-effectiveness of healthcare locally, regionally and nationally. We are the largest consortium of its kind in the country, representing 70+ member HIE organizations that together cover more than 200 million people across the United States—well over half of the American population. We advocate on behalf of our member organizations to ensure their needs are represented in nationwide conversations about critical healthcare issues, including health IT, health data sharing and stewardship.</blockquote>		* [https://strategichie.com/ The Strategic Health Information Exchange Collaborative (SHIEC)] is the national collaborative representing health information exchanges (HIEs) and their strategic business and technology partners.<blockquote>SHIEC strives to enable the secure exchange of patient information to improve the quality, coordination, and cost-effectiveness of healthcare locally, regionally and nationally. We are the largest consortium of its kind in the country, representing 70+ member HIE organizations that together cover more than 200 million people across the United States—well over half of the American population. We advocate on behalf of our member organizations to ensure their needs are represented in nationwide conversations about critical healthcare issues, including health IT, health data sharing and stewardship.</blockquote>
	* [http://hieofone.org/ HIE of one]<blockquote>Our solution is a patient-centered approach to privacy protection in cloud computing and information based on digital consent standards, blockchain identity, and blockchain audit. This enables each patient and each licensed practitioner to own and completely control their open source connected health records within a secure environment. </blockquote>		* [http://hieofone.org/ HIE of one] is an open source cooperative based on blockchain and [https://www.w3.org/2017/vc/WG/ W3C Verifiable Claims.] <blockquote>Our solution is a patient-centered approach to privacy protection in cloud computing and information based on digital consent standards, blockchain identity, and blockchain audit. This enables each patient and each licensed practitioner to own and completely control their open source connected health records within a secure environment. </blockquote>

	[[Category:Glossary]]		[[Category:Glossary]]
	[[Category:Profile]]		[[Category:Profile]]
	[[Category:Health]]		[[Category:Health]]

Tomjones: /* References */

2019-09-27T03:27:06Z

References

← Older revision		Revision as of 03:27, 27 September 2019
Line 83:		Line 83:
	* [https://kantarainitiative.org/groups/identity-assurance-work-group/ Kantara Identity Assurance Work Group]<blockquote>The IAWG is an active discussion forum that maintains the Kantara Identity Assurance Framework (IAF) and supports Kantara Initiative Inc. governance and assurance programs. The IAF includes the standards, processes, practices, guidance and methods by which participants in identity federations gain assurance of the reliability, security, thoroughness and degree of assurance of each others’ processes for identity and credential information verification, validation and exchange.</blockquote>		* [https://kantarainitiative.org/groups/identity-assurance-work-group/ Kantara Identity Assurance Work Group]<blockquote>The IAWG is an active discussion forum that maintains the Kantara Identity Assurance Framework (IAF) and supports Kantara Initiative Inc. governance and assurance programs. The IAF includes the standards, processes, practices, guidance and methods by which participants in identity federations gain assurance of the reliability, security, thoroughness and degree of assurance of each others’ processes for identity and credential information verification, validation and exchange.</blockquote>
	* [https://openid.net/wg/heart/ OpenID HEART WG]<blockquote>HEART (Health Relationship Trust) is a set of profiles that enables patients to control how, when, and with whom their clinical data is shared. The HEART model builds on existing state-of-the-art security and adds additional components to ensure that patient clinical data is securely exchanged. In addition to giving patients control over how their own data is shared, HEART defines the interoperable process for systems to exchange patient-authorized healthcare data consistent with open standards, specifically FHIR (Fast Healthcare Interoperability Resources), OAuth, OpenID Connect, and UMA (User-Managed Access).</blockquote>		* [https://openid.net/wg/heart/ OpenID HEART WG]<blockquote>HEART (Health Relationship Trust) is a set of profiles that enables patients to control how, when, and with whom their clinical data is shared. The HEART model builds on existing state-of-the-art security and adds additional components to ensure that patient clinical data is securely exchanged. In addition to giving patients control over how their own data is shared, HEART defines the interoperable process for systems to exchange patient-authorized healthcare data consistent with open standards, specifically FHIR (Fast Healthcare Interoperability Resources), OAuth, OpenID Connect, and UMA (User-Managed Access).</blockquote>
			* [https://strategichie.com/ The Strategic Health Information Exchange Collaborative (SHIEC)] is the national collaborative representing health information exchanges (HIEs) and their strategic business and technology partners.<blockquote>SHIEC strives to enable the secure exchange of patient information to improve the quality, coordination, and cost-effectiveness of healthcare locally, regionally and nationally. We are the largest consortium of its kind in the country, representing 70+ member HIE organizations that together cover more than 200 million people across the United States—well over half of the American population. We advocate on behalf of our member organizations to ensure their needs are represented in nationwide conversations about critical healthcare issues, including health IT, health data sharing and stewardship.</blockquote>
	* [http://hieofone.org/ HIE of one]<blockquote>Our solution is a patient-centered approach to privacy protection in cloud computing and information based on digital consent standards, blockchain identity, and blockchain audit. This enables each patient and each licensed practitioner to own and completely control their open source connected health records within a secure environment. </blockquote>		* [http://hieofone.org/ HIE of one]<blockquote>Our solution is a patient-centered approach to privacy protection in cloud computing and information based on digital consent standards, blockchain identity, and blockchain audit. This enables each patient and each licensed practitioner to own and completely control their open source connected health records within a secure environment. </blockquote>