Page 1 of 1

MPIC interface with Medinotes

Posted: Sun Aug 12, 2018 5:49 pm
by ExpertSkinDoc
I recently upgrade the server, backup and restore, everything went fine, even the MPIC interface between Medisoft and Medinotes, patients were updated, but the appointment list wasn't so lucky, it lost its functionality in the upgrade process.
How does Medinotes pull the MPIC information into its database?
Is there a way to reset the database so the appointment list gets sync again?
Please PM me to see if I need a technician to take a look to fix the problem.

Mychael Luu, MD
Silicon Valley Dermatology

Re: MPIC interface with Medinotes

Posted: Mon Aug 13, 2018 10:01 am
by Gavin Walker
We have one client left still interfacing Medisoft to Medinotes. Running that one on Windows Server 2012 R2 and I am scared to try running Medinotes on a higher version of Windows. You need MPIC, Mirth, and the ASAService all running. Maybe one of the Mirth channels is stopped or the option to send appointments is turned off in MPIC.

Re: MPIC interface with Medinotes

Posted: Thu Dec 08, 2022 9:07 pm
by ExpertSkinDoc
I recently had to restore Medisoft and Medinotes and rebuild MPIC interface. Everything went fine using the default defaultconfig.xml for setting Mirth. MPIC would extract and export the pt's demographics and appointments from Medisoft just fine. But error occurs when MediHL7s.exe imports the HL7 files into Medinotes. Pt's demographic is imported into Medinotes OK, but error would occur for the importing of pt's appointments. Each time it there is an error importing into Medinotes with "Could not find user External ID" error showing in MediHL7s.log. MPIC is working well, the Mirth channels for outbound demographics and outbound appointments are working well, I just can't get MediHL7s.exe to import correctly into Medinotes.
Here is an exerpt of the error that is generated by MediHL7s.ese:

---------------------- Received S12 message ---------------------------------
Could not find user External ID
---------------------- Received S14 message ---------------------------------
Could not find user External ID
---------------------- Received S14 message ---------------------------------
Could not find user External ID
---------------------- Received A08 message ---------------------------------
Failed to Create Physician Record! FirstName = LastName =
Failed to Create Physician Record! FirstName = LastName =
Failed to Create Physician Record! FirstName = LastName =
Updated <Pt name> - <Chart Number> on 12/8/2022 2:23:36 PM

Gavin, could you help? What should I use to setup Mirth, apparently the defaultconfig.xml is OK for pt's demographics, but not for appointments. I saw there are other files in C:\Program Files\Mckesson\Mckesson Practice Interface Center\Mirth such as MPIC-Outbound-Appointments.xml, MPIC-Outbound-Demographics.xml, etc. Do I need to do something else for MediHL7s.exe to import appointments properly?

Mychael Luu, MD
Silicon Valley Dermatology

Re: MPIC interface with Medinotes

Posted: Fri Dec 09, 2022 9:38 am
by Gavin Walker
Was Medinotes discontinued 11 years ago? There is no where to go back for support if we run into issues. And, we don't even know if it will work on modern operating systems. I'm inclined not to take the job 'cause I'll have to charge you for my time and I still may not get it to work and then you're out the money. In fact the one customer we had on Medinotes is gone now because he switched to a different EMR, but he wanted us to keep the old systems running in case any of his old clients had any questions. I had to tell him 'no' because we can't support it anymore. Sorry. :(

Re: MPIC interface with Medinotes

Posted: Mon Dec 12, 2022 2:37 pm
by ExpertSkinDoc
Problem solved! Had to run HL7 import from HL7 tab in Workgroup Notification Server = CP32SERVER_Communication_Server
= MediNotes e Server as opposed to MediHL7s.exe or MediHL7server.exe.

Medinotes was discontinued many years ago, but I still find it indispensable for keeping track of image files and writing up letters from templates. It is quite configurable, that's what I like about it. I am certainly not using it for EMR/EHR, it's so antiquated.