New to OpenLMIS: A few questions

Hi Everyone,

I’m new to OpenLMIS2 and working to understand some of the capabilities for integration with MOTECH. Can you help me with the following questions?

  • Does OpenLMIS generate push events that can be consumed by 3rd party systems? I see the atomFeed in the core module, but don’t know the type of events exposed to it. To provide an example, other systems (CommCare, ODK Aggregate, etc) are able to “forward forms” when they are received. Does OpenLMIS do this when requisitions are submitted, products are shipped/distributed, Proof of Delivery is submitted, or stock Cards are updated?

  • I see the stock-management API endpoints in Swagger, but does the stock management have a front end? Are there open source ODK forms or SMS workflows that are available?

  • In the requisitions API area, I see the ability to post to both “sdp-requisitions” and “requisitions” What’s the difference between these endpoints?

  • In the API, I don’t see any endpoints for distributions. For example, when a service delivery point distributes products to a CHW so they can take those products out to the field to patients. Are distributions handled through the webapp? If so, under which navigation menu?

I think that’s it for now, thank you for your help!

Sincerely,

Craig

Re: stock management front end - ThoughtWorks is building an Android smart phone front end, but quite specific to one country’s requirement. We found it quite challenging to balance between user experience and universalness. There is an ongoing discussion on building a reusable Android front end, but still at its early stage.

Other ThoughtWorks colleagues might have further insights on your questions.

···

On 25 December 2015 at 03:02, Craig A cappl@grameenfoundation.org wrote:

Hi Everyone,

I’m new to OpenLMIS2 and working to understand some of the capabilities for integration with MOTECH. Can you help me with the following questions?

  • Does OpenLMIS generate push events that can be consumed by 3rd party systems? I see the atomFeed in the core module, but don’t know the type of events exposed to it. To provide an example, other systems (CommCare, ODK Aggregate, etc) are able to “forward forms” when they are received. Does OpenLMIS do this when requisitions are submitted, products are shipped/distributed, Proof of Delivery is submitted, or stock Cards are updated?
  • I see the stock-management API endpoints in Swagger, but does the stock management have a front end? Are there open source ODK forms or SMS workflows that are available?
  • In the requisitions API area, I see the ability to post to both “sdp-requisitions” and “requisitions” What’s the difference between these endpoints?
  • In the API, I don’t see any endpoints for distributions. For example, when a service delivery point distributes products to a CHW so they can take those products out to the field to patients. Are distributions handled through the webapp? If so, under which navigation menu?

I think that’s it for now, thank you for your help!

Sincerely,

Craig

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

To post to this group, send email to openlmis-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/50c2dedc-fbee-41e6-a1ad-290f41c5e864%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Jeff Xiong
ThoughtWorks
+86 186 826 53819

Hi Craig,

  •     Push events:  no, OpenLMIS currently does  not broadcast any events.
    
  •      Stock management front end:  to build on Jeff’s reply, OpenLMIS does not have a global UI for stock management.  This functionality was added recently, and a little background is in order.  Two concurrent projects had basic stock management needs:  one in Mozambique  and the other in Tanzania.  VillageReach worked on the core API, which was shared by the two projects, which respectively built their own UI and additional logic per the project needs (The Android front end was for Mozambique).  A proper UI is on the OpenLMIS roadmap, as well as enhancements to make stock management more robust, but no immediate plans for when to implement.
    
  •     Some of the API end points you mentioned were developed by JSI for other projects – I hope our JSI colleagues can help with specifics
    
  •      Distributions:  OpenLMIS does not have specific functionality for tracking commodities beyond the service delivery point, such as to a CHW or actual dispensing.  That said, the CHAI/ThoughtWorks project for Mozambique has added some level of tracking – mainly stock management - at the CHW level.  I can’t say with authority, but I believe most of the admin is done via that Mozambique Android app.
    

Hope this helps, and look forward to replies from others.

Rich

···

