eData Information Web Meeting

eData Information Web MeetingeData Information Web Meeting

Pending File Consumability Pending File Consumability Evaluation ResultsEvaluation Results

June 27, 2012June 27, 2012

Pending File Pending File ConsumabilityConsumability

Governance Structure (0a)

Implementation Governance (1)

Technology (2)

Tooling Development (2a)

Same-time Exchange (2b)

Development Process (1b)

Process Governance (0)

Review, Maintain Plan (0c)

Recruitment (0b)

Maintenance

Maintenance

Maintenance

Maintenence

Mediation Services (1c)

d

Data Agreement Templates (1d)

RFP process (1a)

a

Carrier-Distributor Data Related Initiatives

Pending (3)

Batch Assessment (3a) Implementation

Same-time Assessment (3b) Implementation

Inforce (5)Inforce Service Assmnt (5a) Implementation

Age/Amt Tables (7)Data Requirements (7a) Implementation

Commission (6)Data Assessment (6a) Implementation

Electronic Stmt Delivery (6b) Implementation

d

c

d

d

d

e

e

c

Reconcil, Mining Assmnt (5b) Implementation

Urgent Notifications (4)Assessment (4a) Implementation

c d

d

Easier Validation of E&O Coverage (9)Company Engagement,E&O Carriers (9a)

Data Requirements (9c)

Implementation

Problem Assessment (9b)

Technology Rqmts (9d)

Electronic Policy Delivery (10)Company EngagementLegal/Compliance Group (10a)

Technology Requirements (10c)

Implementation

Delivery Requirements (compliance) (10b)c

dData Requirements (10d)

Paramed (8)Cmp Eng (8a) Improvement Analysis (8b)

Data Requirements (8c) Implementation

New Business Process Improvements involving third parties

ReqCodes standardized e

Same-time technology in place

Tooling in place d

RFP process commencesa

Proof of Concept started

c

b

d

cb

b

• First project as part of First project as part of eData planeData plan

• Addressing issues Addressing issues with pending feeds in with pending feeds in place todayplace today Quality of informationQuality of information Timeliness of Timeliness of

informationinformation

ApproachApproach• One on one sessions with each partyOne on one sessions with each party

Review issues from each individual perspectiveReview issues from each individual perspective• Categorize issues based on where they may be happening (e.g. Categorize issues based on where they may be happening (e.g.

carrier, vendor, business interpretation)carrier, vendor, business interpretation)• Group issues by company and communicate specific concernsGroup issues by company and communicate specific concerns

Carrier List based on distributorCarrier List based on distributor Vendor List based on distributorVendor List based on distributor

• Face to face meeting held to discuss common issues as an eData Face to face meeting held to discuss common issues as an eData opportunityopportunity

Hosted by Manulife, open to all premiere membersHosted by Manulife, open to all premiere members Tie back to company specific concern should be knownTie back to company specific concern should be known

• Agree on resolutionAgree on resolution• Gain commitment to make adjustments as neededGain commitment to make adjustments as needed

Participants to DateParticipants to DateOne on One Review SessionsOne on One Review Sessions

Carriers:Carriers:• ManulifeManulife• Sun LifeSun Life• Canada LifeCanada Life• Industrial AllianceIndustrial Alliance• TransamericaTransamerica• RBCRBC

Solution Providers:Solution Providers:• VirtgateVirtgate• WinfundWinfund• Blue SunBlue Sun• Univeris Univeris • AgemanAgeman

Distributors:Distributors:• HubHub• DundeeDundee• PPIPPI• Financial HorizonsFinancial Horizons• Investors GroupInvestors Group• Bridgeforce Bridgeforce • CredentialCredential• IDC WorldsourceIDC Worldsource

Sessions can still be scheduled.Please contact Tana Sabatino for more information.

Distributor ViewDistributor View

• Reviewed role of case managerReviewed role of case manager WorkflowWorkflow

• Number of cases handledNumber of cases handled• How workload is managedHow workload is managed• What triggers a case to be looked atWhat triggers a case to be looked at

Issues experienced with data in current feedsIssues experienced with data in current feeds• What causes reconciliation issuesWhat causes reconciliation issues• What requires manual processingWhat requires manual processing• What requires going to website for reviewWhat requires going to website for review

