API browser of tarmedValidator100 COM module


/images/arrow_right.png ITarmedInput::SetTreatment method
Set the treatment input data.
 
PATCH
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.
This patch describes how to externally set the validity barrier between Tarmed 1.08BR and Tarmed 1.09 UV/IV/MV by using the bstrEanNumberSection variable.
space
 
/images/arrow_right.png C/C++ calling syntax
HRESULT SetTreatment( CantonType
LawType
TreatmentType
SettlementType
BSTR
VARIANT_BOOL
eCanton,
eLaw,
eType,
eSettlement,
bstrEanNumberSection,
*pbStatus);
 
/images/arrow_right.png Calling argument description
[in] CantonType eCanton Canton type.
[in] LawType eLaw Law type.
[in] TreatmentType eType Treatment type.
[in] SettlementType eSettlement Settlement type.
[in] BSTR bstrEanNumberSection EAN number of the section - leave empty if the section concept is unused.
 
PATCH
Append the validity barrier '#VB109=dd.mm.yyyy' to the bstrEanNumberSection variable, where
the patch is case-insensitive and applicable for eLaw = UV|MV|IV only.
 
By defining the validity barrier, the tarmedValidator automatically switches between the two Tarmed versions UV/IV/MV and its different rule spaces.
[out, retval] VARIANT_BOOL *pbStatus Return status of the method
 
/images/arrow_right.png C/C++ return value
S_OK This value is returned if the function call was successful or if the return value of a boolean method signalling a true value. In this case the VARIANT_BOOL is set to VARIANT_TRUE.
S_FALSE This is the return value of a boolean method signalling a false return value. In this case the VARIANT_BOOL is set to VARIANT_FALSE.
E_name This value is returned if the function call was unsuccessful and an error exception was generated. Note that if you are using SmartPointers an exception is thrown under these conditions.