What's Fixed
The following HDR FHIR bugs are ported from HDR 8.1.4 release to this 8.2 release. Also included are the following support enhancement in this release:
Table 1-1 Fixed in 8.2
Bug Number | Description |
---|---|
Enhancement 36285820 | Support to include HDR 7.0.2.x in HDR 8.2 release.
Now HDR 8.2 is packaged only with HDR 7.0.2.x and HDR FHIR 8.1.4 modules in this release. Note that HDR 8.1.x RIM server is removed in this release. Now HDR 7.0.2.x RIM server is HDR 8.2 RIM server. |
Bug 35593497 | HDR FHIR did not support FHIR versions R4B and R5.
Now HDR FHIR supports FHIR experimental versions R4B and R5. But it does not support transformation between the versions i.e. R4.0.1 to R4B, R4.0.1 to R5 and R4B to R5. Note: The database schema configured and used for one FHIR version should not be used for other FHIR versions. i.e. Schema configured to be used for R4, should not be used for R4B and R5, configured to be used for R4B, should not be used for R4 and R5, and configured to be used for R5, should not be used for R4 and R4B. |
Bug 35393352 | In HDR FHIR schema, the partitioning columns (partition_date and
partition_id) were not added on to the resources extended tables.
Now HDR FHIR supports partitioning, and the corresponding partitioning columns (partition_date and partition_id) are added on to the resources extended tables. |
Bug 35599740 | HDR FHIR did not support searching resources using patient
:identifier modifier. Now HDR FHIR supports for searching resources
using patient :identifier.
Example:
[Searches for all Consent resources that reference a patient by a particular patient identifier.] |
Bug 35393317 | HDR FHIR server did not have the property to enable/disable the
scheduler JOB that check Resource Count.
Now HDR FHIR server is able to enable/disable the scheduler JOB that check the Resource Count via the following property.
If this property is enabled, the Resource Count scheduler JOB will be triggered for every configured interval of time and retain the resource count in cache with configured cache expiry time in minutes. This can also be controlled with the following properties:
|
Parent topic: Oracle Healthcare Data Repository