Thekob
commented
11 years ago I agree with the Microsoft aspect. I'd prefer not to use it but like you said that can be easier to market and since the UI is still iOS then i think the product will be fine. As that is mostly over my head i'll let you handle that as you see fit.
I'm working on following the NEMSIS requirements for the ePCR based off national standards. I have a shortened list of data fields for the pcr and will get you a rough layout shortly here. The biggest thing I noticed with the "current epcr" is it is incredibly redundant. There's really no reason the CAD can't store or at least auto populate many of the fields i.e. mileage, transport dest/mode, times.
Another thing to explore is a bluetooth link to upload ecg info from various monitors. I think that would expand the hospital clients to all er's not just the base/trauma fac.
So I will design this ePCR solution as a Model View Controller. Now, we have to discuss the technologies that we will use. Marshalling the transctions between the front end and the back end will be handled with JSON or XML as is the current standard. With a flexible RESTful API our client can be easily ported to any platform desired. Both a Ubuntu - Apache, Rails with Mongrel Clusters with any flavor of database or Microsoft ASP .NET with SQL Server will work, and as much as I hate to say it, using MS is probably the safest for customer IT departments. It is actually a pretty slick solution, and I have interfaced many an OSX application with with ASP .NET based API's and it is really easy. Also much of the security is built in, granted it would not be as secure, it seems to be an industry standard so... if it's good enough for them. Plus, since it is .NET we can push much of the security off on the customer.
I am willing to throw down on buying and building a nice Windows 7 Server machine to uses as a Testing/Developing machine, and all the required software. Any thoughts???