Re: stock management front end - ThoughtWorks is building an Android smart phone front end, but quite specific to one country’s requirement. We found it quite challenging to balance between user experience and universalness. There is an ongoing discussion on building a reusable Android front end, but still at its early stage.

Other ThoughtWorks colleagues might have further insights on your questions.

On 25 December 2015 at 03:02, Craig A cappl@grameenfoundation.org wrote:

Hi Everyone,

I’m new to OpenLMIS2 and working to understand some of the capabilities for integration with MOTECH. Can you help me with the following questions?

  • Does OpenLMIS generate push events that can be consumed by 3rd party systems? I see the atomFeed in the core module, but don’t know the type of events exposed to it. To provide an example, other systems (CommCare, ODK Aggregate, etc) are able to “forward forms” when they are received. Does OpenLMIS do this when requisitions are submitted, products are shipped/distributed, Proof of Delivery is submitted, or stock Cards are updated?
  • I see the stock-management API endpoints in Swagger, but does the stock management have a front end? Are there open source ODK forms or SMS workflows that are available?
  • In the requisitions API area, I see the ability to post to both “sdp-requisitions” and “requisitions” What’s the difference between these endpoints?
  • In the API, I don’t see any endpoints for distributions. For example, when a service delivery point distributes products to a CHW so they can take those products out to the field to patients. Are distributions handled through the webapp? If so, under which navigation menu?

I think that’s it for now, thank you for your help!

Sincerely,

Craig

Hi Craig,

On the question about requisitions vs sdp-requisitions: I believe this “sdp-requisitions” is used for emergency requisitions. The “requisitions” endpoint is for regular requisitions.

-Danni

···

On Tue, Dec 29, 2015 at 1:45 AM, Rich Magnuson rich.magnuson@villagereach.org wrote:

Hi Craig,

  •     Push events:  no, OpenLMIS currently does  not broadcast any events.
    
  •      Stock management front end:  to build on Jeff’s reply, OpenLMIS does not have a global UI for stock management.  This functionality was added recently, and a little background is in order.  Two concurrent projects had basic stock management needs:  one in Mozambique  and the other in Tanzania.  VillageReach worked on the core API, which was shared by the two projects, which respectively built their own UI and additional logic per the project needs (The Android front end was for Mozambique).  A proper UI is on the OpenLMIS roadmap, as well as enhancements to make stock management more robust, but no immediate plans for when to implement. 
    
  •     Some of the API end points you mentioned were developed by JSI for other projects – I hope our JSI colleagues can help with specifics
    
  •      Distributions:  OpenLMIS does not have specific functionality for tracking commodities beyond the service delivery point, such as to a CHW or actual dispensing.  That said, the CHAI/ThoughtWorks project for Mozambique has added some level of tracking – mainly stock management - at the CHW level.  I can’t say with authority, but I believe most of the admin is done via that Mozambique Android app.
    

Hope this helps, and look forward to replies from others.

Rich

From: openlmis-dev@googlegroups.com [mailto:openlmis-dev@googlegroups.com] On Behalf Of Jie Xiong

Sent: Thursday, December 24, 2015 5:27 PM

To: Craig A cappl@grameenfoundation.org

Cc: OpenLMIS Dev openlmis-dev@googlegroups.com

Subject: Re: [openlmis-dev] New to OpenLMIS: A few questions

Re: stock management front end - ThoughtWorks is building an Android smart phone front end, but quite specific to one country’s requirement. We found it quite challenging to balance between user experience and universalness. There is an ongoing discussion on building a reusable Android front end, but still at its early stage.

Other ThoughtWorks colleagues might have further insights on your questions.

On 25 December 2015 at 03:02, Craig A cappl@grameenfoundation.org wrote:

Hi Everyone,

