• The Forum Datenaustausch has revised the generalInvoiceRequest450 schema (Revision 5) as of 1st August 2024 regarding the service attribute list. The list is augmented by Bit 3 (0x000004): drugOffLabelUse and Bit 4 (0x000008): withoutDoctorsOrder.
   
  

  Bit	Meaning
  Bit 3: (0x000004)	drugOffLabelUse: off label use of a drug in accordance with Art. 71a-c KVV   If this bit ("drugOffLabelUse") is set, the service provider declares that the off-label prescription of the drug has been approved by the healthcare insurance by means of a prior accepted credit request.
  Bit 4: (0x000008)	withoutDoctorsOrder: Services without a doctor's order (Art. 59 KVV, Abs. 3bis)   If this bit ("withoutDoctorsOrder") is set, the service provider declares that the service was provided without a doctor's order.

  
  Service Attributes are supplied by the lServiceAttributes variable or alternatively by including the defined keywords {drugOffLabelUse | withoutDoctorsOrder} as part of the bstrRemark variable - please study the documentation of
  • IGeneralInvoiceRequest::AddService()
  • IGeneralInvoiceRequest::AddServiceEx()
  
  Please note, that these service attributes are automatically migrated/printed onto the remark (e.g. "<withoutDoctorsOrder> ist definiert") in a printout.
   
  
• There is a minor correction in the adaptiveQuantity methode, which calculates the number of significant digits.
  Under certain conditions (very small quantities), the number of significant digits for the quantity has been underestimated. The consequence was a higher numerical error, which may have led to a rejection of the invoice. It should be noted that this situation only occurred in a printed calculation - the XML was always unaffected.
  This error has been fixed with this update.
   
  
• oopProxyGeneralInvoiceRequestManager450.exe and generalInvoiceRequestManagerServer450.exe has been upgraded due to internal changes.
  You are encouraged to update to this build!

• Improved cleanup procedure of the temporary files. The files are deleted 24h after its generation. There was a bug that these are not deleted under some circumstances and thus accumulating.
   

• Improved validation/pattern matching of eMail and URI addresses.
   
• Improved maxLength trim function for the generation of XML infoset elements and attributes
   
• Optimized error detection and logging for the management of Base64-coded file attachments. Failure reason details (stemming from the os system) are inputed into the logfile and error message.
   

• generalInvoiceRequestManager450.dll: bug fixing in IServiceExInput:
  • Due to a 'race condition' occurring in IServiceExInput under certain conditions, the synchronisation of data from IServiceExInput towards ITarmedInput was sometimes disrupted potentially leading to 'false-positive' Tarmed rule violations.
     
    This error is fixed with that build.
    We apologize again for any inconveniences this might have caused!
     
    
  • Improved code to distinguish and dispatch services of type 'service' and 'serviceEx' and their mutual blocking in the generation and XML loading process.
    
  
  You are strongly encouraged to update to this build!

• generalInvoiceRequestManager450.dll: bug fixing in IServiceExInput:
  • Inside IServiceExInput::SetPhysician() parameters of the treatment were wrongly initialized (enKVG,enCantonAG). If IServiceExInput::SetTreatment() was not called thereafter the wrong law (enKVG) was defined leading to errors in IGeneralInvoiceRequest::AddServiceEx() if and only if the correct, initial law was unequal enKVG!
     
    This error is fixed with that build.
    We apologize for any inconveniences this might have caused!
  
  You are strongly encouraged to update to this build!

• Initial version of the RESTServer generalInvoiceRequestManagerServer450 is published
  An introduction/overview and detailed documentation can be found at API Documentation
   
• generalInvoiceRequestManager450.dll: bug fixing, code improvements and optimizations have been made, among others these are:
  • Production of the 'unknown' IV case number with the new base '280' as requested by the IV authorities. This unknown IV case number is automatically generated if no or an illegal case number is supplied as input.
  • Improved algorithm for generating the temporary working directory especially for the situation where the COM module runs under "local system service".
  
  You are strongly encouraged to update to this build!

• Bug fixing of the XML generation for DRG invoices with a 3-party splitting situation.
   
• Improved invoice printing/PDF production for the situation where the COM module runs under "local system service". Should your environment be modelled like that, than you are strongly encouraged to update to this build.