Understanding the Understanding the Case ManagerCase Manager

Discovery:Discovery:

The case manager is the true customer The case manager is the true customer

of the pendingof the pending information.information.

A typical day of the case manager A typical day of the case manager

1.1. Look at the follow-ups for todayLook at the follow-ups for today These are automated task entries that These are automated task entries that

trigger the case manager to follow up on the trigger the case manager to follow up on the casecase

2.2. Handle email communications of new Handle email communications of new requirementsrequirements

A typical day of the case managerA typical day of the case manager

• Follow ups generated by:Follow ups generated by:1.1. Internal service standardsInternal service standards

• Example standards:Example standards: Initial 14 days; subsequent 7-10 daysInitial 14 days; subsequent 7-10 days Every 7 daysEvery 7 days Every 7-10 days Every 7-10 days Every 4-5 days Every 4-5 days

• They manually set a follow up task in the future based on They manually set a follow up task in the future based on these standards and it will trigger an event when it comes these standards and it will trigger an event when it comes due due

2.2. Requirements being updated in the feedRequirements being updated in the feed• This depends if the vendor system has this functionality This depends if the vendor system has this functionality

AND if it is activatedAND if it is activated• If utilized, cases that had an update to a requirement will If utilized, cases that had an update to a requirement will

also appear in their task list for the dayalso appear in their task list for the day


• How many follow ups?How many follow ups? About 40 cases today in follow up. About 40 cases today in follow up.

• 300-400 pending cases total being managed.300-400 pending cases total being managed. About 30 cases today in follow up. About 30 cases today in follow up.

• 200-300 pending cases total being managed.200-300 pending cases total being managed. 200 pending cases total being managed.200 pending cases total being managed. 52 follow ups for today.52 follow ups for today.


• Each item flagged as a follow up is acted onEach item flagged as a follow up is acted on Case manager goes to the case and then to the requirements screen to Case manager goes to the case and then to the requirements screen to

see what has happenedsee what has happened• Some case managers go to carrier website first as their preferenceSome case managers go to carrier website first as their preference• Not all carriers sending feeds, so website is only source in this caseNot all carriers sending feeds, so website is only source in this case

Carrier website checked for data not availableCarrier website checked for data not available• ““Other” requirementsOther” requirements• Additional DetailsAdditional Details• Underwriter notesUnderwriter notes• EventsEvents• DecisionsDecisions• Case StatusCase Status

While in feed, many distributors do not update this automaticallyWhile in feed, many distributors do not update this automatically Carrier website checked for missing requirementsCarrier website checked for missing requirements

• Manual requirement comparison conductedManual requirement comparison conducted Carrier website checked 100% of the time for cases being reviewed for Carrier website checked 100% of the time for cases being reviewed for

these reasonsthese reasons


• Once case reviewedOnce case reviewed Agent provided an update if that is their Agent provided an update if that is their

processprocess• E.g. Case manager emails themE.g. Case manager emails them

Follow up flag reset on agency management Follow up flag reset on agency management system based on service standardsystem based on service standard


• Once follow ups are completed the case is Once follow ups are completed the case is not reviewed again unless there is activitynot reviewed again unless there is activity It’s time again based on service standardsIt’s time again based on service standards A requirement was updated (or added) via A requirement was updated (or added) via

feedfeed• If they use a vendor systemIf they use a vendor system process that triggers a process that triggers a

follow upfollow up Notification of new requirement or event, e.g. Notification of new requirement or event, e.g.

status changestatus change


• Notification of new requirements and eventsNotification of new requirements and events These come in via electronically to the distributorThese come in via electronically to the distributor Distributors are notified of most new requirements Distributors are notified of most new requirements

and events in some electronic formand events in some electronic form Method of obtaining them varies by carrierMethod of obtaining them varies by carrier

• Carrier secure email system (requires log-in)Carrier secure email system (requires log-in)• Email with detailsEmail with details

May or may not be emailed to agent directly; depends on May or may not be emailed to agent directly; depends on carriercarrier

• Notification of emailNotification of email Requires log into carrier email system to see what it isRequires log into carrier email system to see what it is

Sample case manager gets 80+ of these notifications Sample case manager gets 80+ of these notifications daily daily


