@vaibhavhp, thanks for sharing your project and progress to date. A couple of questions come to mind:
Is there a near-term target that you could get deployed well before GSoC ends?
As the end of GSoC quickly approaches, work with @surangak to define the smallest amount of functionality needed to be useful and try to get that deployed before working on additional features or enhancements.
Are you implementing a REST interface (i.e., using the RESTWS module)?
It seems more likely that people would want to create clients to consume CDAs by hitting a REST web service with a patient identifier to download their CDA (vs. an administrator manually downloading CDAs one at a time).
Is there a near-term target that you could get deployed well before GSoC ends?
Yes, the goal is to focus on completing a very good APHP message. We are working on adding answers to aphp message sections and get it deployed before working on any additional features or enhancements.
Are you implementing a REST interface (i.e., using the RESTWS module)?
Currently, we don’t have any plans to use RESTWS Module. I’ll have a discussion with @surangak on this and reply ASAP.
Our goal for the summer is to focus on getting a good APHP message out. This involves being able to output section content (questions/answers) in a re-usable and valid way.
An underlying target for the summer - Identify and list out which LOINC codes CDA needs, and work with Andy to get them into the MVP CIEL Dictionary - this is very important because without these, the CDA generator module becomes useless to implementers.
In regard to the REST interface, we’re not really focussing on that at this point. If we get fully valid and well populated CDA message generated, i’ll be happy to call it a great success. But if we DO have the time, then we will definitely try for it !
,