• This is a feature update, that does allow to read and analyze XML infosets without the named namespace prefix 'invoice:'. The corresponding XSD qualifies each element with elementFormDefault='qualified', that make XML files without a named namespace schema in effect invalid. However, it seems that such files are produced and this feature update allows to successfully overcome this error.
   
• Improved PDF invoice production for the situation where COM module runs as system service.
   
• Improved validation code for inputted mail adresses.
   

• Improved and stabilized PDF generation for environments where the generalInvoiceRequest450 module is called from within a System service component. In such an environment the device context is minimal and different from the desktop device context.
  
• The input for the generation of the QR code is scanned for unwanted characters (ASCII codes below 32) and eventually deleted
  
• Cumulative update: a few small low-priority bugs have been corrected, which were reported by users of the COM modules over time.
  

• Improved validation of mail addresses, removal of non-printable characters, and verification of the required mail pattern '.+@.+'.
  
• Change of the GLN_UNKNOWN to '2099999999998' and improved management regarding the GLN_UNKNOWN

• Binding/dispatching the new tariff "454 - MiGel for Care Providers" (becoming active at 01.10.2021) onto the migelValidator100 such that the validation service becomes available for these types of service records.
   
• Binding/dispatching the new tariff "030 - STReha" and "031 - STReha Additions" (becoming active at 01.01.2022) onto the drgValidator100 such that the validation service becomes available for these types of service records.
   

• To improve the quality assurance of the QR code, the data entered for the QR part is increasingly checked for illegal characters such as lf,cr,tab etc. and eventually removed. This applies in particular to the variable 'customerNote'.
   

• The decoding of Base64-encoded attachments has been enhanced to successfully process the standard, 72-character chunks formatting as well as a non-standard, single-string formatting.
   
  This measure is important for the correct processing of non-Sumex1 generated and potentially non-standard compliant XML files.

• IGeneralInvoiceRequest::AddService()
• IGeneralInvoiceRequest::AddServiceEx()

• A typo error in the italian QR invoice template was corrected.
  
• The size of the leftsided amount field in the QREsr+ situation was corrected to a smaller rectangle.
   
  

• A possible error in the IServiceExInput auxiliary interface has been corrected, which could have occurred under very special and rarely occurring conditions.
   
  The dignities added by IServiceExInput::AddDignity() store a data pair 'provider GLN/qualitative dignity' in the tarmedValidator. This data input is further extended by the Boolean 'fullFMH'. 'fullFMH' indicates whether the dignity is coupled to a scaling factor (e.g. dignity '3000' is scaled with 0.93). This status is retrieved from the currently open Tarmed database. But only Tarmed1.09 knows the concept 'fullFMH', Tarmed1.08BR qualifies all dignities as 'fullFMH'.
   
  If the first data entry in IServiceExInput is not IServiceExInput::SetTreatment() (this method controls the use of the correct Tarmed database), it is possible that the status 'fullFMH' is set false positive regarding any non-'fullFMH' dignity inputted before the SetTreatment() method.
   
  This fix corrects that such a false positive result regarding 'fullFMH' could no longer occur.
   
  

• 04.04.2020 - API Patch: query/check the reachability of a recipient bstrToEAN
• 04.04.2020 - Documentation: IGeneralInvoiceRequest::SetTransport

• The IGeneralInvoiceRequestManager::LoadXML method might return a false positive error ("XML is not well formed or is not schema valid") if the XML file contains xtraHospital/ambulatory data. Under such a condition the cardinality of BfS, DRG and Case Detail records has been misinterpreted. This bug was fixed with the current new build.
   

• Update of the code part responsible for the QR code production and layout. This update became necessary due to standardization change published by the QR standardization body.
  The updated code now produces standard compliant QR invoices that becomes normative beginning mid of 2020
   
• Performance optimization of the logging management regarding the recycling process when reaching the high water mark of the logfile. This change improves the performance of the recycling process having an effect primarily for a massive multi-threaded environment.
   
• Bug fix occuring in rare cases when an interface error is signalled but the error message is returned empty in GetAbortInfo()
   

• Performance optimization of the logging management regarding the recycling process when reaching the high water mark of the logfile. This change improves the performance of the recycling process having an effect primarily for a massive multi-threaded environment.
   
• Bug fix of the printing engine having in rare cases a z-order problem of the 2D Datamatrix code partially obscuring the services' date.
   

