The ATL COM module tarmedValidator provides methods to
browse, search & validate records of the Tarmed tariff
browse, search & validate records of the Tarmed tariff
Patch: how to externally set the validity barrier between Tarmed 1.08BR and Tarmed 1.09 UV/IV/MV
Due to the disagreement between the tariff partners in the social insurance area, Tarmed 1.09 cannot be introduced uniformly as of April 1, 2018. The official date to change from Tarmed 1.08BR to Tarmed 1.09 is removed from the tarmedValidator.
This patch describes how the validity barrier for switching between Tarmed 1.08BR and Tarmed 1.09 can be set externally such as to introduce Tarmed 1.09 UV/IV/MV.
Please note that in case of an invoice generation the validity barrier must be set via the auxilliary interface IGeneralInvoiceRequestManager::ITarmedInput as well in order to delegate the information into the tarmedValidator!
Due to the disagreement between the tariff partners in the social insurance area, Tarmed 1.09 cannot be introduced uniformly as of April 1, 2018. The official date to change from Tarmed 1.08BR to Tarmed 1.09 is removed from the tarmedValidator.
This patch describes how the validity barrier for switching between Tarmed 1.08BR and Tarmed 1.09 can be set externally such as to introduce Tarmed 1.09 UV/IV/MV.
Please note that in case of an invoice generation the validity barrier must be set via the auxilliary interface IGeneralInvoiceRequestManager::ITarmedInput as well in order to delegate the information into the tarmedValidator!
- append the validity barrier '#VB109=dd.mm.yyyy' to the bstrEanNumberSection variable in: ITarmedInput::SetTreatment(eCanton,eLaw,eType,eSettlemnt,"aEANSection#VB109=01.04.2018")
where the patch is case-insensitive and applicable for eLaw = UV|IV|MV only.
By defining the validity barrier, the tarmedValidator automatically switches between the two Tarmed versions UV/IV/MV and its different rule spaces.