@prefix fhir: <;http://hl7.org/fhir/>; .
@prefix rdf:  <;http://www.w3.org/1999/02/22-rdf-syntax-ns#>; .
@prefix rdfs: <;http://www.w3.org/2000/01/rdf-schema#>; .
@prefix sct:  <;http://snomed.info/id#>; .
@prefix xsd:  <;http://www.w3.org/2001/XMLSchema#>; .
<;https://smilecdr.com/hapi-fhir/blog/fhir/baseR4/Communication/20201119_hapi_fhir_5_2_0/_history/1>;
        rdf:type                    fhir:Communication;
        fhir:Communication.payload  [ fhir:Communication.payload.contentString
                                              [ fhir:value  "<p>It's August, so it's time for our next quarterly relese: HAPI FHIR 5.2.0 (Codename: Numbat).</p>\n<p>Security Notice:</p>\n<ul>\n<li>Security Issue CVE-2020-24301: An XSS vulnerability has been fixed in the testpage overlay project. This issue affects only the testpage overlay module, but users of this module should upgrade immediately. Note that this issue is addressed in HAPI FHIR 5.1.0 (as well as 5.2.0+) so users who have already upgraded to HAPI FHIR 5.1.0 do not need to upgrade again to resolve this issue. It is listed here as we experienced a delay in obtaining a CVE number.</li>\n</ul>\n<p>Major New Features:</p>\n<ul>\n<li>\n<p>The JPA SearchBuilder (which turns FHIR searches into SQL statements to be executed by the database) has been completely rewritten to not use Hibernate. This allows for much more efficient SQL to be generated in some cases. For some specific queries on a very large test repository running on Postgresql this new search builder performed 10x faster. Note that this new module is enabled by default in HAPI FHIR 5.2.0 but can be disabled via a JpaStorageSettings setting. It is disabled by default in Smile CDR 2020.11.R01 but will be enabled by default in the next major release.</p>\n</li>\n<li>\n<p>Support for RDF Turtle encoding has been added, finally bringing native support for the 3rd official FHIR encoding to HAPI FHIR. This support was contributed by Josh Collins and Eric Prud'hommeaux of the company Janeiro Digital. We greatly appreciate the contribution! To see an example of the RDF encoding: hapi.fhir.org/baseR4/Patient?_format=rdf</p>\n</li>\n</ul>\n<p>Terminology Enhancements:</p>\n<ul>\n<li>\n<p>Integration with remote terminology services has been improved so that required bindings to closed valuesets are no longer delegated to the remote terminology server. This improves performance since there is no need for remote services in this case.</p>\n</li>\n<li>\n<p>The <code>CodeSystem/$validate-code</code> operation has been implemented for R4+ JPA servers.</p>\n</li>\n<li>\n<p>The JPA Terminology Server is now version aware, meaning that multiple versions of a single CodeSystem can now be stored in a single FHIR terminology server repository. ValueSet expansion, CodeSystem lookup, and ConceptMap translation are all now fully version aware. Note that implementing support for fully versioned terminology is mostly complete, but some validation operations may still not work. This should be completed by our next major release.</p>\n</li>\n<li>\n<p>ValueSet expansion with filtering (e.g. using the <code>filter</code> parameter on the <code>$expand</code> operation) has now been implemented in such a way that it fully supports filtering on pre-expanded ValueSets, including using offsets and counts. This is a major improvement for people building picker UIs leveraging the $expand operation.</p>\n</li>\n</ul>\n<p>EMPI Improvements:</p>\n<ul>\n<li>\n<p>Identifier matchers have been added, providing native FHIR support for matching on resource identifiers</p>\n</li>\n<li>\n<p>The <code>$empi-clear</code> operation performance has been greatly improved</p>\n</li>\n</ul>\n<p>Other Notable Improvements:</p>\n<ul>\n<li>\n<p>A new combined &quot;delete+expunge&quot; mode has been added to the DELETE operation in the JPA server. This mode deletes resources and expunges (physically deletes) them in a single fast operation. Note that with this mode must be enabled, and completely bypasses interceptor hooks notifying registered listeners that data is being deletes and expunged. It is several orders of magnitude faster when deleting large sets of data, and is generally intended for test scenarios.</p>\n</li>\n<li>\n<p>The Package Server module now supports installing non-conformance resources from packages.</p>\n</li>\n<li>\n<p>The <code>_typeFilter</code> parameter has been implemented for the $bulk-export module.</p>\n</li>\n</ul>\n<p>As always, see the <a href=\"https://smilecdr.com/hapi-fhir/docs/introduction/changelog.html\">changelog</a> for a full list of changes.</p>\n<p>Thanks to everyone who contributed to this release!</p>\n" ];
                                      fhir:index  0
                                    ];
        fhir:Communication.sender   [ fhir:Reference.display    [ fhir:value  "James Agnew" ];
                                      fhir:Reference.reference  [ fhir:value  "https://smilecdr.com/about_us/#james" ]
                                    ];
        fhir:Communication.sent     [ fhir:value  "2020-11-19T08:00:00-05:00"^^xsd:dateTime ];
        fhir:Communication.status   [ fhir:value  "completed" ];
        fhir:DomainResource.text    [ fhir:Narrative.div     "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>It's August, so it's time for our next quarterly relese: HAPI FHIR 5.2.0 (Codename: Numbat).</p>\n<p>Security Notice:</p>\n<ul>\n<li>Security Issue CVE-2020-24301: An XSS vulnerability has been fixed in the testpage overlay project. This issue affects only the testpage overlay module, but users of this module should upgrade immediately. Note that this issue is addressed in HAPI FHIR 5.1.0 (as well as 5.2.0+) so users who have already upgraded to HAPI FHIR 5.1.0 do not need to upgrade again to resolve this issue. It is listed here as we experienced a delay in obtaining a CVE number.</li>\n</ul>\n<p>Major New Features:</p>\n<ul>\n<li>\n<p>The JPA SearchBuilder (which turns FHIR searches into SQL statements to be executed by the database) has been completely rewritten to not use Hibernate. This allows for much more efficient SQL to be generated in some cases. For some specific queries on a very large test repository running on Postgresql this new search builder performed 10x faster. Note that this new module is enabled by default in HAPI FHIR 5.2.0 but can be disabled via a JpaStorageSettings setting. It is disabled by default in Smile CDR 2020.11.R01 but will be enabled by default in the next major release.</p>\n</li>\n<li>\n<p>Support for RDF Turtle encoding has been added, finally bringing native support for the 3rd official FHIR encoding to HAPI FHIR. This support was contributed by Josh Collins and Eric Prud'hommeaux of the company Janeiro Digital. We greatly appreciate the contribution! To see an example of the RDF encoding: hapi.fhir.org/baseR4/Patient?_format=rdf</p>\n</li>\n</ul>\n<p>Terminology Enhancements:</p>\n<ul>\n<li>\n<p>Integration with remote terminology services has been improved so that required bindings to closed valuesets are no longer delegated to the remote terminology server. This improves performance since there is no need for remote services in this case.</p>\n</li>\n<li>\n<p>The <code>CodeSystem/$validate-code</code> operation has been implemented for R4+ JPA servers.</p>\n</li>\n<li>\n<p>The JPA Terminology Server is now version aware, meaning that multiple versions of a single CodeSystem can now be stored in a single FHIR terminology server repository. ValueSet expansion, CodeSystem lookup, and ConceptMap translation are all now fully version aware. Note that implementing support for fully versioned terminology is mostly complete, but some validation operations may still not work. This should be completed by our next major release.</p>\n</li>\n<li>\n<p>ValueSet expansion with filtering (e.g. using the <code>filter</code> parameter on the <code>$expand</code> operation) has now been implemented in such a way that it fully supports filtering on pre-expanded ValueSets, including using offsets and counts. This is a major improvement for people building picker UIs leveraging the $expand operation.</p>\n</li>\n</ul>\n<p>EMPI Improvements:</p>\n<ul>\n<li>\n<p>Identifier matchers have been added, providing native FHIR support for matching on resource identifiers</p>\n</li>\n<li>\n<p>The <code>$empi-clear</code> operation performance has been greatly improved</p>\n</li>\n</ul>\n<p>Other Notable Improvements:</p>\n<ul>\n<li>\n<p>A new combined &quot;delete+expunge&quot; mode has been added to the DELETE operation in the JPA server. This mode deletes resources and expunges (physically deletes) them in a single fast operation. Note that with this mode must be enabled, and completely bypasses interceptor hooks notifying registered listeners that data is being deletes and expunged. It is several orders of magnitude faster when deleting large sets of data, and is generally intended for test scenarios.</p>\n</li>\n<li>\n<p>The Package Server module now supports installing non-conformance resources from packages.</p>\n</li>\n<li>\n<p>The <code>_typeFilter</code> parameter has been implemented for the $bulk-export module.</p>\n</li>\n</ul>\n<p>As always, see the <a href=\"https://smilecdr.com/hapi-fhir/docs/introduction/changelog.html\">changelog</a> for a full list of changes.</p>\n<p>Thanks to everyone who contributed to this release!</p>\n</div>";
                                      fhir:Narrative.status  [ fhir:value  "generated" ]
                                    ];
        fhir:Resource.id            [ fhir:value  "20201119_hapi_fhir_5_2_0" ];
        fhir:Resource.language      [ fhir:value  "en" ];
        fhir:Resource.meta          [ fhir:Meta.tag        [ fhir:Coding.code    [ fhir:value  "Release" ];
                                                             fhir:Coding.system  [ fhir:value  "https://smilecdr.com/hapi-fhir/blog/tag"^^xsd:anyURI ];
                                                             fhir:index          0
                                                           ];
                                      fhir:Meta.versionId  [ fhir:value  "1" ]
                                    ];
        fhir:nodeRole               fhir:treeRoot .