• Bug fix of the printing engine not showing certain print objects like Datamatrix/QR codes when running the COM dll under a service environment.
   
• Revised/optimised logging regarding the binding to the interface instance has been implemented. This change improves analysis in a massive multi-threaded environment.
   
• Revised error management (enhanced binding to the interface instance) suitable for a massive multi-threaded environment
   

• The processing of a XML file is done in two passes due to memory and performance considerations. Any Base64 attachments are extracted and saved separately, beforehand the basis XML data are loaded into the DOM.
  When splitting up these Base64 files a bug occurring with very small attachments was fixed.

• Validation of tariff 030 services by the drgValidator was activated due to the presence of tariff 030 in the drgValidator tariff pool.

• calculation of lengthOfStay in the stationary case: a memory exception was thrown in the calculation of the lengthOfStay if there was no DRG service present.
  This assumption was dropped and the bug fixed.
   
  
• thrown exception inside log method: in rare cases with a puny set of data a memory exception could be thrown inside the function argument logging that effectively "swallowed" a prior generated error message.
  The cause for the memory exception was eliminasted and thus the correct error message is populated back to the main software as expected.

• internal adjustments needed for the upcoming new tariffs like TarPsy, and Physio KV.

• consult the methods IGeneralInvoiceRequestManager:Print, IGeneralInvoiceRequestManager:PrintAdjust and IGeneralInvoiceRequestManager:PrintSetup
  nbsp;
• check the document «Syntax of the printTemplate variable» to learn, how to change the layout of the print template.

Please read the document "Changes from V4.40 to V4.50..." for an overview about the major changes

• This is a feature update, that does allow to read and analyze XML infosets without the named namespace prefix 'invoice:'. The corresponding XSD qualifies each element with elementFormDefault='qualified', that make XML files without a named namespace schema in effect invalid. However, it seems that such files are produced and this feature update allows to successfully overcome this error.
   
• Improved validation code for inputted mail adresses.
   

• Improved validation of mail addresses, removal of non-printable characters, and verification of the required mail pattern '.+@.+'.
  
• Change of the GLN_UNKNOWN to '2099999999998' and improved management regarding the GLN_UNKNOWN

• Binding/dispatching the new tariff "454 - MiGel for Care Providers" (becoming active at 01.10.2021) onto the migelValidator100 such that the validation service becomes available for these types of service records.
   
• Binding/dispatching the new tariff "030 - STReha" and "031 - STReha Additions" (becoming active at 01.01.2022) onto the drgValidator100 such that the validation service becomes available for these types of service records.
   

• The decoding of Base64-encoded attachments has been enhanced to successfully process the standard, 72-character chunks formatting as well as a non-standard, single-string formatting.
   
  This measure is important for the correct processing of non-Sumex1 generated and potentially non-standard compliant XML files.

• IGeneralInvoiceRequest::AddService()
• IGeneralInvoiceRequest::AddTarmedService()
• IGeneralInvoiceRequest::AddTarmedServiceEx()

• Performance optimization of the logging management regarding the recycling process when reaching the high water mark of the logfile. This change improves the performance of the recycling process having an effect primarily for a massive multi-threaded environment.
   
• Bug fix occuring in rare cases when an interface error is signalled but the error message is returned empty in GetAbortInfo()
   

• Performance optimization of the logging management regarding the recycling process when reaching the high water mark of the logfile. This change improves the performance of the recycling process having an effect primarily for a massive multi-threaded environment.
   
• Bug fix of the printing engine having in rare cases a z-order problem of the 2D Datamatrix code partially obscuring the services' date.
   

• Bug fix of the printing engine not showing certain print objects like Datamatrix/QR codes when running the COM dll under a service environment.
   
• Revised/optimised logging regarding the binding to the interface instance has been implemented. This change improves analysis in a massive multi-threaded environment.
   
• Revised error management (enhanced binding to the interface instance) suitable for a massive multi-threaded environment
   

• The processing of a XML file is done in two passes due to memory and performance considerations. Any Base64 attachments are extracted and saved separately, beforehand the basis XML data are loaded into the DOM.
  When splitting up these Base64 files a bug occurring with very small attachments was fixed.

• Validation of tariff 030 services by the drgValidator was activated due to the presence of tariff 030 in the drgValidator tariff pool.

• calculation of lengthOfStay in the stationary case: a memory exception was thrown in the calculation of the lengthOfStay if there was no DRG service present.
  This assumption was dropped and the bug fixed.
   
  
