Formfeed problem printing to Windows print devices corrected.
Electronic claims to new GA Medicaid approved.
Incident control number added to Paycode 2 screen (used in block 22 of HCFA 1500 form).
Old GA Medicaid Paycode 2 information removed.
HCFA 1500 form modified for GA Medicaid to print type of service 9 in block 24C.
The wording for option "P" in the Patient signature source code was modified to say, "Signature generated by provider because the patient was not physically able to sign for services".
New flag added to page 4 of COMPANY file that controls the default value of PATIENT screen "Save Info" field when adding a new patient.
AL Medicaid electronic claims extraction program error messages improved.
Print one invoice now always prints the invoice reguardless of the selection rules.
New "privacy notice sent" field added to PATIENT file. A single "X" is printed on the perforation line of the invoice, if the field is "N". The flag is set to "Y" after the invoice is printed. This "X" marker can be used to remind you to include a privacy notice in the envelope with the invoice the first time a patient is billed.
AL Medicaid no longer allows a 2nd modifier in claims for dates of service on or after 1/15/2003. Both the electronic claims extraction program and the HCFA 1500 form modified.
Added support for 6 character HCPCS codes.
Corrected problem with WINPRINT printing extra page at end of printout.
Corrected V16.1 bug with VEHID missing in print invoice report.
Added "7 - Retrieve Claim Status From Medicaid" to GA Medicaid Telecom menu. When selected an entry is created in the Outbox to allow connecting to GA Medicaid to retrieve response files. This entry does not contain any claims to transmit. It is only used to make the connection. Since response files are not easily read, everyone should get a Web Portal account to retrieve the response files.
HCFA1500 printing improved for 6 char HCPCS codes.
Added new field to INSURANCE file to control printing of Block 24H on HCFA1500 form. Most carriers require a "N" in block 24H. Medicare requires a BLANK in block 24H.
Corrected printing of Block 22 on HCFA1500 form for Medicaid claims.
New Y/N flag added to page 4 of COMPANY file.
Posting payments F2 writeoff function improved to allow entering allowed amount for paycodes 3, 4, 5, and 6.
Removed Gramm Rudman percentage from COMPANY file and expected payment report.
Improved ANSI 837 extraction to remove commas, periods, and trailing white space.
FL Medicare electronic claims now supports retreiving response files.
Now supports retreiving response files from FL Medicare.
New FROM/TO street field added to FROMTO file. When specifing the origin or destination of the ambulance trip on page 2 of the invoice screen, a FROM/TO code is selected to point to the desired FROM/TO location record.
The street address transmitted to Medicare is the value entered in the invoice. The name of the location, city, state, and zip code are pulled from the FROMTO file. This technique allows multiple locations that have the same name, city, state, and zip code to use the same from/to record.
Street entered in Invoice: 206 Lukken Industrial Drive, E.
Homeland Security and the Tennessee Department of Health in Tennessee is asking ambulance services to email an exported data file containing information useful in tracking bioterrorism incidents or infectious outbreaks. Select Monthly Menu Option 8 - Export Data and then Exports Option 9 – Export Homeland Security Data.
A new time of pickup field was added to the invoice as requested by Homeland Security. Note that this field is not used for billing purposes at this time.
The exported file is saved in the data directory indicated on page 5 of the COMPANY file.
The exported filename is the first 2 characters of your company name plus the month, day, and year in the format MMDDYY. The file type is .TXT.
The file should be exported and emailed every day.
Improvements to Export Homeland Security Data made.
Statement printed date is now set when an invoice is printed if the statement printed date was blank before (only occurs if patient has only one invoice).
List of 10 supplies now displays DEFAULT field.
New field added to INSURANCE screen to control printing Block 24C on HCFA 1500 form. Most carriers accept a blank in this box; however, AL, GA, and TN Medicaid require a '9'.
G/L transaction log improved to show all writeoff types and totals.
New flag added to page 4 of COMPANY file to enable/disable editing/deleting memos.
FL Medicare approved ANSI 837 transmissions.
Posting payments F2 writeoff for insurance now computes allowed amount from charge and supply file information. The definition of the SUPPLY file Medicare allowed amount field changed to Medicare/Insurance allowed amount.
Corrected from and to names on invoices.
Problem with ISA07 for GA Medicaid electronic claims corrected.
Homeland Security export for TN modified to have separate ICD-9 and description fields.
GA Medicaid Adjustment Request form (DMA 501) is used by the new carrier.
Corrects problem with electronic claims if AL Medicare provider number is different from BC/BS of AL provider number.
EDI Healthcare clearinghouse extraction program modified to support Tri-Care.
Now supports displaying electronic report files from AL/GA/MS Medicare.
Event logging added to Medicare NSF and ANSI 837 electronic claims.
Event logging bug (V16.26) in ANSI 837 electronic claims corrected.
New item "5 – List Statement Printed on Date" added to Print Monthly Statements menu.
New field, date of last statement, added to "2 – Export Payor Data" file.
New option added to INSURANCE file for printing HCFA1500, block 29. Option 6 causes block 29 to only include payments to paycodes 1 thru 7. This option should be used for GA Medicaid.
GA Customers – Edit INSURANCE file record MEDICAID and change block 29 to option 6.
Added ability to retrieve response files in AL, GA, and MS with ANSI 837 file format.
Added edit check to prevent FROM/TO name being BLANK.
Corrected FROM/TO on contract statements.
Added new MISC Report (option 4) to "List Records Using Specified Insurance Code".
Added batching BCBS/AL claims with AL Medicare ANSI 837 claims.
Improved memos to automatically remove leading and trailing white space before and after editing.
Corrected issue with setting date statement printed.
New export option (option A) added to export list of invoices by selected patient code.
New export option (option B) added to export list of outstanding invoices for selected year. Collection invoices are not included.
ANSI 837 change made for AL BC/BS claims.
ANSI 837 improvement made for cases where patient is not subscriber.
AL Medicare now generates text based response files for ANSI 837 transmissions (V1.33 addition no longer required).
Support added for KY Medicare ANSI 837 electronic claims.
ANSI 837 improvements made to HL records and filtering of invalid characters.
ISA segment in ANSI 837 is no longer filtered for special characters.
New option added to Exports Menu, "C – Export List Of Payments With Age".
Payments to paycodes 8 and 9 and payments marked as accounting adjustments are not exported.
Corrected V16.32 bug concerning deleting a memo.
Electronic claims data, CA0 – Field 09, for clearinghouses corrected.
HCFA1500 form improved for GA Medicaid.
HCFA1500 form improved for GA Medicaid. Block 29 always zero if primary is Medicare.
Event logging added to clearinghouse extraction program.
Improved option in INSURANCE screen to control how to print modifiers in block 24D of HCFA1500 form. Some insurance carriers, for instance Railroad Medicare, only want to see one modifier.
HCFA1500 form improved for GA Medicaid ICN number.
Improved Medicare expected payment report now skips invoices with zero or negative balances and charges marked as accounting adjustments.
At this time GA Medicaid is unable to electronically process crossovers from Medicare. Instead these claims must be filed using the HCFA1500 form and the word "CROSSOVER" should be written on the top of the form. Block 29 should be zero or blank and block 33 should contain your Medicaid provider number. A copy of the Medicare EOB should be included.
File viewer now defaults to CDEDIT.EXE.
Modified GA Medicaid electronic claims to include claim frequency value.
GA Medicaid changes not implemented.
Modified HCFA1500 form to accomadate GA Medicaid. New option 3 added to block 30 in INSURANCE file options.
Block 29 – Option 3 – Include payments to paycodes 3, 4, 5, and 6.
Block 30 – Option 3 – Block 28 minus payments to all paycodes except 7 (see V16.53 update).
AL Medicare and Blue Cross and Blue Shield of AL approved ANSI 837 HIPAA compliant electronic claims.
Improved display of information during electronic extraction now includes the group control number (submission number) and the outbox filename. Georgia Medicaid providers can use the outbox filename (.DAT file) to manually submit batches to the web portal site if desired.
GA Medicaid electronic claims batches are now being processed. Any batches that have not been processed in the past should be resubmitted. The web portal site can now be used to check the status of claims that have been submitted.
HCFA1500 modified to ignor the patient's employment status when deciding where to mail the claim.
Printing invoices improved to include entire from and to addresses. HCFA1500 improved to include from street address in block 32.
It has been reported that GA Medicaid wants block 30 of HCFA1500 form to be Option 1 – Block 28 minus Block 29.
HCFA1500 program now prints place of service code 41 for Kentucky Medicaid claims with dates of service on and after 7/1/2003.
Patient list for selected past due invoices improved to allow selecting past due over 180 days.
Electronic claims for Zirmed modified to send blanks for GA0 fields concerning hospital admission and discharge.
Writeoff old invoices improved to ignor marked payments.
Improvements made to logon process for customers using Citrix or Microsoft terminal services. On startup if the computer name is not found in the USER file, the user is now prompted to enter their logon name.
ANSI 837 improved for GA Medicare to include destination facility information.
Block 19 destination zip code added.
Date extracted added to Inbox and Sent folder displays.
ANSI 837 improved for AL Medicaid.
Updatex improved to work with V16.54 changes to allow user logon.
ANSI 837 improved for FL Medicaid.
New pregnancy indicator added to PAYCODE2 file for FL Medicaid.
Corrected event log problem in Clearinghouse electronic claims extraction program.
Corrected problem with AL Medicare ANSI 837 and BC/BS of AL batches extracting together.
Modified "Payments Received This Month" review report to include invoices with zero balance.
Changes for AL Medicaid ANSI 837 made.
Changes for FL Medicaid ANSI 837 made.
Right anchor on main form set true.
Changes for FL Medicaid ANSI 837 made; EDIFECS test approved.
Electronic claims authorized signature field added to COMPANY file. This field must be non-blank.
ANSI 837 for AL Blue Cross and Blue Shield modified to use PIN number in INSURANCE file.
ANSI 837 modified to set the control numbers and group numbers to the same value.
Problem corrected with BC/BS of AL electronic claims not receiving primary modifier.
New export program (Option D) creates list of invoices between a selected range of service dates that have a charge with a specified HCPCS code.
FL Medicare ANSI 837 electronic claims switch to addendum A1. All Florida customers will switch to the new format on August 10th.
Changes made to ANSI 837 electronic claims for AdminaStar Federal (KY Medicare).
New export added (E – Export list of patients needing privacy notice).
Patients with bad addresses are not extracted.
Block 19 (option 2) destination zip code now prints correctly on HCFA1500 form.
Block 22 on LA Medicaid form now prints correctly.
End of month improved to delete the transaction log for users that don't run cleanup each month.
Cleanup no longer deletes invoices that have no charges posted.
Phone number removed from the CITY file; the area code remains.
List of payments by date financial report improved to allow printing payment descriptions. The patient code was also added to the report.
ANSI 837 modified for KY Medicare.
Billing type 5 added to COMPANY file (page 3) to support DME (durable medical equipment) billing. When enabled, a second service date can be entered. The place of service should be code 12 (residence). Invoices and HCFA1500 were modified to support the new billing type.
Problem with V16.70 HCFA1500 support for DME corrected.
Corrected problem when adding new invoice, Homeland Security time was being updated from old invoice.
New driver code that references the EMT file added to page 2 of the invoice. This is an optional (may be left blank if desired) entry field in most states. The field is used in a new report that list the total calls for each EMT/Driver. To print the new report, select the PRINT pulldown menu, then "B-Print Miscellaneous Reports", then "5-List EMTs and Total Calls".
Customers who have been entering the driver information in the PAYCODE2 screen (LA), must now enter the driver code in the invoice. The program will continue to use the paycode2 driver information for old invoices.
Improvements made to ANSI837. You can't release medical information if no signature is on file. Also, you can't transmit if the electronic signature in the COMPANY file is blank.
Problem with HCFA1500 block 21 when option 5 used in the insurance record corrected.
Update program improved to look for both UPDATE.BAT and UPDATE.TXT files on the update drive. This now allows updates to be sent via email without having to send the batch file which some email servers disallow for security reasons.
KY Medicare ANSI 837 now uses addendum A1.
ANSI 837 problem with destination address corrected.
ANSI 837 problem with BC/BS of AL provider number corrected.
ANSI 837 better error checking added.
Problem adding new invoice (flag21 not defined) caused by V16.70 update corrected.
Problem corrected restoring old backups from 1997 or before.
Clearinghouse electronic claims (NSF) improved to consider transmiting secondary insurance if primary rejects.
Improved ANSI 837 error checking. TN Medicare now using addendum A1.
AL Medicare and BC/BS of AL now using addendum A1 of ANSI 837.
GA Medicaid (GHP) is saying you should wait 45 days after being paid from Medicare before filing a paper crossover claim.
Paycode 2 ICN control number cleared when adding new invoice.
New option 6 added to past due patient list (>365 days past due).
Problem with V16.80 clearing paycode 2 ICN corrected.
Warning added to print 1 statement if patient has bad address.
Improved city validation in FROM/TO edit screen.
Improved print screen (ALT+P) now uses the REPORTS printer device and works with all printer devices including Windows printer drivers.
Improved ANSI 837 error checking: blank primary ICD code not allowed.
Problem with "*NM1*PR" segment in ANSI 837 corrected.
New F10 filter function added to "List of Patient" screen.
Problem with V16.84 print screen fixed.
Problem with AL/GA/MS billing agencies transmitting multiple batches during one session corrected.
ANSI 837 electronic claims now removes all numerics from From/To location names as required by AL Medicare.
ANSI 837 modified for AL Medicare to allow first 4 digits of Medicare provider number to be something other than "0000".
Recently TN Medicare were assigned a new logon to begin electronically transmitting HIPAA compliant ANSI 837 file format claims.
After connecting to the Medicare computer and logging on, the following steps must be done to enable correct transmission of the file.
If you have sent any batches previously without setting the proper data type, those batches should be retransmitted.
Customers using the EmsClaims program for the first time, should be aware that when the batch is extracted, the date filed is immediately set (the claim is not marked for transmission).
Improved status messages for AL/GA/MS sessions.
Recently you were assigned a new mailbox account (logon) to TN Medicare to begin electronically transmitting HIPAA compliant ANSI 837 file format claims.
Before extracting your claims, in the TELECOM file (page 1) set the "File Format: 2 – ANSI 837".
If you do not receive an acknowledgement report within 2 days after sending a batch, call for help. If you have not yet received your new mailbox logon, call for help.
NSF 3.01 GA0 field 18 and 19 improved to include complete address.
NSF 3.01 GA0 field 18 and 19 modified for MS Medicare to include name and address.
Note to all customers: Medicare's new HIPAA compliant electronic claims does not allow numerics in the FROM/TO "location/description" field. Some customers are accustom to putting zip codes in this field. This technique should be discontinued. The program will filter out all numerics that are entered before transmitting.
Some customers have forgotten to enter a value in the "Electronic Signature" field in the COMPANY file on page 1. If this field is blank, the new HIPAA compliant electronic claims system will reject the entire batch.
Any batches transmitted with the above problems should be retransmitted.
The TN Medicare response reports were designed to be printed on wide paper. Select "Landscape" mode in printer setup before printing the report for best results.
Added new level 1 and 2 edits to ANSI 837.
Fixed list of 10 scrolling problem with CITY file.
Improved update program to handle old backups that do not contain TECH_PF field.
Corrected problem with alias not found error in TELECOM1 program.
Added new level 2 edit to ANSI 837 for PCS narrative.
Improved error checking and status messages for AL/GA/MS sessions.
Clear screen display for TN Medicare after TX or RX file.
HCFA1491 form improved to print full orgin/destination address.
Georgia Medicare customers who have not transitioned to the new FTP electronic claims system should do so as soon as possible. The new system is superior and the old system may be shut down on October 16th. To get your new FTP logon and password, call GA Medicare Part B EDI support at (866)582-3253. When you are ready to transmit, call for help.
NSF 3.01 GA0 field 18 and 19 modified for AL Medicare to include name and address.
Improved printing of FROMTO file.
Modifing "Report" printer device now correctly updates ALT+P printscreen device.
HCFA1500 print all or print range now only includes "Active" invoices.
Added charge description to ANSI 837 for TN Medicare.
Improved printing of HCFA1500 for GA Medicaid (block 11).
GA Medicare ANSI 837 moved to addendum A1.
FL Medicaid ANSI 837 now supported.
NSF 3.01 extraction modified to handle last names like O'Brian. In the patient file, enter the patient's name as "O'Brian" or "O Brian". The extraction program will substitute a space for the "'" character.
Improved ANSI 837 level 2 edits, patient's street address cannot be blank.
Corrected paging problems with Operations Report.
Effective 10/3/03 GA Medicaid is requesting the From/To information in block 19 of the HCFA 1500 form. The program supports this by selecting option 2 for block 19 in the MEDICAID insurance record.
NSF 3.01 electronic claims modified to skip charge items with negative quantities.
V16.95 change to ANSI 837 made for TN Medicare causes problems in AL and GA. The problem is now corrected; however, any batches sent in AL or GA with V16.95 thru V16.98 will need to be retransmitted. The audit log error will look like "SEGMENT SV1 POSITION 35 ELEMENT 1 VIOLATES EXCLUSION CONDITION".
Improved ANSI 837 error checking of invalid medigap codes.
ANSI 837 modified to not transmit Medigap information if the insured's date of birth is unknown.
Since some carriers are requiring odd values for the place of service field, all validation for this field has been removed.
In Kentucky if the primary payor is Medicaid and the call is an emergency, the place of service defaults to "23" instead of "41".
EMT report improved to sort by total calls.
Corrected problem with temp folder name being more than 8 characters.
If the street address is blank in the FROMTO file, the street address in the INVOICE is not modified when the FROMTO code is changed.
New feature added to allowing connecting to a remote system using parameters (telephone number, user id, and password) obtained from a file in the Sent folder. Just select the file in the Sent folder and click the Connect button on the toolbar. This allows you to connect and download audit reports even though you may not have any new claims to transmit.
A new feature was added to allow the seamless change of supply rates based on the invoice's date of service (see V16.105).
Rate changes can now be made based on the invoice's date of service. New fields were added to the SUPPLIES file to allow specifing 2 unit prices and the starting date of service for the second price.
Based on the invoice's date of service, either unit price #1 or unit price #2 will be used when posting charges.
The new ANSI 837 file format requires that the total miles be included even if you do not bill for mileage. A new flag was added to the COMPANY file (page 4) to indicate whether you bill for mileage or not. If you do not bill for mileage, a new data entry field will appear on page 2 of the invoice that allows you to enter the total miles; otherwise, the program will get the total miles from the posted charges.
V16.101 KY Medicaid change removed.
Block 19 prints location of pickup code (from origin FROMTO record) and military time of pickup (from PAYCODE2 record).
Block 24B prints place of service (from page 2 of INVOICE).
Block 24K prints destination code (from destination FROMTO record).
All dates are now in MM DD YY format.
FL Medicaid electronic claims modified (ANSI 837, ISA08).
Improved AL Medicaid logic for 2nd modifier.
KY Medicaid military problem corrected.
Problem with Export #6 corrected.
Transmitting electronic claims in AL using the new HIPAA compliant ANSI 837 file format involves several steps. This same process is also used in GA and MS; however, BC/BS claims are not extracted in those states.
The first step involves extracting the batch of claims to be transmitted. In the EMS billing program, from the TELECOM menu select option "1-Medicare" and then option "1-Extract Claims to Transmit". When asked whether to print the log report answer yes; this report should be filed for later reference. In Alabama two batches are created, one for Medicare and one for Blue Cross and Blue Shield of Alabama.
The extraction program scans the invoice file looking for any claims that can be filed electronically with AL Medicare or BC/BS. An ANSI 837 data file containing detailed information about the selected claims is created and the file is placed in the Outbox folder ready for transmission. Another informational file is also created that contains various data such as the date of extraction, the payer, the number of claims in the batch, the telephone number of the computer to call, the user logon, and the password.
The date filed is automatically set for the primary payer in the selected invoices. If the secondary payer is Medicaid or an insurance company that has a non-blank Medigap code in the INSURANCE file, the secondary's date filed is also set.
If for some reason the extracted batch of claims needs to be refiled at a later time, option "4-Reset Date Filed of Claims Filed on Date" can be used. This will reset the date filed of all claims filed electronically on the selected date.
To transmit the extracted batch, close the EMS billing program and run the EmsClaims program from the Windows desktop.
Files listed in the Outbox are ready to be transmitted. Select the file to transmit by left-clicking on the filename in the list. To view the number of claims, the phone number, and other information about the batch, click on the Details button on the toolbar. To transmit the batch click the Connect button. This opens another window titled "AL/GA/MS Medicare".
Click the Dial button to dial the phone and connect to the AL Medicare network. You should hear the phone dial, then the Medicare modem will answer the phone and a squealing sound will be heard while the modems negotiate a speed and protocol for communicating. Your computer will then try to connect to the Medicare network using the security information specified. If the connection is successful, a message will appear in the status line indicating that the program is ready for you to click the Logon button. When the Logon button is clicked, the program tries to logon to the Medicare FTP server, again using security information provided. If successful the program will prompt you to either click the Transmit button or the Receive button. To transmit the batch click the Transmit button. If you selected the "Transmit All" option in the Outbox screen, all files in the Outbox that have the same payer and logon information are transmitted at this time. After successfully transmitting the batch, select the Receive button to receive files from the Medicare computer. These files contain information about previously transmitted batches. After successfully receiving any files available, click the Close button to logoff and hangup.
Select in Inbox tab to view any files that you received from the Medicare FTP server. Note that the files are sorted from newest to oldest. The date and time the file was received is shown. To view a file, double-click on the file name. If a printout is desired, left-click the Printer button inside the viewer program (CDEdit). Files of interest received from Medicare have a "Host Name" ending with AUDREPT.ZIP. The host name also contains the date of the audit report contained in the file. The audit report contains information about the claims accepted and rejected. Information about rejected claims includes why the claim was rejected and your invoice number.
You should receive an audit report for every batch you send. These reports are usually generated the night after a batch is transmitted; however, sometimes it can take two days if Medicare has a problem processing batches. If you do not receive an audit report, it indicates that something was wrong with the batch. If this happens, you need to call for help.
To retrieve an audit report even when you do not have any batches to transmit, simply click on the Sent tab and select any batch previously transmitted. Click the Connect button and then go through the normal steps to dial the phone, logon, and receive files.
Improvements to ANSI 837 were made. The first 80 characters of the secondary diagnosis information will now be transmitted if there is no physician's certification statement on file; otherwise, the PCS information is transmitted. The file format does not allow us to transmit both.
The purpose of stretcher narrative is transmitted if a stretcher is indicated in the condition indicator field. Make sure that in one or more of the narrative fields the patient's condition and why an ambulance was necessary is clearly indicated.
Also, claims that do not contain an ICD-9 code can now be transmitted. It is our understanding that ICD-9 codes are not required by Medicare; however, they may help support justifing the ambulance trip. Also, other carriers do require the ICD-9 code even though Medicare does not. Note that the primary diagnosis description is not transmitted; Medicare already knows what the ICD-9 code means.
NSF clearinghouse electronic claims improved to include hospital admit and discharge dates.
HCFA1500 form printing of block 9 and 11 improved.
Additional message lines added to message numbers 1, 41, and 51.
Zero total miles can now be transmitted using ANSI 837 (dead on arrival cases for instance).
Posting charges for AL no longer automatically adds 2nd modifier "5A" to oxygen charge.
Level 2 edits for ANSI 837 improved. Blank notes detected. Blank or no signature detected.
Corrected problem if connect clicked when outbox empty. Also enlarged inbox listbox.
Corrected problem for FL Medicare when receiving response files by selecting batch in Sent folder and connecting.
AL Medicare has notified us that they will have the zero mileage problem corrected by 11/6/03. They will no longer reject claims that have zero miles. MS and GA Medicare are being notified of the problem.
Some customers have received PR-50 rejections (not medically necessary) on their EOB because Medicare was not receiving any narrative information about the condition of the patient and why the patient needed to be transported by ambulance.
If a stretcher was used in the transport, be sure you're specifing the "S" in the condition field.
After several discussions with Medicare tech support, we are now able to transmit all narrative information (primary diagnosis, secondary diagnosis, purpose of stretcher, purpose of round trip, and physicians certification statement) using the ANSI 837 format.
Removed charge description (not used) from ANSI 837.
Changes made in V16.118 to allow transmitting all narrative information with the ANSI 837 file format are not working. Any ANSI 837 batches sent with the V16.118 program should be reset, reextracted, and retransmitted.
If a stretcher was used, the program transmits the purpose of stretcher narrative (80 chars).
If a round trip was indicated (not recommended, use 2 invoices instead), the program transmits the purpose of round trip narrative (80 chars).
If the secondary diagnosis is non-blank, the program transmits the first 80 chars of the secondary diagnosis.
If the secondary diagnosis is blank and the PCS narrative is non-blank, the program transmits the PCS information.
Level 2 edit improved to catch blank purpose of round trip.
AL/GA/MS now correctly skips trying to transmit empty files.
TN Medicare terminal window now uses larger font.
On some systems CDEdit does not correctly print in landscape mode when "Printer Setup" selected. Selecting "Print" and then "Properties" and then selecting landscape mode does work.
AL Medicaid electronic claims now correctly shows extraction date in EmsClaims.
Changed FL Medicare back to XModemCRC protocol.
ANSI 837 problem with Medigap situations corrected.
New field, date invoice reviewed, added as last field in export #2.
Changes made to ANSI 837 program for AZ Medicare.
Corrected problem with Export 11 and added new patient code field.
Export 11 improved to allow selecting whether to include zero and negative balance invoices.
Problem with Export 2 change in V16.121 corrected.
New export added (F - Export A/R balances for invoices with dates of service in the selected year).
Improved ANSI 837 error checking on zip codes.
Error checking added to all state fields.
Improved log report in ANSI 837 extraction program.
New 2310B loop added to ANSI 837 for AL Medicaid.
HCFA1500 improved to give option to enter invoice status for print job.
Balance due statements now allow specifing invoice status.
Login now shows computer name.
Faclity reference id qualifier in ANSI 837 for Medicaid corrected.
Problem transmitting GA Medicaid claims (ANSI 837) with prior approval numbers corrected. Any batches containing claims with prior approval numbers should be retransmitted.
Support for new AL Medicaid ANSI 837 electronic claims completed.
Problem updating program using CD-ROM corrected.
Added support for AL Medicaid electronic claims to website.
Printing list of patients with bad addresses contains new invoice status filter.
Problem with printing HCFA 1500 block 19 purpose of stretcher corrected.
Added support for AZ Medicare ANSI 837 electronic claims.
dded support for AZ Medicare BBS for ANSI 837 electronic claims.
Corrected problem with V16.132 moving AL Medicaid submitter ID to new field.
PWK segment removed from all ANSI 837 claims. This corrects problem with GA Medicaid holding claims waiting on attachments.
AL Medicaid transmit menu option now correctly runs EmsClaims program.
New level 1 edit added to ANSI 837 to insure correct federal tax id format.
Corrected problem with destination location and address for GA Medicare ANSI 837 electronic claims. Also, the destination is always transmitted, not just the hospital to hospital claims.
Rendering provider information removed from ANSI 837.
All batches electronically transmitted to FL Medicaid since 10/3/03 must be retransmitted using the new ANSI 837 format.
Added support for multiple viewers (use SETUP to select desired viewer). The default viewer is "CDEDIT"; however, "NOTEPAD" is also a good option.
Level 2 edit added to ANSI 837 for AL Medicaid to catch blank ICD-9 code errors.
Improved TN Medicare electronic claims. If you have trouble downloading files be sure that ZModem text mode is selected in the default options.
Improved AZ Medicare electronic claims using ZModemFinishRetry and FinishWait values.
Corrected problem with ALT+P print screen function modifing current selected table.
New miscellaneous report added: List Invoices for Date of Service. The report prints a list of invoices grouped and sorted by date of service for any selected month/year. Both detail and summary charges, cash payments, non-cash payments, and amount due are shown.
ANSI 837 improved level 2 edit checks for blank patient zip code.
Corrected problem with ALT+P print screen function modifing current page.
Logic in printing statements was modified so that invoices where Medicaid has rejected do not print. Just because Medicaid rejects payment does not mean that the patient is not a Medicaid patient.
Georgia Medicaid has eliminated their old round trip base rate codes. When billing a round trip or the 2nd trip on the same day, the "ET" modifier (extra transport) should be used in posting charges (2nd modifier). At this time the GA Medicaid computer is having trouble processing these type claims; also, there is ambuguity about the effective date of the change, either Jan 1st or Feb 1st .
Instead of Y0501 use A0429 now with the "ET" 2nd modifier.
Instead of Y0502 use A0420 now with no 2nd modifier.
GA Medicare has published a list of "Ambulance Condition Indicators" that can be used when entering narrative information (purpose of stretcher and secondary diagnosis). The Jan 2004 document "CGBA 2004-1 Special Bulletin" provides shorthand "condition codes" that can optionally be used.
Now supports viewing .HTM host files from inbox (AZ Medicare).
Now supports viewing .997 files with new EdiView program.
EdiView program now supports viewing AL Medicaid .CSR files, Ansi.997 files, other Ansi files, and any normal text file terminated with a CR/LF.
Modified ANSI837 street address format for origin/destination.
Added new level 2 edits for ANSI837.
Corrected problem with cleanup removing invoices with –0.01 cent balance.
New flag added to page 4 of COMPANY file to enable adding a leading formfeed to the HCFA1500 file by modem printouts. This is only needed in Utah at this time.
Improved miscellaneous report: List Invoices for Date of Service. The report now allows filtering by invoice status.
Improved printing of HCFA1500 form block 10d when Medicare secondary.
Improved list of patients with bad address report.
ANSI837 improved to remove forbidden characters.
Added detail option to "List of Charges by Supply Code" report.
Added invoice status to list payments by invoice financial report.
Added warning message if new invoice created with patient record that has bad address.
Improved LA Medicaid form to include modifier and correct origin/destination addresses.
EmsClaims improved to automatically display .997 files for TNM1 payor with EdiView.
EmsClaims setup now auto registers EdiView with Windows for viewing .997 and .CSR files.
Program now automatically creates export/collection folder if it does not exist.
ANSI 837 extraction improved to check for blank place of services.
Clearinghouse electronic extraction modified to check for non-blank review date if vendor code is "LOGIST".
Statements improved to always included patient code on every page.
Printing HCFA 1500 forms for KY Medicaid improved. Only charge modifiers now print in block 24d. Also, military time was removed from block 19. Block 23 improved.
A new feature was added to posting charges (R-Reverse) to make editing charges posted to previous periods easier. Point to the unmarked charge posted in a previous period and hit the "R" key. The current charge is automatically marked as an accounting adjustment. In addition a new charge is added, identical to the first charge, except the amount is negative. This new charge is also marked as an accounting adjustment. A third charge is then automatically created with all the fields identical to the first charge. It can be edited to make any desired changes.
Improved "List of Invoices by Service Date" to include total calls in summary.
Corrected problem with "List Payments by Insurance Company" displaying incorrect date of services.
Improved "Print List of Patients With Bad Addresses" to include option to print detailed list of invoices and dates of service.
HCFA 1500 form and posting charges improved for KY Medicaid. Charge modifiers default to blanks except for mileage (UA-ALS mileage, UB-BLS mileage).
Clearinghouse NSF extraction modified to not include charge description in HA0 narrative field (5.0).
Corrected problem with locking record during printing invoices.
Corrected problem with printing heading in "List of Payments by Invoice" financial report (summary).
A new condition indicator, "A", was added to indicate that the patient was admitted to the hospital (page 2 of the invoice).
Improved "List of Invoices by Service Date" to include summary only option.
Improved "Invoices Moved to Collections This Period" to include totals.
New fields added to SUPPLIES file to support two Medicare, Medicaid, and Insurance allowed amounts. The second allowed amount takes affect on the entered starting date.
Change made to ANSI 837 electronic claims for AZ Medicare (NM1-1000B-Element 9).
EmsClaims improved to automatically display .997 files for AZM1 payor with EdiView.
Added new export #16, List of Invoices for Range of Service Dates".
Bug in V16.165 update mistakenly zero'ed the Medicaid allowed amount field in the SUPPLIES file. The field must be non-zero for supplies that should be transmitted to Medicaid. Everyone that was affected was notified by phone.
There are certain electronic claim errors that AL Medicaid's computer cannot currently include in their standard audit reports; therefore, you may receive in the mail from AL Medicaid a printed error report. If you have trouble interpreting the report, don't hesitate to call for help.


