To use Document Queue, you must have enabled the TX Text Control by run the TX Text document conversion.
Note: NextGen Healthcare does not recommend offline document generation through VMware®.
Document Queue uses basically the same software as real-time document generation and has similar requirements to NextGen® Enterprise EHR.
- CPU, memory, operating system: Same requirements as NextGen® Enterprise EHR.
- Database connectivity: Basically the same requirements as NextGen® Enterprise EHR with the following exception:
If the database connection is lost and then restored, Document Queue should begin processing documents again once the connection is restored. This differs from NextGen® Enterprise EHR, which must be shut down and restarted if the connection is lost.
- Document Queue must run on the windows desktop as a user, the same as NextGen® Enterprise EHR.
- Document Queue must be shut down and restarted if universal preferences are changed, the same as NextGen® Enterprise EHR.
- NextGen Healthcare recommends that you run Document Queue on a dedicated workstation.
Document Queue experiences the best performance when run on a machine with no other actively running applications or relatively lightweight or sporadically active applications. Other applications that have very high CPU or database usage may slow down performance of Document Queue.
- To properly use Document Queue, all workstations (including the one that runs the utility) must be connected to the same database.
- To ensure proper document generation, all workstations running an instance of the Document Queue must have a default Windows printer. The default printer must be a physical printer, and not a file-based printer such as a PDF or XPS printer.
Contact your implementation specialist or NextGen Healthcare Client Support regarding the workstation setup for offline document generation.
