Saving, Copying, & Sharing Responses



Purpose

This article explains how Consult stores conversations, how to copy text from a response, and how to share a response with a colleague.


How Conversations Are Saved

Consult saves every conversation as a persistent thread. The thread is created as soon as a message is submitted, before the response is generated, so conversations are preserved even if the response is interrupted or the session ends unexpectedly.

To return to a previous conversation:

  1. Open Consult.
  2. Next to the blue send message button, click the clock icon.
  3. A sidebar will appear on the right side of the screen, select the conversation from the thread history.
  4. The full conversation, including all prior exchanges, loads in the main view.


Copying Response Text

Consult includes a built-in copy tool at the bottom of any given response. To copy a response:

  1. Locate the copy icon at the bottom of your Consult response.
  2. Click the icon and paste into a document, clinical note, or messaging application.

For smaller selections, you can select the text using your cursor and use the standard keyboard shortcut for your device (Command + C on macOS; Ctrl + C on Windows). In text citation numbers are included but not the actual referenced piece of literature if selected or if the built-in copy tool is used but can be removed.


Sharing A Response

Consult does not currently include a native share or permalink feature for individual responses. To share a response with a colleague:

  1. Copy the relevant text as described above.
  2. Paste into an email, clinical note, or institutional messaging application.

Important To Remember

  • Conversations are private and visible only to the signed-in physician. They are not shared across users within the same organization.
  • Conversation threads persist across sessions.
  • Consult does not delete old conversations, you can find all of your previous conversations in the history drawer.

Related Articles

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us