Russ is correct in that the data is your own and that you are free to share it; however, the Clarity data model is Epic's IP. I.e., if you want to share the format of the resultant data set (or the data itself) among your peers then we have no concerns with that, but if you want to share SQL code that directly references the Clarity data model then we would ask that you do so in an appropriate manner.
Here are two appropriate ways that organizations have followed in the past: 1. Directly send the SQL scripts between two organizations using a secure communication mechanism (this is assuming both organizations are members of the Epic community) 2. Upload the SQL scripts to the Report Repository<https://documentation.epic.com/DataHandbook/Reports/ReportSearch> on Epic's UserWeb where any member of the Epic community can securely login and access them (here's an example script<https://documentation.epic.com/DataHandbook/Reports/Details/9000129>) If these methods are unacceptable for one reason or another then please let me know your concerns. I'm happy to work with you to figure out something that will meet your needs and allow us to fulfill our obligations to protect our IP. Rob Szymanski | Cogito R&D | Epic From: [email protected] [mailto:[email protected]] On Behalf Of daniella meeker Sent: Wednesday, August 06, 2014 1:00 AM To: Campbell, James R Cc: Waitman Russ; Rob Szymanski; STANDARDS GPC; Brown Jeff; Nancy Smider; Don Torok ([email protected]); Mark Khayter ([email protected]); Kahn, Michael ([email protected]); Patrick Ryan ([email protected]); Murphy Shawn; Apathy Nate; McClay, James C Subject: Re: Epic ETL repo I suppose that one solution might be to take a similar approach that we do to PHI, replacing epic table and field names with hash where encryption keys are only available to epic/clarity clients. This seems equal or lesser in risk as Epic's vulnerability to adversaries that might be interested in hacking healthcare databases. Fortunatly for the sake of privacy, most adversaries would find themselves as discombobulated as normal humans when confronted with Clarity for the first time. On Tuesday, August 5, 2014, Campbell, James R <[email protected]<mailto:[email protected]>> wrote: Daniella Epic has offered to host the ETL repository. It will be behind the Epic Userweb firewall. Russ thinks that it is not Epic's intellectual property, our data is our own, and we should host it on PCORI or Babel. I am frankly uncertain as to proper resolution of the issue. I am copying the principals in this exchange because we at Nebraska have lots of work to share with the community as well. I would like to decide where we will do that. Jim James R. Campbell MD [email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');> Office: 402-559-7505 Secretary: 402-559-7299 Pager: 402-888-1230 On Aug 5, 2014, at 2:01 PM, "Meeker, Daniella" <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: Hi Jim, Do we have an Epic-sanctioned repository for ETL documents from Clarity? We have a github account for internal circulation, but you mentioned that Epic would not be friendly to this. Don and Mark have made significant progress in ETL from one of our Clarity instances to OMOP, and I'd like to share them with others in the community. Some interesting things have come up for the PCORnet use case - for example, how to record the location of a visit if it might be used for recruiting purposes. Thanks, Daniella __________________________________________________________________________ This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender.
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
