On Nov. 20, 2025, we plan to release an update to the FHIR
address data type handling logic to better align with FHIR specifications and prevent inclusion of empty address objects and arrays in bundles. In v0.10.0 and v0.11.1 we identified an issue where we were missing an empty address guard, which allowed addresses containing only metadata fields (e.g., use or type) but no actual content (line, city, state, postalCode) to be included in FHIR bundles. Example of affected payload:
"address": {
"use": "work",
"type": "physical"
}
A guard will be added to filter out
After the change, empty addresses will be omitted from FHIR bundles, bringing behavior in line with the FHIR specification, which states: “Objects and arrays are never empty, and properties never have null values".
address objects and arrays that contain only metadata fields.After the change, empty addresses will be omitted from FHIR bundles, bringing behavior in line with the FHIR specification, which states: “Objects and arrays are never empty, and properties never have null values".
The images below show examples before (red) and after (green) the
address array and object change:
We recommend that you review your integration logic to ensure that you are properly processing omitted
address fields. Following the release, if you notice any unexpected errors, please report it via ocean.tips/support, including your site number and examples.