Report comment

And you'll be aware that the MIB restrict access to MID, AskCUE and Medco with onerous user agreements and the like, but let's have a little thought experiment.

There needs to be a unless z=1 then do not proceed to the next stage string in the system.

You need to link Private Company 1 + Private Company 2 to the CRU in a form where PC1 + PC2 present their data in a consistent manner, so as to allow the claim to proceed to the next stage (the costs of accessing PC1+2 will be limited but scaled up will cost real money, who is to be liable for these costs and who will remit monies and how) while the data sets may be broadly comparable the information will need to be presented in the same way to allow this to be fully integrated A2A unless there is an interace to take PC1 +PC2 data and wash it so as to be able for CRU to accept the registration.

Now the sensible way of doing this is to have LiP portal i/d company PC1 +PC2 CRU MID, AskCue, Medco LiP all via an integrated A2A system and this would require the data structure to be the same across the 6 sites / systems as the CRU is DWP, and although MID, ASkCUE and Medco are all MIB I doubt that when they designed the dbase structure was built with commonality and perhaps even using different types of dbase, packages or even a different language.