As you are aware, Jeremy Keiper and I have been working with a student named Vaibhav Agarwal to develop a module to produce CDA messages from OpenMRS data. This work was undertaken as part of the OpenMRS Google Summer of Code program.
At this point, we’ve developed a design that can be extended on to support any CDA message type.
We’re currently working on implementing an APHP message. Based on our time availability, we may or may not expand to implement APS messages as well.
To date, we have made a lot of progress. Attached below is a sample message that we are able to produce at this point.
I wanted to write this mail to,
(1) Introduce Vaibhav to the community
(2) Highlight the GREAT work that we’ve done
(3) Launch a channel where Vaibhav and I can obtain your input on the work that we’ve performed so far, and what else we need to do.
We have also requested an OpenMRS JIRA account for this project, and will share it with you once it has been created. Feel free to jump in, review and comment on what we’ve done / going to do.
I was just wondering what protocol you plan to use to export the CDA documents? Will the module support IHE’s XDS.b profile to send documents to a central repository or are you thinking of something different?
Cheers,
Ryan
···
On Thu, Jun 12, 2014 at 9:02 PM, Suranga Kasthurirathne surangak@openmrs.org wrote:
Hi everyone,
As you are aware, Jeremy Keiper and I have been working with a student named Vaibhav Agarwal to develop a module to produce CDA messages from OpenMRS data. This work was undertaken as part of the OpenMRS Google Summer of Code program.
At this point, we’ve developed a design that can be extended on to support any CDA message type.
We’re currently working on implementing an APHP message. Based on our time availability, we may or may not expand to implement APS messages as well.
To date, we have made a lot of progress. Attached below is a sample message that we are able to produce at this point.
I wanted to write this mail to,
(1) Introduce Vaibhav to the community
(2) Highlight the GREAT work that we’ve done
(3) Launch a channel where Vaibhav and I can obtain your input on the work that we’ve performed so far, and what else we need to do.
We have also requested an OpenMRS JIRA account for this project, and will share it with you once it has been created. Feel free to jump in, review and comment on what we’ve done / going to do.
At this point, we’re focussing simply on getting the CDA documents created. We haven’t really thought about any protocol, and its likely that this wont be part of our scope, seeing as theres so much validation and testing of messages to be done
As you can see, this is a valid message, but the sections contain only the questions, and not answers. We will be fixing that next
···
On Tue, Jun 17, 2014 at 5:55 AM, Ryan Crichton ryan@jembi.org wrote:
Hi Suranga,
This sounds great.
I was just wondering what protocol you plan to use to export the CDA documents? Will the module support IHE’s XDS.b profile to send documents to a central repository or are you thinking of something different?
Cheers,
Ryan
On Thu, Jun 12, 2014 at 9:02 PM, Suranga Kasthurirathne surangak@openmrs.org wrote:
Hi everyone,
As you are aware, Jeremy Keiper and I have been working with a student named Vaibhav Agarwal to develop a module to produce CDA messages from OpenMRS data. This work was undertaken as part of the OpenMRS Google Summer of Code program.
At this point, we’ve developed a design that can be extended on to support any CDA message type.
We’re currently working on implementing an APHP message. Based on our time availability, we may or may not expand to implement APS messages as well.
To date, we have made a lot of progress. Attached below is a sample message that we are able to produce at this point.
I wanted to write this mail to,
(1) Introduce Vaibhav to the community
(2) Highlight the GREAT work that we’ve done
(3) Launch a channel where Vaibhav and I can obtain your input on the work that we’ve performed so far, and what else we need to do.
We have also requested an OpenMRS JIRA account for this project, and will share it with you once it has been created. Feel free to jump in, review and comment on what we’ve done / going to do.