Greetings,
We were prompted with the question today as to whether OnBase could work with the Welcome kiosk module of Epic. From my understanding, these kiosks are places for patients to check themselves in for a visit (Enter and validate identification, insurance cards, etc).
I was curious if any of you had successfully interfaced OnBase with one of these before.
The environment this will be used on: Epic 2012, Onbase 11.0.2.254
Our current solution has staff scanning in all of these documents through Epic and integrated/stored into OnBase. So if my company goes with the Welcome kiosk they'd like for the information to still be stored/retrieved via OnBase. (Our BLOB server isn't set up to start handling a large load of registration documents).
The Epic TS that's working with our Registration team seemed to indicate that there was no direct OnBase integration with this module so I'm not sure if there's an indirect route that can be used.
There's also a section in the Welcome configuration pdf that mentions configuring for External Third party system for documents. I'll paste it at the bottom for reference. But if anyone has worked with this module and wants to give me some tips on your experiences or on configuration, I'd welcome the feedback.
Thanks
Configure Welcome to Use an External Third-Party
System for Documents
If you are using a non-Epic system to manage documents, you can configure Welcome to
send information using a web service.
Configure the Plug In
1. In Hyperspace, open a kiosk workstation record.
2. Go to the Plug Ins form.
EpicUUID: C871B763-AA59-420E-B784-1941D1383C36
Welcome 135
3. Set the following fields:
Interface: Epic.Kiosk.Interfaces.IDocument
Filename: Epic.Kiosk.DocumentHttpService.dll
4. In the Plug In Configuration Settings, configure the appropriate mnemonics for the plug
in. See the Tip section for more information on the available mnemonics.
The DocumentHttpService plug-in has a couple of configuration parameters that
determine how it functions. When you set up this feature, you have the following
options:
Server. An HTTP address that determines what web service the plug-in
connects to in order to send the document.
FileToPrelude. A Yes/No setting that determines whether Welcome files esignature
documents to the Prelude Documents table in addition to sending the
document to the web service. The default is No.
DateFormat. A string that specifies the format of the date that is replaced in
the %TODAYSDATE% mnemonic in the XML. The default is yyyy/MM/dd.
This format must be a valid .NET DateTime format.
Timeout. The number of seconds to wait before a timeout occurs when
connecting to the web service. The default value is 30.
AuthenticationType. The type of authentication to use when connecting to the
web service. Only the Basic authentication type is supported.
AuthenticationUserName. The user name for authentication with the web
service. This parameter is available in the
%AUTHENTICATIONUSERNAME% mnemonic if you need to insert it into
the XML templates. For example, if you're going to pass in the authentication
as part of the XML instead of in the HTTP headers.
AuthenticationPassword. The password to use for authentication with the web
service. This parameter is also available in the
%AUTHENTICATIONPASSWORD% mnemonic if you need to insert it into
the XML templates. For example, if you're going to pass in the authentication
as part of the XML instead of in the HTTP headers.
