Enriches a form data record with surgical implants. The user has to be logged in before attempting to invoke this operation, the user must also know the id of the form data record to be updated, see the insert form and search form use cases.

  1. Call the web service operation server.addImplantToFormData providing the server session id, a preferred language, and a set of implants, see server.addImplantFormDataRequest. Each implant to be added can either be explicitly described, see ImplantDescription, or consist of its barcode information, see BarcodeData. The response object, see server.addImplantFormDataReponse, provides the indication of success/failure of the operation, as well as a set of collision elements, each describing  a BarcodeData  element from the request  for which more than one implant product was a match in the Memdoc product catalog. This is illustrated in the server.SOAP-Request-Reply example.

 

Special care must be taken by a web service client trying to add implants with GS1-128 encoded barcodes due to its variable length application identifiers (AI), such as AI (10) Batch number. These barcodes require not only for the client to provide this web service operation with all the visible/printable characters of the barcode, but also each variable length AI Field must be flagged with a terminator character sequence (by the default we assume ^] will be used ). See BarcodeData for an in depth description concerning this topic. 

 

See server.SOAP-Request-Reply for an illustration of this operation. See also, GS1-128 decoding and the Group Separator concerning the topic of variable length AI elements.