• Notification of new requirementsNotification of new requirements Case manager adds the correspondence to the Case manager adds the correspondence to the

case in the system (copy and paste)case in the system (copy and paste)• Adds it as a note, location depends on systemAdds it as a note, location depends on system

Case manager may check to see if requirement Case manager may check to see if requirement already received in feedalready received in feed

• Not all doNot all do Case manager may add them as a new Case manager may add them as a new

requirement and include the detailsrequirement and include the details• Even if requirement there, they may opt to add it Even if requirement there, they may opt to add it

again separately to provide details that were not in again separately to provide details that were not in the feed anywaythe feed anyway

When case comes up for follow up, they will When case comes up for follow up, they will sometimes check to see if the requirement later sometimes check to see if the requirement later appeared in the feedappeared in the feed

• If so, some opt to close the one they added; others If so, some opt to close the one they added; others leave them both openleave them both open

About the Data

What they see

Data Content IssuesData Content Issues

• Case status interpretation and communicationCase status interpretation and communication What it means for a case to be ‘done’ varies What it means for a case to be ‘done’ varies

• Between distributor and carrierBetween distributor and carrier• Between different distributorsBetween different distributors

Unclear on definitionsUnclear on definitions• Approved, issued, inforceApproved, issued, inforce

Need to ensure all relevant status changes are Need to ensure all relevant status changes are understood and communicated to allow distributors to understood and communicated to allow distributors to manage their businessmanage their business

UnderwritingDecision

Made

PolicyIssued

PolicyPages

Delivered

Issue RqmtsReceived Policy placed

inforce

Data Content ResolutionsData Content Resolutions

• Case status interpretation and communicationCase status interpretation and communication Distributors notified of major milestones of policy status changes Distributors notified of major milestones of policy status changes

as soon as possible. as soon as possible. • Examples include case approval, case approved as substandard, Examples include case approval, case approved as substandard,

case declined. case declined. Acknowledge thatAcknowledge that workflow of carrier may not be in sync with the workflow of carrier may not be in sync with the

status changes that are trackedstatus changes that are tracked Agree on standard list of ACORD codes to communicate the Agree on standard list of ACORD codes to communicate the

milestones – and agree on what they meanmilestones – and agree on what they mean• Distributors need to agree on using the same breakdown else the Distributors need to agree on using the same breakdown else the

information will still be lost in translation information will still be lost in translation • Vendor systems must support the same listVendor systems must support the same list

• Next step:Next step: complete a cross mapping of company policy complete a cross mapping of company policy status codes for review at industry level. This includes status codes for review at industry level. This includes both carrier and distributor system codes.both carrier and distributor system codes.


• Identification of requirements Identification of requirements Unclear what requirement codes are being usedUnclear what requirement codes are being used Same requirement uses different requirement code Same requirement uses different requirement code

between carriersbetween carriers Different requirement code used to communicate Different requirement code used to communicate

same requirement between carrierssame requirement between carriers Different requirements mapped to a single Different requirements mapped to a single

requirement code within a carrier making items requirement code within a carrier making items appear as duplicates when they are notappear as duplicates when they are not

Requirements incorrectly mapped to CITS codesRequirements incorrectly mapped to CITS codes Too many requirements mapped to ‘other’, ‘additional’ Too many requirements mapped to ‘other’, ‘additional’

information information


Use of Requirement CodesUse of Requirement Codes• Next Step:Next Step: Provide a cross industry mapping of Provide a cross industry mapping of

all requirement codes in use today in order to all requirement codes in use today in order to ensure they are all supported. This effort will ensure they are all supported. This effort will also result in recommendations to add new also result in recommendations to add new codes, remove the use of certain codes, and codes, remove the use of certain codes, and remap existing codes. remap existing codes. Follow up:Follow up: All trading partners should send their list All trading partners should send their list

of current requirement codes/mappings.of current requirement codes/mappings.


• Missing requirementsMissing requirements Not all requirements are being sent from carrier that Not all requirements are being sent from carrier that

appear on websiteappear on website• Doesn’t treat what distributors view as equal requirements Doesn’t treat what distributors view as equal requirements

equally, so not all sentequally, so not all sent Event notifications top this listEvent notifications top this list

