[{"innerBlocks":[],"name":"core\/freeform","postId":1397,"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":"Health Level 7 International has published Release 4 of its Fast Healthcare Interoperability Resources, marking a major milestone for the emerging standard, which is based on modern internet conventions.

According to HL7, the most significant advancement with FHIR Release 4 (R4) is that the base platform of the standard has passed a normative ballot and will be submitted to the American National Standards Institute.

\u201cSome of the resources are normative, meaning that backward compatibility is assured for those,\u201d says Chuck Jaffe, MD, HL7\u2019s CEO, who contends that applications that implement the normative parts of R4 no longer risk being non-conformant to the standard.

\u201cThis is critical, because it assures stability of the standard for both the community of developers and, perhaps more importantly, the implementers,\u201d adds Jaffe.

App developers, health IT vendors and providers have widely embraced FHIR\u2014which includes the RESTful application programming interface\u2014to help solve the interoperability challenges confronting the healthcare industry as it seeks to increase access to electronic health records and data sharing.

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

Josh Mandel, MD, chief architect for Microsoft Healthcare and a strong supporter of FHIR, sees R4 as a \u201ctremendous milestone\u201d for the healthcare interoperability standards community.

\u201cR4 is the first release of the FHIR specification to include normative content, meaning that for 11 resources labeled as \u2018normative,\u2019 we\u2019re committed to maintaining forward compatibility with future versions of FHIR,\u201d says Mandel. \u201cThese new resources include core clinical definitions like Patient and Observation, as well as some of the internal data structures used for defining conformance requirements (for example, StructureDefinition).\u201d

Specifically, the following portions of FHIR R4 are now considered normative:

\u2022\tThe RESTful API, the XML and JSON formats and the basic datatypes

\u2022\tThe Terminology Layer (CodeSystem and ValueSet)

\u2022\tThe Conformance Framework (StructureDefinition and CapabilityStatement)

\u2022\tThe key resources Patient and Observation

In addition to a set of normative resources, Mandel notes that FHIR R4 includes a wide array of updates and improvements based on collective implementation experience over the past two years.

\u201cFor example, the resources needed to support the Meaningful Use Common Clinical Data Set\/US Core Data for Interoperability have continued to progress through the FHIR Maturity Model,\u201d he adds. \u201cI expect we\u2019ll see broadening adoption of these resources as more organizations enable FHIR-based access.\u201d

The standard will to continue to evolve \u201cas it responds to the interoperability needs of the robust FHIR implementation community,\u201d states HL7\u2019s announcement. Going forward, HL7 says its priority for the next release is to \u201cbring more sections of the standard to normative status and continue to respond to the needs of the community that is building solutions.\u201d

For its part, the Argonaut Project is a collaboration HIT vendors and providers designed to accelerate the adoption of FHIR by creating \u201croad-tested\u201d implementation guides accessible to developers to build interoperability capabilities.

\u201cHL7 FHIR R4 is a beginning,\u201d adds Jaffe. \u201cIt is the legacy of eight years of innovation and collaboration among a community of thousands around the world. It is a commitment from HL7 to create a platform from which Interoperability can someday emerge. It is a promise to provide reusable data across the continuum of biomedical research, patient care, and population health.\u201d

\"Overall, FHIR's continued maturity is a great sign,\" says Steve Posnack, executive director of ONC\u2019s office of technology. \"This first batch of 'normative' components will provide a new level of stability for the standard and its implementers. The hard work continues though. Through our cooperative agreement with HL7, ONC will support updates to the older FHIR profiles and implementation guides the industry needs to put this release into production. <\/b>We look forward to seeing innovative uses of FHIR R4.\"

A complete list of resources included in FHIR R4 can be found here<\/a>.
","saveContent":"Health Level 7 International has published Release 4 of its Fast Healthcare Interoperability Resources, marking a major milestone for the emerging standard, which is based on modern internet conventions.

According to HL7, the most significant advancement with FHIR Release 4 (R4) is that the base platform of the standard has passed a normative ballot and will be submitted to the American National Standards Institute.

\u201cSome of the resources are normative, meaning that backward compatibility is assured for those,\u201d says Chuck Jaffe, MD, HL7\u2019s CEO, who contends that applications that implement the normative parts of R4 no longer risk being non-conformant to the standard.

\u201cThis is critical, because it assures stability of the standard for both the community of developers and, perhaps more importantly, the implementers,\u201d adds Jaffe.

App developers, health IT vendors and providers have widely embraced FHIR\u2014which includes the RESTful application programming interface\u2014to help solve the interoperability challenges confronting the healthcare industry as it seeks to increase access to electronic health records and data sharing.

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

Josh Mandel, MD, chief architect for Microsoft Healthcare and a strong supporter of FHIR, sees R4 as a \u201ctremendous milestone\u201d for the healthcare interoperability standards community.

\u201cR4 is the first release of the FHIR specification to include normative content, meaning that for 11 resources labeled as \u2018normative,\u2019 we\u2019re committed to maintaining forward compatibility with future versions of FHIR,\u201d says Mandel. \u201cThese new resources include core clinical definitions like Patient and Observation, as well as some of the internal data structures used for defining conformance requirements (for example, StructureDefinition).\u201d

Specifically, the following portions of FHIR R4 are now considered normative:

\u2022\tThe RESTful API, the XML and JSON formats and the basic datatypes

\u2022\tThe Terminology Layer (CodeSystem and ValueSet)

\u2022\tThe Conformance Framework (StructureDefinition and CapabilityStatement)

\u2022\tThe key resources Patient and Observation

In addition to a set of normative resources, Mandel notes that FHIR R4 includes a wide array of updates and improvements based on collective implementation experience over the past two years.

\u201cFor example, the resources needed to support the Meaningful Use Common Clinical Data Set\/US Core Data for Interoperability have continued to progress through the FHIR Maturity Model,\u201d he adds. \u201cI expect we\u2019ll see broadening adoption of these resources as more organizations enable FHIR-based access.\u201d

The standard will to continue to evolve \u201cas it responds to the interoperability needs of the robust FHIR implementation community,\u201d states HL7\u2019s announcement. Going forward, HL7 says its priority for the next release is to \u201cbring more sections of the standard to normative status and continue to respond to the needs of the community that is building solutions.\u201d

For its part, the Argonaut Project is a collaboration HIT vendors and providers designed to accelerate the adoption of FHIR by creating \u201croad-tested\u201d implementation guides accessible to developers to build interoperability capabilities.

\u201cHL7 FHIR R4 is a beginning,\u201d adds Jaffe. \u201cIt is the legacy of eight years of innovation and collaboration among a community of thousands around the world. It is a commitment from HL7 to create a platform from which Interoperability can someday emerge. It is a promise to provide reusable data across the continuum of biomedical research, patient care, and population health.\u201d

\"Overall, FHIR's continued maturity is a great sign,\" says Steve Posnack, executive director of ONC\u2019s office of technology. \"This first batch of 'normative' components will provide a new level of stability for the standard and its implementers. The hard work continues though. Through our cooperative agreement with HL7, ONC will support updates to the older FHIR profiles and implementation guides the industry needs to put this release into production. <\/b>We look forward to seeing innovative uses of FHIR R4.\"

A complete list of resources included in FHIR R4 can be found here<\/a>.
","order":0,"get_parent":{},"attributes":[],"attributesType":{"content":{"type":"string","source":"raw"},"lock":{"type":"object"}},"dynamicContent":""}]

HL7 publishes normative version of FHIR standard

More for you