A set of skills to equip individuals to work in compliance with laws of particular relevance to the hospitality industry. This skill set is for front-line hospitality service personnel whose jobs involve food handling, the sale and service of alcohol, and the provision of gaming services; and who must comply with laws of particular relevance to these job functions.
Certification requirements apply at a state and territory level to individuals involved in the sale, service, and promotional service of alcohol in licenced premises. Certification in some States relies on the achievement of SITHFAB002 Provide responsible service of alcohol.
Certification requirements also apply at a state and territory level to individuals involved in food handling or supervision. Certification in some States relies on the achievement of SITXFSA001 Use hygienic practices for food safety and SITXFSA002 Participate in safe food handling practices.
Food safety legislative and knowledge requirements may differ across borders. Those developing training to support SITXFSA001 and SITXFSA002 must consult the relevant state or territory food safety authority to determine any accreditation arrangements for courses, trainers and assessors.
Achievement of these units provides credit towards qualifications in tourism, travel, hospitality, events, holiday parks and resorts in the SIT Tourism, Travel and Hospitality Training Package.


text:
Blanch Case Highlight – Antitrust Fines Exceed $300 Million
April 10, 2014 By The Blanch Law Firm Leave a Comment
BRITISH AIRWAYS PLC AND KOREAN AIR LINES CO. LTD. AGREE TO PLEAD GUILTY AND PAY CRIMINAL FINES TOTALING $600 MILLION FOR FIXING PRICES ON PASSENGER AND CARGO FLIGHTS
WASHINGTON — U.K.-based British Airways Plc and South Korean-based Korean Air Lines Co. Ltd. have each agreed to plead guilty and pay separate $300 million criminal fines for their roles in conspiracies to fix the prices of passenger and cargo flights, announced the Department of Justice. Today's plea agreements are the first to arise from the Antitrust Division's ongoing investigation into the Air Transportation Industry.
The charges against the two airline companies were filed today in the U.S. District Court for the District of Columbia. Under the plea agreements, which are subject to court approval, British Airways and Korean Air have agreed to cooperate with the Department's ongoing investigation.
"The Department of Justice is committed to vigorous antitrust enforcement and will continue to bring to justice those who fix prices and thereby deprive the American public of the benefits afforded by a truly competitive market," said Attorney General Alberto R. Gonzales. "International law enforcement cooperation is crucial in prosecuting global cartels such as these, and today's enforcement actions represent the successful coordination between the United States and the U.K.'s Office of Fair Trading."
The Department said that passengers who flew on British Airways flights between the United Kingdom and the United States during the charged period paid more for their tickets as a result of the illegal cartel. In 2004, British Airways' fuel surcharge for round-trip passenger tickets was around $10 per ticket. By the time the passenger conspiracy was cracked in 2006, the surcharge was nearly $110 per ticketa 10-fold increase, said the Department. The Department noted that during the air cargo conspiracy, British Airways' fuel surcharge on shipments to and from the United States changed more than 20 times and increased from four cents per kilogram of cargo shipped to as high as 72 cents per kilogram.
The Department charged Korean Air with agreeing with air cargo competitors on rates charged to customers in the United States and elsewhere for international air cargo shipments. The Department noted that the conspirators agreed to increase the fuel surcharge over time from 10 cents per kilogram to as high as 60 cents for each kilogram of cargo shipped from the United States. The Department also charged that Korean Air reached an agreement with its rival to fix certain passenger fares for flights from the United States to Korea.
"When British Airways, Korean Air and their co-conspirators got together and agreed to raise prices for passenger and air cargo fares, American consumers and businesses ended up picking up the tab for their illegal conduct," said Acting Associate Attorney General William W. Mercer. "Today's enforcement actions demonstrate that the Antitrust Division will investigate and prosecute illegal cartel activity–here and abroad–in order to ensure that American consumers and businesses are not harmed by illegal cartel activities."
British Airways is charged with engaging in a conspiracy to suppress and eliminate competition by fixing the rates charged to customers for international air shipments of cargo, including shipments to and from the United States. Billions of dollars of consumer and other goods, including produce, clothing, electronics and medicines, are shipped by British Airways and its competitors in the air cargo industry. British Airways participated in that conspiracy between March 2002 and February 2006.
The Department also charged that between August 2004 and February 2006, British Airways engaged in a conspiracy to suppress and eliminate competition by fixing the fuel surcharge charged to passengers on long-haul international flights, including flights between the United States and the United Kingdom. British Airways' long-haul flights are flights between the United Kingdom and certain foreign destinations, including any flight to and from the United States. Passengers pay hundreds of millions of dollars in ticket prices each year, and the conspiracy raised the price on virtually every ticket purchased between 2004 and 2006 for the conspirators' long-haul international flights, the Department said.
British Airways is charged with carrying out the two price-fixing conspiracies with co-conspirators by, among other methods:
* Participating in meetings, conversations, and communications to discuss the cargo rates on shipments to and from the United States and passenger fuel surcharges to be charged for flights between the United States and the United Kingdom;
* Agreeing, during those meetings, conversations, and communications, on certain components of the cargo rates on shipments to and from the United States and passenger fuel surcharges to levy for flights between the United States and the United Kingdom;
* Levying cargo rates and passenger fuel surcharges in accordance with the agreements reached; and
* Engaging in meetings, conversations, and communications to monitor and enforce the agreed-upon rates.
The Department charged that between January 2000 and July 2006, Korean Air participated in a conspiracy to fix fares charged passengers and certain travel agents for flights from the United States to Korea. Korean Air is also charged with engaging in a conspiracy to suppress and eliminate competition by fixing the rates charged to customers in the United States and elsewhere for international air cargo shipments from at least January 2000 to February 2006.
Korean Air is charged with carrying out the two price-fixing conspiracies with co-conspirators by, among other methods:
* Participating in meetings, conversations, and communications to discuss the cargo rates to be charged on certain routes to and from the United States and on components of passenger fares and certain wholesale fares to be charged for flights from the United States to Korea;
* Agreeing, during those meetings, conversations, and communications, on certain cargo rates for certain routes to and from the United States and components of passenger fares and certain wholesale fares on flights from the United States to Korea;
* Levying cargo rates and passenger and wholesale fares in accordance with the agreements reached; and
Two other airlines  Virgin Atlantic and Lufthansa AG  have agreed to cooperate in the Division's ongoing investigations. Both Virgin Atlantic and Lufthansa have been conditionally accepted into the Antitrust Division's Corporate Leniency Program. The Division's Corporate Leniency Program allows a qualifying company that is the first to voluntarily disclose its participation in an antitrust crime and which fully cooperates in the subsequent investigation to avoid criminal conviction and a heavy fine. Virgin Atlantic entered the program after reporting its participation with British Airways in the passenger fuel surcharge conspiracy. Lufthansa was conditionally accepted after it disclosed its role in the international cargo conspiracy in which British Airways and Korean Air were participants. Virgin Atlantic and Lufthansa are obligated to pay restitution to the U.S. victims of their conspiracies.
"The Antitrust Division's Corporate Leniency Program is a valuable tool in breaking up illegal cartels," said Scott D. Hammond, Deputy Assistant Attorney General for Criminal Enforcement of the Department's Antitrust Division. "As a result of the leniency program, the Antitrust Division has broken up dozens of cartels and has obtained more than $2 billion in fines in cases assisted by amnesty applicants."
The ongoing investigation is being conducted by the Antitrust Division's National Criminal Enforcement Section and the Washington Field Office of the Federal Bureau of Investigation.
British Airways and Korean Air are each charged with two counts of price fixing in violation of the Sherman Act. Each count of the Sherman Act carries a maximum sentence of 10 years of imprisonment for individuals and a fine of $100 million for corporations. The maximum fine may be increased to twice the gain derived from the crime or twice the loss suffered by the victims of the crime, if either of those amounts is greater than the statutory maximum fine.
British Airways and Korean Air are among the top 10 largest international cargo carriers. During the conspiracy, their combined United States-related cargo revenues have been reported to be a total of more than $1 billion annually. Additionally, Korean Air is the largest passenger carrier from the United States to Korea and averages more than $250 million a year on those flights. British Airways is the largest passenger carrier from the United Kingdom to the United States. It had $14 billion in total passenger revenues in 2006.
Anyone with information concerning price fixing or other anticompetitive conduct in the air transportation industry is urged to call the National Criminal Enforcement Section of the Antitrust Division at 202-307-6694.
For further information Antitrust Litigation and how you can fight antitrust charges and government investigations, Contact The Blanch Law Firm today.

