Notifications
Clear all
General Discussion
8
Posts
4
Users
0
Reactions
114
Views
Topic starter
I have a ScheduleLink Import interface created through LinkLogic in my test environment but am having an error that I cannot seem to get past. The error message that I am getting is "Schedule Import: Appointment: (Lastname Firstname, 11/15/2016 4:00 PM) with Resource: ResourceName was not created. Not able to lock the Slots.
Import file: C:\USERS\ABULSARA\DESKTOP\BATES - COPY (2).SL"
Does anyone have any idea as to how to resolve this error? The appointment does exist for the patient and the resource for the date and time specified in the HL7 messages. I can post the message on here if required. I am hoping that someone can help.
Posted : December 15, 2016 10:17 am
I don't have any inbound schedule interfaces, but I want to clarify a question: Do you mean the appointment already exists prior to import, or that it didn't exist and the import appears to be successful?
Posted : December 15, 2016 11:23 am
Can you manually schedule the same slot you have referenced in your HL7? Might be a problem with the actual schedule.
Posted : December 15, 2016 11:45 am
I have a decent amount of experience with this error.
It means that there is a conflict in the facility, appt type, resource or available appt slot that is causing the error. (There needs to be an exact match on appt type/facility/resource or it will error out) . If you have an open schedule, there must be empty space in the schedule to accommodate the entire appt.
Finding the resolution is half the problem and then the other problem is sending the message back through. As far as I am aware, you have to find the *.slq file - rename it to *.sl file; delete the error entry in the Linklogic error log and throw it back through linklogic to reprocess.
I would love to find an easier way if anyone knows one.
Posted : December 16, 2016 1:03 am
Topic starter
First off, thank you all for responding.
I have tried both ways, using an existing appointment and with no existing appointment - still receive the same error. I have made sure that the Resource, Facility and Appointment type are exactly the same. Because this is a ScheduleLink import through LinkLogic, it relies on MIK, which I have configured and mapped the Resource, Facility and Appointment Types to what is in the HL7 message.
I am attaching the HL7 message for reference as that may help.
Posted : December 16, 2016 5:21 am
@jennfranco Mirth Connect is the way to go for reprocessing HL7. We route all of our interfaces through Mirth even if we don't need to manipulate the HL7 at all.
Posted : December 16, 2016 5:30 am
Topic starter
Ok, I got it working just as Jenn said.
Jenn, I have a question are you able to import custom Appointment Status as part of this process or are we limited to what is defined for ScheduleLink interface?
Posted : December 16, 2016 7:42 am
I didn't have to experiment with that because we only use the standard ones.
Posted : December 16, 2016 7:55 am
