16730: add more details for convertDateTimeToReceiverLocalTimezone

prime-router/docs/onboarding-users/migrating-receivers.md

@@ -68,7 +68,7 @@ In order to migrate existing covid pipeline settings to the UP a few settings ne
 * `schemaName:` Schema name specifies how the RS FHIR bundle should be translated to HL7 if the receiver's format is HL7. 
 If they're receiving HL7 v2 ORU_R01. The schema name can be updated to `azure:/metadata/hl7_mapping/ORU_R01/ORU_R01-base.yml`. 
 If the receiver has any specific receiver transforms the schema name should be updated to point to the schema location.
-* `convertDateTimesToReceiverLocalTime` This setting is no longer able to be used directly. If this setting is present, it should be set to `false`. To enable similar functionality to convert datetimes instead, an enrichment schema can be added under the `enrichmentSchemaNames` list.
+* `convertDateTimesToReceiverLocalTime` This setting is no longer able to be used directly. If this setting is present, it should be set to `false`. To enable similar functionality to convert datetimes instead, an enrichment schema can be added under the `enrichmentSchemaNames` list. See also: [Translate#extending-schemas](https://github.com/CDCgov/prime-reportstream/blob/master/prime-router/docs/universal-pipeline/translate.md#extending-schemas)
 * `jurisdictionalFilter:` The jurisdictional filter needs to be updated to use FHIR path. 
 The most common way to route messages to a STLT is based on the patient's or performer's state. 
 The FHIR path for that looks like this: `"(Bundle.entry.resource.ofType(ServiceRequest)[0].requester.resolve().organization.resolve().address.state = 'MT') or (Bundle.entry.resource.ofType(Patient).address.state = 'MT')"`
@@ -167,6 +167,7 @@ If the receiver has any of the following settings enabled they will need a recei
 - suppressAoe: true
 - defaultAoeToUnknown
 - replaceUnicodeWithAscii
+- convertDateTimesToReceiverLocalTime: false
 - useBlankInsteadOfUnknown
 - usePid14ForPatientEmail: true
 - suppressNonNPI

prime-router/docs/onboarding-users/receivers.md

@@ -123,6 +123,7 @@ The mechanism for how each record is translated is laid out in the schema, which
 specific to your receiver.
 * In the UP for HL7 v2 we have to check what HL7 message type they want to receive data in. We support ADT_A01, OML_O21 and ORU_R01. Depending on the message type we can set `translationSchema` to the respective message type schema.
 * If the receiver wants specific receiver transforms that are not supported by the translation settings a schema can be created for them. More information on how to manage translation schemas can be found here (https://github.com/CDCgov/prime-reportstream/blob/main/prime-router/docs/universal-pipeline/translate.md)
+  * For example: the `convertDateTimesToReceiverLocalTime` translation is no longer able to be used directly. If this setting is present, it should be set to `false`. To enable similar functionality to convert datetimes instead, an enrichment schema can be added under the `enrichmentSchemaNames` list.
 
 
 ### 3. Test and commit, and deploy to Test and maybe Prod

prime-router/docs/universal-pipeline/translate.md

@@ -63,6 +63,8 @@ California specifies receiving HL7 ORU_R01 messages that mostly match the conver
 the
 datetimes changed to be PST.
 
+Another enrichment schema extension for converting time zones can be added to replace the function of the `convertDateTimesToReceiverLocalTime` translation field. An example of this is for the US Mountain time zone. Example: [datetime-to-local-mtz.yml](prime-router/docs/onboarding-users/migrating-receivers.md)
+
 #### De-identification
 
 There is limited support for de-identification in the universal pipeline by applying the RADx_MARS-base-deidentified.yml