redpajama_set_name: RedPajamaCommonCrawl


Before you get your hopes up for lots of details about Byron Bay, I should warn you… this is a blog about a boy.
I love the rain. Rainy days at home always make me happy to be inside, snuggled up on the couch, drinking hot tea and reading a book. Rainy days at work also make me happy to be inside, and I'm pretty sure they promote both productivity and creativity. However, if you had told me in advance that it would rain for the entire week I was in Byron Bay, Australia, I would have been terribly disappointed.
As it turned out, it did rain. And it rained and it rained and it rained. And as it turns out, I love the rain in Australia too. We waded through ankle deep water in town to get burgers and beer. We took advantage of one night when the rain let up to hike out to the most Easterly point of Australia and see the Byron Bay Lighthouse. But for the most part, I just sat in a hammock breathing clean, wet, Australian air while the wind brushed my face with rainy mist every few minutes. Byron Bay was good for my soul. I put down my camera, picked up a book (or several), and wrote.
There was a giant teepee behind our hostel in Byron Bay where they boasted a full yoga schedule with multiple classes a day. I had never done yoga in a teepee before, and figured it would give me a good reason to get out of the hammock. I took 6 classes in 5 days, and struck up a friendship with the yoga teacher, a 30-something Australian surfer, who had just come back from a year in India. One day, after yoga, he took me surfing in the rain. We drove through twisting dirt roads on our way to the local's cove. For a few seconds, halfway there, I remembered that you really aren't supposed to take rides from strangers but I pushed the thought out of my head, and told myself that if anyone believes in karma, it's the yogis.
I didn't have a board so we had planned on taking turns with his, but the board was smaller and the waves were bigger than I was used to, so I wisely decided to sit this one out. I stayed on the beach and drew pictures in the wet sand, while I thought about a boy back in the States. A friend. Just a friend. For two years, my best friend. A friend my whole heart loved, but who I had given myself a million reasons to stay just friends with. (For the record, he had given me more than a couple of good reasons as well.) I sat on that beach with rain soaking my skin, my hair, dripping off my eyelashes and down my face like tears. I just sat there and watched the waves, my fingers tracing patterns in the sand. I watched as some surfers fought them, paddling when they should duck, getting washed back 20 meters, just to paddle the same distance again. I watched others whose swift, efficient strokes made it look easy. Rolling and ducking to avoid the turbulence and surfacing again on the other side of it.
I thought about the last two years of our friendship. The midnight calls to complain about relationships that were just so darn difficult. I thought about the gallant efforts on both of our parts to fight for things that everyone around us (especially each other) could see were doomed from the word go. How hard we had been willing to work on a relationship, not because it was good, but because our pride wouldn't allow us to just cut our losses. And then I thought about the last seven days, how every night as the sun was setting in Australia, it was rising in the States and I would walk out to that hammock with my phone to facetime with him. Thought about how easy everything came with us, except for the decision of where to go next.
I laughed out loud when I had a SATC flashback. I could almost hear Charlotte saying, "I've been dating since I was 15, I'm exhausted! Where is he?" I didn't feel that way. Not yet. Sure, I'd said it, and I had probably meant it after some of the more heartbreaking moments, but I was still having fun with it. I loved every minute of my vagabond life, not tied down to anything or anyone. I could tell there was something changing between us while I was in Australia. Something in the tone of our conversations. Something in the prolonged goodbyes before hitting the little "disconnect" button. But I wasn't ready to acknowledge it yet. I knew then, and looking back had known for a long time, that once we crossed a certain line, we could never go back. And I didn't feel ready for my last first kiss. So just like the stubborn surfers who couldn't quite catch the rhythm of the waves, I just kept fighting it for months… until I stopped.
I'm DYING to go back! It rained the whole time and I did almost nothing other than talk to Dane and practice yoga! I want to explore!
Gorgeous shots, Byron is where I grew up. Such a special spot!
I have Byron on my list of places to revisit some day. I think if I had spent time exploring a bit more I might never have wanted to leave!
Wow, this really didn't end up where I thought it would, but I loved the journey. And I love the photos!
Great to hear you're having fun. Deb and I in Cancun right now!!