• e.g. case status changes, underwriting decisions e.g. case status changes, underwriting decisions • Intentional screening done at carrier sideIntentional screening done at carrier side

Carrier decides what they think distributor wants to seeCarrier decides what they think distributor wants to see• E.g. screen out issue requirementsE.g. screen out issue requirements

Not all requirements being displayed in vendor Not all requirements being displayed in vendor agency management system agency management system

• Only displays requirements with known codes Only displays requirements with known codes • Intentional screening done at vendor sideIntentional screening done at vendor side


Provide All RequirementsProvide All Requirements• Screening out requirements at carrier level is inconsistentScreening out requirements at carrier level is inconsistent

Next Step:Next Step: All carriers should be advised to not screen out particular All carriers should be advised to not screen out particular requirements. Different distributors are interested in seeing different requirements. Different distributors are interested in seeing different things. They should have the option to screen at their discretion. things. They should have the option to screen at their discretion.

Next Step:Next Step: Screening of requirements by vendor system should be Screening of requirements by vendor system should be considered to avoid the complaint of ‘meaningless’ requirements considered to avoid the complaint of ‘meaningless’ requirements appearing in feed, simply because that particular distributor doesn’t care appearing in feed, simply because that particular distributor doesn’t care about it.about it.

• Competitive advantage opportunity of vendorCompetitive advantage opportunity of vendor• Events not actual requirements but are wanted to be treated as such Events not actual requirements but are wanted to be treated as such

Next Step:Next Step: determine which events are provided today and ensure there’s determine which events are provided today and ensure there’s a requirement code available for mappinga requirement code available for mapping

• Emails are sent for requirements that never appear in feedsEmails are sent for requirements that never appear in feeds This relates to the above two pointsThis relates to the above two points Next Step:Next Step: Determine if these 2 items (along with providing details as Determine if these 2 items (along with providing details as

described next slide) closes this gap completelydescribed next slide) closes this gap completely


• Missing details for requirementsMissing details for requirements Free form comments not sent in feed so it is Free form comments not sent in feed so it is

impossible to know what the full requirement impossible to know what the full requirement is without looking at websiteis without looking at website• ““Other”Other”• ““Additional information”Additional information”• ““See insurance company memo”See insurance company memo”• ““Respond to Question # 10”Respond to Question # 10”


Provide complete informationProvide complete information

• Provide additional details in feed itself to Provide additional details in feed itself to level it is available on websitelevel it is available on website Next Step:Next Step: Work with carriers to provide this Work with carriers to provide this

information in the feeds themselves in the information in the feeds themselves in the appropriate free form text strings availableappropriate free form text strings available

Next Step:Next Step: Recommend vendor systems read Recommend vendor systems read both (not just one) text string so that no both (not just one) text string so that no details are inadvertently lost in the conversion details are inadvertently lost in the conversion


• Requirement status interpretation and Requirement status interpretation and communicationcommunication Different status codes selected by different Different status codes selected by different

carriers that mean the same thingcarriers that mean the same thing• e.g. Evaluated versus completede.g. Evaluated versus completed

Vendors not supporting full list of CITS codesVendors not supporting full list of CITS codes• Cancelled, waived not showing in some systemsCancelled, waived not showing in some systems

Deleted requirementsDeleted requirements• No way to know it went awayNo way to know it went away


Provide full support for needed statusesProvide full support for needed statuses

• Next step:Next step: complete a cross mapping of complete a cross mapping of company requirement status codes for company requirement status codes for review at industry level. This includes both review at industry level. This includes both carrier and distributor system codes.carrier and distributor system codes. Follow up:Follow up: All trading partners should send All trading partners should send

their list of current statuses/mappings.their list of current statuses/mappings.

Data Content – Data Content – Next MeetingsNext Meetings

• Requirement code and status mappingRequirement code and status mapping Cross mapping between all companiesCross mapping between all companies To be done by eData project managerTo be done by eData project manager Teleconference scheduled to discuss results, Teleconference scheduled to discuss results,

next stepsnext steps August 13 11:00-1:00pm ETAugust 13 11:00-1:00pm ET

• IN ADVANCE - carriers and vendors to IN ADVANCE - carriers and vendors to provide full requirement code and status provide full requirement code and status mapping for cross industry analysismapping for cross industry analysis

