What to do and when?

• Obtain a list of supported EDI messages from your Engagement Partner (Refer to Velonetic’s list of supported EDI customisations in Sep to see which ones will be supported).
• Complete assessment of all EDI messages to identify all non-standard / customised messages (including source system and teams supporting queries). 
• Engage vendors as required to understand their plans to support message changes within phase one timelines
• For non-supported EDI customisations, map the full as-is data flow and complete an impact assessment.
• The critical issue will be how to handle any customised EDI messages that will no longer be supported. 

Should you have any customised EDI messages that won’t be supported, you need to undertake the following steps:

• Define EDI change approach for different messages.

• Complete process, people and technology changes to support impacted data flows and processes.

After which you have two options to consider to resolve the situation:

Option 1 (Preferred): Engaging with your system vendors to make a change to enable them to accept the new messages. This may be a non-trivial change and potentially require major version upgrades. Remember to include internal and external vendors for your PAS, CAS and any other systems that receive EDI messages

Option 2:
Creating or acquiring an EDI conversion tool to convert standard messages into your customised format prior to ingestion. This is potentially a complex change that will require specialist knowledge of EDI messages. 

You should let your Engagement Partner know immediately if your organisation is not going to be able to enact one of these options by the end of Mar 2024, in time for market self-testing.

• Using the EDI message catalogue created above, identify how all data is collected and submitted currently via EDI, Writeback, CWT and DRI.
• Understand where the connection and authentication configuration is and how to change it.
• Identify the downstream data flows in order to validate that they are not impacted by the gateway changes.

• Reconfigure your internal systems to be able to connect to the new end-point URL.

• Match the list of no longer available portals to the teams that use them. Remember to include internal and external teams, e.g., BPO providers, third-party administrators and delegated claims authorities.
   
• Document the current business processes, IT systems used, and the data flows around each of these.
   
• Map the new processes. If you’re looking to adopt phase two, be mindful of considering longer-term target processes and commonalities and efficiencies that you can gain.
   
• Create new work guides for all internal and external teams.

• Complete training needs analysis and identify the target audiences
• Assign resources and complete portal and process training
• Arrange internal demos of the new portals and functionality to the affected teams – detail on these demos is to be confirmed.
• Get new credentials for the new portals.

• Review the list of reports once published and check which ones of them you receive by email today.
   
• The reports will continue to exist but will require a change to ways of working, as they will require self-service extraction from Qliksense.
   
• Understand current business processes and data flows.

• Assign resources and train them on the process to extract the necessary reports by self-service in Qliksense and feed them to the right processes and systems downstream.
• Consider how many resources you will need and what departments they will need to be part of.

• Direct Settlement is a new method of settlement for both premiums and claims that will be introduced in phase one. When used for claims, Direct Settlement will allow market participants to pay anyone involved in the claims process, including experts and third-party fee collectors.

• Consider if you would like to adopt Direct Settlement and when.
   
• Once detail is released about onboarding, get in touch with Velonetic or your Engagement Partner to organise onboarding and training.