I’m new to OpenLMIS2 and working to understand some of the capabilities for integration with MOTECH. Can you help me with the following questions?

  • Does OpenLMIS generate push events that can be consumed by 3rd party systems? I see the atomFeed in the core module, but don’t know the type of events exposed to it. To provide an example, other systems (CommCare, ODK Aggregate, etc) are able to “forward forms” when they are received. Does OpenLMIS do this when requisitions are submitted, products are shipped/distributed, Proof of Delivery is submitted, or stock Cards are updated?
  • I see the stock-management API endpoints in Swagger, but does the stock management have a front end? Are there open source ODK forms or SMS workflows that are available?
  • In the requisitions API area, I see the ability to post to both “sdp-requisitions” and “requisitions” What’s the difference between these endpoints?
  • In the API, I don’t see any endpoints for distributions. For example, when a service delivery point distributes products to a CHW so they can take those products out to the field to patients. Are distributions handled through the webapp? If so, under which navigation menu?

I think that’s it for now, thank you for your help!

Sincerely,

Craig

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

To post to this group, send email to openlmis-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/BN1PR02MB02109B8C7BFBB71BE063D9093FB0%40BN1PR02MB021.namprd02.prod.outlook.com.

For more options, visit https://groups.google.com/d/optout.

Thanks Everyone!

···

On Mon, Dec 28, 2015 at 6:50 PM, Danni Yu dyu@thoughtworks.com wrote:

Hi Craig,

On the question about requisitions vs sdp-requisitions: I believe this “sdp-requisitions” is used for emergency requisitions. The “requisitions” endpoint is for regular requisitions.

-Danni

On Tue, Dec 29, 2015 at 1:45 AM, Rich Magnuson rich.magnuson@villagereach.org wrote:

Hi Craig,

  •     Push events:  no, OpenLMIS currently does  not broadcast any events.
    
  •      Stock management front end:  to build on Jeff’s reply, OpenLMIS does not have a global UI for stock management.  This functionality was added recently, and a little background is in order.  Two concurrent projects had basic stock management needs:  one in Mozambique  and the other in Tanzania.  VillageReach worked on the core API, which was shared by the two projects, which respectively built their own UI and additional logic per the project needs (The Android front end was for Mozambique).  A proper UI is on the OpenLMIS roadmap, as well as enhancements to make stock management more robust, but no immediate plans for when to implement. 
    
  •     Some of the API end points you mentioned were developed by JSI for other projects – I hope our JSI colleagues can help with specifics
    
  •      Distributions:  OpenLMIS does not have specific functionality for tracking commodities beyond the service delivery point, such as to a CHW or actual dispensing.  That said, the CHAI/ThoughtWorks project for Mozambique has added some level of tracking – mainly stock management - at the CHW level.  I can’t say with authority, but I believe most of the admin is done via that Mozambique Android app.
    

Hope this helps, and look forward to replies from others.

Rich

From: openlmis-dev@googlegroups.com [mailto:openlmis-dev@googlegroups.com] On Behalf Of Jie Xiong

Sent: Thursday, December 24, 2015 5:27 PM

To: Craig A cappl@grameenfoundation.org

Cc: OpenLMIS Dev openlmis-dev@googlegroups.com

Subject: Re: [openlmis-dev] New to OpenLMIS: A few questions

Re: stock management front end - ThoughtWorks is building an Android smart phone front end, but quite specific to one country’s requirement. We found it quite challenging to balance between user experience and universalness. There is an ongoing discussion on building a reusable Android front end, but still at its early stage.

Other ThoughtWorks colleagues might have further insights on your questions.

On 25 December 2015 at 03:02, Craig A cappl@grameenfoundation.org wrote:

Hi Everyone,

I’m new to OpenLMIS2 and working to understand some of the capabilities for integration with MOTECH. Can you help me with the following questions?

  • Does OpenLMIS generate push events that can be consumed by 3rd party systems? I see the atomFeed in the core module, but don’t know the type of events exposed to it. To provide an example, other systems (CommCare, ODK Aggregate, etc) are able to “forward forms” when they are received. Does OpenLMIS do this when requisitions are submitted, products are shipped/distributed, Proof of Delivery is submitted, or stock Cards are updated?
  • I see the stock-management API endpoints in Swagger, but does the stock management have a front end? Are there open source ODK forms or SMS workflows that are available?
  • In the requisitions API area, I see the ability to post to both “sdp-requisitions” and “requisitions” What’s the difference between these endpoints?
  • In the API, I don’t see any endpoints for distributions. For example, when a service delivery point distributes products to a CHW so they can take those products out to the field to patients. Are distributions handled through the webapp? If so, under which navigation menu?