Register: www.cliedis.ca/edatacurrentmeeting.php

Data TimingData Timing

• Focus on notificationsFocus on notifications Has greatest impact on improving workflow of Has greatest impact on improving workflow of

case managercase manager• Case manager does not look at the case unless Case manager does not look at the case unless

they know there is a reason tothey know there is a reason to• Notifications will allow vendor systems to build Notifications will allow vendor systems to build

functionality as desired to trigger case manager of functionality as desired to trigger case manager of activityactivity

• Notifications can replace the manual email process Notifications can replace the manual email process in place todayin place today


• Carrier PerspectiveCarrier Perspective Don’t just tack on more alternatives to get at Don’t just tack on more alternatives to get at

datadata

BatchSametime

Notify Portal

RqRs

Carrier-Distributor Environment with eData - From Business Case

Information presentedas available, close to real time

ClientWebsite

DistributorEnvironment

CarrierEnvironment

eData

Web

Services

Information accessibleas available, close to real time

Pending Case StatusRequest

Response

Inforce ServicingRequestResponse

Urgent NotificationsPoll

Notification

Additional eData services

eData

Web

Services

CITSXML

CITSXML

CITSXML

PendingNightly

InforceWeekly

FTP

CommissionsPeriodic

Additional eData batch feeds

FTPFTP

Batch Processing

For reconciliation, data mining, marketing

Bat

ch F

ile

Del

ive

ry

Bat

ch F

ile

Pro

cess

ing

ALL Pending and Urgent Inforce Notifications

Carrier-Distributor Environment with eData – After Analysis

Information presentedas available, close to real time

ClientWebsite

DistributorEnvironment

CarrierEnvironment

eData

Web

Services

Information accessibleas available, close to real time

Inforce ServicingRequestResponse

PollNotification

Additional eData services

eData

Web

Services

CITSXML

CITSXML

InforceWeekly

FTP

CommissionsPeriodic

Additional eData batch feeds

FTPFTP

Batch Processing

For reconciliation, data mining, marketing

Bat

ch F

ile

Del

ive

ry

Bat

ch F

ile

Pro

cess

ing



• Carrier PerspectiveCarrier Perspective Don’t just tack on more alternatives to get at Don’t just tack on more alternatives to get at

datadata• With this approachWith this approach

request/response not needed for pendingrequest/response not needed for pending

• With this approachWith this approach overnight batch can go away if notifications of changes overnight batch can go away if notifications of changes

are provided throughout the dayare provided throughout the day


• Carrier PerspectiveCarrier Perspective Web Portal approachWeb Portal approach

• Must allow carriers to move toward this with a Must allow carriers to move toward this with a batch interim approachbatch interim approach

• Focus on improving timing, and quality of Focus on improving timing, and quality of information firstinformation first

Standardizing how it is delivered comes laterStandardizing how it is delivered comes later Minimize menu of options / expectations of presentation Minimize menu of options / expectations of presentation

from carrierfrom carrier

Carrier Distributor

Post WebPortal

Load intoDistributor

system

Post Batch CITSXML

PendingMany times

Per day FTP

Option B – More Frequent Batch Delivery

Option A – Web Portal Delivery

PollNotification


NotificationsIdentified

A or B – Distributor experience identical Vendor processing issue

Understanding How FeedsUnderstanding How Feedsare Processedare Processed

Processing FeedsProcessing Feeds

• Feeds come in the morningFeeds come in the morning Service standards varyService standards vary

• But all should be in by 9amBut all should be in by 9am• Days of delivery varyDays of delivery vary

Mon-FriMon-Fri Tues-SatTues-Sat

• Feeds get loadedFeeds get loaded Most have an automated process for loadingMost have an automated process for loading Cases match when they canCases match when they can

The rest are flagged for The rest are flagged for reconciliationreconciliation

Processing FeedsProcessing Feeds• Feed VolumeFeed Volume

Sample from distributor:Sample from distributor:• 1 day snapshot1 day snapshot

930 cases total930 cases total Approx 700 in policies that get feedsApprox 700 in policies that get feeds 190 cases came in on feed (190/700 = 27%)190 cases came in on feed (190/700 = 27%)