Recent incidents in BC's forest industry, in which trees being felled have contacted energized transmission lines, have led to the creation of some new documents by BC Hydro. These new documents support discussions with forest companies/harvesting contractors to ensure obligations to identify the hazardous areas associated with harvesting near powerlines are addressed. One of these documents, the Logging Near Powerlines Emergency Contact Form, focuses on strict compliance with current WorkSafeBC Regulations.
Section 26.2, Planning and conducting a forestry operation.
Electricity seeks the path of least resistance to the ground. That path could include a tree, mobile equipment, tools, or the human body. If any of these makes contact with an energized powerline, or if a broken powerline falls to the ground or lands on a vehicle or fence, electricity will flow to the ground and spread out in irregular concentric circles, in what is known as a ripple effect. The ripple effect can affect the ground for some distance away from the direct path of the electrical current, thereby posing a risk to workers and others nearby.
Health and safety in forestry workplaces is the responsibility of all parties that have an influence on how work is carried out. Owners and licensees need to provide the employer or prime contractor with information necessary for identification and elimination or control of workplace hazards, including the location of powerlines in close proximity to the worksite. Planning of the operation needs to address how hazards are to be controlled and managed before work starts, and needs to be documented. Supervisors also need to ensure that workers are aware of the hazard that powerlines pose, and of the means to control the hazard.
Before any harvesting activities occur near powerlines, a qualified person authorized by the power company must inspect the worksite and assess the area for hazards. Hazards include situations where any part of a tree to be pruned or felled is within the limits of approach or may fall within that distance (limits of approach are defined in table 19-1A of the WorkSafeBC regulations). A qualified person must also inspect the worksite immediately before the work starts to ensure that the initial assessment is still valid and that no additional hazards are identified.
Where possible as part of the initial planning process ensure that cut block boundaries are well away from the powerline corridor. If it is determined that a tree is within the limits of approach or may fall within that distance then a plan must be put in place to eliminate the electrical hazard in order to conduct harvesting in a safe manner. Part of the plan shall include consulting with the power company about de-energizing the lines. If that is not possible, consider eliminating the hazard in another way such as topping the trees or creating a buffer zone.
If the hazard cannot be eliminated, then the plan must include obtaining assurance from the power authority that any reclose feature has been disabled. This assurance must be held on site by someone authorized by the utility. Proper procedures must also be in place to conduct the harvesting in a safe manner. These procedures must include the requirements for proper training of all workers as well as the appropriate equipment and supervision to carry out the work safely.


