Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Chris George : I think to not confuse from the use of the top level picture of 'central', 'intermediate', and 'service delivery site' in the other slides, could get rid of this diagram here - I was just worried the viewer might be inclined to group the below items up to a specific level as was done in the previous slides, even though interoperability is more cross-cutting through the whole system.
  • Chris Wright: Should we also include interoperability with a WMS/ERP in situations where the eLMIS manages stock at lower levels but not at central? 
  • Mary Jo: I’d suggest renaming the slide to “eLMIS Interoperability”. I think the word layer may be confusing since sometimes the “layer” may be outside of the eLMIS solution itself. I’d focus on the eLMIS must provide ways to be interoperable with the following systems. I’d also suggest that eLMIS can “push”/export data into the WHO DVDMT and SMT since that is the desired use case. For WMS, I’d suggest two way interoperability/integration so that orders can be sent to WMS and shipment information can be received. You could even through in a syncing of product lists (or a nationally maintained product list or GDSN).  I’d suggest adding another system, a national facility registry. For example, clearly breaking out the different types of systems which it would be ideal for LMIS to interoperate with. I agree it is confusing to make these generalized statements given the detailed nature of each integration and at what level.

Image Modified

Ian shared the following version after reviewing the communities feedback. 

2017_6_29 vLMIS Minimum Requirements v9 (002).pptx