User Tools

Site Tools



Hyperledger Healthcare Working Group Charter

1. Mission of the Hyperledger Healthcare working group (“HLHC”)

The HLHC’s mission is to house and foster technical and business-level conversations about appropriate applications for blockchain technology in the healthcare industry. These conversations will initially be broad and educational, but will transition to focus on identifying opportunities for near-term collaboration between participants on common software to implement a given application. If appropriately scoped and resourced, these conversations will lead to one or more proposals for new software development efforts to be hosted at Hyperledger.

2. Membership

The HLHC Group membership is composed of individuals and companies interested in identifying blockchain-related use cases applicable to the healthcare industry and potential collaborative software development projects to help interested parties address those use cases. Participating individuals and companies need not be members of the Hyperledger Project.

3. Discussion Format and Content

The HLHC will host meetings and discussions (in person and online) for member contributions that are intended to accelerate its mission. Initial topics will include, but are not limited to:

  1. Discovery and exploration of healthcare-related blockchain use cases that address real world problems
    1. Explore fundamental Distributed Ledger applications first, such as establishing registries, interoperability and identities
    2. Later, look to expand to more advanced topics, such as smart contracts and process automation
  2. Technical opportunities to address those use cases

4. Operating Principles

  1. HLHC member communication mechanisms
    1. The primary forum for this Working Group will be a group email list. This list shall be open to any subscriber and publicly archived, and moderated by Hyperledger staff or other volunteers. The email list should be considered the discussion system of record for the community.
    2. The group may decide to also host conference phone calls, on an ad-hoc or recurring basis, which can be convened and minuted by Hyperledger staff. This may be useful as a way to motivate the community towards a consensus on a position, or hear from those for whom email is too noisy. However notes should be posted back to the email list, and important discussions or decisions should not be closed without input from the list
    3. The group may also decide to meet face-to-face, for example at a healthcare conference where many participants will also be attending. As with phone calls, the mailing list should be updated on important points raised or notes taken, and important discussions or decisions should be brought to the list.
    4. The group may elect to shift to a different tool than email down the road, so long as the Linux Foundation agrees.

5. Antitrust Guidelines

  1. All members shall abide by The Linux Foundation Antitrust Policy available at:​.
  2. All members shall encourage open participation from any organization able to meet the membership requirements, regardless of competitive interests. Put another way, the HLHC Group shall not seek to exclude members based on any criteria, requirements or reasons other than those used for all members.

6.General Rules and Operations

The HLHC shall be conducted so as to:

  1. Engage in the work of the project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of The Linux Foundation in the open source software community;
  2. Respect the rights of all trademark owners, including any branding and usage guidelines;
  3. Engage The Linux Foundation for all HLHC press and analyst relations activities;
  4. Upon request, provide information regarding Project participation, including information regarding attendance at Project-sponsored events, to The Linux Foundation;
  5. Coordinate with The Linux Foundation in relation to any websites created directly for HLHC; and
  6. Operate under such rules and procedures as may from time to time be required by The Linux Foundation.
  7. Under no circumstances shall The Linux Foundation be expected or required to undertake any action on behalf of HLHC that is inconsistent with the tax exempt purpose of The Linux Foundation.

7. Intellectual Property Policy [With regards to any software or IP contribution, including methods proposed in email]

  1. All contributions shall be accompanied by a Developer Certificate of Origin sign-off (​).
  2. All new inbound code contributions to HLHC shall be made under the Apache License, Version 2.0 (available at ​​). All documentation will be contributed to and made available to HLHC under the Creative Commons Attribution 4.0 International License (available at
  3. All outbound code will be made available under the Apache license.
groups/healthcare/wg-governance-charter.txt · Last modified: 2018/09/30 23:15 by Mikhail Elias