I think that’s it for now, thank you for your help!

Sincerely,

Craig

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

To post to this group, send email to openlmis-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/BN1PR02MB02109B8C7BFBB71BE063D9093FB0%40BN1PR02MB021.namprd02.prod.outlook.com.

For more options, visit https://groups.google.com/d/optout.

Craig Appl

Lead Technical Program Manager, Mobile Health Innovations

Grameen Foundation

2101 4th Ave | Suite 1550 | Seattle, WA 98121

Skype:craigappl

FacebookTwitterYouTube | www.motechsuite.org

Connecting the World’s Poor to Their Potential

Hi Craig,

Here is a little more detail about requisitions vs sdp-requisitions api.

** Requisitions API:

  • Developed to be consumed by CommCare.

  • It assumes that CommCare will submit Regular Requisitions only (No Emergency Orders).

  • CommCare does not say which period the report is for, always submits report for next period in chronological order.

  • Once CommCare submits a report for a period, It will never re-submit for the same period. No Updates.

  • CommCare does not skip periods.

** Requisition-SDP

  • Developed to be consumed by another thick client application installed at the service delivery points called SDP.

  • SDP can submit both Emergency as well as Regular R&Rs

  • SDP can send R&R at any point in time, When submitting, SDP informs for which period the R&R is submitted for. Eg- SDP did not submit requisition for 3 months, it wants to submit requisition for current month. It is allowed to submit with this API.

  • SDP can re-submit a report to update previous submissions. Resubmissions are accepted as long as the status of the R&R did not pass through approvals (as long as the status is pre-authorize).

  • SDP can skip periods and submit reports for subsequent periods.

···

On Monday, December 28, 2015 at 10:05:21 PM UTC-5, Craig A wrote:

Thanks Everyone!

On Mon, Dec 28, 2015 at 6:50 PM, Danni Yu d...@thoughtworks.com wrote:

Hi Craig,

On the question about requisitions vs sdp-requisitions: I believe this “sdp-requisitions” is used for emergency requisitions. The “requisitions” endpoint is for regular requisitions.

-Danni

On Tue, Dec 29, 2015 at 1:45 AM, Rich Magnuson rich.m...@villagereach.org wrote:

Hi Craig,

  •     Push events:  no, OpenLMIS currently does  not broadcast any events.
    
  •      Stock management front end:  to build on Jeff’s reply, OpenLMIS does not have a global UI for stock management.  This functionality was added recently, and a little background is in order.  Two concurrent projects had basic stock management needs:  one in Mozambique  and the other in Tanzania.  VillageReach worked on the core API, which was shared by the two projects, which respectively built their own UI and additional logic per the project needs (The Android front end was for Mozambique).  A proper UI is on the OpenLMIS roadmap, as well as enhancements to make stock management more robust, but no immediate plans for when to implement. 
    
  •     Some of the API end points you mentioned were developed by JSI for other projects – I hope our JSI colleagues can help with specifics
    
  •      Distributions:  OpenLMIS does not have specific functionality for tracking commodities beyond the service delivery point, such as to a CHW or actual dispensing.  That said, the CHAI/ThoughtWorks project for Mozambique has added some level of tracking – mainly stock management - at the CHW level.  I can’t say with authority, but I believe most of the admin is done via that Mozambique Android app.
    

Hope this helps, and look forward to replies from others.

Rich

From: openlm...@googlegroups.com [mailto:openlm...@googlegroups.com] On Behalf Of Jie Xiong

Sent: Thursday, December 24, 2015 5:27 PM

To: Craig A ca...@grameenfoundation.org

Cc: OpenLMIS Dev openlm...@googlegroups.com

