01-14-2022 10:06 AM
Hello Everyone.
We want to thank you for your valuable participation in this thread as well as everywhere else that you engage on Community. We were recently able to have a new topic added to Community for Forum posts, which is simply titled "Hyperdrive". This will enable us to build a collection of Forum posts, both Q&A and Discussion types, specifically for Hyperdrive. Example:
In addition, using separate Forum posts with the Hyperdrive topic will better support answering specific questions or discussing issues/concerns/best practices in their own threads instead of here in this long thread, where information is more likely to get lost.
For current/ongoing discussions that are already taking place in this thread, please feel free to continue to use it or start a new Integration for Epic Forum post with the Hyperdrive topic (when applicable).
In the future, we will add a final post to this thread notifying you that it's locked to new replies and asking that we create new Forum posts with the Hyperdrive topic instead.
To create a new Forum post with the Hyperdrive topic:
1. Navigate to the Integration for Epic Forum.
2. Click
3. In the Topic field, choose "Hyperdrive" from the dropdown menu.
If you have any questions, please feel free to reach out. If you have any issues using this functionality, please reach out to Community Support.
02-15-2022 09:44 AM
Hi
FOS and SAS need to interact with the scanner driver installed on the local scanning machine which is why there is still a technical footprint. This is different that Healthcare Web Viewer (viewing) and DefPop for Epic (deficiencies) which with Hyperdrive are all web based.
02-15-2022 12:15 PM
Another question I would like to ask (and yes I know I asked it in the recent webinar), but I want to ask it here.
With the new Healthcare Web Viewer, I know in the original release it was pointing directly to the Application Server itself, similar to how it does it today. However, I will note that it has been mentioned that it will eventually being pointed directly to the Web Servers since it is going to be a web based program. Since currently we can easily spin up additional application servers as we see fit (since there is no real licensing needed), that is fine and dandy, but in order to spin up additional Web Servers requires the purchasing of additional licensing.
Is Hyland looking to make any sort of changes in how licensing will be performed? This is specifically for the Web Servers since this could mean some customers (especially those of us on-prem still) could need to spin up additional Web Servers to handle the additional traffic.
Thanks.
02-16-2022 11:01 AM
I know the question was asked about Citrix. Has this been certified for use on Horizon as well for FOS and Docpop?
thanks!
02-21-2022 04:00 PM
Hi
I definitely understand your concern with potentially needing additional Web Server licenses to handle the increased volume/traffic as you move to the Healthcare Web Viewer. I have put the question out to some resources at Hyland and will follow up here when I have more information.
Thanks!
02-21-2022 04:04 PM
Hello
We don't certify the integration with any virtualization platform. However, we would expect the Hyperdrive integration to continue to work as your Hyperspace integration does today. Of course, if you run into any issues using it on Horizon, please don't hesitate to reach out to Support. We do not anticipate there being any issues with Horizon at this time.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.