A powerful yet compact BBQ. The Broil King Gem™ 320 is ideal when you barbecue for small numbers of family or friends and want to provide no fuss, reliable, consistent, flavoursome dishes. With three stainless steel tube BBQ burners for even heat, corner to corner, and producing 23,544 British Thermal units, (the measurement for energy on the grill) from the main burner, this little Gem has a whole lot of grunt. Compact, with drop down shelves and crack-proof wheels for easy movability. it's a great BBQ solution if you're short on space but big on BBQ'ing. Visit your nearest 4 Seasons BBQ shop.


text:
Влади́мир Никола́евич Пугачёв (род. 5 января 1969, город Бор, Горьковская область, РСФСР, СССР) — российский , пейзажист.

Образование
 Горьковский авиационный техникум (1984—1988)
 Московский государственный академический художественный институт имени В. И. Сурикова (1996—2002)

Биография
После окончания 8 классов учился в Горьковской авиационном техникуме, одновременно занимаясь в изостудиях города Горького. С 1991 года жил в Москве и обучался в изостудии ДК МАИ у И. В. Ольховой. В 1996 году поступил в МГАХИ, где учился у М. М. Курилко-Рюмина, Р. И. Лебедевой, Н. Н. Меркушева., О. И. Ардемасова.

Живёт в Обнинске. По некоторым оценкам, один из трёх самых «продаваемых» (вместе с Сергеем Галицыным и Сергеем Вишняковым) художников Обнинска.

