Let's just keep it as-is for tomorrow tillour next reguarly
scheduled telecon meeting.
On 7/13/2020 1:13 PM,
wrote:
That would typically work for me as well.
Scott?
I have another meeting tomorrow, however
and will not be able to join at either time.
Elysa
From: Waters, Jeffry H (53622)
CIV USN NIWC PACIFIC CA (USA) <>
Sent: Monday, July 13, 2020 2:52 PM
To: Rex Brooks <> ;
; 'Scott M. Robertson'
<> ;
Subject: RE: [Non-DoD Source] Re: [emergency-rim]
Ongoing conflict with RIM meetings
I could do an
hour earlier, but I have conflicts an hour later.
--Jeff
From:
<>
On Behalf
Of Rex Brooks
Sent: Monday, July 13, 2020 7:05 AM
To:
; 'Scott M. Robertson'
<> ;
Subject: [Non-DoD Source] Re: [emergency-rim]
Ongoing conflict with RIM meetings
Moving back an hour works for me.
Rex
On 7/12/2020 10:19 AM,
wrote:
Scott, I’m sorry to see this is now a
conflict for you. Should we consider moving this call to an
hour later? Elysa
From:
<>
On Behalf Of Scott M. Robertson
Sent: Friday, July 10, 2020 6:57 PM
To:
Subject: [emergency-rim] Ongoing conflict with
RIM meetings
I have been assigned to a new project
which has meetings every Tuesday at 8am PT. I will not be
able to join the RIM calls unless (a) a project call
instance is cancelled, or (b) or I am specifically needed on
the RIM call.
Priorities are shifting …
Be well,
-Scott
Scott
M Robertson
PharmD, RPh, FHL7, GISP,
CISSP
Principal Technology
Consultant
Kaiser
Permanente
Technology
Risk Office
Health IT Strategy & Policy
310-200-0231
tro.kp.org
----------
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.
This
email has been checked for viruses by Avast
antivirus software.
www.avast.com
