You can't really do that. Let me explain.

I develop an electronic medical record system specifically designed for hospices. I have extensive experience modelling clinical documents into electronic records. Each type of document has it's own set of required data points. On top of that, each federally issued mandate actually allows for some degree of interpretation, so each vendor may tailor their data collection to the needs of the clinicians and customers (this is a good thing). This allows me to add or remove data points. For example, I generally don't need to document data for pediatrics in hospice work. (OH: Pediatric hospice. Sad panda.)

I already implement changes to follow CMS regulations several times a year -- usually for billing purposes. This doesn't guarantee that when CMS mandated that each nurse's visit a patient received in a billing statement is the same kind of nurse visit that some other software vendor records. We both record a nurse visit in some capacity, but i'm certain that my visit is more relevant for my customers than software for optometrists.

By forcing me to use a mandated format, i would have to (potentially) rewrite my application to fit the data, migrate all of my data into the new format (which may or may not be efficient), fix reports that depend on those data pieces... The list keeps growing. This would require some amount of time (cost) that i would provide directly to my customers (read: price increase for everyone).

Once i do have my data migrated, why would my customers keep using my software? Why would they not just write their own and open source it? It could lower costs, for sure. Just cut out the software cost, right? You could use something like OpenEMR (http://www.oemr.org/)... but that is not suited for my clients. It's suited for a hospital. My clients work with patients in their homes and in various medical facilities (hospitals, nursing homes, long term care facilities, etc). The expression cutting flowers with chainsaw comes to mind. This is not to say that my software is as simple as a pair of scissors, just that the tools are appropriate for the job at hand.

Each software provides it's own data set. Forcing us to use one set of data would be absolute chaos and it would in the end creating a monopoly on the medical software industry. It would reduce innovation not only because of monopolistic tendencies (american broadband, anyone?), but also due to constraints on the data format (you can't change it, now). I prefer to have a choice between Ford and Ferrari. I don't want to just settle for a Toyota Camry simply because it was the last one left standing after regulation legislated everyone into irrelevance. Legislating a data format would undermine every free market principle of our economy -- especially since the data format is an integral part of the software industry. My data format is kind of why my clients pick my software and not G.E. or McKesson or AllScripts or Misys. That, and my support team rocks my customers' faces off daily.

Not only that, but the last time data formats were mandated, look at the fucked up repugnant shit we ended up with:
http://en.wikipedia.org/wiki/HL7
http://en.wikipedia.org/wiki/ASC_X12

It seems like an easy way to have the stories distributed in a fashion guaranteed to come from these guys is to use something like Konspire2B (http://konspire.sourceforge.net/)

It supports sharing of files through "channels" and you are always guaranteed that files received through a particular channel because of public/private key encryption.

Cheers (:^)