Reminders and Requests for Support

[Mary Jo Kochendorfer]

Hello Product Committee,

 

I’m sending out a friendly reminder for the following Action Items from the last Product Committee meeting.

 

□    Mary Jo Kochendorfer will circulate instructions for requested UAT during the Jan 17th meeting. Will include test scripts/stories and a demo of the system.

□    Mary Jo Kochendorfer will present an updated scope for 3.0 on Jan 17th

□    Ashraf Islam will share example report specifications

□    Chris George and/or Danni Yu will share example report specifications

□    All participants are welcome to share example diagrams/specifications so our Functional Spec Toolkit is the best.

 

Please share your resources as soon as you can. We would like to leverage the information for the gap analysis work.  In addition, it would be greatly appreciated if anyone would be willing to share UAT test scripts/stories used in the past to test OpenLMIS/eLMIS, so I may build off of those.

 

Website: Request for Suport

The team is moving forward with the revamping of the OpenLMIS website. Please let me know if anyone from the PC is willing to review and provide feedback on product related sections of the website content.  For example, the feature list for OpenLMIS.  Many of you have been working on business development and socializing OpenLMIS so I’d like to reflect those learnings and reflect your opinions. Your input would be greatly appreciated. Let me know directly if you are willing to review some website content.

 

Thanks,

Mary Jo

 

P.S. Next product committee meeting is the 17^th of January

 

[Danni Yu]

Hi Mary Jo,

Attached is a document with some of our report specs. Note that there had been updates since we created these. Let me know if you have any questions.

Danni

--
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+unsub...@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/DM5PR02MB23777A2BD749719BCF842E7C81640%40DM5PR02MB2377.namprd02.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

[Taliesin, Brian]

Thank you, Danni!

 

This is a nice example as is along the line of what I’d hope we’d be able to gather for the critical reports:

 

Description	What is the purpose of this report, and what actions would the user expect to take based on the values?
User	Who is the primary user? Who else might have access and use the reporting data?
Frequency	How often is the report being accessed?
Data Elements	What are names of the fields and the sources?
Layout	What additional report characteristics are there such as input parameters, filters, grouping, ordered by, subtotals, summaries, etc.
Example	Do you have a wireframe or picture of an existing report

 

Ashraf, do you have a similar reporting spec from the work you’ve done on eLMIS?

 

Warm regards,

 

Brian Taliesin

Digital Health Solutions

 

2201 Westlake Ave. Suite 200, Seattle, WA 98121 USA

Direct:  +1.206.302.6039

Mobile: +1.206.387.8932

Skype: btaliesin

Email:  btal...@path.org

 

Learn more about our work in health information systems and supply chain solutions.

 

 

From: openlmis_prod...@googlegroups.com [mailto:openlmis_prod...@googlegroups.com] On Behalf Of Danni Yu
Sent: Thursday, January 12, 2017 10:17 PM
To: Mary Jo Kochendorfer <MaryJo.Ko...@openlmis.org>
Cc: openlmis_prod...@googlegroups.com; Tenly Snow <Tenly...@openlmis.org>
Subject: Re: Reminders and Requests for Support

 

Hi Mary Jo,

 

Attached is a document with some of our report specs. Note that there had been updates since we created these. Let me know if you have any questions.

 

Danni

 

 

On Tue, Jan 10, 2017 at 7:14 AM, Mary Jo Kochendorfer <MaryJo.Ko...@openlmis.org> wrote:

Hello Product Committee,

 

I’m sending out a friendly reminder for the following Action Items from the last Product Committee meeting.

 

□    Mary Jo Kochendorfer will circulate instructions for requested UAT during the Jan 17th meeting. Will include test scripts/stories and a demo of the system.

□    Mary Jo Kochendorfer will present an updated scope for 3.0 on Jan 17th

□    Ashraf Islam will share example report specifications

□    Chris George and/or Danni Yu will share example report specifications

□    All participants are welcome to share example diagrams/specifications so our Functional Spec Toolkit is the best.

 

Please share your resources as soon as you can. We would like to leverage the information for the gap analysis work.  In addition, it would be greatly appreciated if anyone would be willing to share UAT test scripts/stories used in the past to test OpenLMIS/eLMIS, so I may build off of those.

 

Website: Request for Suport

The team is moving forward with the revamping of the OpenLMIS website. Please let me know if anyone from the PC is willing to review and provide feedback on product related sections of the website content.  For example, the feature list for OpenLMIS.  Many of you have been working on business development and socializing OpenLMIS so I’d like to reflect those learnings and reflect your opinions. Your input would be greatly appreciated. Let me know directly if you are willing to review some website content.

 

Thanks,

Mary Jo

 

P.S. Next product committee meeting is the 17^th of January

 

--

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_co...@googlegroups.com.
To post to this group, send email to openlmis_prod...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis_product_committee/DM5PR02MB23777A2BD749719BCF842E7C81640%40DM5PR02MB2377.namprd02.prod.outlook.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_co...@googlegroups.com.
To post to this group, send email to openlmis_prod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis_product_committee/CAMdhj_CQCUum7bJuf90gJ_cdEDtLWWAs%2BtonME0Z15fv6M%2BFRg%40mail.gmail.com.

