[{"innerBlocks":[],"name":"core\/freeform","postId":4340,"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":"The first open application programming interface (API) software platform has been certified using HL7\u2019s emerging Fast Healthcare Interoperability Resources (FHIR) standard to meet Stage 3 Meaningful Use interoperability requirements.

This distinction belongs to OpenAPI from Carefluence, a Michigan-based company that offers software solutions and technology integration services to electronic health record vendors and healthcare providers.

Drummond Group, which is authorized by the Office of the National Coordinator for Health IT to test software for compliance with Meaningful Use interoperability requirements, has certified that the Carefluence OpenAPI software module can be deployed alongside existing EHR systems, providing functionality that enables open access to EHRs and lets providers receive incentive payments from the federal government.

\u201cThis is the first open API that is fully standards-compliant based on FHIR,\u201d says Adam Boris, an advisor to the board of Carefluence. \u201cWe offer a module that can be a drop-in to any existing EHR to provide that standards-based interface.\u201d

According to Boris, Carefluence adopted as early as 2014 the FHIR standard, an interoperability framework that leverages the latest web standards. The FHIR API and core data services specification are designed to enable information sharing between EHRs and other health IT systems.

Carefluence contends that their OpenAPI is a \u201ccomprehensive, \u2018plug-and-play\u2019 software solution\u201d that fully complies with the FHIR standard, \u201cwhich describes data formats and elements for exchange of health information across disparate EHR systems.\u201d The company says that any EHR vendor can license Carefluence\u2019s OpenAPI and offer it to their customers \u201cwith the assurance that their product will be Meaningful Use compliant, avoiding the costly internal development of a custom open API solution.\u201d

APIs were included in the final Meaningful Use Stage 3 rule, requiring certified EHR technology to provide an API through which patient information can be viewed, downloaded, and transmitted to a third party. In addition, APIs are part of the 2015 Edition of Health IT Certification Criteria, which requires certified EHRs to demonstrate the ability to provide a patient-facing app access to the Common Clinical Data Set via an API.

\u201cWe know that a lot of existing EHR vendors are struggling to keep up with all the changes from Meaningful Use,\u201d Boris adds. \u201cEvery EHR system used by doctor\u2019s offices and health systems that want to be Meaningful Use certified are going to have to have an API. They can create a proprietary API if they want to, but that will be costly in terms of software development and runs contrary to the purpose and spirit of what the industry is trying to be accomplish nationally with open APIs.\u201d

HL7 CEO Chuck Jaffe, MD, congratulated Carefluence for their distinction in being the first open API platform to be certified using the FHIR standard to meet Stage 3 MU interoperability requirements. He observes that this milestone is just the first of many to come for a host of vendors and healthcare organizations working towards this goal.

\u201cThere are dozens, maybe hundreds, of entities doing the same thing,\u201d Jaffe says. \u201cThe process has been made dramatically easier by the work of the Argonaut Project.\u201d

The Argonaut Project is an industry-wide effort to accelerate the development and adoption of FHIR. Major EHR vendors and healthcare providers have joined forces as part of this initiative to refine the profiles and implementation guides, which are the \u201crules of the road\u201d for FHIR.","saveContent":"The first open application programming interface (API) software platform has been certified using HL7\u2019s emerging Fast Healthcare Interoperability Resources (FHIR) standard to meet Stage 3 Meaningful Use interoperability requirements.

This distinction belongs to OpenAPI from Carefluence, a Michigan-based company that offers software solutions and technology integration services to electronic health record vendors and healthcare providers.

Drummond Group, which is authorized by the Office of the National Coordinator for Health IT to test software for compliance with Meaningful Use interoperability requirements, has certified that the Carefluence OpenAPI software module can be deployed alongside existing EHR systems, providing functionality that enables open access to EHRs and lets providers receive incentive payments from the federal government.

\u201cThis is the first open API that is fully standards-compliant based on FHIR,\u201d says Adam Boris, an advisor to the board of Carefluence. \u201cWe offer a module that can be a drop-in to any existing EHR to provide that standards-based interface.\u201d

According to Boris, Carefluence adopted as early as 2014 the FHIR standard, an interoperability framework that leverages the latest web standards. The FHIR API and core data services specification are designed to enable information sharing between EHRs and other health IT systems.

Carefluence contends that their OpenAPI is a \u201ccomprehensive, \u2018plug-and-play\u2019 software solution\u201d that fully complies with the FHIR standard, \u201cwhich describes data formats and elements for exchange of health information across disparate EHR systems.\u201d The company says that any EHR vendor can license Carefluence\u2019s OpenAPI and offer it to their customers \u201cwith the assurance that their product will be Meaningful Use compliant, avoiding the costly internal development of a custom open API solution.\u201d

APIs were included in the final Meaningful Use Stage 3 rule, requiring certified EHR technology to provide an API through which patient information can be viewed, downloaded, and transmitted to a third party. In addition, APIs are part of the 2015 Edition of Health IT Certification Criteria, which requires certified EHRs to demonstrate the ability to provide a patient-facing app access to the Common Clinical Data Set via an API.

\u201cWe know that a lot of existing EHR vendors are struggling to keep up with all the changes from Meaningful Use,\u201d Boris adds. \u201cEvery EHR system used by doctor\u2019s offices and health systems that want to be Meaningful Use certified are going to have to have an API. They can create a proprietary API if they want to, but that will be costly in terms of software development and runs contrary to the purpose and spirit of what the industry is trying to be accomplish nationally with open APIs.\u201d

HL7 CEO Chuck Jaffe, MD, congratulated Carefluence for their distinction in being the first open API platform to be certified using the FHIR standard to meet Stage 3 MU interoperability requirements. He observes that this milestone is just the first of many to come for a host of vendors and healthcare organizations working towards this goal.

\u201cThere are dozens, maybe hundreds, of entities doing the same thing,\u201d Jaffe says. \u201cThe process has been made dramatically easier by the work of the Argonaut Project.\u201d

The Argonaut Project is an industry-wide effort to accelerate the development and adoption of FHIR. Major EHR vendors and healthcare providers have joined forces as part of this initiative to refine the profiles and implementation guides, which are the \u201crules of the road\u201d for FHIR.","order":0,"get_parent":{},"attributes":[],"attributesType":{"content":{"type":"string","source":"raw"},"lock":{"type":"object"}},"dynamicContent":""}]

OpenAPI is the first to be certified using FHIR standard for Stage 3 MU

More for you