Demonstrating extensibility for 3.0: Approve requested quantities in packs

Hi everyone,

Achieving extensibility in OpenLMIS through Extension Points and Extension Modules is as we all know a core aspect to our architecture. To date we have built a good example for the basic mechanism which is available in the Example Service repository.

What’s needed now is to show how a point of variance between previous releases of OpenLMIS could be solved using extensions in our new architecture. In doing this we’ll be able to highlight within the community how we can support differing country needs without forking the code-base. The team here in Seattle has been racking our brains on what point of variance we’d like to use to demonstrate this new mechanism. We’ve been looking for something that:

  1. was a point of variance between v1 and v2
  2. demonstrates the use of extension points & modules
  3. would provide a straightforward example for implementations to follow

What we’ve chosen is the feature in version 2 that allowed for a Requisition Template to be configured in such a way that an Approver would enter Approved Quantities in Packs rather than Dispensing Units. This feature seems to satisfy our criteria above quite well.

We’ll be designing and slotting this work soon so your feedback would be appreciated: would demonstrating how to utilize an extension point from an extension module so that an Approver would enter the Approved Quantity in their Requisition in terms of Packs rather than Dispensing Units sufficiently show how Extension Points and Modules will be used to address country variance without forking the code?

Best,

Josh

Hello PC,

I wanted to forward the following note from Josh on demonstrating extension points.

Please let us know if you have any thoughts or comments in response to our approach.

For more details on the example please review the ticket, here.

Regards,

Mary Jo

···

From: openlmis-dev@googlegroups.com [mailto:openlmis-dev@googlegroups.com] On Behalf Of Josh Zamor

Sent: Monday, October 24, 2016 2:38 PM

To: OpenLMIS Dev openlmis-dev@googlegroups.com

Subject: [openlmis-dev] Demonstrating extensibility for 3.0: Approve requested quantities in packs

Hi everyone,

Achieving extensibility in OpenLMIS through Extension Points and Extension Modules is as we all know a core aspect to our architecture. To date we have built a good example for the basic mechanism which is available in the Example Service repository.

What’s needed now is to show how a point of variance between previous releases of OpenLMIS could be solved using extensions in our new architecture. In doing this we’ll be able to highlight within the community how we can support differing country needs without forking the code-base. The team here in Seattle has been racking our brains on what point of variance we’d like to use to demonstrate this new mechanism. We’ve been looking for something that:

  1. was a point of variance between v1 and v2

  2. demonstrates the use of extension points & modules

  3. would provide a straightforward example for implementations to follow

What we’ve chosen is the feature in version 2 that allowed for a Requisition Template to be configured in such a way that an Approver would enter Approved Quantities in Packs rather than Dispensing Units. This feature seems to satisfy our criteria above quite well.

We’ll be designing and slotting this work soon so your feedback would be appreciated: would demonstrating how to utilize an extension point from an extension module so that an Approver would enter the Approved Quantity in their Requisition in terms of Packs rather than Dispensing Units sufficiently show how Extension Points and Modules will be used to address country variance without forking the code?

Best,

Josh

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/2faee205-a54c-4ad0-996b-8fffc21bc2a5%40googlegroups.com
.

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

Hi all,

Based on the fact that this is an enhancement request directly from users, this looks like a good test case to me.

If we are looking for a more complex extension point for a second test case, requiring a physical inventory prior to a initiating a requisition comes to mind.

Cheers,

···

Kevin Cussen | kevin.cussen@villagereach.org

Manager, Information Systems

Village****Reach Starting at the Last Mile

2900 Eastlake Ave. E, Suite 230, Seattle, WA 98102, USA

CELL: 1.206.604.4209 FAX: 1.206.860.6972

SKYPE: kevin.cussen.vr

www.villagereach.org

Connect on Facebook,
Twitter and our Blog


From: openlmis_product_committee@googlegroups.com openlmis_product_committee@googlegroups.com on behalf of Mary Jo Kochendorfer maryjo.kochendorfer@villagereach.org

Sent: Tuesday, October 25, 2016 08:55

To: openlmis_product_committee@googlegroups.com

Subject: FW: [openlmis-dev] Demonstrating extensibility for 3.0: Approve requested quantities in packs

Hello PC,

I wanted to forward the following note from Josh on demonstrating extension points.

Please let us know if you have any thoughts or comments in response to our approach.

For more details on the example please review the ticket,
here
.

Regards,

Mary Jo

From: openlmis-dev@googlegroups.com [mailto:openlmis-dev@googlegroups.com] On Behalf Of Josh Zamor

Sent: Monday, October 24, 2016 2:38 PM

To: OpenLMIS Dev openlmis-dev@googlegroups.com

Subject: [openlmis-dev] Demonstrating extensibility for 3.0: Approve requested quantities in packs

Hi everyone,