• Possible that cases are counted multiple times. Unclear if this stat Possible that cases are counted multiple times. Unclear if this stat is based on requirements; each insured; or policy numbersis based on requirements; each insured; or policy numbers

Sample from carrier:Sample from carrier:• 10 day sampling of select MGAs10 day sampling of select MGAs

Average 737 cases; average 116 in feed (16%)Average 737 cases; average 116 in feed (16%)• 4 day sampling4 day sampling

1258 cases; 168 case average over 4 days (13%)1258 cases; 168 case average over 4 days (13%)• 1 day snapshot1 day snapshot

10890 cases pending; 2139 in feed (20%)10890 cases pending; 2139 in feed (20%)• 4 day sampling of select MGAs4 day sampling of select MGAs

Average 27% Average 27%

Processing FeedsProcessing Feeds• Reconciliation processReconciliation process

What triggers a case for reconciliation depends on the agency What triggers a case for reconciliation depends on the agency management system management system

• Their match criteriaTheir match criteria• Processing for when an exact match is not foundProcessing for when an exact match is not found

Load it in separateLoad it in separate Flag it to see if a match could be foundFlag it to see if a match could be found

Common issues reportedCommon issues reported• Unmatched policy numbers Unmatched policy numbers

New case so didn’t have policy number assigned yet, app was sent to carrier New case so didn’t have policy number assigned yet, app was sent to carrier directly so they didn’t see it yet, number entered with different formatdirectly so they didn’t see it yet, number entered with different format

• Child insureds (treated as insureds in feed, but not by distributor)Child insureds (treated as insureds in feed, but not by distributor)• Name mismatches (with or without middle names)Name mismatches (with or without middle names)• Treatment of joint casesTreatment of joint cases

Reconciliation manualReconciliation manual• Must find possible matching caseMust find possible matching case

Some systems help in identifying possibilitiesSome systems help in identifying possibilities• Must change data to make matchMust change data to make match

Feed reprocessed for those updates once changes madeFeed reprocessed for those updates once changes made

Processing FeedsProcessing Feeds

• Sample reconciliation stats:Sample reconciliation stats: Distributor A:Distributor A:

• Today: 608 cases / 27 were unmatched (4.5%)Today: 608 cases / 27 were unmatched (4.5%) Distributor B:Distributor B:

• Yesterday: 206 cases / 36 were unmatched (17%)Yesterday: 206 cases / 36 were unmatched (17%)• Today: 235 cases / 17 cases were unmatched (7%)Today: 235 cases / 17 cases were unmatched (7%)

• Quote from distributor:Quote from distributor:

“ “ Feed reconciliation is extremely cumbersome and takes a lot Feed reconciliation is extremely cumbersome and takes a lot

of time. It is very problematic. of time. It is very problematic. ”” { because of all the work in match, reprocess, and then still have to { because of all the work in match, reprocess, and then still have to

research requirements }research requirements }

• Not all distributors reconcile casesNot all distributors reconcile cases

Reconciliation IssuesReconciliation Issues

• Reconciliation challenges by typeReconciliation challenges by type• Unmatched policy numbers Unmatched policy numbers

New case so didn’t have policy number assigned yetNew case so didn’t have policy number assigned yet App was sent to carrier directly so they didn’t see it yetApp was sent to carrier directly so they didn’t see it yet Policy number different/changed than what was utilized initiallyPolicy number different/changed than what was utilized initially Number entered with different formatNumber entered with different format

• Child insureds Child insureds treated as insureds in feed, but not by distributortreated as insureds in feed, but not by distributor

• Name mismatches Name mismatches Eg with or without middle namesEg with or without middle names Period or no period in abbreviationPeriod or no period in abbreviation

• Treatment of joint casesTreatment of joint cases Requirements matched at case level and split across insureds correctlyRequirements matched at case level and split across insureds correctly

• Recognize differences in vendor processingRecognize differences in vendor processing Understand areas of competitive advantageUnderstand areas of competitive advantage

Reconcilitation – Next MeetingsReconcilitation – Next Meetings

• Reconciliation process explorationReconciliation process exploration July 18July 18thth 11:00am-1:00pm ET 11:00am-1:00pm ET

• CITS product feed overviewCITS product feed overview Why necessaryWhy necessary Format, expectations for deliveryFormat, expectations for delivery July 26July 26thth 11:00am-12:00pm ET 11:00am-12:00pm ET

