Use Case Scenarios
      Back to home
      1. IT Support
      2. XactAnalysis Integration
      3. Use Case Scenarios

      Client/Carrier creates the claim in XactAnalysis and Adjuster enters inspection data after scoping in Hubvia/Scoping App

      • In this case, the claims would still be created and assigned in XactAnalysis. 
      • The same data would be available in Brush Claims instance of XactAnalysis. (like a parent-child relation, where the parent is the XactAnalysis owned by Verisk and Child would be Brush Claims instance of XactAnalysis).
      • The claim must be created in Hubvia through EDI.
      • The Adjuster gets the assignment of the claim and will use either Hubvia or Scoping App to enter the inspection data.
      • Any information entered by the Adjuster in scoping App must be imported to XactAnalysis and pushed to Xactimate. Xactimate calculates the estimates with the data imported.
      • The supervisor reviews the estimates and if no corrections are needed then the status would change to QA approved.
      • The estimates would be pushed to XactAnalysis Parent Instance and Hubvia as well. This data would be kept in Hubvia storage.
      • Hubvia will use the estimates to populate TGL and will change the status of the claim to 'Ready to Invoice'.
      • The details of inspection, docs, attachments, images and all of the estimation data is stored in Hubvia's data storage as they set the base for any future references.(History Data).
      • The role of Hubvia in this scenario would be to scope the losses, capture the inspection data and also take care of the invoicing and payment part done.