Sketch My Roof

Tags - Popular | FAQ  

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 05/15/2007 8:00 PM by  Gale Hawkins
XML Open Standard for Property Claims
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Gale Hawkins
PowerClaim.com
Member
Member
Posts:386


--
03/15/2007 12:18 AM

    Now that different property claims handling software vendors are starting to develop around a XML Open Standard I went back to a discussion John started about 5 years ago where he talks about their use of XML in moving claim files between different software solutions for the purpose of data mining. His view and that of the others that posted 5 years ago shows how slow things have moved until very recently.

     

    In CADO chat last night the question came up by an adjuster as to what does XML Open Standard mean? Now that software vendors are talking up the new found compatibilities (especially the sales folks) by using an Open Standard based on XML this question will come up more and more often so maybe over the coming months the current vendors and new software vendors coming on board through the XML Open Standard plus others that will be embracing the concept in the coming months and years will add their knowledge and experiences.

     

    While today no one questions the fact that a property XML Open Standard is being embraced by software vendors in the property claims handling arena there are those that will resist the trend because they will now have to compete based on quality and value alone. The XML Open Standard is lowering claims handling cost because of competition which is a good thing for all except those that show up to the Open Standard party late.

     

    Once a software vendor announces they support an Open Standard then there is no turning back without legal ramifications. When John five years wrote, “I may be opening up a Pandora's Box but here goes...” he was on target. As the years past and the XML (or the technology to follow) Open Standard evolves from input by all of the software vendors then property claims will move as freely as auto claims do today through their XML Open Standard for auto claims. Auto estimates have less variables than property claims and a much higher frequency so the carriers acted first in that arena.

     

    http://www.catadjuster.org/discus/m.../4517.html

    0
    Gale Hawkins
    PowerClaim.com
    Member
    Member
    Posts:386


    --
    03/15/2007 11:42 AM

    http://www.w3schools.com/xml/xml_whatis.asp is a good link for an overview or detail understanding of XML. The below is a sample.

     

    What is XML?

    • XML stands for EXtensible Markup Language
    • XML is a markup language much like HTML
    • XML was designed to describe data
    • XML tags are not predefined. You must define your own tags
    • XML uses a Document Type Definition (DTD) or an XML Schema to describe the data
    • XML with a DTD or XML Schema is designed to be self-descriptive
    • XML is a W3C Recommendation

     

    XML Does not DO Anything

    XML was not designed to DO anything.

    Maybe it is a little hard to understand, but XML does not DO anything. XML was created to structure, store and to send information.

    The following example is a note to Tove from Jani, stored as XML:

    < note >
    < to >Tove
    < from >Jani
    < heading >Reminder
    < body >Don't forget me this weekend!
    < /note >

    The note has a header and a message body. It also has sender and receiver information. But still, this XML document does not DO anything. It is just pure information wrapped in XML tags. Someone must write a piece of software to send, receive or display it.


    XML is Free and Extensible

    XML tags are not predefined. You must "invent" your own tags.

    The tags used to mark up HTML documents and the structure of HTML documents is predefined. The author of HTML documents can only use tags that are defined in the HTML standard (like

     

    XML allows the author to define his own tags and his own document structure.

    The tags in the example above (like and ) are not defined in any XML standard. These tags are "invented" by the author of the XML document.


    [/quote] [/quote] [/quote]
    0
    legcat10
    Guest
    Guest
    Posts:4


    --
    03/16/2007 1:53 PM
    Thanks for bringing up this topic again, Gale. I personally cannot wait until this takes off. As we have discussed previously, we have been applying this concept for some years now - to the extent that we can - and find the flow of information very easy and efficient, using XML. We'll see what happens - hopefully sooner rather than later...................

    Take care.
    0
    Gale Hawkins
    PowerClaim.com
    Member
    Member
    Posts:386


    --
    05/15/2007 8:00 PM
    While I meant to get back here before now below is a partial example of XML code that third party claim management system (CMS) vendors can use to export from their software directly to PowerClaim XML. As other software vendors open up their claims data structure and openly define it then you will see CMS packages that permits live claims files to be sent to and received from all brands of estimating software packages. The nice part about working with an XML Open Standard is there are known field names as well as their Type and Length.
     
    While this may sound complex it really is not and does not require renaming of fields of the different CMS and estimating software packages. While we used < PolicyNo > to name the Policy Number field another vendor could have used < policyNo > or < PolicyNumber > or < policyNumber > for example. By mapping in the export/import stage to a known field name, type and length the difference in tag names can be addressed.
     
    As more join the XML Open Standard group the objective will be for a true XML Open Standard to appear so there is no mapping required to exchange live claims data between different software packages. Ideally this should happen before the fact as it as happened in other industries but due to perhaps mainly financial considerations by some software vendors and the lack of interest in managing claims handling cost at the carrier level it has not happen in property claims so the Open Standard is evolving over time from the bottom up instead of from top down.
     
    Thankfully this will lessen the need for carrier/IA vendors to require specific brands of estimating software and they can still get what they want and need.
     
     
    XML Schema for PowerClaim XML Claim Setup Data
     
     
    The following two pages are an example of a PowerClaim XML claim saved in xml format. The notes in the blue text describe the information contained in the claim setup fields and in the contact fields. The data type, the maximum length, and / or the possible values are also included in the notes.
     
    There are eleven different types of contacts that can be saved in each PowerClaim XML claim. The type of contact is specified by one of these numbers:
     
    Number
    Contact Type
    1
    Insured
    2
    Loss Address
    3
    Contact
    4
    Claimant
    5
    Carrier
    6
    Agency
    7
    Adjusting Company
    8
    Adjuster
    9
    Contractor
    10
    Mortgagee 1
    11
    Mortgagee 2
     
     
     
     
    < Claims >                   beginning of the xml                                         
    < Claim >                     each claim will have a claim tag
      < ClaimData >                        claim setup information and general claim information
        < ID >3< /ID >                                                               
        < FileNumber >File 123< /FileNumber >                  file number (text, 50)
        < ClaimNumber >Claim 123< /ClaimNumber >                    claim number (text, 50)
        < PolicyNo >Number 12< /PolicyNo >                                policy number (text, 50)
        < PolicyType >Type < /PolicyType >                                   policy type (text, 30)
        < EffectiveDate >05/07/2007< /EffectiveDate >                    policy effective date (date/time)
        < ExpirationDate >05/07/2008< /ExpirationDate >  policy expiration date    (date/time)
        < Coinsurance >80< /Coinsurance >                         policy coinsurance (number, integer)
        < FilingDeadline >180< /FilingDeadline >            supplement filing deadline (number, integer)
        < InsuredInterest >Insured’s Interest< /InsuredInterest >    insured’s interest (text, 50)
        < PolicyChanges >Changes to Policy< /PolicyChanges >   changes to policy (text, 200)
        < ReportDate / >                                                     
        < NextReport >05/01/2007< /NextReport >                        next report date (date/time)
        < Status >Closed< /Status >                                                 claim status (text, 20)
        < DateAssigned >05/02/2007< /DateAssigned >                  date assigned (date/time)
        < DateContacted >05/03/2007< /DateContacted > date contacted (date/time)
        < DateInspected >05/04/2007< /DateInspected >                date inspected (date/time)
        < DateClosed >05/05/2007< /DateClosed >                        date closed (date/time)
        < LossDate >05/06/2007< /LossDate >                               loss date (date/time)
        < LossTime >12:45 AM< /LossTime >                                 loss time (date/time)
        < LossCause >Loss Cause< /LossCause >               loss cause (text, 50)
        < CATNo >CAT #123< /CATNo >                                    catastrophe number (text, 50)
        < LossComments >Loss Comments< /LossComments >       loss comments (memo, 255)
        < LossSameAsMailing >True< /LossSameAsMailing > loss address same as insured (true / false)
        < RC >0< /RC >
        < DEP >0< /DEP >
        < RDEP >0< /RDEP >
        < ACV >0< /ACV >
        < RCClaim >0< /RCClaim >
        < ACVClaim >0< /ACVClaim >
        < Holdback >0< /Holdback >
        < TotalLoss >0< /TotalLoss >
        < Reserves >0< /Reserves >
        < TotalInsBLDG >0< /TotalInsBLDG >
        < TotalInsCNTS >0< /TotalInsCNTS >
        < PropertyRC >0< /PropertyRC >
        < PropertyACV >0< /PropertyACV >
        < CoversheetComment / >
        < EstimateDisclaimer / >
        < AdditionalPaymentAgreement / >
        < DefaultDepreciation >10< /DefaultDepreciation >
        < BlanketDed >False< /BlanketDed >
        < BlanketDedAmnt >0< /BlanketDedAmnt >
    < /ClaimData>
    < Settings / >               
    < Coverages / >
    < Photos / >
    < Diagrams / >
    < Diary / >
    < Documents / >
    < Invoices / >
    < ShortForm / >
    < Contacts >                            contact information      
      < Contact >                            there are 11 contacts, but only one is needed for this example   
         < City >City< /City >                                                          city (text, 40)
         < CompanyName >Adjuster Company< /CompanyName > company name (text, 60)
         < ContactTypeID >8< /ContactTypeID >                            specifies the type of contact (1 - 11)
         < Country / >                                                                      country (text, 50)
         < County / >                                                                       county (text, 50)
         < Email >email@address.com< /Email >                              email address (text, 100)
         < FAX >(234) 567-8999< /FAX >                                     fax number (text, 25)
         < FirstName >Adjuster< /FirstName >                                first name (text, 40)
         < ID >404< /ID >              
         < LastName >Name< /LastName >                                    last name (text 40)
         < Line1 >123 Adjuster Lane< /Line1 >                                address line 1 (text, 60)
         < Line2 / >                                                                          address line 2 (text, 60)
         < Line3 / >                                                                          address line 3 (text, 60)
         < Line4 / >                                                                          address line 4 (text, 60)
         < MiddleName / >                                                               middle name (text, 40)
         < NickName / >                                                                  nick name (text, 40)
         < Phone1 >(123) 456-7898< /Phone1 >                             phone 1 number (text, 25)
         < Phone1Type >Office< /Phone1Type >                             phone 1 type (text, 15)
         < Phone2 >(123) 456-7777< /Phone2 >                             phone 2 number (text, 25)
         < Phone2Type >Home< /Phone2Type >                             phone 2 type (text, 15)
         < PostalCode >12345< /PostalCode >                                postal code (text, 10)
         < Prefix / >                                                              name prefix (text, 4)
         < StateProvince >KY< /StateProvince >                             state or province (text, 20)
         < Suffix / >                                                              name suffix (text, 10)
         < TaxID >taxID 12345< /TaxID >                         tax id (text, 50)
         < Title / >                                                                            name title (text, 40)
         < UniqueName / >                                      
     < /Contact >
    < /Contacts >
    < CaptionedReports / >
    < NFIPForms / >
    < PILRForm / >
    < TWIAForm / >
    < /Claim >                                end of this claim
    < /Claims >                              end of the xml
    0
    You are not authorized to post a reply.


    These Forums are dedicated to discussion of Claims Adjusting.

     

    For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines: 

    • No Advertising. 
    • No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or others to respond. Any post that looks like trolling / poaching will be removed.
    • No Flaming or Trolling.
    • No Profanity, Racism, or Prejudice.
    • Terms of Use Apply

      Site Moderators have the final word on approving / removing a thread or post or comment.