anonymously. in the days after the launch qssi worked around the clock to enhance the tool to meet this unexpected demand. as i understand it, this has largely succeeded. by october 8, even at high levels of registration, the eidm tool was processing those volumes at error rates close to displeasure. the eidm tool continues to keep pace with demand and at cms s request we re working with other vendors to plan for higher levels of peak activity. finally, qssi was one of several contractors used. and our testing role we identified errors in code that was provided to us by others. in this function, we reported back the results to cms and the relevant contractor who in tumpb was responsible for fixing coding errors or making any necessary changes. to conclude, the data services hub has performed well.