Next in thread →
Next in month →
RE: HAVE call today
Thanks Robert, I have it now. As Darryl advised, I’ll make my contributions in an external document and provide to you guys who are keeper of the spec. I hope you will be able to join the call today at 11CDT/12EDT so we can divide up the work and concur this HAVE 2.0 PR! Cheers, Elysa From: O'Connor, Robert [mailto:Robert.O'] Sent: Monday, July 31, 2017 8:36 AM To: Elysa Jones <>; 'Darrell O'Donnell' <> Cc: 'HAVE SC' <>; ; 'Tim Grapes' <> Subject: RE: HAVE call today This looks like the document I uploaded to the OASIS SVN last month. The link is: https://tools.oasis-open.org/version-control/svn/emergency/HAVE/edxl-have-v2.0-wd03.doc If you need help updating it, I’ll set aside some time today and we’ll get it updated and posted to the SVN. Thanks, Robert From: Elysa Jones [mailto:] Sent: Monday, July 31, 2017 8:00 AM To: 'Darrell O'Donnell' <> Cc: 'HAVE SC' <>; ; 'Tim Grapes' <>; O'Connor, Robert <Robert.O'> Subject: RE: HAVE call today Will do, thank you! Elysa From: Darrell O'Donnell [mailto:] Sent: Monday, July 31, 2017 7:52 AM To: Elysa Jones <> Cc: HAVE SC <>; ; Tim Grapes <>; O'Connor, Robert <Robert.O'> Subject: Re: HAVE call today It is in SVN at the TC level. Attached here. I suggest just looking for the blank spot and crafting your words in a separate clean (and small) doc. We can merge the verbiage in easily. On Mon, Jul 31, 2017 at 8:12 AM, Elysa Jones <> wrote: Friends, We will have our HAVE call at 12EDT today. We must make some progress on HAVE 2.0. I was unable to find the WD where I need to input my comments re HL7 work. Please post it to this list. Cheers, Elysa Jones Disclaimer This e-mail and its attachments may contain privileged or confidential information. Please consult IEM before sharing this e-mail with anyone else. If you are not the intended recipient of this e-mail, you may not use, copy, distribute, or forward this e-mail. If you received this e-mail by mistake, please notify IEM and immediately delete this message. Although IEM does not know of any viruses present in this e-mail, you are encouraged to scan it using antivirus software, and IEM will not accept responsibility for any loss or damage arising from this e-mail. This e-mail neither constitutes an agreement to conduct transactions by electronic means nor creates any legally binding contract or enforceable obligation in the absence of a fully signed written contract. IEM takes no responsibility for any unauthorized reliance on the contents of this e-mail.
Next in thread →
Next in month →