[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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
310-200-0231 (office) From: Scott M. Robertson
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:
1Although 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
310-200-0231 (office) From: Karen Van Hentenryck (HL7) [mailto:karenvan@hl7.org]
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:
Please advise on your preference. Thanks, Karen From: Scott M. Robertson <Scott.M.Robertson@kp.org>
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:
Merging the front content would produce a document as:
There are 2 versions of HAVE v2.0 attached
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).
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
310-200-0231 (office) 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] | [List Home]