http://clinfowiki.org/wiki/api.php?action=feedcontributions&user=Erickchristensen&feedformat=atomClinfowiki - User contributions [en]2024-03-28T14:13:31ZUser contributionsMediaWiki 1.22.4http://clinfowiki.org/wiki/index.php/HL7_FHIRHL7 FHIR2019-10-21T18:44:16Z<p>Erickchristensen: /* Related Pages */</p>
<hr />
<div>===What is FHIR?===<br />
<br />
Fast Healthcare Interoperability Resources (FHIR) is an interoperability standard created by [[HL7]]. FHIR utilizes a more modular approach to inter-system messaging than previous HL7 standards versions. These modules, termed "resources", allow implementations to be more flexible to changing system processes than the traditional HL7V2 or V3 standards. The initial version of FHIR was created in 2012 and has undergone multiple revisions to date. There is currently an implementation standard in the draft standard for trial use (DTSU) phase, and not yet fully approved. Balloting for the current DSTU is slated for April of 2015 with a projected release of DSTU 2 for July 2015. <ref name="dtsu2014">FHIR DTSU v. 1.1. (2014). Retrieved October 21, 2014 from http://www.hl7.org/implement/standards/fhir/index.html</ref><br />
Rather than using multi-element structured messages such at HL7v2, HL7v3, and [[CDA]] standards, FHIR uses application programming interfaces (APIs) to select specific elements vs. the entire message as in the older HL7 standards. These APIs utilize a "RESTful" architecture, designed for web applications<ref name="dtsu2014" /><ref name="mckenzie2013">Mckenzie, L. (2013, May 13)Introduction to FHIR. Retrieved October 20, 2014 from http://gforge.hl7.org/svn/fhir/trunk/presentations/2013-05%20Tutorials/Introduction%20to%20FHIR.pptx</ref>. REST stands for Representational State Transfer which allows for exchange of resources on an as needed basis, typically communicated via widely used HTTP or HTTPS protocols<ref name="restful2013">What exactly is RESTful programming? (2013, Jan 16). Retrieved October 23, 2014 from http://stackoverflow.com/questions/671118/what-exactly-is-restful-programming</ref>.<br />
<br />
[[Trusted Exchange Framework and Common Agreement (TEFCA)]]<br />
<br />
===FHIR Governance=== <br />
<br />
FHIR is governed by three separate bodies within HL7. The FHIR Governance Board, appointed by the FHIR Technical Steering Committee, provides broad oversight of the standard. The FHIR Management Group, also appointed by the Technical Steering Committee, manages the day-to-day operations of the standard. Finally, the Modeling and Methodology Work Group handles the resource creation, guidelines, and best practices<ref name="hl7wiki">HL7. (2014, Oct 22) FHIR Wiki. Retrieved October 23, 2014 from http://wiki.hl7.org/index.php?title=FHIR</ref>.<br />
<br />
===Why FHIR?===<br />
<br />
FHIR is HL7's answer to the call for a new interoperability standard that could more easily be used on mobile and cloud-based applications, and also speed the implementation process. These implementations can often be completed within a day or week, versus the traditional month- or year-long implementation timeline<ref name="dtsu2014" />. FHIR is a needed update to HL7v2, but expected to be much less disruptive to workflows than HL7v3.<br />
<br />
The specification is free and allows unrestricted use. FHIR uses the building blocks of HL7v2, HL7v3, and [[CDA]] while improving the ease of use and flexibility to alter implementations as needed. The RESTful architecture is applied to web services to allow for easy transfer of resources between systems, since they can be accessed through a uniform resource locator (URL). Due to this architecture, FHIR is well suited for mobile and cloud-based platforms.<br />
<br />
The RESTful API architecture also allows for transfer of data between systems without requiring the receiving system to know the structure of the API itself. This simplifies the interface between systems. (3) Once called to the receiving system, these individual resources can be extended and adapted based on individual implementation needs<ref name="dtsu2014" />.<br />
<br />
===The FHIR Code===<br />
From "Fundamental Principles of FHIR (aka The FHIR Code)"<ref name="fundprinc">Fundamental Principles of FHIR. (16 Sept 2014, 20:28). Retrieved 6 Dec 2015 from http://wiki.hl7.org/index.php?title=Fundamental_Principles_of_FHIR&oldid=90696</ref>.<br />
#Prioritize implementation<br />
#Provide a flexible framework for interoperability<br />
#Keep complexity where it belongs<br />
#Support but not mandate tight specifications<br />
#Leverage open source development principles<br />
#Free to use<br />
#Supports multiple exchange paradigms/architectures<br />
#Leverage common web technologies<br />
#Forward and backward compatibility<br />
#Tooling requirements are mainstream and minimal<br />
<br />
===FHIR Basics===<br />
<br />
Resources are classified as either clinical, administrative, or infrastructural. These resources were developed from HL7v2 and from HL7v3's Reference Information Model (RIM); as such they are intended to coexist with previous HL7 standards<ref name="dtsu2014" />. Resources are accessed via web protocol calls to specific URLs, and represented using either [[XML]] or [[JSON]] format. Resources are exchanged and manipulated via PUT, GET, POST, and DELETE operations via individual APIs. Using these APIs, the resources can be queried by a receiving system or pushed from a host system.<br />
<br />
FHIR resources have related profiles to specify their metadata, associated structures, and relevant extensions used in those structures. Resource metadata includes resource ID, version ID, last modified date, and other information. Metadata can contain tags linking a specific resource to a workflow event; these tags can be used to trigger events that initiate system interactions. Metadata also allows for resources to be searched efficiently. Resources can also be referenced by one another using resource links, allowing for connection of various data elements.<br />
<br />
===Resource Classifications===<br />
Individual resources are contained within one of three primary categories, then sub-classified within each category<ref name="dtsu2014" />:<br />
<br />
# '''Clinical'''<br />
#* General<br />
#* Medications<br />
#* Diagnostic<br />
#* Device Interactions<br />
# '''Administrative'''<br />
#* Attribution<br />
#* Entities<br />
#* Workflow Management<br />
#* Financial<br />
# '''Infrastructural'''<br />
#* Support<br />
#* Document Handling<br />
#* Exchange<br />
#* Conformance<br />
<br />
===FHIR enabled apps in use today===<br />
<br />
[[SMART uses for public health|Sustainable Medical Applications, Reusable Technologies (SMART)]] is a collaboration between the Harvard Medical School and the Office of the National Coordinator for Health Information Technology ([[ONC]]). SMART sought to develop a platform for the rapid development of health applications that could run across multiple EHRs<ref name="raths2014">Raths, D. (2014). "Trend: standards development. Catching FHIR: A new HL7 draft standard may boost web services development in healthcare." Healthcare Inform 31(2): 13, 16.</ref>. They succeeded, and now a variety of apps are "SMART-enabled". The apps are used in clinical back-office settings, research, patient communication and patient facing applications<ref name="smart2014">SMART. (2014). SMART-Enabled HIT. Accessed October 23, 2014 from http://smartplatforms.org/smart-enabled-hit/</ref>.<br />
<br />
FHIR is also gaining support in the U.K. Nearly ten apps have already been developed for use in various setting. Additionally, an alliance with the UK Renal Data Collaboration is planned.<br />
<br />
==Related Pages==<br />
* Review of Bender, D., & Sartipi, K. (2013, June). [[HL7 FHIR: An Agile and RESTful approach to healthcare information exchange]]. In 2013 IEEE 26th International Symposium on Computer-Based Medical Systems (CBMS) (pp. 326-331). IEEE.<br />
* Review of Kasthurirathne, S., Mamlin, B., Kumara, H., Grieve, G., & Biondich, P. (2015). [[Enabling Better Interoperability for HealthCare: Lessons in Developing a Standards Based Application Programing Interface for Electronic Medical Record Systems]]. J Med Syst Journal of Medical Systems, 39(182).<br />
* Review of Smits, M., Kramer, E., Harthoorn, M., & Cornet, R. (2015). [[A comparison of two Detailed Clinical Model representations: FHIR and CDA]]. ''European Journal for Biomedical Informatics, 11''(2), 7-17.<br />
<br />
===References===<br />
<references/><br />
<br />
[[Category:BMI512-FALL-14]]<br />
[[Category:Interoperability]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/HL7_FHIRHL7 FHIR2019-10-21T18:43:49Z<p>Erickchristensen: /* Related Pages */</p>
<hr />
<div>===What is FHIR?===<br />
<br />
Fast Healthcare Interoperability Resources (FHIR) is an interoperability standard created by [[HL7]]. FHIR utilizes a more modular approach to inter-system messaging than previous HL7 standards versions. These modules, termed "resources", allow implementations to be more flexible to changing system processes than the traditional HL7V2 or V3 standards. The initial version of FHIR was created in 2012 and has undergone multiple revisions to date. There is currently an implementation standard in the draft standard for trial use (DTSU) phase, and not yet fully approved. Balloting for the current DSTU is slated for April of 2015 with a projected release of DSTU 2 for July 2015. <ref name="dtsu2014">FHIR DTSU v. 1.1. (2014). Retrieved October 21, 2014 from http://www.hl7.org/implement/standards/fhir/index.html</ref><br />
Rather than using multi-element structured messages such at HL7v2, HL7v3, and [[CDA]] standards, FHIR uses application programming interfaces (APIs) to select specific elements vs. the entire message as in the older HL7 standards. These APIs utilize a "RESTful" architecture, designed for web applications<ref name="dtsu2014" /><ref name="mckenzie2013">Mckenzie, L. (2013, May 13)Introduction to FHIR. Retrieved October 20, 2014 from http://gforge.hl7.org/svn/fhir/trunk/presentations/2013-05%20Tutorials/Introduction%20to%20FHIR.pptx</ref>. REST stands for Representational State Transfer which allows for exchange of resources on an as needed basis, typically communicated via widely used HTTP or HTTPS protocols<ref name="restful2013">What exactly is RESTful programming? (2013, Jan 16). Retrieved October 23, 2014 from http://stackoverflow.com/questions/671118/what-exactly-is-restful-programming</ref>.<br />
<br />
[[Trusted Exchange Framework and Common Agreement (TEFCA)]]<br />
<br />
===FHIR Governance=== <br />
<br />
FHIR is governed by three separate bodies within HL7. The FHIR Governance Board, appointed by the FHIR Technical Steering Committee, provides broad oversight of the standard. The FHIR Management Group, also appointed by the Technical Steering Committee, manages the day-to-day operations of the standard. Finally, the Modeling and Methodology Work Group handles the resource creation, guidelines, and best practices<ref name="hl7wiki">HL7. (2014, Oct 22) FHIR Wiki. Retrieved October 23, 2014 from http://wiki.hl7.org/index.php?title=FHIR</ref>.<br />
<br />
===Why FHIR?===<br />
<br />
FHIR is HL7's answer to the call for a new interoperability standard that could more easily be used on mobile and cloud-based applications, and also speed the implementation process. These implementations can often be completed within a day or week, versus the traditional month- or year-long implementation timeline<ref name="dtsu2014" />. FHIR is a needed update to HL7v2, but expected to be much less disruptive to workflows than HL7v3.<br />
<br />
The specification is free and allows unrestricted use. FHIR uses the building blocks of HL7v2, HL7v3, and [[CDA]] while improving the ease of use and flexibility to alter implementations as needed. The RESTful architecture is applied to web services to allow for easy transfer of resources between systems, since they can be accessed through a uniform resource locator (URL). Due to this architecture, FHIR is well suited for mobile and cloud-based platforms.<br />
<br />
The RESTful API architecture also allows for transfer of data between systems without requiring the receiving system to know the structure of the API itself. This simplifies the interface between systems. (3) Once called to the receiving system, these individual resources can be extended and adapted based on individual implementation needs<ref name="dtsu2014" />.<br />
<br />
===The FHIR Code===<br />
From "Fundamental Principles of FHIR (aka The FHIR Code)"<ref name="fundprinc">Fundamental Principles of FHIR. (16 Sept 2014, 20:28). Retrieved 6 Dec 2015 from http://wiki.hl7.org/index.php?title=Fundamental_Principles_of_FHIR&oldid=90696</ref>.<br />
#Prioritize implementation<br />
#Provide a flexible framework for interoperability<br />
#Keep complexity where it belongs<br />
#Support but not mandate tight specifications<br />
#Leverage open source development principles<br />
#Free to use<br />
#Supports multiple exchange paradigms/architectures<br />
#Leverage common web technologies<br />
#Forward and backward compatibility<br />
#Tooling requirements are mainstream and minimal<br />
<br />
===FHIR Basics===<br />
<br />
Resources are classified as either clinical, administrative, or infrastructural. These resources were developed from HL7v2 and from HL7v3's Reference Information Model (RIM); as such they are intended to coexist with previous HL7 standards<ref name="dtsu2014" />. Resources are accessed via web protocol calls to specific URLs, and represented using either [[XML]] or [[JSON]] format. Resources are exchanged and manipulated via PUT, GET, POST, and DELETE operations via individual APIs. Using these APIs, the resources can be queried by a receiving system or pushed from a host system.<br />
<br />
FHIR resources have related profiles to specify their metadata, associated structures, and relevant extensions used in those structures. Resource metadata includes resource ID, version ID, last modified date, and other information. Metadata can contain tags linking a specific resource to a workflow event; these tags can be used to trigger events that initiate system interactions. Metadata also allows for resources to be searched efficiently. Resources can also be referenced by one another using resource links, allowing for connection of various data elements.<br />
<br />
===Resource Classifications===<br />
Individual resources are contained within one of three primary categories, then sub-classified within each category<ref name="dtsu2014" />:<br />
<br />
# '''Clinical'''<br />
#* General<br />
#* Medications<br />
#* Diagnostic<br />
#* Device Interactions<br />
# '''Administrative'''<br />
#* Attribution<br />
#* Entities<br />
#* Workflow Management<br />
#* Financial<br />
# '''Infrastructural'''<br />
#* Support<br />
#* Document Handling<br />
#* Exchange<br />
#* Conformance<br />
<br />
===FHIR enabled apps in use today===<br />
<br />
[[SMART uses for public health|Sustainable Medical Applications, Reusable Technologies (SMART)]] is a collaboration between the Harvard Medical School and the Office of the National Coordinator for Health Information Technology ([[ONC]]). SMART sought to develop a platform for the rapid development of health applications that could run across multiple EHRs<ref name="raths2014">Raths, D. (2014). "Trend: standards development. Catching FHIR: A new HL7 draft standard may boost web services development in healthcare." Healthcare Inform 31(2): 13, 16.</ref>. They succeeded, and now a variety of apps are "SMART-enabled". The apps are used in clinical back-office settings, research, patient communication and patient facing applications<ref name="smart2014">SMART. (2014). SMART-Enabled HIT. Accessed October 23, 2014 from http://smartplatforms.org/smart-enabled-hit/</ref>.<br />
<br />
FHIR is also gaining support in the U.K. Nearly ten apps have already been developed for use in various setting. Additionally, an alliance with the UK Renal Data Collaboration is planned.<br />
<br />
==Related Pages==<br />
* Review of Bender, D., & Sartipi, K. (2013, June). [[HL7 FHIR: An Agile and RESTful approach to healthcare information exchange]]. In 2013 IEEE 26th International Symposium on Computer-Based Medical Systems (CBMS) (pp. 326-331). IEEE.<br />
* Review of Kasthurirathne, S., Mamlin, B., Kumara, H., Grieve, G., & Biondich, P. (2015). [[Enabling Better Interoperability for HealthCare: Lessons in Developing a Standards Based Application Programing Interface for Electronic Medical Record Systems]]. J Med Syst Journal of Medical Systems, 39(182).<br />
* Review of Smits, M., Kramer, E., Harthoorn, M., & Cornet, R. (2015). [[A comparison of two Detailed Clinical Model representations: FHIR and CDA]]. ''European Journal for Biomedical Informatics, 11''(2), 7-17.<br />
*[[Trusted Exchange Framework and Common Agreement (TEFCA)]] <br />
<br />
===References===<br />
<references/><br />
<br />
[[Category:BMI512-FALL-14]]<br />
[[Category:Interoperability]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T16:24:33Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF)==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
TEFCA establishes QHIN to standardize HIE inter-connectivity. Each health information network has to enter into agreements with TEFCA which facilitates the standardized methodology to share information. Once they have made these agreements they are able to become a qualified health information network (QHIN)<ref>https://www.impact-advisors.com/regulatory/interoperability/tefca-in-a-nutshell/</ref>.<br />
<br />
A recognized coordination entity is established to act as the governing body of multiple QHINs. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The second draft addresses principles for trusted exchange networks that apply to HINs. It expanded the definition to allow for a larger application pool to be considered for QHIN<ref>https://www.impact-advisors.com/regulatory/tefca/tefca-nutshell-part-2/</ref>.<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs)==<br />
These are the mandatory terms and condition that bind those who elect to sign the Common Agreement. Under MRTC draft 2, the Common Agreement specifies greater privacy and security protections for all groups who elect to participate. This will also cover entities not covered by Health Insurance Portabilty and Accountabilty Act (HIPAA)<ref>https://www.himss.org/news/onc-releases-second-draft-tefca-public-comment</ref>.<br />
<br />
== The QHIN Technical Framework (QTF)==<br />
The QHIN technical framework (QTF) provides additional information regarding the technical requirements to exchange information among QHINs.<br />
<br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T16:02:35Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF)==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
TEFCA establishes QHIN to standardize HIE inter-connectivity. Each health information network has to enter into agreements with TEFCA which facilitates the standardized methodology to share information. Once they have made these agreements they are able to become a qualified health information network (QHIN)<ref>https://www.impact-advisors.com/regulatory/interoperability/tefca-in-a-nutshell/</ref>.<br />
<br />
A recognized coordination entity is established to act as the governing body of multiple QHINs. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The second draft addresses principles for trusted exchange networks that apply to HINs. It expanded the definition to allow for a larger application pool to be considered for QHIN.<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs)==<br />
These are the mandatory terms and condition that bind those who elect to sign the Common Agreement. Under MRTC draft 2, the Common Agreement specifies greater privacy and security protections for all groups who elect to participate. This will also cover entities not covered by Health Insurance Portabilty and Accountabilty Act (HIPAA)<ref>https://www.himss.org/news/onc-releases-second-draft-tefca-public-comment</ref>.<br />
<br />
== The QHIN Technical Framework (QTF)==<br />
The QHIN technical framework (QTF) provides additional information regarding the technical requirements to exchange information among QHINs.<br />
<br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T15:48:47Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF)==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
TEFCA establishes QHIN to standardize HIE inter-connectivity. Each health information network has to enter into agreements with TEFCA which facilitates the standardized methodology to share information. Once they have made these agreements they are able to become a qualified health information network (QHIN)<ref>https://www.impact-advisors.com/regulatory/interoperability/tefca-in-a-nutshell/</ref>.<br />
<br />
A recognized coordination entity is established to act as the governing body of multiple QHINs. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The second draft addresses principles for trusted exchange networks that apply to HINs.<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs)==<br />
These are the mandatory terms and condition that bind those who elect to sign the Common Agreement.<br />
<br />
== The QHIN Technical Framework (QTF)==<br />
The QHIN<br />
<br />
<br />
<br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T15:33:28Z<p>Erickchristensen: /* Recognized Coordinating Entity (RCE) */</p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
TEFCA establishes QHIN to standardize HIE inter-connectivity. Each health information network has to enter into agreements with TEFCA which facilitates the standardized methodology to share information. Once they have made these agreements they are able to become a qualified health information network (QHIN)<ref>https://www.impact-advisors.com/regulatory/interoperability/tefca-in-a-nutshell/</ref>.<br />
<br />
A recognized coordination entity is established to act as the governing body of multiple QHINs. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. <br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
== Recognized Coordinating Entity (RCE) ==<br />
'<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T15:32:54Z<p>Erickchristensen: /* Recognized Coordinating Entity (RCE) */</p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
TEFCA establishes QHIN to standardize HIE inter-connectivity. Each health information network has to enter into agreements with TEFCA which facilitates the standardized methodology to share information. Once they have made these agreements they are able to become a qualified health information network (QHIN)<ref>https://www.impact-advisors.com/regulatory/interoperability/tefca-in-a-nutshell/</ref>.<br />
<br />
A recognized coordination entity is established to act as the governing body of multiple QHINs. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. <br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
===== Recognized Coordinating Entity (RCE) =====<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T15:32:24Z<p>Erickchristensen: /* Recognized Coordinating Entity (RCE) */</p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
TEFCA establishes QHIN to standardize HIE inter-connectivity. Each health information network has to enter into agreements with TEFCA which facilitates the standardized methodology to share information. Once they have made these agreements they are able to become a qualified health information network (QHIN)<ref>https://www.impact-advisors.com/regulatory/interoperability/tefca-in-a-nutshell/</ref>.<br />
<br />
A recognized coordination entity is established to act as the governing body of multiple QHINs. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. <br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
==== Recognized Coordinating Entity (RCE) ====<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T15:32:04Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
TEFCA establishes QHIN to standardize HIE inter-connectivity. Each health information network has to enter into agreements with TEFCA which facilitates the standardized methodology to share information. Once they have made these agreements they are able to become a qualified health information network (QHIN)<ref>https://www.impact-advisors.com/regulatory/interoperability/tefca-in-a-nutshell/</ref>.<br />
<br />
A recognized coordination entity is established to act as the governing body of multiple QHINs. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. <br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
=== Recognized Coordinating Entity (RCE) ===<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T15:26:48Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
TEFCA establishes QHIN to standardize HIE inter-connectivity. Each health information network has to enter into agreements with TEFCA which facilitates the standardized methodology to share information. Once they have made these agreements they are able to become a qualified health information network (QHIN)<ref>https://www.impact-advisors.com/regulatory/interoperability/tefca-in-a-nutshell/</ref>.<br />
<br />
A recognized coordination entity is established to act as the governing body of multiple QHINs. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. <br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
== Recognized Coordinating Entity (RCE) ==<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T15:22:25Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
TEFCA establishes QHIN to standardize HIE inter-connectivity. Each health information network has to enter into agreements with TEFCA which facilitates the standardized methodology to share information. Once they have made these agreements they are able to become a qualified health information network (QHIN).<br />
<br />
A recognized coordination entity is established to act as the governing body of multiple QHINs. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. <br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
== Recognized Coordinating Entity (RCE) ==<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T14:54:24Z<p>Erickchristensen: /* The Trusted Exchange Framework (TEF) Draft 2 */</p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. <br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
== Recognized Coordinating Entity (RCE) ==<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T14:44:43Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>. The framework focused on:<br />
<br />
*Empowering individuals to use their Electronic Health Information to the fullest extent;<br />
*Enabling providers and communities to deliver smarter, safer, and more efficient care; and<br />
*Promotes innovation at all levels<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>.<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
== Recognized Coordinating Entity (RCE) ==<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T14:33:51Z<p>Erickchristensen: /* The Trusted Exchange Framework (TEF) Draft 1 */</p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEF was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
== Recognized Coordinating Entity (RCE) ==<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T14:32:57Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to allow healthcare stakeholders to exchange information across health information networks (HIN).<br />
<br />
<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. It provides a framework and vision for how qualified health information networks (QHIN) and the recognized coordinating entity (RCE) function. Of note, on September 3, 2019 ONC awarded The Sequoia Project a cooperative agreement to serve as the RCE<ref> https://www.hhs.gov/about/news/2019/09/03/onc-awards-the-sequoia-project-cooperative-agreement.html</ref>.<br />
<br />
<br />
<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
== Recognized Coordinating Entity (RCE) ==<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T14:03:00Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA) outline a set of principles, terms and conditions to facilitate the development of health information exchange network across the nation<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref>. The process engages Government, private and public entities to develop a common agreement to exchange information across health information networks (HIN).<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 5, 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. The framework addresses the need for an trusted exchange outlines ways to achieve the vision of a system where patient<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 19, 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
== Recognized Coordinating Entity (RCE) ==<br />
<br />
<br />
<br />
<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref><br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T13:32:34Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. The framework addresses the need for an trusted exchange outlines ways to achieve the vision of a system where patient<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== The Trusted Exchange Framework (TEF) Draft 2 ==<br />
Draft 2 was published in April 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
== The Minimum Required Terms and Conditions (MRTCs) Draft 2 ==<br />
<br />
== The QHIN Technical Framework (QTF) Draft 1 ==<br />
<br />
== Recognized Coordinating Entity (RCE) ==<br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T13:28:25Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
== TEF Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. The framework addresses the need for an trusted exchange outlines ways to achieve the vision of a system where patient<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== TEF Draft 2 ==<br />
Draft 2 was published in April 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
<br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T13:28:02Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
== TEF Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. The framework addresses the need for an trusted exchange outlines ways to achieve the vision of a system where patient<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== TEF Draft 2 ==<br />
*Draft 2 was published in April 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
<br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-18T13:25:16Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
== TEF Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. The framework addresses the need for an trusted exchange outlines ways to achieve the vision of a system where patient<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== TEF Draft 2 ==<br />
Draft 2 was published in April 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
<br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T20:13:41Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
== TEFCA Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. The framework addresses the need for an trusted exchange outlines ways to achieve the vision of a system where patient<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
== TEFCA Draft 2 ==<br />
Draft 2 was published in April 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
== References ==<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T20:13:27Z<p>Erickchristensen: /* TEFCA Draft 1 */</p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
== TEFCA Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. The framework addresses the need for an trusted exchange outlines ways to achieve the vision of a system where patient<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This<br />
<br />
= TEFCA Draft 2 =<br />
Draft 2 was published in April 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
= References =<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T20:13:19Z<p>Erickchristensen: /* TEFCA Draft 2 */</p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
== TEFCA Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. The framework addresses the need for an trusted exchange outlines ways to achieve the vision of a system where patient<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This <br />
<br />
= TEFCA Draft 2 =<br />
Draft 2 was published in April 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
= References =<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T20:08:10Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
== TEFCA Draft 1 ==<br />
The first draft of TEFCA was published by the ONC (Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/sites/default/files/draft-trusted-exchange-framework.pdf</ref>. The framework addresses the need for an trusted exchange outlines ways to achieve the vision of a system where patient<br />
the Health Information Technology for Economic and Clinical Health (HITECH) Act of 2009. This <br />
<br />
== TEFCA Draft 2 ==<br />
Draft 2 was published in April 2019<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref><br />
<br />
= References =<br />
<references/><br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T19:53:43Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
== TEFCA Draft 1 ==<br />
The first draft of TEFCA was published by the ONC ( Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref> . The framework outlines <br />
<br />
<br />
<br />
= References =<br />
<references/><br />
<br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T19:52:59Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
The first draft of TEFCA was published by the ONC ( Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref> . The framework outlines <br />
<br />
<br />
<br />
= References =<br />
<references/><br />
<br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T19:52:38Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
The first draft of TEFCA was published by the ONC ( Office of the National Coordinator for Health Information Technology) in January 2018<ref>https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement</ref> . The framework outlines <br />
<br />
<br />
<br />
= References =<br />
<references/><br />
<br />
<br />
1. https://www.healthit.gov/topic/interoperability/trusted-exchange-framework-and-common-agreement<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T19:42:29Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
The first draft of TEFCA was published by the ONC ( Office of the National Coordinator for Health Information Technology) in January 2018. The framework outlines <br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]<br />
[[Category:Government, Public and Private Initiatives | Government, Public and Private Initiatives]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T19:27:56Z<p>Erickchristensen: </p>
<hr />
<div>Trusted Exchange Framework and Common Agreement (TEFCA)<br />
<br />
<br />
<br />
Submitted by Erick Christensen<br />
[[Category:BMI512-FALL-19]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/Trusted_Exchange_Framework_and_Common_Agreement_(TEFCA)Trusted Exchange Framework and Common Agreement (TEFCA)2019-10-17T15:38:20Z<p>Erickchristensen: Replaced content with "TEFCA"</p>
<hr />
<div>TEFCA</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/HL7_FHIRHL7 FHIR2019-10-17T15:37:12Z<p>Erickchristensen: </p>
<hr />
<div>===What is FHIR?===<br />
<br />
Fast Healthcare Interoperability Resources (FHIR) is an interoperability standard created by [[HL7]]. FHIR utilizes a more modular approach to inter-system messaging than previous HL7 standards versions. These modules, termed "resources", allow implementations to be more flexible to changing system processes than the traditional HL7V2 or V3 standards. The initial version of FHIR was created in 2012 and has undergone multiple revisions to date. There is currently an implementation standard in the draft standard for trial use (DTSU) phase, and not yet fully approved. Balloting for the current DSTU is slated for April of 2015 with a projected release of DSTU 2 for July 2015. <ref name="dtsu2014">FHIR DTSU v. 1.1. (2014). Retrieved October 21, 2014 from http://www.hl7.org/implement/standards/fhir/index.html</ref><br />
Rather than using multi-element structured messages such at HL7v2, HL7v3, and [[CDA]] standards, FHIR uses application programming interfaces (APIs) to select specific elements vs. the entire message as in the older HL7 standards. These APIs utilize a "RESTful" architecture, designed for web applications<ref name="dtsu2014" /><ref name="mckenzie2013">Mckenzie, L. (2013, May 13)Introduction to FHIR. Retrieved October 20, 2014 from http://gforge.hl7.org/svn/fhir/trunk/presentations/2013-05%20Tutorials/Introduction%20to%20FHIR.pptx</ref>. REST stands for Representational State Transfer which allows for exchange of resources on an as needed basis, typically communicated via widely used HTTP or HTTPS protocols<ref name="restful2013">What exactly is RESTful programming? (2013, Jan 16). Retrieved October 23, 2014 from http://stackoverflow.com/questions/671118/what-exactly-is-restful-programming</ref>.<br />
<br />
[[Trusted Exchange Framework and Common Agreement (TEFCA)]]<br />
<br />
===FHIR Governance=== <br />
<br />
FHIR is governed by three separate bodies within HL7. The FHIR Governance Board, appointed by the FHIR Technical Steering Committee, provides broad oversight of the standard. The FHIR Management Group, also appointed by the Technical Steering Committee, manages the day-to-day operations of the standard. Finally, the Modeling and Methodology Work Group handles the resource creation, guidelines, and best practices<ref name="hl7wiki">HL7. (2014, Oct 22) FHIR Wiki. Retrieved October 23, 2014 from http://wiki.hl7.org/index.php?title=FHIR</ref>.<br />
<br />
===Why FHIR?===<br />
<br />
FHIR is HL7's answer to the call for a new interoperability standard that could more easily be used on mobile and cloud-based applications, and also speed the implementation process. These implementations can often be completed within a day or week, versus the traditional month- or year-long implementation timeline<ref name="dtsu2014" />. FHIR is a needed update to HL7v2, but expected to be much less disruptive to workflows than HL7v3.<br />
<br />
The specification is free and allows unrestricted use. FHIR uses the building blocks of HL7v2, HL7v3, and [[CDA]] while improving the ease of use and flexibility to alter implementations as needed. The RESTful architecture is applied to web services to allow for easy transfer of resources between systems, since they can be accessed through a uniform resource locator (URL). Due to this architecture, FHIR is well suited for mobile and cloud-based platforms.<br />
<br />
The RESTful API architecture also allows for transfer of data between systems without requiring the receiving system to know the structure of the API itself. This simplifies the interface between systems. (3) Once called to the receiving system, these individual resources can be extended and adapted based on individual implementation needs<ref name="dtsu2014" />.<br />
<br />
===The FHIR Code===<br />
From "Fundamental Principles of FHIR (aka The FHIR Code)"<ref name="fundprinc">Fundamental Principles of FHIR. (16 Sept 2014, 20:28). Retrieved 6 Dec 2015 from http://wiki.hl7.org/index.php?title=Fundamental_Principles_of_FHIR&oldid=90696</ref>.<br />
#Prioritize implementation<br />
#Provide a flexible framework for interoperability<br />
#Keep complexity where it belongs<br />
#Support but not mandate tight specifications<br />
#Leverage open source development principles<br />
#Free to use<br />
#Supports multiple exchange paradigms/architectures<br />
#Leverage common web technologies<br />
#Forward and backward compatibility<br />
#Tooling requirements are mainstream and minimal<br />
<br />
===FHIR Basics===<br />
<br />
Resources are classified as either clinical, administrative, or infrastructural. These resources were developed from HL7v2 and from HL7v3's Reference Information Model (RIM); as such they are intended to coexist with previous HL7 standards<ref name="dtsu2014" />. Resources are accessed via web protocol calls to specific URLs, and represented using either [[XML]] or [[JSON]] format. Resources are exchanged and manipulated via PUT, GET, POST, and DELETE operations via individual APIs. Using these APIs, the resources can be queried by a receiving system or pushed from a host system.<br />
<br />
FHIR resources have related profiles to specify their metadata, associated structures, and relevant extensions used in those structures. Resource metadata includes resource ID, version ID, last modified date, and other information. Metadata can contain tags linking a specific resource to a workflow event; these tags can be used to trigger events that initiate system interactions. Metadata also allows for resources to be searched efficiently. Resources can also be referenced by one another using resource links, allowing for connection of various data elements.<br />
<br />
===Resource Classifications===<br />
Individual resources are contained within one of three primary categories, then sub-classified within each category<ref name="dtsu2014" />:<br />
<br />
# '''Clinical'''<br />
#* General<br />
#* Medications<br />
#* Diagnostic<br />
#* Device Interactions<br />
# '''Administrative'''<br />
#* Attribution<br />
#* Entities<br />
#* Workflow Management<br />
#* Financial<br />
# '''Infrastructural'''<br />
#* Support<br />
#* Document Handling<br />
#* Exchange<br />
#* Conformance<br />
<br />
===FHIR enabled apps in use today===<br />
<br />
[[SMART uses for public health|Sustainable Medical Applications, Reusable Technologies (SMART)]] is a collaboration between the Harvard Medical School and the Office of the National Coordinator for Health Information Technology ([[ONC]]). SMART sought to develop a platform for the rapid development of health applications that could run across multiple EHRs<ref name="raths2014">Raths, D. (2014). "Trend: standards development. Catching FHIR: A new HL7 draft standard may boost web services development in healthcare." Healthcare Inform 31(2): 13, 16.</ref>. They succeeded, and now a variety of apps are "SMART-enabled". The apps are used in clinical back-office settings, research, patient communication and patient facing applications<ref name="smart2014">SMART. (2014). SMART-Enabled HIT. Accessed October 23, 2014 from http://smartplatforms.org/smart-enabled-hit/</ref>.<br />
<br />
FHIR is also gaining support in the U.K. Nearly ten apps have already been developed for use in various setting. Additionally, an alliance with the UK Renal Data Collaboration is planned.<br />
<br />
==Related Pages==<br />
* Review of Bender, D., & Sartipi, K. (2013, June). [[HL7 FHIR: An Agile and RESTful approach to healthcare information exchange]]. In 2013 IEEE 26th International Symposium on Computer-Based Medical Systems (CBMS) (pp. 326-331). IEEE.<br />
* Review of Kasthurirathne, S., Mamlin, B., Kumara, H., Grieve, G., & Biondich, P. (2015). [[Enabling Better Interoperability for HealthCare: Lessons in Developing a Standards Based Application Programing Interface for Electronic Medical Record Systems]]. J Med Syst Journal of Medical Systems, 39(182).<br />
* Review of Smits, M., Kramer, E., Harthoorn, M., & Cornet, R. (2015). [[A comparison of two Detailed Clinical Model representations: FHIR and CDA]]. ''European Journal for Biomedical Informatics, 11''(2), 7-17.<br />
<br />
<br />
===References===<br />
<references/><br />
<br />
[[Category:BMI512-FALL-14]]<br />
[[Category:Interoperability]]</div>Erickchristensenhttp://clinfowiki.org/wiki/index.php/HL7_FHIRHL7 FHIR2019-10-17T15:36:07Z<p>Erickchristensen: /* What is FHIR? */</p>
<hr />
<div>===What is FHIR?===<br />
<br />
Fast Healthcare Interoperability Resources (FHIR) is an interoperability standard created by [[HL7]]. FHIR utilizes a more modular approach to inter-system messaging than previous HL7 standards versions. These modules, termed "resources", allow implementations to be more flexible to changing system processes than the traditional HL7V2 or V3 standards. The initial version of FHIR was created in 2012 and has undergone multiple revisions to date. There is currently an implementation standard in the draft standard for trial use (DTSU) phase, and not yet fully approved. Balloting for the current DSTU is slated for April of 2015 with a projected release of DSTU 2 for July 2015. <ref name="dtsu2014">FHIR DTSU v. 1.1. (2014). Retrieved October 21, 2014 from http://www.hl7.org/implement/standards/fhir/index.html</ref><br />
Rather than using multi-element structured messages such at HL7v2, HL7v3, and [[CDA]] standards, FHIR uses application programming interfaces (APIs) to select specific elements vs. the entire message as in the older HL7 standards. These APIs utilize a "RESTful" architecture, designed for web applications<ref name="dtsu2014" /><ref name="mckenzie2013">Mckenzie, L. (2013, May 13)Introduction to FHIR. Retrieved October 20, 2014 from http://gforge.hl7.org/svn/fhir/trunk/presentations/2013-05%20Tutorials/Introduction%20to%20FHIR.pptx</ref>. REST stands for Representational State Transfer which allows for exchange of resources on an as needed basis, typically communicated via widely used HTTP or HTTPS protocols<ref name="restful2013">What exactly is RESTful programming? (2013, Jan 16). Retrieved October 23, 2014 from http://stackoverflow.com/questions/671118/what-exactly-is-restful-programming</ref>.<br />
<br />
===FHIR Governance=== <br />
<br />
FHIR is governed by three separate bodies within HL7. The FHIR Governance Board, appointed by the FHIR Technical Steering Committee, provides broad oversight of the standard. The FHIR Management Group, also appointed by the Technical Steering Committee, manages the day-to-day operations of the standard. Finally, the Modeling and Methodology Work Group handles the resource creation, guidelines, and best practices<ref name="hl7wiki">HL7. (2014, Oct 22) FHIR Wiki. Retrieved October 23, 2014 from http://wiki.hl7.org/index.php?title=FHIR</ref>.<br />
<br />
===Why FHIR?===<br />
<br />
FHIR is HL7's answer to the call for a new interoperability standard that could more easily be used on mobile and cloud-based applications, and also speed the implementation process. These implementations can often be completed within a day or week, versus the traditional month- or year-long implementation timeline<ref name="dtsu2014" />. FHIR is a needed update to HL7v2, but expected to be much less disruptive to workflows than HL7v3.<br />
<br />
The specification is free and allows unrestricted use. FHIR uses the building blocks of HL7v2, HL7v3, and [[CDA]] while improving the ease of use and flexibility to alter implementations as needed. The RESTful architecture is applied to web services to allow for easy transfer of resources between systems, since they can be accessed through a uniform resource locator (URL). Due to this architecture, FHIR is well suited for mobile and cloud-based platforms.<br />
<br />
The RESTful API architecture also allows for transfer of data between systems without requiring the receiving system to know the structure of the API itself. This simplifies the interface between systems. (3) Once called to the receiving system, these individual resources can be extended and adapted based on individual implementation needs<ref name="dtsu2014" />.<br />
<br />
===The FHIR Code===<br />
From "Fundamental Principles of FHIR (aka The FHIR Code)"<ref name="fundprinc">Fundamental Principles of FHIR. (16 Sept 2014, 20:28). Retrieved 6 Dec 2015 from http://wiki.hl7.org/index.php?title=Fundamental_Principles_of_FHIR&oldid=90696</ref>.<br />
#Prioritize implementation<br />
#Provide a flexible framework for interoperability<br />
#Keep complexity where it belongs<br />
#Support but not mandate tight specifications<br />
#Leverage open source development principles<br />
#Free to use<br />
#Supports multiple exchange paradigms/architectures<br />
#Leverage common web technologies<br />
#Forward and backward compatibility<br />
#Tooling requirements are mainstream and minimal<br />
<br />
===FHIR Basics===<br />
<br />
Resources are classified as either clinical, administrative, or infrastructural. These resources were developed from HL7v2 and from HL7v3's Reference Information Model (RIM); as such they are intended to coexist with previous HL7 standards<ref name="dtsu2014" />. Resources are accessed via web protocol calls to specific URLs, and represented using either [[XML]] or [[JSON]] format. Resources are exchanged and manipulated via PUT, GET, POST, and DELETE operations via individual APIs. Using these APIs, the resources can be queried by a receiving system or pushed from a host system.<br />
<br />
FHIR resources have related profiles to specify their metadata, associated structures, and relevant extensions used in those structures. Resource metadata includes resource ID, version ID, last modified date, and other information. Metadata can contain tags linking a specific resource to a workflow event; these tags can be used to trigger events that initiate system interactions. Metadata also allows for resources to be searched efficiently. Resources can also be referenced by one another using resource links, allowing for connection of various data elements.<br />
<br />
===Resource Classifications===<br />
Individual resources are contained within one of three primary categories, then sub-classified within each category<ref name="dtsu2014" />:<br />
<br />
# '''Clinical'''<br />
#* General<br />
#* Medications<br />
#* Diagnostic<br />
#* Device Interactions<br />
# '''Administrative'''<br />
#* Attribution<br />
#* Entities<br />
#* Workflow Management<br />
#* Financial<br />
# '''Infrastructural'''<br />
#* Support<br />
#* Document Handling<br />
#* Exchange<br />
#* Conformance<br />
<br />
===FHIR enabled apps in use today===<br />
<br />
[[SMART uses for public health|Sustainable Medical Applications, Reusable Technologies (SMART)]] is a collaboration between the Harvard Medical School and the Office of the National Coordinator for Health Information Technology ([[ONC]]). SMART sought to develop a platform for the rapid development of health applications that could run across multiple EHRs<ref name="raths2014">Raths, D. (2014). "Trend: standards development. Catching FHIR: A new HL7 draft standard may boost web services development in healthcare." Healthcare Inform 31(2): 13, 16.</ref>. They succeeded, and now a variety of apps are "SMART-enabled". The apps are used in clinical back-office settings, research, patient communication and patient facing applications<ref name="smart2014">SMART. (2014). SMART-Enabled HIT. Accessed October 23, 2014 from http://smartplatforms.org/smart-enabled-hit/</ref>.<br />
<br />
FHIR is also gaining support in the U.K. Nearly ten apps have already been developed for use in various setting. Additionally, an alliance with the UK Renal Data Collaboration is planned.<br />
<br />
==Related Pages==<br />
* Review of Bender, D., & Sartipi, K. (2013, June). [[HL7 FHIR: An Agile and RESTful approach to healthcare information exchange]]. In 2013 IEEE 26th International Symposium on Computer-Based Medical Systems (CBMS) (pp. 326-331). IEEE.<br />
* Review of Kasthurirathne, S., Mamlin, B., Kumara, H., Grieve, G., & Biondich, P. (2015). [[Enabling Better Interoperability for HealthCare: Lessons in Developing a Standards Based Application Programing Interface for Electronic Medical Record Systems]]. J Med Syst Journal of Medical Systems, 39(182).<br />
* Review of Smits, M., Kramer, E., Harthoorn, M., & Cornet, R. (2015). [[A comparison of two Detailed Clinical Model representations: FHIR and CDA]]. ''European Journal for Biomedical Informatics, 11''(2), 7-17.<br />
<br />
<br />
===References===<br />
<references/><br />
<br />
[[Category:BMI512-FALL-14]]<br />
[[Category:Interoperability]]</div>Erickchristensen