You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When attempting to use a dateTime value with fractional seconds of more than 6 digits of precision in a FHIRPath expression, an exception is returned: com.ibm.fhir.path.exception.FHIRPathException: java.time.format.DateTimeParseException: Text '2012-04-15T15:00:00.000000000Z' could not be parsed, unparsed text found at index 26
To Reproduce
Steps to reproduce the behavior:
use a dateTime value with a fractional seconds precision of more than 6 digits in a FHIRPath expression
Expected behavior
In order to be consistent with parsing of dateTime and instant fields on object creation (see issue #1446), and date values in search queries (see issue #1505), up to 9 digits of precision should be allowed for fractional seconds in FHIRPath dateTime values, and should be truncated to 6 digits of precision when evaluating the FHIRPath expression.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When attempting to use a dateTime value with fractional seconds of more than 6 digits of precision in a FHIRPath expression, an exception is returned:
com.ibm.fhir.path.exception.FHIRPathException: java.time.format.DateTimeParseException: Text '2012-04-15T15:00:00.000000000Z' could not be parsed, unparsed text found at index 26
To Reproduce
Steps to reproduce the behavior:
Expected behavior
In order to be consistent with parsing of dateTime and instant fields on object creation (see issue #1446), and date values in search queries (see issue #1505), up to 9 digits of precision should be allowed for fractional seconds in FHIRPath dateTime values, and should be truncated to 6 digits of precision when evaluating the FHIRPath expression.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: