| Panel |
|---|
| borderColor | blue |
|---|
| bgColor | #B3D4FF |
|---|
| borderWidth | 1 |
|---|
| borderStyle | solid |
|---|
| Communication Worklist Screen |
The Communication Worklist is a central location in VetView to monitor, view, and control the automatic medical record communications that fire upon scheduled events, such as patient check-in or document approval. A client coordinator or another staff member who has been designated to review these communications can confirm that the information is complete and accurate before sending it to an owner or RDVM. Note that these scheduled communications are different from Patient Reminders, which occur based on product triggers, or Scheduled Appointment Reminders, which occur based on upcoming appointments. Clinical staff may also have the option to manually send certain communications directly from the patient record when appropriate.
Search For CommunicationThe top part of this screen contains two sets of fields for narrowing down the list of communications in the system. If you click the Search button without a limiter, it will load all communications that have been sent, past and present, which may not be useful. Narrow down your search results depending on what task you are trying to accomplish to load only the communications that matter. Episode/PatientThis section looks for communications based on the hospital episode, patient, or unit associated with the communication. 
Communication OptionsThis section allows you to search based on the communication itself - the current status, the type, the event that triggered it, or the date it was created. 
Search ResultsThe results will display below. A one line summary will be visible for each communication, with the option to expand it and view further details. 
Create NewThis button will open a new window to manually created a new communication. 
| Field | Description |
|---|
| Case No / Patient / Client | Selects the patient and the client type for this communication (RDVM or Owner.) | | Episode | Searches episodes associated with the patient, which will be used to make the communication. | | Send To | Chooses the client that this communication will be sent to. | | Via | Selects the route that this communication will be sent by - mail, email, or fax. | | Write In Route | If there is no available write, you can create a new method using this button. | | Email/Fax Contents | The Email Subject and Body, or Fax Subject and Body, depending on which method you are using. |
AttachmentsThis tab allows you to select the documents from the episode that will be sent with the communication. 
Daily UpdatesThis action will create and send the "Daily Updates" report for any patients who are currently listed on the Patient Census. Use this feature to update RDVMs on the patient status. Actions on Multiple CommunicationsSelect the communication using the checkbox on the left and then click a button on the top to perform actions on all selected | Field | Description |
|---|
| Send Selected | Sends communications that are Pending when all other conditions are met. | | Delete Selected | Deletes the communications that are selected, and they will not be sent. Use this to clear out old communications, or communications that are not necessary. |
Detailed View of CommunicationTo view each communication's details, click on the expander. The basic episode details, the communication details, and the message contents will appear. If a communication is incomplete, the missing information will appear in red. In the example below, the client doesn't have a contact method set to receive the Owner communications, and the document has not been verified. Once these issues are resolved, the status on the communication will change to Pending. CTRL+ click on the underlined fields to open the client, patient, or PA in a new tab. 
| Field/Button | Description |
|---|
| Episode Details | General information about the episode, such as when it was created and opened, and when it was closed. Note that episodes that were not discharged and closed when the patient actually visited may have a wide disparity in dates - this information is intended to guide you in determining whether the communication should even be sent at all. In the example above, it is probably safe to cancel this communication. | | Contacts | The client to whom this communication was to be sent, and the faculty, students, and staff who were assigned to the episode. | | Communication Details | The event that fired off this automatic communication. For this episode type, the event of "Close Order" was set to automatically fire off a verified Discharge document. | | Route Details | The method that this communication was intended to be sent. The client did not have a communication method set for Owner communications, so you must choose one, or manually add a new one, before this communication is ready to go. For most owners, this is usually an email address, but some RDVMs may still prefer that documents are sent via fax instead. | | Message Contents | The subject and body of the communication. Items in brackets are "placeholders" and will pull in the appropriate patient and client information from the database when it is sent. | | Attachment | The PDF of the medical record document that will be attached to the communication. Documents and Request reports must be verified by the clinical staff before they can be sent. Documents may also be missing from the medical record. | | Refresh | If you are in contact with the clinical staff and they have confirmed they have Verified the missing documentation, click this button to update the status of the document. | | Preview | Opens a window to display how the communication will look once sent, including pulling in the appropriate placeholders. | | Edit Details | Change basic information about the communication - which patient, which episode, which client. Change the email subject and body. Change the attachment to a different document from the episode. | | Cancel | Cancels the communication, but leaves it intact in the queue in case someone may need to review it in the future. The communication will not be sent. | | Delete | Deletes the communication and removes it from the queue. The communication will not be sent. Deleted communications cannot be searched from VetView. Use this to remove duplicate communications, or communications that were incorrectly fired off during an event (e.g. if a patient was discharged but then seized before client pickup and was re-admitted, the initial Discharge communication should be deleted.) |
|