The ATL COM module tarmedValidator provides methods to
browse, search & validate records of the Tarmed tariff
API browser of tarmedValidator100 COM module


/images/arrow_right.png IUtility::Expand method space
Expands the given main code, according to the supplied number and as multiples of the base unit.
 
PATCH:
  • If the instruction "#noTimeLimit" is appended to the service code (e.g. "00.0010#noTimeLimit"), then a full expansion without obeying any time restrictions or limits is performed.
     
    A suchwise generated expansion of a service chain might of course provoke validation errors and then generates messages about the violation of the quantity limit! The newly built-in
    time restrictions of Tarmed 1.09 are thus made "visible" and the over time is not silently discarded.
     
  • If the instruction #INFO is appened to the service code (e.g. "00.0010#INFO") the IUtility::GetFirstExpandRecord method returns "non-expandable, dropped" fraction too large for a full expansion under the current rule regime.
     
    For example, after expanding IUtility::Expand("00.0010#INFO",23,) under a "paper limits", the method IUtility::GetFirstExpandRecord returns "00.0010#INFO3" as code meaning that 3 min out of 23 min are not applicable (aka dropped) within the current TarMed rule set regime.
space
/images/arrow_right.png Restful webservice calling syntax
[POST] /baseURL/IUtility/Expand
[JSON input data] pIUtility:
bstrCode:
dNumber:
dDate:
eSettlement:		 longValue,    //interface address
"utf8StringValue",
doubleValue,
variantDateValue | "stringISODateValue",
longValue
[JSON result data] pbStatus: booleanValue
 
[HTTP result status] 200 Return status 200 signals a successful method call
204 Return status 204 (noContent) signals that the end of an iteration is reached
>= 400 Return status >= 400 signals an unsuccessful function call. The returned JSON{errorCode: code, errorText:"text"} supplies the error message the same as GetAbortInfo() would do.
space
/images/arrow_right.png C/C++ calling syntax
HRESULT Expand( BSTR
double
DATE
SettlementType
VARIANT_BOOL 		bstrCode,
dNumber,
dDate,
eSettlement,
*pbStatus);
[C/C++ return value] S_OK This value is returned if the function call was successful.
S_FALSE This value is returned if the end of an iteration is reached
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.
space
/images/arrow_right.png Calling argument description
[in] BSTR bstrCode Tarmed main service code
 
Patch:
  • bstrCode can be appended with #noTimeLimit to fully expand the service chain without any time restriction.
     
  • bstrCode can be appended with #INFO to retrieve the droped minutes in the IUtility::GetFirstExpandRecord method
[in] double dNumber Number supplied as multiples of the base unit.
For example if a consultation lasted 23 Minutes, 23 would be entered.
 
The base unit information for the code can be retrieved from the ISearch::GetUnit property interface.
[in] DATE dDate Date of the service.
[in] SettlementType eSettlement Settlement type.
[out,retval] VARIANT_BOOL *pbStatus Return status. VARIANT_TRUE means S_OK, VARIANT_FALSE means S_FALSE (e.g. in an iterator) or an error (E_name).
In the later case check for possible errors with the GetAbortInfo method.
space