EMR Help submissions intermittently do not create EMR Request Data when remote_session_info is emptyIssue When a record producer using EMR Help is submitted, the associated EMR Request Data record may intermittently not be created. The system log contains the warning:Empty JSON string A downstream flow that expects the EMR Request Data record may subsequently fail because the record is unavailable. The affected submissions have an empty remote_session_info variable. Release Not release specific. Cause RecordProducerDataProcessor reads the remote_session_info variable and parses its value as JSON. When the variable is empty, JSON processing generates the “Empty JSON string” warning and the EMR Request Data record is not created. The variable is populated by the EMR Help Session Information widget. The associated header stores the incoming parameters in the server session and then places an EMRTABID value in the browser’s sessionStorage. The widget reads that tab identifier when it loads and uses it to retrieve the stored parameters. The available investigation indicates that remote_session_info can remain empty if the widget does not retrieve the stored parameters. A timing or session mismatch between the header and widget was suspected, but the case did not confirm this as a product defect. Resolution Use the following relief when the record producer is launched from an external application: Change the external launch URL to open the EMR Help home page, emr_assist_home_page, while preserving the required launch parameters.From the EMR Help home page, navigate to the applicable record producer.Submit a test request.Confirm that remote_session_info is populated.Confirm that an EMR Request Data record is created for the submitted request.Monitor subsequent submissions to determine whether the intermittent empty-value condition continues. Opening the home page first allows the header to process the launch parameters before the record producer and its Session Information widget load.