Участие в творческих организациях
 Член Союза художников России (2003)
 Член ТЖ МСХ «Московские Живописцы»

Выставки

Персональные выставки
 2020 — Персональная выставка «Радостное небо» в Совете федерации РФ.
 2014 — Персональная выставка. Нижегородский государственный художественный музей, г. Нижний Новгород.
 2014 — Персональная выставка «Град Петров», г. Обнинск.
 2013 — Персональная выставка. Тульская область, «Государственный музей-заповедник В. Д. Поленова».
 2013 — Персональная выставка «Солнечная галерея» в городе Малоярославец.
 2013 — Персональная выставка. Нижегородская обл., г. Бор.
 2012 — Персональная выставка. Академия управления МВД России «Моя любимая Родина», г. Москва
 2012 — Персональная выставка в Представительстве правительства Калужской области при правительстве РФ, г. Москва
 2012 — Персональная выставка «Волшебная страна Любовь» , Бизнес Центре Легион1, г. Москва.
 2012 — Персональная выставка, Российский университет дружбы народов, г. Москва
 2012 — Персональная выставка. «Любимой Родины мотивы», г. Таруса
 2011 — Персональная выставка в г. Обнинск.
 2011 — Персональная выставка «Весна на нашей улице» в галерее г. Химки
 2011 — Выставка в ЦДХ «Мерцающий свет». г. Москва
 2011 — Персональная выставка,, Российский университет дружбы народов, г. Москва
 2010 — Москва, Государственный театр Владимира Назарова (совместная выставка с Алексеем Никитенковым).
 2007 — Серпухов.
 2006 — Калуга, галерея «Образ».
 2006 — Обнинск, Музей истории города Обнинска (совместная выставка с Сергеем Галицыным).
 2005 — Вязьма.
 2005 — Малоярославец.
 2004 — Наро-Фоминск.
 2003 — Боровск.
 2001 — Обнинск, Музей истории города Обнинска.
 2000 — Малоярославец.

