使用MDHT API生成CCD文档

Question

I am trying to use MDHT API to generate CCD documents. I am doing this in the following way.

Downloaded Java runtime libraries and placed them in classpath and writing code to generate all the sections using MDHT API.

Writing code for each section is taking long (a bit complicated). I was wondering if I am missing anything. Is there any open source mdht GUI that generates code for each section or am I moving in the right direction?

I am currently stuck at Medications Section/Immunization Section. Can anyone please redirect me to any examples/tutorials related to each section. I have already looked at user guide/developers guide.
Any help is appreciated.

Answer 1

I think MDHT API will only provide a Model for the CCD document. if it contains any default implimentaion to generate CCD document,,i dont know.. any way better you just generate the XML in DOM,STAXs API.

CCD example link

Another better API that i found is MIRTH follow the link

Mirth User guide

Answer 2

The best place to look for help/sample code is the developers forum: Eclipse Community Forums » Model Driven Health Tools .

You may need to create a (free) account to get access.

You could also go to the forums to post your specific MedicationsSection/immunization question for a possible specific answer.

Another good site is CDA tools: MDHT Developers Guide . Look at Produce CDA Content using MDHT API .

There are countless examples of building documents in the test code projects. Download the All In One (MDHT_CDATools) from GitHub linked in the MDHT project site and look at the code in the test projects such as: org.openhealthtools.mdht.cda.consol.example

The closest (current) thing to a GUI based document building application in MDHT would be using the all in one to modify the existing models and generate sample snippets/documents that way (or creating a model from scratch, which includes only what you need). If you wanted the entire document produced in XML, you could then generate the instance from GeneralHeaderConstraints as opposed to any of the many child templates (which would give you snippets). Either way, this is not really the intention of the model interface (it's more for conformance) and would take you far longer to implement than using the API itself - which accesses the models which already exist in order to auto-generate conformant content quickly.