Forum Replies Created
-
AuthorReplies
-
January 24, 2007 at 8:04 pm in reply to: Engine to Weblogic connection – getting rid of MQ Series #58115
I’m trying to get the simple Java Class Test to work on our system. I was able to compile and add to the outbound disp list, but get “invalid command name “cljTPS”” in the log. Am I missing a library or something? I’d be glad to help you out, but not quite sure what you’re asking for. What version/OS of QDX are you on and what training/experience do you have with HL7 and the engine? What version of Meditech C/S are you on? We’ve done lab results, but not to EMR yet. We are currently working on Muse, Cathlab and PACS to Meditech ITS. We’re finalizing the contract with GE for the PCS User query response interface. It is my understanding that queries are initiated at the client level which could be any client workstation – Did you limit the workstations queries could be initiated from? I’d be interested in learning more on how you implemented this. Did you use the Multi-Server connection option in QDX with this or is there a central server all querries are sent from? My guess is you’re getting mixed signals due to the nature of Meditech’s Database. We currently have inbound interfaces to Meditech – Specifically Lab Results, Radiology(ITS) Results, Billing(B/AR) Charges and soon PACS Results. These are all purchased interfaces and work well with relative ease to develop in conjunction with QDX. You have some control on the Meditech side in the MIS Database “Background Jobs” and “IN/OUT Boxes”. The confusion comes into play in regards to the Database – It is a Windows file based system and very proprietary. Inorder to gain access to the database for some items not worthy of the outlay for an interface, we initially had to resort to a combination of screen scraping tools(Automate Pro) and sending reports to files to get some info out. We also used screen scrapes to get some data in through the GUI on a limited basis. We are now working with Ipeople(Meditech Partner) to access the database using an ODBC tool they have developed for getting info out with out the screen scrapes – It works quite well, but does not allow for populating data. Another potential partner is Boston Software. Hope this helps; good luck. I too am interested in this topic. The procedure I used without issue in our test evironment was to change the process name in netconfig too the more consolidated version and then move all old process directories in the file structure to a temp backup folder. I haven’t had issues thus far. I was able to resolve with another posting I found and copied below. Thanks to Terry Kellum <<<<<<<<>>>>>>>>>>>..
Make sure that you can ping the box.
Make sure that you have the same version of server and client (different versions use different ports..).
Make sure that you have this stanza in your
/server/server.ini file: [firewall]
rmi_exported_server_port=1.1.1.240
Please replace the IP with the IP of your cloverleaf server.
Restart the host server.
Alternatively, open the hicservedradmin gui on the server x-windows session, and go to the host server firewall tab and enter the IP address there under “exported server address”.
Tom Did you get a resolution to this? I’m running into the same issue.
Thanks for the info Dennis the log files didn’t exist and only get the one I posted if start from a shell prompt – Gui doesn’t produce it.
we have 4GB memory
Yes they are HL7 Compliant with pretty smooth deliveries. When issues do come up with regards to message formatting, they work relatively quickly to address them – relative based on criticality. We interface with Meditech Client/Server Version 5.4 – Not Magic(a big difference. Current segments utilized with QDX are ADT, DFT, RDE/RDS, ORM and ORU. As with most vendors’, you have to drive the project and not wait too long for responses. There documentation isn’t great, but is enough to get you to a testing phase. The general response to an interface delivery request is 3 months out after paperwork is signed. Meditech has a call tracking management portal that notifys you with emails when the task is updated – this provides a nice accountablity trail. They provide you with a tools to minimally control/view interfaces and messages once implemented. Let me know if you have any specific questions, I’m more than willing to share more. Bob
-
AuthorReplies