Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Missing asGetSlots Stored Procedure

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

5 Posts

2 Users

0 Reactions

74 Views

RSS

rzadera

(@rzadera)

Posts: 3

Active Member

Topic starter

The asGetSlots stored procedure is missing after upgrading from 12.0.7 to 12.0.13. We were using this stored procedure in conjunction with the cusasAppointmentSearchSingle stored procedure to develop a Third Next Available Appointment report. The cusasAppointmentSearchSingle stored procedure still calls asGetSlots, but gives the error:

[SQLSTATE 42000] (Error 313) An insufficient number of arguments were supplied for the procedure or function asGetSlots.

Has anyone else run into this issue?

Posted : February 24, 2017 9:43 am

mikeseale

(@mikeseale)

Posts: 344

Reputable Member

asGetSlots is a function. That error is telling you that you are calling asGetSlots with the incorrect number of arguments. I would look in your custom stored procedure to make sure you use 5 parameters. asAppointmentSearchSingle calls it like this:

SELECT s.* FROM asGetSlots(@DateCounterStart, @DateCounterEnd, @GUID, @ListOrder, @IncludeUnallocated) as s

Posted : February 24, 2017 10:13 am

rzadera

(@rzadera)

Posts: 3

Active Member

Topic starter

Thanks for your reply! The code you provided is how our cusasAppointmentSearchSingle is calling asGetSlots, but it seems that asAppointmentSearchSingle is calling the following:

SELECT s.* FROM asGetSlots(@DateCounterStart, @DateCounterEnd, @GUID, @ListOrder, @IncludeUnallocated, @SearchFilterDailyLimit, @SearchFilterFinLimit, @PatientId, @CaseId ) as s

Is it possible that after the update to 12.0.13 asGetSlots is requiring 9 parameters?

Posted : February 27, 2017 4:58 am

mikeseale

(@mikeseale)

Posts: 344

Reputable Member

Yes. We are on 12.0.11, and it is still using 5 parameters. I looked on my demo database for 12.2 and here are the notes for the 4 newly added parameters:

@FilterDailyLimit CHAR(1) = 'N' -- default to "No", DO include Daily Limit"

@FilterFinLimit CHAR(1) = 'N' -- default to "No", DO include Daily Finance Limit"

@PatientId INT -- In the case of Patient Appointment pass the value for Patient Profile ID

@CaseId INT -- In the case of Patient Appointment a case has attached while searching appt slot. a non zeo value is passed if case attached

Posted : February 27, 2017 5:06 am

rzadera

(@rzadera)

Posts: 3

Active Member

Topic starter

Thanks a lot! Everything is fixed.

Posted : February 27, 2017 7:17 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0