[Ashraf Islam]

Hi Brian and Mary Jo,

As promised on our OpenLMIS product committee discussion on 1/17, please find attached a sample report specification template we used for eLMIS.

Thanks

Ashraf

 

On Fri, Jan 13, 2017 at 7:31 PM, Taliesin, Brian <btal...@path.org> wrote:

Thank you, Danni!

This is a nice example as is along the line of what I’d hope we’d be able to gather for the critical reports:

Description

What is the purpose of this report, and what actions would the user expect to take based on the values?

User

Who is the primary user? Who else might have access and use the reporting data?

Frequency

How often is the report being accessed?

Data Elements

What are names of the fields and the sources?

Layout

What additional report characteristics are there such as input parameters, filters, grouping, ordered by, subtotals, summaries, etc.

Example

Do you have a wireframe or picture of an existing report


Ashraf, do you have a similar reporting spec from the work you’ve done on eLMIS?

Warm regards,

Brian Taliesin
Digital Health Solutions

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

2201 Westlake Ave. Suite 200, Seattle, WA 98121 USA
Direct:  +1.206.302.6039
Mobile: +1.206.387.8932
Skype: btaliesin

Email:  btal...@path.org<mailto:btalie...@path.org>

Learn more about our work in health information systems<http://sites.path.org/hmis/> and supply chain solutions<http://sites.path.org/vpsse/>.

From: openlmis_product_committee@googlegroups.com [mailto:openlmis_product_comm...@googlegroups.com] On Behalf Of Danni Yu
Sent: Thursday, January 12, 2017 10:17 PM
To: Mary Jo Kochendorfer <MaryJo.Kochendorfer@openlmis.org>
Cc: openlmis_product_committee@googlegroups.com; Tenly Snow <Tenly...@openlmis.org>
Subject: Re: Reminders and Requests for Support

Hi Mary Jo,

Attached is a document with some of our report specs. Note that there had been updates since we created these. Let me know if you have any questions.

Danni



On Tue, Jan 10, 2017 at 7:14 AM, Mary Jo Kochendorfer <MaryJo.Kochendorfer@openlmis.org<mailto:MaryJo.Kochen...@openlmis.org>> wrote:
Hello Product Committee,

I’m sending out a friendly reminder for the following Action Items from the last Product Committee meeting.

□    Mary Jo Kochendorfer<https://openlmis.atlassian.net/wiki/display/~maryjo.kochendorfer> will circulate instructions for requested UAT during the Jan 17th meeting. Will include test scripts/stories and a demo of the system.
□    Mary Jo Kochendorfer<https://openlmis.atlassian.net/wiki/display/~maryjo.kochendorfer> will present an updated scope for 3.0 on Jan 17th
□    Ashraf Islam<https://openlmis.atlassian.net/wiki/display/~ashraf_islam> will share example report specifications
□    Chris George<https://openlmis.atlassian.net/wiki/display/~chrisgeorge> and/or Danni Yu<https://openlmis.atlassian.net/wiki/display/~dyu> will share example report specifications

□    All participants are welcome to share example diagrams/specifications so our Functional Spec Toolkit is the best.

Please share your resources as soon as you can. We would like to leverage the information for the gap analysis work.  In addition, it would be greatly appreciated if anyone would be willing to share UAT test scripts/stories used in the past to test OpenLMIS/eLMIS, so I may build off of those.

Website: Request for Suport
The team is moving forward with the revamping of the OpenLMIS website. Please let me know if anyone from the PC is willing to review and provide feedback on product related sections of the website content.  For example, the feature list for OpenLMIS.  Many of you have been working on business development and socializing OpenLMIS so I’d like to reflect those learnings and reflect your opinions. Your input would be greatly appreciated. Let me know directly if you are willing to review some website content.

Thanks,
Mary Jo

P.S. Next product committee meeting is the 17th of January

--
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+unsub...@googlegroups.com<mailto:openlmis_product_committee+unsubscribe@googlegroups.com>.
To post to this group, send email to openlmis_product_committee@googlegroups.com<mailto:openlmis_product_committee@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis_product_committee/DM5PR02MB23777A2BD749719BCF842E7C81640%40DM5PR02MB2377.namprd02.prod.outlook.com<https://groups.google.com/d/msgid/openlmis_product_committee/DM5PR02MB23777A2BD749719BCF842E7C81640%40DM5PR02MB2377.namprd02.prod.outlook.com?utm_medium=email&utm_source=footer>.

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+unsub...@googlegroups.com<mailto:openlmis_product_committee+unsubscribe@googlegroups.com>.
To post to this group, send email to openlmis_product_committee@googlegroups.com<mailto:openlmis_product_committee@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis_product_committee/CAMdhj_CQCUum7bJuf90gJ_cdEDtLWWAs%2BtonME0Z15fv6M%2BFRg%40mail.gmail.com<https://groups.google.com/d/msgid/openlmis_product_committee/CAMdhj_CQCUum7bJuf90gJ_cdEDtLWWAs%2BtonME0Z15fv6M%2BFRg%40mail.gmail.com?utm_medium=email&utm_source=footer>.