{ "resourceType": "Communication", "id": "20221117_hapi_fhir_6_2_0", "meta": { "versionId": "1", "tag": [ { "system": "https://smilecdr.com/hapi-fhir/blog/tag", "code": "Release" } ] }, "language": "en", "text": { "status": "generated", "div": "
Welcome to the winter release of HAPI FHIR! Support has been added for FHIR R4B (4.3.0). See the R4B Documentation for more information on what this means. Now onto the rest!
\nActionRequestDetails
class has been dropped (it has been deprecated\nsince HAPI FHIR 4.0.0). This class was used as a parameter to the\nSERVER_INCOMING_REQUEST_PRE_HANDLED
interceptor pointcut, but can be\nreplaced in any existing client code with RequestDetails
. This change\nalso removes an undocumented behaviour where the JPA server internally\ninvoked the SERVER_INCOMING_REQUEST_PRE_HANDLED
a second time from\nwithin various processing methods. This behaviour caused performance\nproblems for some interceptors (e.g. SearchNarrowingInterceptor
) and\nno longer offers any benefit so it is being removed.reindex-terminology
command.":nickname
qualifier only worked with the predefined name
and given
SearchParameters.\nThis has been fixed and now the :nickname
qualifier can be used with any string SearchParameters.Accept
\nheader that matched the contentType
of the stored resource, the server would return an XML representation of the Binary resource. This has been fixed, and a request with a matching Accept
header will receive\nthe stored binary data directly as the requested content type.STORAGE_TRANSACTION_PROCESSING
has been added. Hooks for this\npointcut can examine and modify FHIR transaction bundles being processed by the JPA server before\nprocessing starts.$meta
operation\nagainst the deleted resource, and will remain if the resource is brought back in a subsequent update.Accept
header._outputFormat
parameter was omitted. This behaviour has been fixed, and if omitted, will now default to the only legal value application/fhir+ndjson
.[fhir base]/Patient/[id]/$export
, which will export only the records for one patient.\nAdditionally, added support for the patient
parameter in Patient Bulk Export, which is another way to get the records of only one patient.$poll-export-status
endpoint so that when a job is complete, this endpoint now correctly includes the request
and requiresAccessToken
attributes.$export
operation receives a request that is identical to one that has been recently\nprocessed, it will attempt to reuse the batch job from the former request. A new configuration parameter has been$mdm-submit
can now be run as a batch job, which will return a job ID, and can be polled for status. This can be accomplished by sending a Prefer: respond-async
header with the request.$reindex
operation failed with a ResourceVersionConflictException
the relatedResourceVersionConflictException
during the $reindex
operation. In addition, the ResourceIdListStep
\nwas submitting one more resource than expected (i.e. 1001 records processed during a $reindex
operation if only 1000\nResources
were in the database). This has been corrected.upload-terminology
operation of the HAPI-FHIR CLI. you can pass the -s
or --size
parameter to specify\nthe maximum size that will be transmitted to the server, before a local file reference is used. This parameter can be filled in using human-readable format, for example:\nupload-terminology -s \\"1GB\\"
will permit zip files up to 1 gigabyte, and anything larger than that would default to using a local file reference.import-csv-to-conceptmap
command in the CLI successfully created ConceptMap resources\nwithout a ConceptMap.status
element, which is against the FHIR specification. This has been fixed by adding a required\noption for status for the command.reindex-terminology
command.DocumentReference
with an Attachment
containing a URL over 254 characters\nan error was thrown. This has been corrected and now an Attachment
URL can be up to 500 characters._include
and _revinclude
parameters in the JPA server has been streamlined, which should\nimprove performance on systems where includes are heavily used.reindex-terminology
command.":text
qualifier was not performing advanced search. This has been corrected.MAP_TO
properties defined in MapTo.csv input file to TermConcept(s).$mdm-submit
can now be run as a batch job, which will return a job ID, and can be polled for status. This can be accomplished by sending a Prefer: respond-async
header with the request.reloadExisting
attribute in PackageInstallationSpec. It defaults to true
, which is the existing behaviour. Thanks to Craig McClendon (@XcrigX) for the contribution!Welcome to the winter release of HAPI FHIR! Support has been added for FHIR R4B (4.3.0). See the R4B Documentation for more information on what this means. Now onto the rest!
\nActionRequestDetails
class has been dropped (it has been deprecated\nsince HAPI FHIR 4.0.0). This class was used as a parameter to the\nSERVER_INCOMING_REQUEST_PRE_HANDLED
interceptor pointcut, but can be\nreplaced in any existing client code with RequestDetails
. This change\nalso removes an undocumented behaviour where the JPA server internally\ninvoked the SERVER_INCOMING_REQUEST_PRE_HANDLED
a second time from\nwithin various processing methods. This behaviour caused performance\nproblems for some interceptors (e.g. SearchNarrowingInterceptor
) and\nno longer offers any benefit so it is being removed.reindex-terminology
command.":nickname
qualifier only worked with the predefined name
and given
SearchParameters.\nThis has been fixed and now the :nickname
qualifier can be used with any string SearchParameters.Accept
\nheader that matched the contentType
of the stored resource, the server would return an XML representation of the Binary resource. This has been fixed, and a request with a matching Accept
header will receive\nthe stored binary data directly as the requested content type.STORAGE_TRANSACTION_PROCESSING
has been added. Hooks for this\npointcut can examine and modify FHIR transaction bundles being processed by the JPA server before\nprocessing starts.$meta
operation\nagainst the deleted resource, and will remain if the resource is brought back in a subsequent update.Accept
header._outputFormat
parameter was omitted. This behaviour has been fixed, and if omitted, will now default to the only legal value application/fhir+ndjson
.[fhir base]/Patient/[id]/$export
, which will export only the records for one patient.\nAdditionally, added support for the patient
parameter in Patient Bulk Export, which is another way to get the records of only one patient.$poll-export-status
endpoint so that when a job is complete, this endpoint now correctly includes the request
and requiresAccessToken
attributes.$export
operation receives a request that is identical to one that has been recently\nprocessed, it will attempt to reuse the batch job from the former request. A new configuration parameter has been$mdm-submit
can now be run as a batch job, which will return a job ID, and can be polled for status. This can be accomplished by sending a Prefer: respond-async
header with the request.$reindex
operation failed with a ResourceVersionConflictException
the relatedResourceVersionConflictException
during the $reindex
operation. In addition, the ResourceIdListStep
\nwas submitting one more resource than expected (i.e. 1001 records processed during a $reindex
operation if only 1000\nResources
were in the database). This has been corrected.upload-terminology
operation of the HAPI-FHIR CLI. you can pass the -s
or --size
parameter to specify\nthe maximum size that will be transmitted to the server, before a local file reference is used. This parameter can be filled in using human-readable format, for example:\nupload-terminology -s \\"1GB\\"
will permit zip files up to 1 gigabyte, and anything larger than that would default to using a local file reference.import-csv-to-conceptmap
command in the CLI successfully created ConceptMap resources\nwithout a ConceptMap.status
element, which is against the FHIR specification. This has been fixed by adding a required\noption for status for the command.reindex-terminology
command.DocumentReference
with an Attachment
containing a URL over 254 characters\nan error was thrown. This has been corrected and now an Attachment
URL can be up to 500 characters._include
and _revinclude
parameters in the JPA server has been streamlined, which should\nimprove performance on systems where includes are heavily used.reindex-terminology
command.":text
qualifier was not performing advanced search. This has been corrected.MAP_TO
properties defined in MapTo.csv input file to TermConcept(s).$mdm-submit
can now be run as a batch job, which will return a job ID, and can be polled for status. This can be accomplished by sending a Prefer: respond-async
header with the request.reloadExisting
attribute in PackageInstallationSpec. It defaults to true
, which is the existing behaviour. Thanks to Craig McClendon (@XcrigX) for the contribution!