The acfValidator provides methods to browse, search,
validate & group records of the ACF and/or LKAAT tariff
validate & group records of the ACF and/or LKAAT tariff
API browser of acfValidator100 COM module
 IValidateTMA::AddService method |
 |
||
|---|---|---|---|
| Adds a new TMA service to the list of services which will be validated against all previously added services of the same session. If the code supplied passes all validations a VARIANT_TRUE value is returned. If the code was not accepted VARIANT_FALSE is returned and the variable plStatus contains the error code. | |||
| |||
| Restful webservice calling syntax |
|||
| [POST] | /baseURL/IValidateTMA/AddService | ||
| [JSON input data] | pIValidateTMA: bstrCode: bstrReferenceCode: dQuantity: lSessionNumber: dDate: eSide: bstrName: eIgnoreValidate: lHook: |
longValue, //interface address "utf8StringValue", "utf8StringValue", doubleValue, longValue, variantDateValue | "stringISODateValue", longValue, "utf8StringValue", longValue, 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. | ||
| |||
| C/C++ calling syntax |
|||
| HRESULT AddService( | BSTR
BSTR double long DATE SideType BSTR YesNoType long VARIANT_BOOL |
bstrCode,
bstrReferenceCode, dQuantity, lSessionNumber, dDate, eSide, bstrName, eIgnoreValidate, lHook, *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. | ||
| |||
| Calling argument description |
|||
| [in] BSTR | bstrCode | Code of the service.
This code can be a drug's GTIN - cf below at bstrName. |
|
| [in] BSTR | bstrReferenceCode | The reference code of the service. The reference code must be set if the enServicePropertyIsNeedsRefCode bit of that service is defined.
If a reference code is needed than that parent service must be supplied before this one. |
|
| [in] double | dQuantity | Quantity of the service | |
| [in] long | lSessionNumber | The session number or patient contact ID.
Please note that the 'SessionNumber" plays a central role in the ACF/LKAAT tariffs, in that this ID serves as a grouping and connection object to combine services (even across days). Furthermore, the same ID is also used in the TMA tariff to bundle the service and link it to the corresponding ICD and capitulum code. |
|
| [in] DATE | dDate | Date of the service to ensure that the validity date range is obeyed | |
| [in] SideType | eSide | The side for which the service is applied or enSideNone if there is noSideDependeny | |
| [in] BSTR | bstrName | The service name. Under normal circumstances you will leave the name variable empty. However if you input a drug by setting the bstrCode=GTIN, than you have to supply the drug's name here since there is no database lookup available inside the module. |
|
| [in] YesNoType | eIgnoreValidate | Flag indicating whether the validation should be ignored or not. To turn off the validation might be useful in the situation when a service should be added even if the validation failed due to a special agreement with the insurance or patient. |
|
| [in] long | lHook | The external hook, that was provided in the AddService call. The lHook ID primarily serves to identify this service when the services are read back. | |
| [out,retval] VARIANT_BOOL | *pbStatus | The principal validation status
|
|
|
|||