Subject: Re: [openlmis-dev] New to OpenLMIS: A few questions

Re: stock management front end - ThoughtWorks is building an Android smart phone front end, but quite specific to one country’s requirement. We found it quite challenging to balance between user experience and universalness. There is an ongoing discussion on building a reusable Android front end, but still at its early stage.

Other ThoughtWorks colleagues might have further insights on your questions.

On 25 December 2015 at 03:02, Craig A ca...@grameenfoundation.org wrote:

Hi Everyone,

I’m new to OpenLMIS2 and working to understand some of the capabilities for integration with MOTECH. Can you help me with the following questions?

  • Does OpenLMIS generate push events that can be consumed by 3rd party systems? I see the atomFeed in the core module, but don’t know the type of events exposed to it. To provide an example, other systems (CommCare, ODK Aggregate, etc) are able to “forward forms” when they are received. Does OpenLMIS do this when requisitions are submitted, products are shipped/distributed, Proof of Delivery is submitted, or stock Cards are updated?
  • I see the stock-management API endpoints in Swagger, but does the stock management have a front end? Are there open source ODK forms or SMS workflows that are available?
  • In the requisitions API area, I see the ability to post to both “sdp-requisitions” and “requisitions” What’s the difference between these endpoints?
  • In the API, I don’t see any endpoints for distributions. For example, when a service delivery point distributes products to a CHW so they can take those products out to the field to patients. Are distributions handled through the webapp? If so, under which navigation menu?

I think that’s it for now, thank you for your help!

Sincerely,

Craig

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.

To post to this group, send email to openlm...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/BN1PR02MB02109B8C7BFBB71BE063D9093FB0%40BN1PR02MB021.namprd02.prod.outlook.com.

For more options, visit https://groups.google.com/d/optout.


Craig Appl

Lead Technical Program Manager, Mobile Health Innovations

Grameen Foundation

2101 4th Ave | Suite 1550 | Seattle, WA 98121

Skype:craigappl

FacebookTwitterYouTube | www.motechsuite.org

Connecting the World’s Poor to Their Potential

Thanks Everyone,

I ran into a few more questions. Can you help me with the following?

  • Is there a way to access the RnR template through the API to determine which data is being collected by which program? Is this integrated into other API endpoints? I see the reference to the RnR template in the Requisitions API endpoint, but don’t know how to get the fields from the template.

  • Is there an API endpoint for distributions? Is this available in the stock-status endpoint or elsewhere?

  • It seems as though there’s an internal event system when a requisition is submitted for approval. This would be a great thing to provide to external services as a as a web hook so they could query the APIs when a requisition is submitted, a distribution is made. Can anyone describe or point me to the code describing what events are exposed and which elements within OpenLMIS use it?

Thank you!

Craig

···

On Tuesday, December 29, 2015 at 7:09:56 PM UTC-8, Elias Muluneh wrote:

Hi Craig,

Here is a little more detail about requisitions vs sdp-requisitions api.

** Requisitions API:

  • Developed to be consumed by CommCare.
  • It assumes that CommCare will submit Regular Requisitions only (No Emergency Orders).
  • CommCare does not say which period the report is for, always submits report for next period in chronological order.
  • Once CommCare submits a report for a period, It will never re-submit for the same period. No Updates.
  • CommCare does not skip periods.

** Requisition-SDP

  • Developed to be consumed by another thick client application installed at the service delivery points called SDP.
  • SDP can submit both Emergency as well as Regular R&Rs
  • SDP can send R&R at any point in time, When submitting, SDP informs for which period the R&R is submitted for. Eg- SDP did not submit requisition for 3 months, it wants to submit requisition for current month. It is allowed to submit with this API.
  • SDP can re-submit a report to update previous submissions. Resubmissions are accepted as long as the status of the R&R did not pass through approvals (as long as the status is pre-authorize).
  • SDP can skip periods and submit reports for subsequent periods.

On Monday, December 28, 2015 at 10:05:21 PM UTC-5, Craig A wrote:

