January 23, 2018 - RESCHEDULED from January 16

Documenting what we want/need to change

Consensus around review with Product Committee

Assign pieces to draft 

Enforcement of branding? (put forth by Ona/Matt Berg (Unlicensed))

Allow access to the info@ email address to create more transparency for the community. In terms of business proposal development, the community could be in a better position to respond. 

Carl: Also some minor logistical things like changing the list of members and removing business processes. And we don't have a way to actually change the charter so we'll have to figure out whether we need a process (small majority?) for changing/approving the charter. 

Matt: Brought up the enforcement of branding, we are getting queries from people who are current users of OpenLMIS who didn't know they were using OpenLMIS. The challenge for open source is that anyone has access to use it, but you have people using it but not using it properly and that could hurt the brand. 

RAML - an example of branding/copyrighting 

Facing this with OpenSRP, we want to be able to protect the modules, saying it's OpenSRP certified/trademarked, and restricts people from doing whatever they want with the code, which is open source. A way to ensure that the quality of the implementation is maintained. This opens up more leverage for the community to manage. 

Kyle: A nuanced opinion. My initial response is that when you start branding things, we need to think this through as we look at technical quality of the product. We're seeing several products in the public good space, OpenSRP, OpenLMIS, and this almost moves them into a space with commercial background, with customers who understand the difference between global public goods and other types of systems. Also if we fast forward 2-3 years, we will have country owned implementations. Malawi and others - what does that mean in terms of the global product? 

Jake: Would suggest that we revisit the license. 

Kaleb: I see the value of having a trademark or a recognizable name. But I do also appreciate the fact that countries are owning it and that they have their own acronyms - "country owned." How do we find that balance of country ownership, the shared value proposition, feeding back into the global good. 

Tenly: The "powered by OpenLMIS" logo

Matt: But do we want an old fork to be labeled as OpenLMIS? Could create confusion. 

Kaleb: That's a good point, we need to consider whether old versions would have that mark. How do people know that the new version, version 3, is the "trusted brand." 

Carl: Is OpenLMIS trademarked? 

Jake: No, it's not. 

Kyle: Need to distinguish between copyright and trademark. We need to decide what to manage and control. 

Need to know what copyrights/trademarks are. Need to look at trademarking the name. 

Promoting shared re-use - if donors want to invest in this tool, we could go down the path where OpenMRS has been with many forks. 

Action item(s): 

Working group to review RAML 

Discuss who would hold the trademark/copyright? 

Someone from DIAL to particpiate (Michael) - give a high-level summary of what options are available 

Matt, Jake, Carl, Ashraf, Tenly , MJ 

Set up a call with Michael 

Carl Leitner

Jake Watson (Deactivated)

Malawi

Carl was in Malawi for the last OpenHIE meeting, worked on their eHealth architecture, facility registry, and OpenLMIS. In the notes for the call we looked at how OpenHIE architecture could be adapted to the Malawian context and how their currently being developed facility register, could interface with OpenLMIS and DHIS2 and how to manage the metadata. 

In two weeks Carl will be in Angola for a "tech camp" that involves the DHIS2 and OpenLMIS implementations. Would be great to get contacts for some of the potential connection points. 

Jake: Kyle, it would be great to hook Carl up with Becky and team. Dercio gave a slight orientation to the new OpenLMIS advisor that was hired for Angola. There is a new MIS advisor, should be in country this week so should be settled and ready to meet. 

Kyle: DHIS2 implementation team, through PSI. They reached out to work together and coordinate in Angola. Especially around these connection points, the master facility list, master data management, governance, etc. Good timing. Make sure that the PSM folks in Angola can meet with Carl and PSI and have time for the meetings 

Carl: Make specific recommendations for attendance. Just want to doublecheck that the right people are on the list. PSI is doing the logistics of the tech camp. We are supporting for facilitation and content. 

Jake: We have a list of attendees to the LMIS workshop that Dercio and Langa led. Jake or Kyle can share with Carl. 

Global FP VAN

Ramy was in touch with Jake to let him know that Malawi and Nigeria were selected for 18 month projects. Above the central medical store (global VAN), and Stew Stremel came to VR a couple weeks ago. They are in the vendor selection stage, 1Network, Intellicog, etc., we will work with them in Malawi to share what we know. Ramy mentioned if there is an opportunity to augment OpenLMIS to facilitate the data sharing, that Ramy had some HQ funds for this project. No action items yet but we're trying ot suppor that effort. 

LB: Questions regarding that to make sure we're staying in the loop. My only concern about this RFP is that it's not a data analytics tool but a workflow tool. What does that mean, what additional data transformation will need to happen, including the eLMIS. It is not as clear cut as they imply it is. 

Jake: Let them know that there is no product master, we didn't take advantage of the GS1 product model because CMST wasn't quite ready. Joyce has been driving this in Malawi, but it wasn't clear whether she knew much about OpenLMIS.

Kyle: I don't know about her level of knowledge of OpenLMIS. Taking a step back, the global FP VAN is an interesting/complimentatary product in this space. The pilots in Nigeria and Malawi will offer us insight into what we've been working on. Interoperability and more standardized data exchange processes. We should keep coming back with updates on the Malawi VAN to the Governance committee, from the PSM side. We are at the forefront for both the OpenLMIS deployment but also the FP VAN. It's still at the evaluation stage and we are separating out teams here for evaluation and implementation, but once the vendor is selected, I see more information sharing on whichever vendor it is and the country specific implementations. We will likely see more of this in the future, maybe not Global VAN, but derivitives off of this for broader data warehousing, GDSN sync, workflows, etc. 

LB: This is only for family planning products, need to keep in mind the broader impact this may have on multiple commodity groups. Keep that as a conversation point. 

Jake: Kelly might be receptive to some proposals in Tanzania by Feb. 1 so we are trying to get a reprioritized list from Alfred for the gap work. 

LB: Need to have the conversation soon because she may not remain in her position too much longer. 

Alfred: Tomorrow we will sit with 5 super users that are non GHSC or USAID projects. Going to talk with program pharmacists, regional pharmacists, hospital pharmacists, to get their inputs. Hopefully we will get something different from TZ. 

Digital Square: Carl will be interim director starting Feb. 2. Be aware that Carl's plate is full. We are bringing in new resources to fill that gap, but just be aware that this is coming.