To Meditech L, I have received some responses stating that the problem may be with the Ops Summ being a static snapshot in time vis a vis BAR.PAT which is a constantly changing structure. However, my report is selecting on @txn.bch.date at the transaction level of BAR.PAT. Shouldn't @txn.bch.date mirror the posting date in BAR.BCH? I actually have a question in to Meditech to verify this point. If you look at the data definition of @txn.bch.date you will see it is a derived field from @txn.ser.date MINUS @txn.bch.date.offset. Maybe this is the problem.
If the close day is always kept up to date, shouldn't @txn.bch.date reflect the posting date exactly and therefore these two data structures (BAR.PAT and BAR.BCH) match exactly? James Purvins Inland Northwest Health Services (509) 232-8384 This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, or have otherwise received this communication in error, please delete it from your inbox, notify the sender immediately by replying to the message, and do not disclose its contents to any other person, use the information for any purpose or store or copy the information in any medium. Thank you for your cooperation ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Purvins, James A. Sent: Thursday, August 09, 2007 7:56 AM To: meditech-l@mtusers.com Subject: [MEDITECH-L] NPR R/W : Billing : Tying To Ops Summary Using BAR.PAT To Meditech-L, I think I have seen this question before on the L but I will throw this out again. Has anyone had success tying to the Ops Summary using transaction in BAR.PAT? I can tie to the Ops Summary consistently using BAR.BCH but am having a heck of a time using BAR.PAT. I can get pretty close but you know how those bean counter people are with <close> :o) In theory, should this not be possible? Can anyone provide reasons that this is not possible? James Purvins Inland Northwest Health Services (509) 232-8384 This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, or have otherwise received this communication in error, please delete it from your inbox, notify the sender immediately by replying to the message, and do not disclose its contents to any other person, use the information for any purpose or store or copy the information in any medium. Thank you for your cooperation
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= To subscribe or unsubscribe to the meditech-l, visit http://mtusers.com/mailman/listinfo/meditech-l_mtusers.com To check the status of the meditech-l, visit MTUsers.NET For help, email [EMAIL PROTECTED] Please visit and add information to the MTUsers WikiPedia at MTUsers.NET/mwiki ______________________________________ meditech-l mailing list meditech-l@MTUsers.com http://mtusers.com/mailman/listinfo/meditech-l_mtusers.com
