Skip to content

Commit 03c9f14

Browse files
committed
Adding additional section to FAQ, TSG, and Release Notes
1 parent 9174f28 commit 03c9f14

File tree

3 files changed

+24
-0
lines changed

3 files changed

+24
-0
lines changed

articles/healthcare-apis/fhir/convert-data-faq.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,12 @@ For more information, see [Access the FHIR service in Azure Health Data Services
4646

4747
The experience and core `$convert-data` operation functionality is similar for both Azure API for FHIR and the FHIR service in Azure Health Data Services(../../healthcare-apis/fhir/overview.md). The only difference exists in the setup for the Azure API for FHIR version of the `$convert-data` operation, which requires assigning permissions to the right resources.
4848

49+
## Why are my dates being converted when transforming JSON data?
50+
51+
Its possible for dates supplied within JSON data to be returned in a different format than what was supplied. During deserialization of the JSON payload, string values, which are identified as dates get converted into .NET DateTime objects. These objects then get converted back to strings before going through the Liquid template engine. This conversion can cause the date value to be reformatted and represented in the local timezone of the FHIR service.
52+
53+
The coercion of strings to .NET DateTime objects can be disabled using the boolean parameter `jsonDeserializationTreatDatesAsStrings`. When set to `true`, the supplied data is treated as a string and won't be modified before being supplied to the Liquid engine.
54+
4955
Learn more:
5056

5157
[Azure API for FHIR: Data conversion for Azure API for FHIR](../../healthcare-apis/azure-api-for-fhir/convert-data.md)

articles/healthcare-apis/fhir/convert-data-troubleshoot.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,12 @@ Default template implementations for many common scenarios can be found on the [
3434

3535
## Debugging and testing
3636
In addition to testing templates on an instance of the service, a [Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-health-fhir-converter) is available. The extension can be used to modify templates and test them with sample data payloads. There are also several existing test scenarios in the [FHIR Converter GitHub repository](https://github.com/microsoft/FHIR-Converter/tree/main/src/Microsoft.Health.Fhir.Liquid.Converter.FunctionalTests) that can be used as a reference.
37+
38+
## Why are my dates being converted when transforming JSON data?
39+
40+
Its possible for dates supplied within JSON data to be returned in a different format than what was supplied. During deserialization of the JSON payload, string values, which are identified as dates get converted into .NET DateTime objects. These objects then get converted back to strings before going through the Liquid template engine. This conversion can cause the date value to be reformatted and represented in the local timezone of the FHIR service.
41+
42+
The coercion of strings to .NET DateTime objects can be disabled using the boolean parameter `jsonDeserializationTreatDatesAsStrings`. When set to `true`, the supplied data is treated as a string and won't be modified before being supplied to the Liquid engine.
3743

3844
## Next steps
3945
[Overview of $convert-data](convert-data-overview.md)

articles/healthcare-apis/release-notes-2024.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,18 @@ ms.custom: references_regions
1515

1616
This article describes features, enhancements, and bug fixes released in 2024 for the FHIR® service, DICOM® service, and MedTech service in Azure Health Data Services.
1717

18+
## July 2024
19+
20+
### Azure Health Data Services
21+
22+
### FHIR service
23+
24+
#### Disabling .NET DataTime objects from JSON data supplied to the $convert-data operation
25+
26+
It's possible for dates supplied within JSON data to be returned in a different format than what was supplied. During deserialization of the JSON payload, string values, which are identified as dates get converted into .NET DateTime objects. These objects then get converted back to strings before going through the Liquid template engine. This conversion can cause the date value to be reformatted and represented in the local timezone of the FHIR service.
27+
28+
The coercion of strings to .NET DateTime objects can be disabled using the boolean parameter `jsonDeserializationTreatDatesAsStrings`. When set to `true`, the supplied data is treated as a string and won't be modified before being supplied to the Liquid engine.
29+
1830
## May 2024
1931

2032
### Azure Health Data Services

0 commit comments

Comments
 (0)