OASIS Open Mailing List Archives  ·  All Lists  ·  emergency-have  ·  2018-04

emergency-have — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

FW: Publication process clarification: OASIS/HL7 HAVE v2.0


For possible discussion on today’s call Scott M Robertson, PharmD, RPh, FHL7 Principal Technology Consultant Health IT Strategy & Policy Kaiser Permanente Information Technology Technology Risk Office Office of the CTRO tro.kp.org Pasadena / Torrance, CA 310-200-0231 (office) [email protected] kp.org/thrive From: Scott M. Robertson Sent: Thursday, March 22, 2018 10:46 AM To: 'Karen Van Hentenryck (HL7)' <[email protected]>; Lynn Laakso (HL7) <[email protected]> Cc: Elysa Jones <[email protected]>; Sandra J. Stuart <[email protected]> Subject: RE: Publication process clarification: OASIS/HL7 HAVE v2.0 Use the standard HL7 cover matter but indicate that the document is jointly copyrighted by HL7 and Oasis. If we do this, Oasis can publish a copy of the document on their own website using their own cover matter that also reflects joint copyright <smr>This is an option – better than the TEP option – but I was trying to avoid having two different “official” documents 1 </smr> We can create a single cover page that combines elements of both HL7 and Oasis cover matter <smr>This is what I was attempted with the “… Joint Format.doc” file</smr> I forgot to mention:  once we come to an agreement (not necessarily on every detail and word), I will take this to OASIS to get their by-in.  Rather than a decision, you could rank the options (now three, see below) and that will go to OASIS.  Publication would “begin” (as described in my first thread) once HL7/OASIS agreement is reached Now three options: SMR opinion 1 As done with TEP:  OASIS publishes with the OASIS cover matter.  HL7 publishes with HL7 cover matter in front of OASIS cover matter Least desirable Two documents:  OASIS publishes with OASIS cover matter plus note of joint publication.  HL7 publishes with HL7 cover matter plus note of joint publication. Works One document:  Combined OASIS/HL7 cover matter. Most desirable 1 Although I’m including my perspective, whatever HL7 and OASIS agree on is what will be done. -Scott Scott M Robertson, PharmD, RPh, FHL7 Principal Technology Consultant Health IT Strategy & Policy Kaiser Permanente Information Technology Technology Risk Office Office of the CTRO tro.kp.org Pasadena / Torrance, CA 310-200-0231 (office) [email protected] kp.org/thrive From: Karen Van Hentenryck (HL7) [ mailto:[email protected] ] Sent: Thursday, March 22, 2018 10:15 AM To: Scott M. Robertson < [email protected] >; Lynn Laakso (HL7) < [email protected] > Cc: Elysa Jones < [email protected] >; Sandra J. Stuart < [email protected] > Subject: RE: Publication process clarification: OASIS/HL7 HAVE v2.0 Caution: This email came from outside Kaiser Permanente. Do not open attachments or click on links if you do not recognize the sender. Scott, Elysa: We can one of two things: Use the standard HL7 cover matter but indicate that the document is jointly copyrighted by HL7 and Oasis. If we do this, Oasis can publish a copy of the document on their own website using their own cover matter that also reflects joint copyright We can create a single cover page that combines elements of both HL7 and Oasis cover matter Please advise on your preference. Thanks, Karen From: Scott M. Robertson < [email protected] > Sent: Wednesday, March 21, 2018 9:58 PM To: Lynn Laakso (HL7) < [email protected] >; Karen Van Hentenryck (HL7) < [email protected] > Cc: Elysa Jones < [email protected] >; [email protected] Subject: Publication process clarification: OASIS/HL7 HAVE v2.0 Not sure if this is for Karen, Lynn, or someone else.  Please forward as appropriate. The HAVE 2.0 document has been updated with all edits from the ballot, the reconciliation package has been posted, and all negatives have been withdrawn.  Next is to move to publication, but I need to clarify the process since this is a joint publication.  There are two paths I see for publication: (1) follow the path used for the last HL7/OASIS joint document (V271_IG_TRANSWOASISTEP_R1_INFORM_2016JUL (TEP)); or (2) merge the front content and copyright. The process used for TEP produced a document structure as: HL7 title & front matter HL7 copyright (same copyright as other HL7 documents) OASIS title & front matter OASIS copyright (same copyright as other OASIS documents) Content Merging the front content would produce a document as: OASIS/HL7 title and front matter OASIS/HL7 joint copyright Content There are 2 versions of HAVE v2.0 attached edxl-have-v2.0-wd04+hl7 edits.doc – the version for the TEP Path edxl-have-v2.0-wd04+hl7 edits+Joint format.doc – the version for the Merged Front Content path. I did the merging.  Since the primary content came from OASIS, I used the OASIS front content as the base.  I added in a few points from the HL7 title/front matter to the OASIS title/front matter.  Copyright also used OASIS as a base.  However, rather than reconciling the two IP postures, I maintained the OASIS IP posture and revised some points to reflect the joint relationship.  My logic for starting with the OASIS text is that since both IP postures are, for the most part, “free IP”, then the issue to be reinforced is the joint ownership.  The joint copyright appears to align with the “Joint Work Product Copyright” clause in the HL7/OASIS SOU (my interpretation). TEP path (as determined by reviewing files on oasis-open.org and HL7.org) Merged Front Content path HL7 opts for “TEP Path” HL7 opts for “Merged Front Content path” Send document to OASIS HQ for Final editing.  (with “© OASIS Open 2016. All Rights Reserved.” footer) Creation of DOCX, PDF and HTML versions. Final OASIS documents posted to oasis-open.org HL7 reviews revised front content Merged title / front matter Merged copyright (could have editing loops) OASIS DOCX version forwarded to HL7 HQ HL7 front matter and copyright added Document footer updated to “© Health Level Seven International, OASIS Open 2016. All Rights Reserved.” Creation of PDF HL7 PDF version posted to HL7.org HL7 approved document to OASIS HQ for front content review Merged titles / front matter Merged copyright (if merged content changed, will go back to HL7 for review) This results in two versions of the PDF, one with (on HL7.org) and one without (on oasis-open.org) the HL7 copyright. OASIS & HL7 approved document to OASIS HQ for final editing Creation of DOCX, PDF, and HTML formats Posting of 3 formats to oasis-open.org HL7 notified of documents posted to oasis-open.org Retrieve DOCX or PDF format to post to HL7.org -or- post link to oasis-open.org on HL7.org Results in consistent document content on both oasis-open.org and HL7.org The question then is:  do you want to go with the prior process (as done with TEP) or work through the merge title, front matter, and copyright. Please let me know which direction is selected. -Scott Scott M Robertson, PharmD, RPh, FHL7 Principal Technology Consultant Health IT Strategy & Policy Kaiser Permanente Information Technology Technology Risk Office Office of the CTRO tro.kp.org Pasadena / Torrance, CA 310-200-0231 (office) [email protected] kp.org/thrive NOTICE TO RECIPIENT:   If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents.  If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them.  Thank you. NOTICE TO RECIPIENT:   If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents.   If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them.   Thank you. Attachment: edxl-have-v2.0-wd04+hl7 edits+Joint format.doc Description: edxl-have-v2.0-wd04+hl7 edits+Joint format.doc

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]