Групповые выставки
 2012 — Академия управления МВД России «Моя любимая Родина», г. Москва
 2010 — «Люблю тебя, мой город», Обнинск, Музей истории города Обнинска.
 2008 — «Традиции современности», Москва, Центральный дом художника.
 2007 — Москва, Венгерский культурный центр.
 2007 — Москва, Международный информационный центр ООН.
 2006 — Выставка живописи ТО малоярославецких художников «Вернисаж», Малоярославец.
 2006 — Выставка обнинских художников (к 50-летию города), Обнинск, Музей истории города Обнинска.
 2005 — II Всероссийская художественная выставка «Возрождение», Белгород.
 2005 — Калужская областная итоговая выставка, Калуга.
 2004 — «Земля калужская», Москва, Центральный дом художника.
 2004 — Боровск.
 2004 — IX Региональная художественная выставка, Липецк.
 2004 — 20th International Festival Exhibition, Лондон, 9 августа — 4 сентября.
 2003 — «АртМанеж» (весна), Москва, ЦВЗ «Манеж».
 2003 — «Москва — Питер», Москва, Центральный дом художника.
 2002 — Москва, Дом журналистов.
 2002 — VII Международная научно-техническая выставка «Технологии России», Китай, Шэньян.
 2002 — «АртСалон», Москва, Центральный дом художника.
 2001 — Европейская выставка у подножия горы Фиджи, Япония.
 2001 — Благотворительная выставка для детей, больных лейкемией, Москва, Московский музей современного искусства.
 2001 — Выставка, посвященная сотрудничеству Германия — Россия, Москва, «Дом дружбы».
 2001 — Российская молодёжная выставка, Москва, Центральный дом художника.
 2001 — ART, Испания, Барселона.
 2001 — «Миллениум», Москва, Центральный дом художника.

