Page 2 - Sat Cms News Today : Breaking News, Live Updates & Top Stories | Vimarsana

Have shopped anonymously. as i understand it, this has largely succeeded. by october 8, even at high levels of registration, the eidm tool was processing atterror late close to 0 -- processing atteror rates close to -- processing at error rates close to zero. our testing role, we you arified errors in code that was provided to us by others. in this function we reported back the results to cms and the relevant contractor to in turn was responsible forificking coding errors or making any necessary changes. to conclude, the data services hub has performed well. and after initial scalability

Concerns with testing were shared with cms. >> what was their response when you shared the pitfalls? >> my understanding is they were working on them but i don't know further. depiction from them but we did fully talk about the risks that we saw and we passed those along, all along the way. >> miss spellecy? >> our solution was ready to go. we successfully end to end testing between equifax workforce solutions and cms data hub prior to that date so we did not anticipate any sort of problems with our connections and have not experienced any. >> mr. lau?

Americans losing their existing health plans help underscore why washington should not be running our private health insurance system. the botched rollout is all the more reason the individual mandate penalty should be delayed. average americans deserve a waiver from obama-care, too. it's only fair when the exchanges are such a mess. the companies represented here were in charge of building the federal exchange. but cms was responsible for insuring everything worked together properly. so the question we have to ask ourselves is in light of all the administrations assurances is this -- are they...

But it was not our decision to go live. >> it was not your decision to go live. >> it was cms' decision. it wasn't our decision one way or the other. >> did you ever recommend to delay the date. >> it was not our position to do so. you chose not to share those thoughts with them. >> cms had the ultimate decision for a live or no-go decision. not cgi. we were not in a position we are there to support our clients. it's not our position to tell our client whether they should go live or not go live. >> who at cms were you sharing that information with or those decisions? >> once again, chairman, i...