Thanks Chet.
Cheers,
Rex
On 2/14/2019 9:55 AM, Chet Ensign
wrote:
Thanks Rex. That will work just fine.Â
/chet
Hi Chet,
Everyone,
Per our
discussion during today's Emergency Member Section
Steering Committee, we want to approve a new
EDXL-HAVE-v2.0-CS with this non-substantive title
change. Elysa is going to be traveling to remote
worksites around the globe for the next three weeks at
least, and I'd like to get this teed up during this
time. So as a first step, I will create a new working
draft over the course of next week and post it to HAVE
SC Documents by next Tuesday, February 19, 2019.
I'm asking
here that members of the HAVE SC and any interested
party review the working draft document to ensure that
no other previously unnoticed changes are needed. Please
send any such changes to me for inclusion in a new
working draft, if needed, by Friday, February 22, 2019.
Elysa, could
you please schedule a HAVE SC meeting for Monday March
4, 2019 at 12:00 p.m. noon ET. Hopefully, we should be
able to vote on releasing the latest working draft to
the TC for approval as a new Committee Specification
Draft, allowing us to request a Special Majority Vote
advancing the document to Committee Specification
status. This TC approval could occur at either the March
5, or 19, 2019 TC Meetings.
Chet, did I
miss anything in here?
This is a
typically optimistic schedule, but we will adapt as we
can,
Cheers,
Rex
On
2/12/2019 12:40 PM, Chet Ensign wrote:
Hi Scott,Â
No, errata are limited to OASIS Standards, mainly
because it is easy enough to approve a new CS.Â
I agree that if you are going to go through the
approval process, another look is a good idea.Â
I'll stand by for all you to let me know when we
need to take the next steps.Â
Best,Â
/chet
An unfortunate oversight.Â
Apparently we (I) read the content, but not the
title. I will admit that I didnât notice it
until Rex pointed it out this morning.
Â
Chet, is an errata possible?Â
If not, we will need to the CS02 path.
Â
For either CS02 or errata, I
suggest that we first to an editorial-only
(offline) review. If we have one (glaring)
edit, we probably have others.
Â
I will contact HL7. For
either route (CS02 or errata), HL7 will need to
update the copy in their standards library.Â
What they have does say âProposedâ.
Â
-Scott
Scott
M Robertson
Principal
Technology Consultant
PharmD, RPh,
FHL7, GISP, CISSP
Â
Kaiser
Permanente
Technology
Risk Office | Health IT Strategy
& Policy
310-200-0231 (office)
tro.kp.org
----------
kp.org/thrive
Â
From: Chet Ensign <chet.ensign@oasis-open.org>
Sent: Tuesday, February 12, 2019 10:45 AM
To: Elysa Jones <elysajones@yahoo.com>
Cc: Rex Brooks <rexb@starbourne.com>;
Scott M. Robertson <Scott.M.Robertson@kp.org>;
Paul Knight <paul.knight@oasis-open.org>
Subject: Re: Important EDXL-HAVE-v2.0
Question
Â
Caution:
This email
came from outside Kaiser Permanente. Do not
open attachments or click on links if you do
not recognize the sender.
Hi Elysa,Â
The problem is that it is
now published and announced. Once specs are
published, I don't change the content
because they have become part of the
historical record.Â
No one told us that
needed to change. The CS was there and in
fact was reapproved while awaiting go-ahead
from HL7 to fix a non-material error.Â
What we could do I
suppose is approve a new CS with that as the
non-material change and then I can publish
it as CS02. Do you want to do that?Â
Â
I agree it
should be changed. That is what I thought
we were working toward. I understand we
had to say âproposedâ until HL7 agreed but
assumed then the âproposedâ word would be
removed. I donât understand why that
canât be done.
Sent
from Yahoo Mail for iPhone
On
Tuesday, February 12, 2019, 12:23 PM,
rexbroo <rexb@starbourne.com>
wrote:
Thanks for the clarification Chet.
We will carry on. I request that
Elysa and Scott weigh in on changing
it on the standards. I think it
should be changed, but that's just
one of three.
Thanks Again.
Much Appreciated,
Rex
On 2/12/2019
10:13 AM, Chet Ensign wrote:
Hi Rex -
Unfortunately, there isn't
anything I can do about that
now. The document was approved
with that designation by both
the TC (twice) and by the HL7
folks. Now that it is published
and part of the public record, I
don't go back and change it. I
can fix it on the standards page
(https://www.oasis-open.org/standards#edxl-have-20)
and I can fix it when you next
approve an update to the work.Â
Â
--
--
Chief
Technical Community
Steward
OASIS: Advancing open
standards for the
information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393Â
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.
--
/chetÂ
----------------
Chet Ensign
Chief
Technical Community Steward
OASIS: Advancing open standards for
the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393Â
--
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670
--
/chetÂ
----------------
Chet Ensign
Chief
Technical Community Steward
OASIS: Advancing open standards for the
information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393Â
--
Rex Brooks
Starbourne Communications Design
Email: rexb@starbourne.com
GeoAddress:
1361 Addison St. Apt. A
Berkeley, CA 94702
Phone: 510-898-0670
|