I have been given the lead on our Invoicing process and I have to say
ugly is an understatement.
CIO direction is to have everything be done via a SP call. This
Invoicing run is an amazing process to say the least. I am 1/3 of the
way through the process I think, and there is stuff that scares me.
Comments are there explaining who wanted something and why. All of
them seem to stem from the fact that we don't validate data on the
front end. We will fix it here over and over again.
After the 50+ combination of SPs are done in the end we have two
tables, Master and Header, that contain the entire days billing or
just one finite group. When that data is either pushed to paper or to
EDI we move the rows to a history table.
There are changes to practice IDs that run nightly
set @Stmt = '' +
'UPDATE p ' +
'SET Pract_Code = CASE WHEN p.Date_of_Service >= ' + '''' +
'2/1/2010' + '''' + ' THEN @NewPract
ELSE @OldPract END ' +
'FROM ' + @Pending +
@Where + 'p.Pract_code IN (@OldPract, @NewPract) '
Yes that is dynamic SQL generated in a SP to be executed within.
Dynamic there doesn't scare me. Changing ID's does!
--
Stephen Russell
Unified Health Services
60 Germantown Court
Suite 220
Cordova, TN 38018
Telephone: 888.510.2667
901.246-0159 cell
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
