2023-01-09 Referral Committee Meeting Minutes

Public Page

Date

Dec 5, 2022

Agenda

• Antitrust

• Meeting minute Review

• Welcome/Networking

• Review Action Items

• Review Project Plan

• Review topics emailed from the committee.

• Review http://cieca.com message workflows

Meeting Minutes

• Antitrust Accepted

• Meeting Minutes Reviewed/Accepted

• Action Items:

  • Research how an EV is identified, do we need a flag, or do we use code list?

    • Yes, we have a code list today that identifies an EV vehicle.

    • There is a new committee getting kicked off first quarter of 2023 for EV, we will leave the data changes to EV to this committee.

    • The question of how we make sure a referral goes to a body shop that is certified and able to work on an EV, this would be the location service and we can look into that.

  • Is Aluminum repairs in the BMS

    • Yes, it's a code list and there's a lot of other code lists there. I didn't look through all of those, but I think that's something that we might wanna look at to see what all we have or what all. If we wanna look and say this is the kind of specialty things that we know that people need to that we need to know for an assignment to make sure it goes to the correct place. If we look at those and if we identify those. And I could take them back to the list and see what's missing that way we're not.

  • Is unrelated Prior damage in the BMS

    • It is under File Attachment where prior damage can be added.

  • Privacy Field/Flag stating that customer has agreed for data to be shared?

    • This is not part of the BMS, JSON has a privacy flag for PII data but does not have a user approval. This needs to be evaluated to determine if it is needed. https://cieca.atlassian.net/browse/R231-43

  • Everyone send Use Cases and current referral diagrams to Paulette and she will start working on combining the flows and use cases to present at the next meeting.

    • No Use Cases were received.

• Meeting minutes

  • Who is sending the initial assignment/referral?

    • Could be a car through telematics, could be insurance, could be third party, could be owner through an app, we have a number of actors that can send a referral or assignment.

  • Do we have automated assignment/referral?

    • Avery high level workflow was generated with last meeting minutes. If vehicle is in an accident, the first thing is does the vehicle have telematics? If not, then it's going to go to the first notice of loss workflow that we have today. If it does have telematics, then we'll see if the vehicle does the process damage. I didn't know what to call that, but if it's figuring out what it needs to do and who it needs to, if it doesn't have that, if it just has a simple well, not simple.

    • That if it has the like on star telematics or that third party built into it Apple whoever it may be, then the vehicle is just going to contact that third party right and say that the vehicle notifies that their party of the vehicle accident and then in that workflow the third party would reach out to the owner of the vehicle to find out if it EMS is needed total loss and if the car is drivable type of thing. And then if the vehicle does it then it would go ahead and identify that it needs an EMS that you know there's enough damage to the car.

    • When EMS isn't being notified then it would look to see if it was a total loss and if it is then it could send that information to the toe on company and the rental company. If the car was drivable referral, then it could if it was drivable, non-drivable, then it would send it to the repair facility the tow so that it could get to the salvage and then it would send it to the rental. And if it was drivable, it may just send something to receive the referral for an estimate and drop off or it can and send it to the rental company. So those are just like the flows that we picked up on last time.

    • At this time, nothing happens from the car without the Owner’s permission. For example, OnStar does not auto send anything except EMS, but does not handle tow or rental. If the person asks the OnStar rep to contact a tow, they may do that for them, but it is just sending a tow to the accident.

    • It is possible the driver of the vehicle is not the owner of the vehicle, it could be an employee, it could be a minor child, friend, when someone is talking to OnStar, they may not have permission to say what happens to the car.

    • When you sign up for an app or for third party or even the OEM apps, you may give permission to data, but it is still necessary to ask at the time of the accident if that data can be shared, it should not be assumed.

  • The Workflow that was created, we need to add the consumer/Owner but it needs to be simplistic.

  • Come up with like a list of, say, 5 or 10 critical elements that we could specifically list to a customer to say, look, these are the things that we're suggesting that we share to third party whatever be a toll vendor insurance company to help move you forward in the claims process and give them the opportunity to decide whether that Group of information is something that they're willing to share or not. Because if somebody sent me, you know, can say that same example, do you opt in for this? You know, data exchange? Well, if I don't have any, you know, what is it? What am I sharing? But if I had a quick list of, you know, a few bullets of things that are critical information that could be shared now from the vehicle to help move the claim process forward, I'd be much more willing to say yes to that.

  • What is CIECA’s role?

    • Enterprise has been asked by every single OEM to accept this referral saying hey, my customer got in an accident. I'm not paying for it, but from a customer service standpoint, I want to get the customer moving. I want to get their car, you know, help them get the car to the shop, help them get a rental car.

    • The reason why I seek it gets involved is so that I as the rental company, don't have to have 20 different integrations with 20 different OEMs. So CIECA is role is to have a standard.

    • On how that data can be sent, but to your point, John, we will have an API set that says these are the data elements that can come over, but if you choose to send ten another OEM chooses to send 15 another OEM chooses to send five. That is a business decision between the OEM and the vendor but seek is there to create that standard so.

    • I don't have to have 25 different integrations. I have one integration that may have different data elements, but it's just one API versus.

    • Different APIs.

  • Better Description of Referral and how it will change to an assignment is needed.

Great Meeting Everyone, Talk to you in 2 weeks.

Up Next

• Antitrust

• Meeting minute Review

• Welcome/Networking

• Review Kim’s example of Referral vs Assignment

Action items

Decisions

Reference Material:

Participants

• @Paulette Reed

• Kim DeVallance Caron

• Stacey Phillips

• David McCreight

• Jason Kurutz

• James Palmer

• John Eck

• Don Porter

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. Referral Committee Home