Register: www.cliedis.ca/edatacurrentmeeting.php

Communication between Communication between Business PartnersBusiness Partners

Distributor

Carrier Vendor

Communication GapCommunication Gap

• Distributors want CLIEDIS involvement in Distributors want CLIEDIS involvement in closing gapsclosing gaps

““Thank goodness someone is looking at this. Thank goodness someone is looking at this. We know what issues we see but we have no We know what issues we see but we have no

ability to identify whose problem it is.ability to identify whose problem it is.””

{carrier versus vendor versus CITS definition}{carrier versus vendor versus CITS definition}


Knowledge baseKnowledge base• Business users lack knowledge of pending Business users lack knowledge of pending

feedsfeeds Crosses carriers and MGAsCrosses carriers and MGAs Although they know the values shown on their own Although they know the values shown on their own

systems, they typically do not know:systems, they typically do not know:• How the feeds are producedHow the feeds are produced• Where they come fromWhere they come from• How values shown on their systems relate to values shown How values shown on their systems relate to values shown

in the feed and/or values that have been imported into in the feed and/or values that have been imported into consumer systemsconsumer systems


Communication channelCommunication channel• Carriers have no clearly defined mechanism for Carriers have no clearly defined mechanism for

addressing feed problems identified by MGAaddressing feed problems identified by MGA• No clear way for MGAs to identify and report back No clear way for MGAs to identify and report back

problems with the data feeds to the carriers such that the problems with the data feeds to the carriers such that the issue will be investigated, prioritised and readied for issue will be investigated, prioritised and readied for Production. Production.

• Getting technical support on data feeds from carrier Getting technical support on data feeds from carrier organisations is at best ad-hoc and is often based on organisations is at best ad-hoc and is often based on personal relationships between personnel involved in the personal relationships between personnel involved in the CLIEDIS CITS and eData initiatives.CLIEDIS CITS and eData initiatives.

Communication Gap ResolutionsCommunication Gap Resolutions

CLIEDIS GovernanceCLIEDIS Governance• Determine role of CLIEDIS in establishing these Determine role of CLIEDIS in establishing these

connections and providing investigative support connections and providing investigative support to uncover cause of issuesto uncover cause of issues

• Determine role of CLIEDIS providing discovery Determine role of CLIEDIS providing discovery and mediation resourcesand mediation resources

• Determine role of CLIEDIS is encouraging Determine role of CLIEDIS is encouraging companies to convert to standard CITS feed or companies to convert to standard CITS feed or provide a CITS feed and move to new versions provide a CITS feed and move to new versions as neededas needed

Next MeetingsNext Meetings• Reconciliation process explorationReconciliation process exploration

July 18 – 11:00am-1:00pm ETJuly 18 – 11:00am-1:00pm ET• Paramed process overviewParamed process overview

To engage paramed companiesTo engage paramed companies Gauge interest, solicit participationGauge interest, solicit participation July 25July 25th th – 11:00am-12:00pm ET– 11:00am-12:00pm ET

• CITS product feed overviewCITS product feed overview Why necessaryWhy necessary Format, expectations for deliveryFormat, expectations for delivery July 26July 26thth – 11:00am-12:00pm ET – 11:00am-12:00pm ET

• Requirement code and status mappingRequirement code and status mapping Cross mapping between all companiesCross mapping between all companies To be done by eData project managerTo be done by eData project manager August 13August 13thth – 11:00am-1:00pm ET – 11:00am-1:00pm ET

• Face to face Paramed kickoffFace to face Paramed kickoff September 11September 11thth at Transamerica’s offices at Transamerica’s offices

• Face to face 2Face to face 2ndnd and hopefully final pending information session and hopefully final pending information session September 12September 12thth at Transamerica’s offices at Transamerica’s offices

Information: www.cliedis.ca/edatacurrentmeeting.php

Next Meetings

• CLIEDIS Annual Seminar

September 13, 2012 Toronto International Centre (near Toronto

Pearson Airport) Registration to begin in July

QuestionsQuestions

Tana Sabatino, eData Project Manager – [email protected] Parrott, CLIEDIS Executive Director – [email protected]

Documents

eData Information Web Meeting