[{"innerBlocks":[],"name":"core\/freeform","postId":1043,"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":"Kansas City-based Cerner has embraced the latest version of HL7\u2019s Fast Healthcare Interoperability Resources standard to encourage third-party developers to build apps on top of its platforms.

By adopting FHIR Release 4, the normative version of the interoperability standard, Cerner contends that it is positioned at the \u201cleading edge\u201d in creating healthcare apps and opening its application programming interfaces (APIs) to developers to foster innovation.

\u201cWe\u2019ve invested in R4 in a significant way as part of our broader strategy at Cerner around advancing interoperability as well as enhancing our ability to facilitate third-party provider, clinical apps and consumer apps integration into our platforms,\u201d says Matt Obenhaus, director and solution executive for Cerner\u2019s Open Developer Experience.

\u201cIt\u2019s extremely important to get to that normative standard,\u201d adds Obenhaus, who emphasizes that R4 assures the maturity and stability of the FHIR standard for developers building on top of Cerner\u2019s Millennium electronic health record and HealtheIntent population health platforms.

Stan Huff, MD, chief medical informatics officer at Intermountain Healthcare, says he is excited to see Cerner advancing their capabilities as a platform.

\u201cI think it is good for the whole healthcare IT ecosystem to have strong support for open standards-based APIs and services,\u201d comments Huff. \u201cI hope other healthcare software developers will follow suit. It will lead to the ability to share applications and knowledge in a way that will improve the care we provide for patients, and decrease the cost of software, while improving usability.\u201d

Cerner has already released a couple of APIs based on R4, according to Obenhaus, adding that \u201cmuch of our 2019 development roadmap will be continuing to develop additional APIs on the R4 standard.\u201d

\u201cIt\u2019s incredibly important that major vendors such as Cerner stay at the forefront of advancing the availability and maturity of the FHIR standard,\u201d says Micky Tripathi, manager of the Argonaut Project, an industry-wide effort to accelerate the development and adoption of FHIR. \u201cCerner\u2019s moving forward and implementing this latest FHIR version is an important signal to regulators that the industry is committed to maintaining the rapid momentum of FHIR adoption.\u201d

Following on the heels of HL7\u2019s December 2018 publication of R4, the Office of the National Coordinator for Health IT in February released a proposed rule\u2014for the first time\u2014requiring FHIR as the standard to which developers must certify their APIs under the ONC Health IT Certification Program.

Also See<\/b>: Proposed ONC rule requires FHIR interoperability standard<\/a>

Specifically, ONC\u2019s proposal seeks to make FHIR Release 2 a requirement. However, Obenhaus says that Cerner\u2014a founding member of the Argonaut Project\u2014is urging the agency to have the industry \u201ccoalesce around R4\u201d instead.

Tripathi points out that both ONC and the Centers for Medicare and Medicaid Services have issued draft rules recently that would require providers and health insurers to make available FHIR-based APIs. \u201cThe overwhelming consensus of the industry is that these rules should be based on the latest balloted version, which is FHIR R4,\u201d he adds.

\u201cFor many of us, the pace at which our partners in both the private and public sectors have embraced HL7 FHIR has been remarkable,\u201d observes Chuck Jaffe, MD, HL7\u2019s CEO. \u201cAs other segments of the diverse community embrace R4, we will move closer to interoperability, and our patients will be the beneficiaries.\u201d","saveContent":"Kansas City-based Cerner has embraced the latest version of HL7\u2019s Fast Healthcare Interoperability Resources standard to encourage third-party developers to build apps on top of its platforms.

By adopting FHIR Release 4, the normative version of the interoperability standard, Cerner contends that it is positioned at the \u201cleading edge\u201d in creating healthcare apps and opening its application programming interfaces (APIs) to developers to foster innovation.

\u201cWe\u2019ve invested in R4 in a significant way as part of our broader strategy at Cerner around advancing interoperability as well as enhancing our ability to facilitate third-party provider, clinical apps and consumer apps integration into our platforms,\u201d says Matt Obenhaus, director and solution executive for Cerner\u2019s Open Developer Experience.

\u201cIt\u2019s extremely important to get to that normative standard,\u201d adds Obenhaus, who emphasizes that R4 assures the maturity and stability of the FHIR standard for developers building on top of Cerner\u2019s Millennium electronic health record and HealtheIntent population health platforms.

Stan Huff, MD, chief medical informatics officer at Intermountain Healthcare, says he is excited to see Cerner advancing their capabilities as a platform.

\u201cI think it is good for the whole healthcare IT ecosystem to have strong support for open standards-based APIs and services,\u201d comments Huff. \u201cI hope other healthcare software developers will follow suit. It will lead to the ability to share applications and knowledge in a way that will improve the care we provide for patients, and decrease the cost of software, while improving usability.\u201d

Cerner has already released a couple of APIs based on R4, according to Obenhaus, adding that \u201cmuch of our 2019 development roadmap will be continuing to develop additional APIs on the R4 standard.\u201d

\u201cIt\u2019s incredibly important that major vendors such as Cerner stay at the forefront of advancing the availability and maturity of the FHIR standard,\u201d says Micky Tripathi, manager of the Argonaut Project, an industry-wide effort to accelerate the development and adoption of FHIR. \u201cCerner\u2019s moving forward and implementing this latest FHIR version is an important signal to regulators that the industry is committed to maintaining the rapid momentum of FHIR adoption.\u201d

Following on the heels of HL7\u2019s December 2018 publication of R4, the Office of the National Coordinator for Health IT in February released a proposed rule\u2014for the first time\u2014requiring FHIR as the standard to which developers must certify their APIs under the ONC Health IT Certification Program.

Also See<\/b>: Proposed ONC rule requires FHIR interoperability standard<\/a>

Specifically, ONC\u2019s proposal seeks to make FHIR Release 2 a requirement. However, Obenhaus says that Cerner\u2014a founding member of the Argonaut Project\u2014is urging the agency to have the industry \u201ccoalesce around R4\u201d instead.

Tripathi points out that both ONC and the Centers for Medicare and Medicaid Services have issued draft rules recently that would require providers and health insurers to make available FHIR-based APIs. \u201cThe overwhelming consensus of the industry is that these rules should be based on the latest balloted version, which is FHIR R4,\u201d he adds.

\u201cFor many of us, the pace at which our partners in both the private and public sectors have embraced HL7 FHIR has been remarkable,\u201d observes Chuck Jaffe, MD, HL7\u2019s CEO. \u201cAs other segments of the diverse community embrace R4, we will move closer to interoperability, and our patients will be the beneficiaries.\u201d","order":0,"get_parent":{},"attributes":[],"attributesType":{"content":{"type":"string","source":"raw"},"lock":{"type":"object"}},"dynamicContent":""}]

Cerner says it is first vendor to adopt the normative version of FHIR

More for you