[{"innerBlocks":[],"name":"core\/freeform","postId":1257,"blockType":{"name":"core\/freeform","keywords":[],"attributes":{"content":{"type":"string","source":"raw"},"lock":{"type":"object"}},"providesContext":[],"usesContext":[],"selectors":[],"supports":{"className":false,"customClassName":false,"reusable":false},"styles":[],"variations":[],"apiVersion":3,"title":"Classic","description":"Use the classic WordPress editor.","category":"text"},"originalContent":"If the Office of the National Coordinator for Health IT has its way, HL7\u2019s Fast Healthcare Interoperability Resources will be the standard to which developers must certify their application programming interfaces.

In ONC\u2019s proposed rule, released on Monday, the agency for the first time has said that it intends to make FHIR a requirement.

Congress required developers participating in the ONC Health IT Certification Program to publish APIs allowing healthcare data to be accessed, exchanged and used \u201cwithout special effort\u201d as a provision of the 21st Century Cures Act.

\u201cWhile there are a variety of relevant healthcare standards for connecting labs, images, claims processing systems, and other pieces of the provider world, when we look at the app economy and the clear trends in modern computing, one API approach seems to clearly emerge\u2013Health Level Seven\u2019s Fast Healthcare Interoperability Resources standards,\u201d wrote National Coordinator for HIT Don Rucker in a blog post regarding ONC\u2019s proposed rule.

\u201cWe believe this approach could lead to industry standard interfaces\u2014interfaces where app developers can develop effective apps that use API technology \u2018without special effort\u2019 to access a patient\u2019s data,\u201d added Rucker.

App developers, health IT vendors, and providers have widely embraced FHIR to help solve the interoperability challenges confronting the healthcare industry as it seeks to increase access to electronic health records and data sharing.

\u201cThe important issue is that we have come to a point where it\u2019s time to agree this is how we\u2019re going to share data,\u201d says Chuck Jaffe, MD, HL7\u2019s CEO, who adds that he wasn\u2019t surprised by ONC\u2019s proposed rule. \u201cThe critical mass has already been achieved\u2014that is, there are enough people who are committed to FHIR that it is a reality. It\u2019s not a draft, an experiment, or an academic concept. It\u2019s real.\u201d

Also See:<\/b> FHIR standard adoption in the U.S. is at a turning point<\/a>

\u201cThe ONC rule not only emphasizes FHIR as the API standard of choice, but it prohibits charging for API access and restricts data blocking,\u201d observed John Halamka, MD, chief information officer at Boston\u2019s Beth Israel Deaconess Medical Center. \u201cThe entire package will accelerate interoperability across all stakeholders.\u201d

\u201cThey should have required FHIR in the first place\u2014it\u2019s about time that they did,\u201d observed Graham Grieve, FHIR\u2019s product director. \u201cI\u2019m pleased to see FHIR written into the regulations with testing.\u201d

In its proposed rule, ONC specifically would make FHIR Release 2 a requirement, according to Steve Posnack, executive director of ONC\u2019s office of technology.

Posnack said that the agency decided to require FHIR Release 2 given that its research late last year indicated that 87 percent of hospitals and 57 percent of Merit-based Incentive Payment System-eligible clinicians are served by health IT developers with products certified to FHIR Release 2.

\u201cWe\u2019re trying to meet the market where it\u2019s best prepared to accelerate the use of FHIR,\u201d commented Posnack. At the same time, he acknowledged that last month HL7 published FHIR Release 4\u2014the normative version of the interoperability standard.

However, Posnack insists that ONC \u201chas a number of different options in terms of what we can finalize (in the rule) to allow industry leaders to perhaps take a step forward and go directly to FHIR Release 4.\u201d

According to HL7, the most significant advancement with FHIR Release 4 is that the base platform of the standard has passed a normative ballot and has been submitted to the American National Standards Institute as such.

\u201cIn addition to the ONC rulemaking, the recent progress for FHIR to become normative allows folks who might have been waiting on the sidelines to start to participate,\u201d said Jocelyn Keegan project manager for the Da Vinci Project, a payer-provider led initiative to leverage FHIR to exchange critical data required for value-based care delivery.","saveContent":"If the Office of the National Coordinator for Health IT has its way, HL7\u2019s Fast Healthcare Interoperability Resources will be the standard to which developers must certify their application programming interfaces.

In ONC\u2019s proposed rule, released on Monday, the agency for the first time has said that it intends to make FHIR a requirement.

Congress required developers participating in the ONC Health IT Certification Program to publish APIs allowing healthcare data to be accessed, exchanged and used \u201cwithout special effort\u201d as a provision of the 21st Century Cures Act.

\u201cWhile there are a variety of relevant healthcare standards for connecting labs, images, claims processing systems, and other pieces of the provider world, when we look at the app economy and the clear trends in modern computing, one API approach seems to clearly emerge\u2013Health Level Seven\u2019s Fast Healthcare Interoperability Resources standards,\u201d wrote National Coordinator for HIT Don Rucker in a blog post regarding ONC\u2019s proposed rule.

\u201cWe believe this approach could lead to industry standard interfaces\u2014interfaces where app developers can develop effective apps that use API technology \u2018without special effort\u2019 to access a patient\u2019s data,\u201d added Rucker.

App developers, health IT vendors, and providers have widely embraced FHIR to help solve the interoperability challenges confronting the healthcare industry as it seeks to increase access to electronic health records and data sharing.

\u201cThe important issue is that we have come to a point where it\u2019s time to agree this is how we\u2019re going to share data,\u201d says Chuck Jaffe, MD, HL7\u2019s CEO, who adds that he wasn\u2019t surprised by ONC\u2019s proposed rule. \u201cThe critical mass has already been achieved\u2014that is, there are enough people who are committed to FHIR that it is a reality. It\u2019s not a draft, an experiment, or an academic concept. It\u2019s real.\u201d

Also See:<\/b> FHIR standard adoption in the U.S. is at a turning point<\/a>

\u201cThe ONC rule not only emphasizes FHIR as the API standard of choice, but it prohibits charging for API access and restricts data blocking,\u201d observed John Halamka, MD, chief information officer at Boston\u2019s Beth Israel Deaconess Medical Center. \u201cThe entire package will accelerate interoperability across all stakeholders.\u201d

\u201cThey should have required FHIR in the first place\u2014it\u2019s about time that they did,\u201d observed Graham Grieve, FHIR\u2019s product director. \u201cI\u2019m pleased to see FHIR written into the regulations with testing.\u201d

In its proposed rule, ONC specifically would make FHIR Release 2 a requirement, according to Steve Posnack, executive director of ONC\u2019s office of technology.

Posnack said that the agency decided to require FHIR Release 2 given that its research late last year indicated that 87 percent of hospitals and 57 percent of Merit-based Incentive Payment System-eligible clinicians are served by health IT developers with products certified to FHIR Release 2.

\u201cWe\u2019re trying to meet the market where it\u2019s best prepared to accelerate the use of FHIR,\u201d commented Posnack. At the same time, he acknowledged that last month HL7 published FHIR Release 4\u2014the normative version of the interoperability standard.

However, Posnack insists that ONC \u201chas a number of different options in terms of what we can finalize (in the rule) to allow industry leaders to perhaps take a step forward and go directly to FHIR Release 4.\u201d

According to HL7, the most significant advancement with FHIR Release 4 is that the base platform of the standard has passed a normative ballot and has been submitted to the American National Standards Institute as such.

\u201cIn addition to the ONC rulemaking, the recent progress for FHIR to become normative allows folks who might have been waiting on the sidelines to start to participate,\u201d said Jocelyn Keegan project manager for the Da Vinci Project, a payer-provider led initiative to leverage FHIR to exchange critical data required for value-based care delivery.","order":0,"get_parent":{},"attributes":[],"attributesType":{"content":{"type":"string","source":"raw"},"lock":{"type":"object"}},"dynamicContent":""}]

Proposed ONC rule requires FHIR interoperability standard

More for you