User Tools

Site Tools


groups:healthcare:2018_11_30_hcwg

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
groups:healthcare:2018_11_30_hcwg [2018/12/01 04:24]
Rich Bloch [Community Announcements]
groups:healthcare:2018_11_30_hcwg [2018/12/01 04:38] (current)
Rich Bloch
Line 33: Line 33:
   * Adrian Berg   * Adrian Berg
   * Leonard Edwin   * Leonard Edwin
-  * Jeff Stollman ​+  * Jeff Stollman ​(Recording)
   * Satarupa Bose   * Satarupa Bose
   * Bryan McWhorter (Guest Speaker)   * Bryan McWhorter (Guest Speaker)
Line 52: Line 52:
     * Tell us where you're geographically located     * Tell us where you're geographically located
     * Share with us your interests in healthcare in general, and blockchain technologies in specific     * Share with us your interests in healthcare in general, and blockchain technologies in specific
 +
 +<WRAP box>
 +Linwan - healthcare interoperability:​ health information exchange and working on blockchain use cases for EMR\\
 +Kamlesh - exploring Hyperledger Fabric use cases for a client (company: Diaspark located in the US)
 +</​WRAP>​
  
 ===== HLHC-SIG Guest Speaker(s) ===== ===== HLHC-SIG Guest Speaker(s) =====
Line 58: Line 63:
     * Bryan McWhorter, Partner at [[https://​www.knobbe.com/​|Knobbe Martens]], Seattle, Washington, USA. Bryan focuses on patent procurement and dispute resolution, particularly for companies in the software, telecommunications,​ and food and beverage areas.  ​     * Bryan McWhorter, Partner at [[https://​www.knobbe.com/​|Knobbe Martens]], Seattle, Washington, USA. Bryan focuses on patent procurement and dispute resolution, particularly for companies in the software, telecommunications,​ and food and beverage areas.  ​
  
 +<WRAP box>
 +* Enterprise collaboration (how do we approach selective sharing IP)
 +
 +  * Presenters:
 +    * Ken Moyle, Chair of Public Policy Committee for Electronic Signature and Records Association
 +    * Bryan McWhorter, IP attorney at Knobbe Martens
 +
 +  * Copyrights vests in creator unless explicit transfer via "work for hire" contract or clause in employment agreement (in most jurisdictions)
 +  * Copyrights don't require formal registration
 +  * General Public License ("​copyleft"​) open-source agreements require anyone who uses and/or enhances code to make it publicly available
 +    * Consider it like a virus: once infected, it spreads to anything that it touches
 +    * Lesser General Public License agreement allows some ability to retain private rights of open-source software that is enhanced by private parties
 +      * Mozilla license ​ -- provide least ability for private licenses
 +      * Apache license ​ -- greater ability to patent enhancements (Hyperledger uses Apache 2.0 license)
 +
 +  * Apache 2.0 tends to be viral -- all derivative works are covered by Apache 2.0
 +  * Patent rights are automatically granted under this
 +  * If you provide code to Hyperledger,​ anyone can use it without copyright and you give up patent protection rights, you can still create unique derivative works and copyright them
 +  * It includes a promise not to sue people who use Apache 2.0 software for patent infringement
 +    * MIT license ​ -- most ability for private use
 +    * Unlicense -- merely limits liability
 +
 +  * Two issues
 +    * What are the limitations for me to use it?
 +    * What are the limitations for me to capitalize my IP built on top of open-source licensed code?
 +
 +  * Patents vs copyrights
 +    * Patents cover "​ideas"​
 +    * Copyrights cover code
 +
 +  * Questions
 +    * What's benefit of patent vs cheaper copyright?
 +      * Copyright covers only code, not the concept which could be implemented using different code
 +</​WRAP>​
  
 ===== Community Announcements ===== ===== Community Announcements =====
Line 77: Line 116:
   * Discussion tabled for next meeting (time constrained)   * Discussion tabled for next meeting (time constrained)
 </​WRAP>​ </​WRAP>​
 +
 ===== HLHC-SIG Subgroup Updates ===== ===== HLHC-SIG Subgroup Updates =====
  
Line 82: Line 122:
   * Payer Subgroup (Raveesh Dewan, Lead)   * Payer Subgroup (Raveesh Dewan, Lead)
   * EMR Subgroup (Rich Bloch, Acting Lead)   * EMR Subgroup (Rich Bloch, Acting Lead)
 +
 +<WRAP box>
 +  * Discussion tabled for next meeting (time constrained)
 +</​WRAP>​
  
 ===== HLHC-SIG Ad Hoc Team Updates ===== ===== HLHC-SIG Ad Hoc Team Updates =====
Line 95: Line 139:
       * Fundamentally to understand the future direction of the EMR Subgroup       * Fundamentally to understand the future direction of the EMR Subgroup
       * To determine if a revised EMR Subgroup strategy might also apply to other subgroups       * To determine if a revised EMR Subgroup strategy might also apply to other subgroups
 +
 +<WRAP box>
 +  * Discussion tabled for next meeting (time constrained)
 +</​WRAP>​
  
 ===== Old Business ===== ===== Old Business =====
Line 104: Line 152:
   * A HIPAA-compliant Hyperledger (Rich)   * A HIPAA-compliant Hyperledger (Rich)
     *** Discussion: not much community feedback to date... next steps?**     *** Discussion: not much community feedback to date... next steps?**
 +
 +<WRAP box>
 +  * Discussion tabled for next meeting (time constrained)
 +</​WRAP>​
  
 ===== New Business ===== ===== New Business =====
Line 119: Line 171:
     * Ostensibly used for onboarding a new chair/​officer,​ but could be used for new members?     * Ostensibly used for onboarding a new chair/​officer,​ but could be used for new members?
     * **Discussion:​ would there be good utility/​value to something like this?**     * **Discussion:​ would there be good utility/​value to something like this?**
 +
 +<WRAP box>
 +  * Change from HLHCWG to HLCH-SIG announced. All other discussions tabled for next meeting (time constrained)
 +</​WRAP>​
  
 ===== Next Meeting ===== ===== Next Meeting =====
groups/healthcare/2018_11_30_hcwg.txt ยท Last modified: 2018/12/01 04:38 by Rich Bloch