This result is being rendered in HTML for easy viewing. You may access this content as Raw JSON or Raw XML or Raw Turtle or view this content in HTML JSON or HTML XML or HTML Turtle . Response generated in 1ms.

HTTP 200 OK

Response Headers

Date: Sat, 31 Jul 2021 13:21:45 GMT
X-Powered-By: HAPI FHIR 5.5.0-PRE7-SNAPSHOT/6f7f787813/2021-07-22 REST Server (FHIR Server; FHIR 4.0.1/R4; Raccoon Nation Edition)
Content-Type: application/fhir+xml;charset=utf-8
X-Request-ID: HWOdclS4zu97aCx6

Response Body

{
"resourceType": "Communication",
"id": "20210520_hapi_fhir_5_4_0",
"meta": {
"versionId": "1",
"tag": [ {
"system": "https://smilecdr.com/hapi-fhir/blog/tag",
"code": "Release"
} ]
},
"language": "en",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>It's time for another release of HAPI FHIR.</p>\n<p>HAPI FHIR 5.4.0 (Codename: Pangolin) brings a whole bunch of great new features, bugfixes, and more.</p>\n<p>Highlights of this release are shown below. See the <a href=\"https://hapifhir.io/hapi-fhir/docs/introduction/changelog.html\">Changelog</a> for a complete list. There will be a live Webinar (recording available on-demand afterward) on May 20 2021. Details available here: https://www.smilecdr.com/quarterly-product-release-webinar-reminder</p>\n<h3>Security Changes</h3>\n<ul>\n<li>A resource exhaustion vulnerability in the HAPI FHIR JPA server was corrected. Learn more about CVE-2021-32053 <a href=\"https://snyk.io/vuln/SNYK-JAVA-CAUHNHAPIFHIR-1290393\">here</a>. Thanks to Zachary Minneker at Security Innovation for reporting!</li>\n</ul>\n<h3>General Client/Server/Parser Changes</h3>\n<ul>\n<li>HAPI FHIR now supports OpenAPI (aka Swagger). See <a href=\"http://hapi.fhir.org/baseR4/swagger-ui/\">here</a> for an example.</li>\n<li>Normalization and Standardization interceptors have been added. These can be used to normalize selected data fields according to configurable rules prior to storage.</li>\n<li>Contained resources can now reference <em>to</em> containing resources, as allowed in the FHIR Specification. Previously this direction was blocked and contained resources with no incoming reference <em>from</em> the containing resource were automatically stripped, as this style was not permitted in early versions of the FHIR specification. In addition, contained resource order will now be preserved during parsing round-trips.</li>\n<li>New interceptors have been added that can automatically map terminology in response resources using HAPI FHIR terminology services, returning configurable canonical terminology in the response payload.</li>\n<li>Support for the FHIR <code>Prefer: handling=lenient</code> header has been added via an optional interceptor.</li>\n<li>The automatic CapabiityStatement generation has been completely rewritten for R4+ servers. CapabilityStatements now include many new data elements, such as supported profiles, revincludes, resource level operations, and more.</li>\n<li>Token Search Parameters in GraphQL expressions are now correctly parsed.</li>\n</ul>\n<h3>JDK Changes</h3>\n<ul>\n<li>HAPI FHIR now supports JDK 16, and this version is used to execute our CI test suite in order to ensure continued compliance. The minimum Java version required in order to use HAPI FHIR remains JDK 8. This may be updated to JDK 11 in an upcoming release, as many of the libraries we use are now either contemplating or have already completed an upgrade to JDK 11 as a minimum requirement.</li>\n</ul>\n<h3>JPA Server General Changes</h3>\n<ul>\n<li>Support for the <code>_list</code> search parameter has been added to the JPA server</li>\n<li>Support for the <code>:contained</code> modifier has been added, allowing searches to select from data in contained resources found within the resource being searches. Note that this feature is disabled by default and must be enabled if needed.</li>\n<li>The JPA server now supports persisting FHIR extensions in <code>Resource.meta</code></li>\n<li>Bulk Export now supports Patient- and Group- based exports</li>\n<li>Auto-created reference target placeholder resources now include an extension and an identifier if one is known</li>\n<li>A profiling effort led to improvements in performance when processing large FHIR Transaction bundles</li>\n<li>Resources imported into a repository via NPM Packages will now attempt to preserve the resource ID defined in the source package.</li>\n</ul>\n<h3>JPA Server Performance Changes</h3>\n<ul>\n<li>Searches with only a single search parameter now generate a more streamlined SQL expression (one unnecessary JOIN was removed), improving performance.</li>\n<li>A new header <code>X-Upsert-Extistence-Check</code> (note there is a typo in the name, this will be addressed in the next release of HAPI FHIR! Please be aware if you are planning on using this feature) can be added which avoids existence checks when using client assigned IDs to create new records. This can speed up performance.</li>\n</ul>\n<h3>JPA Server Partitioning Changes</h3>\n<ul>\n<li>Resource Reindexing is now supported on partitioned servers.</li>\n<li>FHIR Bulk Export is now supported on partitioned servers (note that this operation is run at the system level and includes data from all partitions. Future enhancements may allow for more nuanced exports on partitioned servers.)</li>\n</ul>\n<h3>Terminology Server and Validation Changes</h3>\n<ul>\n<li>ValueSet expansion can now optionally return codes in the same hierarchy that they are defined in their source CodeSystem.</li>\n<li>Validation can now be configured to return only a warning when a code is found from a CodeSystem that is unknown/unavailable to the validator.</li>\n</ul>\n<h3>JPA Server MDM Enhancements</h3>\n<ul>\n<li>A new search mdm-expansion syntax has been added to FHIR searches on MDM-enabled servers. For example <code>Observation?patient:mdm=Patient/123</code> can be used to search for Observation resources belonging to <code>Patient/123</code> but also to other MDM-linked patient records.</li>\n<li>MDM matching rules can now use FHIRPath expressions as selection criteria.</li>\n<li>A new syntax has been added to Group Bulk Export that allows MDM matching to be used to include matches in the group to export.</li>\n<li>MDM matching rules can now match on extensions, checking the URL and Value for equality.</li>\n<li>A new NUMERIC matcher has been added, allowing matching using numeric values.</li>\n</ul>\n</div>"
},
"status": "completed",
"sent": "2021-05-19T08:00:00-05:00",
"sender": {
"reference": "https://smilecdr.com/about_us/#james",
"display": "James Agnew"
},
"payload": [ {
"contentString": "<p>It's time for another release of HAPI FHIR.</p>\n<p>HAPI FHIR 5.4.0 (Codename: Pangolin) brings a whole bunch of great new features, bugfixes, and more.</p>\n<p>Highlights of this release are shown below. See the <a href=\"https://hapifhir.io/hapi-fhir/docs/introduction/changelog.html\">Changelog</a> for a complete list. There will be a live Webinar (recording available on-demand afterward) on May 20 2021. Details available here: https://www.smilecdr.com/quarterly-product-release-webinar-reminder</p>\n<h3>Security Changes</h3>\n<ul>\n<li>A resource exhaustion vulnerability in the HAPI FHIR JPA server was corrected. Learn more about CVE-2021-32053 <a href=\"https://snyk.io/vuln/SNYK-JAVA-CAUHNHAPIFHIR-1290393\">here</a>. Thanks to Zachary Minneker at Security Innovation for reporting!</li>\n</ul>\n<h3>General Client/Server/Parser Changes</h3>\n<ul>\n<li>HAPI FHIR now supports OpenAPI (aka Swagger). See <a href=\"http://hapi.fhir.org/baseR4/swagger-ui/\">here</a> for an example.</li>\n<li>Normalization and Standardization interceptors have been added. These can be used to normalize selected data fields according to configurable rules prior to storage.</li>\n<li>Contained resources can now reference <em>to</em> containing resources, as allowed in the FHIR Specification. Previously this direction was blocked and contained resources with no incoming reference <em>from</em> the containing resource were automatically stripped, as this style was not permitted in early versions of the FHIR specification. In addition, contained resource order will now be preserved during parsing round-trips.</li>\n<li>New interceptors have been added that can automatically map terminology in response resources using HAPI FHIR terminology services, returning configurable canonical terminology in the response payload.</li>\n<li>Support for the FHIR <code>Prefer: handling=lenient</code> header has been added via an optional interceptor.</li>\n<li>The automatic CapabiityStatement generation has been completely rewritten for R4+ servers. CapabilityStatements now include many new data elements, such as supported profiles, revincludes, resource level operations, and more.</li>\n<li>Token Search Parameters in GraphQL expressions are now correctly parsed.</li>\n</ul>\n<h3>JDK Changes</h3>\n<ul>\n<li>HAPI FHIR now supports JDK 16, and this version is used to execute our CI test suite in order to ensure continued compliance. The minimum Java version required in order to use HAPI FHIR remains JDK 8. This may be updated to JDK 11 in an upcoming release, as many of the libraries we use are now either contemplating or have already completed an upgrade to JDK 11 as a minimum requirement.</li>\n</ul>\n<h3>JPA Server General Changes</h3>\n<ul>\n<li>Support for the <code>_list</code> search parameter has been added to the JPA server</li>\n<li>Support for the <code>:contained</code> modifier has been added, allowing searches to select from data in contained resources found within the resource being searches. Note that this feature is disabled by default and must be enabled if needed.</li>\n<li>The JPA server now supports persisting FHIR extensions in <code>Resource.meta</code></li>\n<li>Bulk Export now supports Patient- and Group- based exports</li>\n<li>Auto-created reference target placeholder resources now include an extension and an identifier if one is known</li>\n<li>A profiling effort led to improvements in performance when processing large FHIR Transaction bundles</li>\n<li>Resources imported into a repository via NPM Packages will now attempt to preserve the resource ID defined in the source package.</li>\n</ul>\n<h3>JPA Server Performance Changes</h3>\n<ul>\n<li>Searches with only a single search parameter now generate a more streamlined SQL expression (one unnecessary JOIN was removed), improving performance.</li>\n<li>A new header <code>X-Upsert-Extistence-Check</code> (note there is a typo in the name, this will be addressed in the next release of HAPI FHIR! Please be aware if you are planning on using this feature) can be added which avoids existence checks when using client assigned IDs to create new records. This can speed up performance.</li>\n</ul>\n<h3>JPA Server Partitioning Changes</h3>\n<ul>\n<li>Resource Reindexing is now supported on partitioned servers.</li>\n<li>FHIR Bulk Export is now supported on partitioned servers (note that this operation is run at the system level and includes data from all partitions. Future enhancements may allow for more nuanced exports on partitioned servers.)</li>\n</ul>\n<h3>Terminology Server and Validation Changes</h3>\n<ul>\n<li>ValueSet expansion can now optionally return codes in the same hierarchy that they are defined in their source CodeSystem.</li>\n<li>Validation can now be configured to return only a warning when a code is found from a CodeSystem that is unknown/unavailable to the validator.</li>\n</ul>\n<h3>JPA Server MDM Enhancements</h3>\n<ul>\n<li>A new search mdm-expansion syntax has been added to FHIR searches on MDM-enabled servers. For example <code>Observation?patient:mdm=Patient/123</code> can be used to search for Observation resources belonging to <code>Patient/123</code> but also to other MDM-linked patient records.</li>\n<li>MDM matching rules can now use FHIRPath expressions as selection criteria.</li>\n<li>A new syntax has been added to Group Bulk Export that allows MDM matching to be used to include matches in the group to export.</li>\n<li>MDM matching rules can now match on extensions, checking the URL and Value for equality.</li>\n<li>A new NUMERIC matcher has been added, allowing matching using numeric values.</li>\n</ul>\n"
} ]
}
Wrote 11.6 KB (25.3 KB total including HTML) in estimated 0ms