TEFCA - Revision history

Tom: /* QTF - QHIN Technical Framework */

2020-03-19T05:48:36Z

‎QTF - QHIN Technical Framework

2020-03-19T05:22:26Z

‎QTF - QHIN Technical Framework

2020-03-19T04:56:41Z

‎QTF - QHIN Technical Framework

2020-03-19T04:48:47Z

‎QTF - QHIN Technical Framework

2020-03-19T04:45:16Z

‎QTF - QHIN Technical Framework

2020-03-19T02:02:08Z

‎QTF - QHIN Technical Framework

2020-03-19T01:59:21Z

‎Solutions

2020-02-29T21:30:52Z

‎Problems

2019-04-28T00:04:12Z

‎Other sources

2019-04-23T21:06:32Z

‎References

@@ Line 37: / Line 37: @@
 TEFCA has pushed some of the technical details in issues like Security and Privacy to the QTF draft 2 - which is (2019-12) to forms the basis for draft 2. The following notes were taken from the annual meeting of Carequality, which is the contractor of the ONC for the QTF.
 * TEFCA requires compliance with the QTF which is included in contracts by reference.
-* QTF 1 was based on SOAP queries as it is in other document exchange by Carequality and other sites. There seems be no drive to move to more modern protocols. Presentation by Dave Cassel Carequality and David Pike.
+* QTF 1 (aka Appendix 3 of TEFCA) was based on SOAP queries as it is in other document exchange by Carequality and other sites. There seems be no drive to move to more modern protocols. Presentation by Dave Cassel Carequality and David Pike.
 * IAT protocols might be updated from a very old version, rather then move to HTML and FHIR.
 * MHTS was proposed as an interim step.
-* FHIR is inevitable, but that seems like too much for version 2.
+* FHIR is inevitable, but that seems like too much for version 2. The moderator, Dave Cassel or Carequality, predicted 10 years.
 * Push people to IHA & XTF for hop-hop as well as direct queries.
 * Seems to be some idea that the patient ID would be the same across QHINs.

@@ Line 44: / Line 44: @@
 * Seems to be some idea that the patient ID would be the same across QHINs.
 * Sites can ask for any document that they want.
 ==References==

@@ Line 36: / Line 36: @@
 ===QTF - QHIN Technical Framework===
 TEFCA has pushed some of the technical details in issues like Security and Privacy to the QTF draft 2 - which is (2019-12) to forms the basis for draft 2. The following notes were taken from the annual meeting of Carequality, which is the contractor of the ONC for the QTF.
-*TEFCA requires compliance with the QTF which is included in contracts by reference.
+* TEFCA requires compliance with the QTF which is included in contracts by reference.
-* QTF 1 was based on SOAP queries as it is in other document exchange by Carequality and other sites. There seems be no drive to move to more modern protocols.
+* QTF 1 was based on SOAP queries as it is in other document exchange by Carequality and other sites. There seems be no drive to move to more modern protocols. Presentation by Dave Cassel Carequality and David Pike.
 * IAT protocols might be updated from a very old version, rather then move to HTML and FHIR.
 * MHTS was proposed as an interim step.
 * FHIR is inevitable, but that seems like too much for version 2.
 ==References==

@@ Line 38: / Line 38: @@
 *TEFCA requires compliance with the QTF which is included in contracts by reference.
 * QTF 1 was based on SOAP queries as it is in other document exchange by Carequality and other sites. There seems be no drive to move to more modern protocols.
+* IAT protocols might be updated from a very old version, rather then move to HTML and FHIR.
 ==References==

@@ Line 35: / Line 35: @@
 *The page on [[Federation Trust Registry]] describes some generic solutions to [[Trust]] in a [[Federated Ecosystem]],
 ===QTF - QHIN Technical Framework===
-TEFCA has pushed some of the technical details in issues like Security and Privacy to the QTF draft 1 - which is either still in development (2019-12) fo forms the basis for draft 2. THe following notes were taken from the annual meeting of CareQuality, which is the contractor of the ONC for the QTF.
+TEFCA has pushed some of the technical details in issues like Security and Privacy to the QTF draft 2 - which is (2019-12) to forms the basis for draft 2. The following notes were taken from the annual meeting of Carequality, which is the contractor of the ONC for the QTF.
 *TEFCA requires compliance with the QTF which is included in contracts by reference.
 ==References==

@@ Line 25: / Line 25: @@
 ==Problems==
 *[[FHIR]] is focused on the data access methods and encoding leveraging existing Security solutions. Security in FHIR needs to focus on the set of considerations required to ensure that data can be discovered, accessed, or altered only in accordance with expectations and policies.
 *[[Privacy]] in FHIR is focused on the data access methods and encoding leveraging existing Security solutions. Security in FHIR needs to focus on the set of considerations required to ensure that data can be discovered, accessed, or altered only in accordance with expectations and policies.
 ==Solutions==

@@ Line 39: / Line 39: @@
 *[https://www.healthit.gov/sites/default/files/page/2019-04/FINALTEFCAQTF41719508version.pdf Trusted Exchange Framework and Common Agreement (TEFCA) Draft 2] (2019-04-19)
 *[https://www.healthit.gov/sites/default/files/page/2019-04/TEFCADraft2UsersGuide.pdf A User’s Guide to Understanding to TEFCA Draft 2] A slide deck that introduces some erroneous simplifications. (like credential)
-*[https://www.healthit.gov/buzz-blog/interoperability/trusted-exchange-framework-common-agreement-common-sense-approach-achieving-health-information-interoperability/ Trusted Exchange Framework and Common Agreement: A Common Sense Approach to Achieving Health Information Interoperability]
+*[https://www.healthit.gov/buzz-blog/interoperability/trusted-exchange-framework-common-agreement-common-sense-approach-achieving-health-information-interoperability/ Trusted Exchange Framework and Common Agreement: A Common Sense Approach to Achieving Health Information Interoperability] (2018-01-05)
 *[[FHIR]] STU3 version of the [http://hl7.org/fhir/secpriv-module.html Security and Privacy Module] has a good overview of protection of health information([[PHI]]).
 *[https://smarthealthit.org/ SMART Health IT] is an open, standards based technology platform that enables innovators to create apps that seamlessly and securely run across the healthcare system.