This project is read-only.

Party Resource

Topics: Resources
Mar 5, 2016 at 6:56 PM
Edited Mar 12, 2016 at 1:32 AM
To kick off the party discussion we are thinking of combining MiscParty|GeneralParty|ClaimsParty|AdjusterParty into one party resource. Please post any sample party XML's here.
Jun 16, 2016 at 2:34 AM
Party Definition: all organizations and persons

Aggregates that would fit under that definition.

  • Producer
  • InsuredOrPrincipal
  • AddititionalInterest
  • Driver
  • Pilot
  • ClaimsParty
  • AdjusterParty
  • The MiscParty aggregate tends to be used in specific instances to capture some personal/business info. But wouldn't be needed with a generic party aggregate.

Entities that Fit

NotifySender and NotifyReceiver Both fit the definition but are both text aggregates.

Common In all

  • ItemIdInfo
  • GeneralPartyInfo

New Party Aggregate

  1. Have GeneralPartyInfo_Type be turned into a PartyInfo Group that would be in both GeneralPartyInfo and Party__
    1. The reason for this is because it really describes Party and all of the party types have it
  2. Question: To include Driver or not that is the question. I know Carriers who have created a Party but leave drivers separate.
    1. For putting Driver in Party: It technically is a person and therefore a party.
    2. For leaving Driver alone:
      It would be compatible with previous driver
      A driver may not be a person the driver of the future may be a thing (Car)
      NOTE: Not a point but if we left driver alone the driver aggregate should collapse PersonalDriverInfo and CommercialDriverInfo?
  3. Question: Should we combine all the Info Aggregates in the new Party object because is there a need to group them in an aggregate? If we needed to group them for documentation we could group them with a group.
  4. Create PartyTypeCd To define what type of party it is.
    1. Producer
    2. Pilot
    3. Driver
    4. AdditionalInterest
    5. ClaimsParty
  5. Question: What should we do with PersonInfo it is in DriverInfo and PilotInfo and ClaimsParty
<Party id ="" SourceSystemRef="" AuthorizedRepRef="" EmployerRef="">
     <PartyTypeCd/><!-- NEW Code List for Type of Party -->
Jamie had said from a previous post he had success collapsing the following aggregates into a simple Party object


The XML below demonstrates how the above aggregates can be collapsed into a reusable Party:
    <Party> <!-- Underwriter -->
    <Party> <!-- Producer -->
    <Party> <!-- InsuredOrPrincipal -->
    <Party> <!-- AdditionalInterest - moved from Policy -->
    <Party> <!-- Driver -->

Jun 20, 2016 at 9:56 PM
This is a little different perspective, but similar, from our codebase:
    <PartyID/> <!-- Person Object ID -->
    <PartyDomainID/> <!-- Person or Organization Indicator-->
        <PersonID/> <!-- Person Instance ID -->
        <Contact/>  <!-- Contact Info Address, Phone, Email, etc -->
            <EmployeeInfoID/> <!-- Employee Information Instance ID -->
            <ObjectID/> <!-- Employee Information Object ID -->
            <PartyID/> <!-- Person Object ID -->
            <AgreementRoleID/> <!-- Role ID for Employee Information -->
        <InterestInfo>  <!-- Additional Interest Sample -->
            <InterestInfoID/> <!-- Interest Information Instance ID (InterestTypeCd in ACORD) -->
            <ObjectID/> <!-- Interest Information Insurable Object ID -->
            <PartyID/> <!-- Person Object ID -->
            <AgreementID/> <!-- Agreement / Policy Object ID -->
            <AgreementRoleID/> <!-- Role ID for Additional Interest Information -->
Jan 10, 2017 at 5:29 PM
Latest updates for v2.2.

We will collapse GeneralPartyInfo into a new Party structure:
  • Name
  • Supplemental Names (Maiden, DBA, etc..)
  • Address
  • Contact (Phone, Email, etc..)
    <CommercialName>Test Business</CommercialName>
        <Addr1>1000 S DEERFIELD AVE</Addr1>
        <City>DEERFIELD BEACH</City>