DHIS2 provides a REST or REST-like interface over HTTP.
So with just those 4 obvious verbs, I dont see that we really need a WSDL.
To send data from an EHR to DHIS2, you should create a report within your EHR to match the reporting frequency, data elements + catcombos and add those as an XML dataValueSet
This is documented here - http://www.dhis2.org/doc/snapshot/en/user/html/ch25s09.html
You would probably need to exchange metadata before to get the UUIDs for the dataelements etc.
If this is fairly fixed, should be fairly easy… if it isn’t fixed you should read the metadata using - http://www.dhis2.org/doc/snapshot/en/user/html/ch25s05.html
and then read from those and compare them with your EHR.
It can be quite challenging to make it work in the first pass… but if you come back with specific questions, once you start integrating, we can help you better.
Does DHIS2 have a WSDL that I can use? I want to build a module in our
java based EHR system that will automatically upload data into our DHIS2
instance.
I have the same thought process as you have described below. I will let the group know how it progresses and/or if I have any questions.
Thanks a lot!
Edwin
···
On Wed, Nov 27, 2013 at 4:31 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
DHIS2 provides a REST or REST-like interface over HTTP.
So with just those 4 obvious verbs, I dont see that we really need a WSDL.
To send data from an EHR to DHIS2, you should create a report within your EHR to match the reporting frequency, data elements + catcombos and add those as an XML dataValueSet
and then read from those and compare them with your EHR.
It can be quite challenging to make it work in the first pass… but if you come back with specific questions, once you start integrating, we can help you better.
I thought the whole point of using WSDL was to answer to "You would probably need to exchange metadata before to get the UUIDs for the dataelements etc.
If this is fairly fixed, should be fairly easy… if it isn’t fixed you should read the metadata using"
and all is fairly easy after. That is not just 4 words, that is lots of coordination and research.
regards,
murod
···
On Wed, Nov 27, 2013 at 7:44 PM, Edwin Mulwa eddiemu@gmail.com wrote:
Hi Saptarsh,
I have the same thought process as you have described below. I will let the group know how it progresses and/or if I have any questions.
On Wed, Nov 27, 2013 at 4:31 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
DHIS2 provides a REST or REST-like interface over HTTP.
So with just those 4 obvious verbs, I dont see that we really need a WSDL.
To send data from an EHR to DHIS2, you should create a report within your EHR to match the reporting frequency, data elements + catcombos and add those as an XML dataValueSet
and then read from those and compare them with your EHR.
It can be quite challenging to make it work in the first pass… but if you come back with specific questions, once you start integrating, we can help you better.
Good to hear from you.
The standard way in which WSDL is used (atleast 2.0 in context of SOAP), is to describe the Service in terms of Endpoints, Binding, Interface, Operation and Types.
Most of this is self-descriptive in REST paradigm and infact not recommended for RESTful services that should support HATEOAS. I know there is the WADL standard, but its a rarely used standard and doesn’t have much to offer for well documented web services.
So, I wouldn’t imagine that the WSDL document will give metadata information. A WSDL document allows clients of web services to generate stubs surrounding the service.
Instead, I think an XForm or DHISReport template will represent the metadata information in a better way.
I agree its not 4 words!! But once Edwin and his team starts the integration process and comes back with specific questions, we can guide them better.
I thought the whole point of using WSDL was to answer to "You would probably need to exchange metadata before to get the UUIDs for the dataelements etc.
If this is fairly fixed, should be fairly easy… if it isn’t fixed you should read the metadata using"
and all is fairly easy after. That is not just 4 words, that is lots of coordination and research.
regards,
murod
On Wed, Nov 27, 2013 at 7:44 PM, Edwin Mulwa eddiemu@gmail.com wrote:
Hi Saptarsh,
I have the same thought process as you have described below. I will let the group know how it progresses and/or if I have any questions.
Thanks a lot!
Edwin
On Wed, Nov 27, 2013 at 4:31 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
DHIS2 provides a REST or REST-like interface over HTTP.
So with just those 4 obvious verbs, I dont see that we really need a WSDL.
To send data from an EHR to DHIS2, you should create a report within your EHR to match the reporting frequency, data elements + catcombos and add those as an XML dataValueSet
and then read from those and compare them with your EHR.
It can be quite challenging to make it work in the first pass… but if you come back with specific questions, once you start integrating, we can help you better.
Another tip for looking up the meta-data you need from the Web API is to go
through the data set resource and append /form to arrive at the form
resource, for instance: