How To Generate CCDA/CCD XML Documents for MU 2014

Most of the IT service providers in the healthcare space are busy taking steps towards getting Meaningful Use (MU 2014) certified. One of the key certification compliance criteria is the generation of various documents in XML format that adhere strictly to the CCDA or Consolidated Clinical Document Architecture. 

If you are new to these terminologies or the concepts then I recommend you go through these immensely helpful tutorials first:

• The bible of all healthcare industry standards: HL7
• Very nicely explained tutorials (videos) at: healthit.gov
• Another one describing MU 2014 and CCDA (ppt) at: healthit.gov

So, you want to generate CCDA compliant document from your .net code.

But How? 

Well, there are 2 parts to the making of a CCDA document. 

1. Prepare a .net type that mimics the XML. When serialized, this type will give us the XML that we want. Now, there are 3 ways to do this:
• Hand-code the entire .net type(s). This requires in-depth analysis and understanding of the CCDA standard. Also considerable effort is required to develop and maintain the code when the standards change.
• Download the schema XSDs as published by HL7 and then generate the .net type(s) out of it. This can be done by using tools like xsd.exe.
• Use an API that already has such a .net object and exposes it to be used in the code. 
2. Populate this .net type with the relevant data and serialize it to generate an XML out of it.

It is obvious that the API approach sounds the most cost effective and quick. In a later blog post we will evaluate a few APIs for this purpose. 

Book Review: JavaScript: Pocket Reference 3rd Edition

- by 
David Flanagan

ToC

Paperback: 280 pages
Publisher: O'Reilly Media; Third Edition edition (April 25, 2012)

ISBN-10: 1449316859 | ISBN-13: 978-1449316853

This is not a javascript pocket reference. It's a guide and an excerpt of a complete reference. Recommended as long as you know what you are buying. 

I was hoping I can use this book as a quick reference to anything Javascript, but I didn't quite get that. A pocket reference should be more about coverage than explanation. This book explains some topics at length and doesn't care about many other topics. From a pocket reference you would expect lots of tables and pictures and charts covering the various methods, properties of built in types

This isn't a match to the 2nd edition of the same book, though the authors mentioned that this is intentional. I personally prefer a reference to be a reference first. What this book aims to be instead is a collection of some good portions from the book "6th edition of JavaScript: The Definitive Guide" by the same author.

However I do feel that, what it explains, it explains well. I am an experienced programmer. So, I skipped the basics and started straight from Ch 9. I found the concepts well explained and the examples quite useful. You can rely on this book for understanding the concepts that it covers. The author, no doubt, is one of the finest and you will know if you read the Definitive Guide.

Disclosure
I reviewed this book for O'Reilly's Blogger Review Program

CodeProject