Местонахождение работ
Музей истории города Обнинска, Картинная галерея имени Е. А. Чернявской, Малоярославецкий художественно-выставочный центр имени Солдатенкова, Калужская областная картинная галерея «Образ», Боровский городской центр искусств, Тарусская картинная галерея, фонды Калужской организации союза художников России, международный фонд «Культурное достояние», частные коллекции в России и за рубежом (Япония, Испания, Германия, Англия, Франция, США).

Примечания

Ссылки
 Владимир Пугачёв на ArtLib.ru
 Владимир Пугачёв на сайте галереи современного искусства «Новая Классика»
 Владимир Пугачёв на Arts.In.UA
 Владимир Пугачёв. pugachev.bos.ru

Художники-пейзажисты России
Выпускники МГХИ им. Сурикова
Члены Союза художников России

redpajama_set_name: RedPajamaWikipedia


text:
Q: Normalization of an addition of two values I have the following expression which I want to normalize:
val = v1+ v2
v1: has real values >0
v2: has values between 0 and 1

I want to normalize val such that it gives values between 0 and 1.
Best regards,

A: Given your definition:
val = v1+ v2
v1: has real values >0
v2: has values between 0 and 1

we know that val is a real value $>0$. Mapping this onto a value between $0$ and $1$ simply requires a monotonic function that stays small as its input goes to infinity. A simple option might be $\text{val}_{\text{norm}} = 1-2^{-\text{val}}$
If you wanted more weight on v2 in the result you might consider normalizing  v1 instead and then adding & scaling into the desired range.

redpajama_set_name: RedPajamaStackExchange


As bikes get more sophisticated the yearly rhythm of changing the whole line-up changes to more sustainable products but the event itself still marks an important milestone in bike industry calendar. In five venues around Taichung, Taiwan the exclusive business visitors are able to meet their component suppliers in a very familiar manner. Without great marketing efforts companies expo their novelties for the next two upcoming years.
After the first products with "bluetooth-only connectivity" are live on the market, more and more OEMs are interested in "autonomous" connectivity solutions including 2G or 3G networks. The main difference is that autonomous solutions allow the manufacturer to permanently communicate with the bike whereas "bluetooth-only solutions" allow communication only when the rider has paired his smartphone to the bike.