Achieving extensibility in OpenLMIS through Extension Points and Extension Modules is as we all know a core aspect to our
architecture
. To date we have built a good example for the basic mechanism which is available in the Example Service
repository
.

What’s needed now is to show how a point of variance between previous releases of OpenLMIS could be solved using extensions in our new architecture. In doing this we’ll be able to highlight within the community how we can support differing country needs without forking the code-base. The team here in Seattle has been racking our brains on what point of variance we’d like to use to demonstrate this new mechanism. We’ve been looking for something that:

  1. was a point of variance between v1 and v2
  2. demonstrates the use of extension points & modules
  3. would provide a straightforward example for implementations to follow

What we’ve chosen is the feature in version 2 that allowed for a Requisition Template to be configured in such a way that an Approver would enter Approved Quantities in Packs rather than Dispensing Units. This feature seems to satisfy our criteria above quite well.

We’ll be designing and slotting this work soon so your feedback would be appreciated: would demonstrating how to utilize an extension point from an extension module so that an Approver would enter the Approved Quantity in their Requisition in terms of Packs rather than Dispensing Units sufficiently show how Extension Points and Modules will be used to address country variance without forking the code?

Best,

Josh

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/2faee205-a54c-4ad0-996b-8fffc21bc2a5%40googlegroups.com
.

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

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

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

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

To view this discussion on the web visit
https://groups.google.com/d/msgid/openlmis_product_committee/DM5PR02MB23459C9173B179D96533137C8FA80%40DM5PR02MB2345.namprd02.prod.outlook.com
.

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

Dear Mary Jo,

Reflecting on the Vaccine Information Management System implementation we have a combination of the vaccine packaging and loose vials that are multiplied to calculate the number of doses (see image below).

Is this something that would be supported through this type of extension point?

Warm regards,

Brian Taliesin

Digital Health Solutions

Description: http://www.charity.org/sites/default/files/images_logos/ca_path_logo_0.png

3rd floor, Oasis Office Complex, Plot No 14/15

Off Haile Selassie Road, Oyster Bay

(Opposite Best Western Plus Peninsula Hotel)

P.O. Box 13600, Dar Es Salaam, 38394

Tanzania: +255.684.488.377

Global: +1.206.387.8932

Skype: btaliesin

Email: btaliesin@path.org

To learn more about our work in health information systems please see PATH’s Digital Health Solutions website.

···

From: openlmis_product_committee@googlegroups.com [mailto:openlmis_product_committee@googlegroups.com] On Behalf Of Mary Jo Kochendorfer

Sent: Tuesday, October 25, 2016 6:55 PM

To: openlmis_product_committee@googlegroups.com

Subject: FW: [openlmis-dev] Demonstrating extensibility for 3.0: Approve requested quantities in packs

Hello PC,

I wanted to forward the following note from Josh on demonstrating extension points.

Please let us know if you have any thoughts or comments in response to our approach.

For more details on the example please review the ticket, here.

Regards,

Mary Jo

From:
openlmis-dev@googlegroups.com [mailto:openlmis-dev@googlegroups.com] On Behalf Of Josh Zamor

Sent: Monday, October 24, 2016 2:38 PM

To: OpenLMIS Dev openlmis-dev@googlegroups.com

Subject: [openlmis-dev] Demonstrating extensibility for 3.0: Approve requested quantities in packs

Hi everyone,

Achieving extensibility in OpenLMIS through Extension Points and Extension Modules is as we all know a core aspect to our architecture. To date we have built a good example for the basic mechanism which is available in the Example Service repository.

What’s needed now is to show how a point of variance between previous releases of OpenLMIS could be solved using extensions in our new architecture. In doing this we’ll be able to highlight within the community how we can support differing country needs without forking the code-base. The team here in Seattle has been racking our brains on what point of variance we’d like to use to demonstrate this new mechanism. We’ve been looking for something that:

  1. was a point of variance between v1 and v2

  2. demonstrates the use of extension points & modules

  3. would provide a straightforward example for implementations to follow

What we’ve chosen is the feature in version 2 that allowed for a Requisition Template to be configured in such a way that an Approver would enter Approved Quantities in Packs rather than Dispensing Units. This feature seems to satisfy our criteria above quite well.

We’ll be designing and slotting this work soon so your feedback would be appreciated: would demonstrating how to utilize an extension point from an extension module so that an Approver would enter the Approved Quantity in their Requisition in terms of Packs rather than Dispensing Units sufficiently show how Extension Points and Modules will be used to address country variance without forking the code?

Best,

Josh

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/2faee205-a54c-4ad0-996b-8fffc21bc2a5%40googlegroups.com
.

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

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

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

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

To view this discussion on the web visit
https://groups.google.com/d/msgid/openlmis_product_committee/DM5PR02MB23459C9173B179D96533137C8FA80%40DM5PR02MB2345.namprd02.prod.outlook.com
.

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