Question

We are using .net framework 4.0 for our application.

I will give a brief idea of what I am trying to do here. My application needs to submit requests to most of the US States for medicaid eligibilty.

The user fills out a eligibility request form 270 with a verification state field. Based on the verification state field we decide which state to send it to. We submit a request 270 to states by doing a Web HTTP POST or ftp. This depends on the state. We also have their username, pwds for the respective states. We need these while making the HTTP Request.Each state has its own URL to be submitted to.

Question: What would be a good place to store all these URL's. App.config might get too clumsy. or database?

How would I do a webservice or WCF for this specific application. This is going to be my first Web service or WCF(if I need one here).

Thank u

Was it helpful?

Solution

I'd think a database would be best. Partly because it will probably grow very quickly. With CAQH CORE http://www.caqh.org/pdf/CLEAN5010/270-v5010.pdf being mandated by the Administration Simplification Act, you might be able to have one web service that does most of them, but Medicaid varies by state, and usually has a budget low enough that you can't count on them being up to date with the standards. So, you may want the database to tell you two things: which URL to send it to, and which web service to send it through. That number will probably grow as the project progresses.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top