It has been identified that the e-RS APIs are not strictly enforcing fields using the FHIR instant datatype.
The FHIR documentation defines the FHIR instant datatype as follows:
“An instant in time - known at least to the second and always includes a time zone.”
The e-RS currently incorrectly accepts FHIR instant values that:
- Do not have a time component (i.e. date only)
- Have a date and time but are missing the timezone
In January 2025 the e-RS will start rejecting FHIR instants that do not have a time component (1).
Later in the year the e-RS will start rejecting FHIR instants that do not contain a timezone (2).
Please take action now to ensure your integration is not impacted by these changes.
We have already contacted partners that have provided non-compliant values in the Integration or Production environment in the last 3 months.