Thanks Everyone!

On Mon, Dec 28, 2015 at 6:50 PM, Danni Yu d...@thoughtworks.com wrote:

Hi Craig,

On the question about requisitions vs sdp-requisitions: I believe this “sdp-requisitions” is used for emergency requisitions. The “requisitions” endpoint is for regular requisitions.

-Danni

On Tue, Dec 29, 2015 at 1:45 AM, Rich Magnuson rich.m...@villagereach.org wrote:

Hi Craig,

  •     Push events:  no, OpenLMIS currently does  not broadcast any events.
    
  •      Stock management front end:  to build on Jeff’s reply, OpenLMIS does not have a global UI for stock management.  This functionality was added recently, and a little background is in order.  Two concurrent projects had basic stock management needs:  one in Mozambique  and the other in Tanzania.  VillageReach worked on the core API, which was shared by the two projects, which respectively built their own UI and additional logic per the project needs (The Android front end was for Mozambique).  A proper UI is on the OpenLMIS roadmap, as well as enhancements to make stock management more robust, but no immediate plans for when to implement. 
    
  •     Some of the API end points you mentioned were developed by JSI for other projects – I hope our JSI colleagues can help with specifics
    
  •      Distributions:  OpenLMIS does not have specific functionality for tracking commodities beyond the service delivery point, such as to a CHW or actual dispensing.  That said, the CHAI/ThoughtWorks project for Mozambique has added some level of tracking – mainly stock management - at the CHW level.  I can’t say with authority, but I believe most of the admin is done via that Mozambique Android app.
    

Hope this helps, and look forward to replies from others.

Rich

From: openlm...@googlegroups.com [mailto:openlm...@googlegroups.com] On Behalf Of Jie Xiong

Sent: Thursday, December 24, 2015 5:27 PM

To: Craig A ca...@grameenfoundation.org

Cc: OpenLMIS Dev openlm...@googlegroups.com

Subject: Re: [openlmis-dev] New to OpenLMIS: A few questions

Re: stock management front end - ThoughtWorks is building an Android smart phone front end, but quite specific to one country’s requirement. We found it quite challenging to balance between user experience and universalness. There is an ongoing discussion on building a reusable Android front end, but still at its early stage.

Other ThoughtWorks colleagues might have further insights on your questions.

On 25 December 2015 at 03:02, Craig A ca...@grameenfoundation.org wrote:

Hi Everyone,

I’m new to OpenLMIS2 and working to understand some of the capabilities for integration with MOTECH. Can you help me with the following questions?

  • Does OpenLMIS generate push events that can be consumed by 3rd party systems? I see the atomFeed in the core module, but don’t know the type of events exposed to it. To provide an example, other systems (CommCare, ODK Aggregate, etc) are able to “forward forms” when they are received. Does OpenLMIS do this when requisitions are submitted, products are shipped/distributed, Proof of Delivery is submitted, or stock Cards are updated?
  • I see the stock-management API endpoints in Swagger, but does the stock management have a front end? Are there open source ODK forms or SMS workflows that are available?
  • In the requisitions API area, I see the ability to post to both “sdp-requisitions” and “requisitions” What’s the difference between these endpoints?
  • In the API, I don’t see any endpoints for distributions. For example, when a service delivery point distributes products to a CHW so they can take those products out to the field to patients. Are distributions handled through the webapp? If so, under which navigation menu?

I think that’s it for now, thank you for your help!

Sincerely,

Craig

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.

To post to this group, send email to openlm...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/BN1PR02MB02109B8C7BFBB71BE063D9093FB0%40BN1PR02MB021.namprd02.prod.outlook.com.

For more options, visit https://groups.google.com/d/optout.


Craig Appl

Lead Technical Program Manager, Mobile Health Innovations

Grameen Foundation

2101 4th Ave | Suite 1550 | Seattle, WA 98121

Skype:craigappl

FacebookTwitterYouTube | www.motechsuite.org

Connecting the World’s Poor to Their Potential