Page 11 - Data Services Hub News Today : Breaking News, Live Updates & Top Stories | Vimarsana

The data services hub has performed well since the marketplace's launch. on october 1, the data services hub successfully processed more than 178,000 transactions. and it has processed millions more since. when occasional discreet bugs in the data services hub were identified, we promptly corrected them. in addition to the data services hub, qqsi also developed the eidm. a registration and access management tool used as one part of the federal marketplace's registration system. the edim tool helps the marketplace create user accounts and is being used successfully currently in at least two oth...

A large and complex project that was the subject of much interest in qssi's work for the marketplace prior to the launch. simply put, the data services hub is a pipeline. it transfers data routing queries and responses between the given marketplace and various trusted data sources. specifically, a consumer interested in purchasing health insurance goes to the marketplace's web portal to fill out enrollment forms and select a plan. the consumer provides the marketplace with information, such as citizenship, which must be verified. the data services hub directs queries from the marketplace to va...

Breakdown. that's even evident when asking very, very simple questions about the testing of this product before it went online. listen. >> that the system -- that our portion of the system, the cgi was responsible for, that our functionality worked. >> and it didn't. >> yes. >> it did not in the end result, correct? >> when it became part of integrated end-to-end system. >> you knew it was going to be integrated. there are many subcontractors than wasn't a surprise. do you have something to say about the testing? >> let me be clear about our role in testing. our work, the data services hub, te...

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

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 functio...