• thrown exception inside log method: in rare cases with a puny set of data a memory exception could be thrown inside the function argument logging that effectively "swallowed" a prior generated error message.
  The cause for the memory exception was eliminasted and thus the correct error message is populated back to the main software as expected.

• internal adjustments needed for the upcoming new tariffs like TarPsy, and Physio KV.

• consult the methods IGeneralInvoiceRequestManager:Print, IGeneralInvoiceRequestManager:PrintAdjust and IGeneralInvoiceRequestManager:PrintSetup
  nbsp;
• check the document «Syntax of the printTemplate variable» to learn, how to change the layout of the print template.

• A cleanup task for temporary files has been added. In fact, all files temporary generated
  are deleted once the main interface is shut down. However, there are situations where files
  are still locked at shutdown and thus are not deletable at that moment. As a remedy, the cleanup
  task is started periodically to check for files older than 5 days that are deleted eventually.

• The code for getting a proper working directory was improved by taking into account more than one
  possible location (AppDATA and TempPath)
   
• The calculation of the summed vat rates has been changed insofar as the summing is done in full precision,
  and the result is thereafter rounded to 2 significant digits.
  This patch eliminates a possible rounding error.

The print object PRINTLANGUAGE=language; forces forces the usage of the print_template for the supplied language and
thus override the print language given in IGeneralInvoiceRequest::Initialize - cf. description in Syntax of the printTemplate variable of the Print method

• enhanced exception/error handling when generating an XML data stream
• better allocation and sorting algorithm for the load process of services from an XML file
• GTIN list in print templates are now correctly splitted into 2 lines if more than 5 provider GTIN are supplied

• The changed interfaces of the final miscValidator200 module enforces a recompilation of this module as the TLBs of the validators are included statically in C++.
   
• The position changes of some print objects due to the usage of a large logo have been refined.

• There are rare cases where the IBAN can contain letters!
  In such a case both the IBAN and account number must be supplied hash separated as IBAN_number#account_number in the IGeneralInvoiceRequest::SetEsrRed method otherwise an error is generated.

• Performance optimization of the logging management regarding the recycling process when reaching the high water mark of the logfile. This change improves the performance of the recycling process having an effect primarily for a massive multi-threaded environment.
   
• Bug fix occuring in rare cases when an interface error is signalled but the error message is returned empty in GetAbortInfo()
   

• Revised/optimised logging regarding the binding to the interface instance has been implemented. This change improves analysis in a massive multi-threaded environment.
   
• Revised error management (enhanced binding to the interface instance) suitable for a massive multi-threaded environment
   

• The processing of a XML file is done in two passes due to memory and performance considerations. Any Base64 attachments are extracted and saved separately, beforehand the basis XML data are loaded into the DOM.
  When splitting up these Base64 files a bug occurring with very small attachments was fixed.

• internal adjustments needed for the upcoming new tariffs like TarPsy, and Physio KV.

• A cleanup task for temporary files has been added. In fact, all files temporary generated
  are deleted once the main interface is shut down. However, there are situations where files
  are still locked at shutdown and thus are not deletable at that moment. As a remedy, the cleanup
  task is started periodically to check for files older than 5 days that are deleted eventually.

• The code for getting a proper working directory was improved by taking into account more than one
  possible location (AppDATA and TempPath)
   
• The calculation of the summed vat rates has been changed insofar as the summing is done in full precision,
  and the result is thereafter rounded to 2 significant digits.
  This patch eliminates a possible rounding error.

• enhanced exception/error handling when generating an XML data stream
• better allocation and sorting algorithm for the load process of services from an XML file
• GTIN list in print templates are now correctly splitted into 2 lines if more than 5 provider GTIN are supplied

• The changed interfaces of the final miscValidator200 module enforces a recompilation of this module as the TLBs of the validators are included statically in C++.
   
• The position changes of some print objects due to the usage of a large logo have been refined.

• Changed whitelist behaviour:
  The whitelist mechanism has been deactivated meaning that all insurances now can receive V430 XML infosets or printed invoices.
   
• There are rare cases where the IBAN can contain letters!
  In such a case both the IBAN and account number must be supplied hash separated as IBAN_number#account_number in the IGeneralInvoiceRequest::SetEsrRed method otherwise an error is generated.