EM Reference Information Model SC

 View Only
  • 1.  Ongoing conflict with RIM meetings

    Posted 07-10-2020 23:58
    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.


  • 2.  Re: [emergency-rim] Ongoing conflict with RIM meetings

    Posted 07-11-2020 03:34
    Thanks for notification Scott, I appreciate it. Cheers and best of luck with the new assignment, Rex On 7/10/2020 4:57 PM, Scott M. Robertson wrote: 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


  • 3.  RE: [emergency-rim] Ongoing conflict with RIM meetings

    Posted 07-12-2020 17:20
    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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Scott M. Robertson Sent: Friday, July 10, 2020 6:57 PM To: emergency-rim@lists.oasis-open.org 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.


  • 4.  Re: [emergency-rim] Ongoing conflict with RIM meetings

    Posted 07-13-2020 14:05
    Moving back an hour works for me. Rex On 7/12/2020 10:19 AM, elysajones@yahoo.com 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Scott M. Robertson Sent: Friday, July 10, 2020 6:57 PM To: emergency-rim@lists.oasis-open.org 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


  • 5.  RE: [Non-DoD Source] Re: [emergency-rim] Ongoing conflict with RIM meetings

    Posted 07-13-2020 19:53
    I could do an hour earlier, but I have conflicts an hour later.   --Jeff   From: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Rex Brooks Sent: Monday, July 13, 2020 7:05 AM To: elysajones@yahoo.com; 'Scott M. Robertson' <Scott.M.Robertson@kp.org>; emergency-rim@lists.oasis-open.org 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, elysajones@yahoo.com 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Scott M. Robertson Sent: Friday, July 10, 2020 6:57 PM To: emergency-rim@lists.oasis-open.org 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 Attachment: smime.p7s Description: S/MIME cryptographic signature


  • 6.  RE: [Non-DoD Source] Re: [emergency-rim] Ongoing conflict with RIM meetings

    Posted 07-13-2020 20:14
      |   view attached
    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) <jeff.waters@navy.mil> Sent: Monday, July 13, 2020 2:52 PM To: Rex Brooks <rexb@starbourne.com>; elysajones@yahoo.com; 'Scott M. Robertson' <Scott.M.Robertson@kp.org>; emergency-rim@lists.oasis-open.org 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Rex Brooks Sent: Monday, July 13, 2020 7:05 AM To: elysajones@yahoo.com; 'Scott M. Robertson' <Scott.M.Robertson@kp.org>; emergency-rim@lists.oasis-open.org 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, elysajones@yahoo.com 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Scott M. Robertson Sent: Friday, July 10, 2020 6:57 PM To: emergency-rim@lists.oasis-open.org 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  


  • 7.  Re: [emergency-rim] RE: [Non-DoD Source] Re: [emergency-rim] Ongoing conflict with RIM meetings

    Posted 07-14-2020 02:47
      |   view attached
    Let's just keep it as-is for tomorrow tillour next reguarly scheduled telecon meeting. On 7/13/2020 1:13 PM, elysajones@yahoo.com 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) <jeff.waters@navy.mil> Sent: Monday, July 13, 2020 2:52 PM To: Rex Brooks <rexb@starbourne.com> ; elysajones@yahoo.com ; 'Scott M. Robertson' <Scott.M.Robertson@kp.org> ; emergency-rim@lists.oasis-open.org 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Rex Brooks Sent: Monday, July 13, 2020 7:05 AM To: elysajones@yahoo.com ; 'Scott M. Robertson' <Scott.M.Robertson@kp.org> ; emergency-rim@lists.oasis-open.org 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, elysajones@yahoo.com 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Scott M. Robertson Sent: Friday, July 10, 2020 6:57 PM To: emergency-rim@lists.oasis-open.org 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  


  • 8.  RE: [emergency-rim] RE: [Non-DoD Source] Re: [emergency-rim] Ongoing conflict with RIM meetings

    Posted 07-14-2020 14:51
      |   view attached
    Sorry but the rest of Tuesday morning is already booked.     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   From: Rex Brooks <rexb@starbourne.com> Sent: Monday, July 13, 2020 7:47 PM To: elysajones@yahoo.com; 'Waters, Jeffry H (53622) CIV USN NIWC PACIFIC CA (USA)' <jeff.waters@navy.mil>; Scott M. Robertson <Scott.M.Robertson@kp.org>; emergency-rim@lists.oasis-open.org Subject: Re: [emergency-rim] RE: [Non-DoD Source] Re: [emergency-rim] Ongoing conflict with RIM meetings   Caution: This email came from outside Kaiser Permanente. Do not open attachments or click on links if you do not recognize the sender. Let's just keep it as-is for tomorrow tillour next reguarly scheduled telecon meeting. On 7/13/2020 1:13 PM, elysajones@yahoo.com 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) <jeff.waters@navy.mil> Sent: Monday, July 13, 2020 2:52 PM To: Rex Brooks <rexb@starbourne.com> ; elysajones@yahoo.com ; 'Scott M. Robertson' <Scott.M.Robertson@kp.org> ; emergency-rim@lists.oasis-open.org 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Rex Brooks Sent: Monday, July 13, 2020 7:05 AM To: elysajones@yahoo.com ; 'Scott M. Robertson' <Scott.M.Robertson@kp.org> ; emergency-rim@lists.oasis-open.org 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, elysajones@yahoo.com 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Scott M. Robertson Sent: Friday, July 10, 2020 6:57 PM To: emergency-rim@lists.oasis-open.org 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   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.


  • 9.  Re: [emergency-rim] RE: [Non-DoD Source] Re: [emergency-rim] Ongoing conflict with RIM meetings

    Posted 07-14-2020 15:15
      |   view attached
    Hi Everyone, With only Jeff and I, we decided we needed more attendees if we wanted to do any business. So I just cancelled the meeting so that it doesn't record attendance, so can't affect anyone's status as a voting member. Better Luck next time. However, we might want to try to have a short meeting Thursday after the Steering Committee meeting. Cheers, Rex On 7/13/2020 1:13 PM, elysajones@yahoo.com 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) <jeff.waters@navy.mil> Sent: Monday, July 13, 2020 2:52 PM To: Rex Brooks <rexb@starbourne.com> ; elysajones@yahoo.com ; 'Scott M. Robertson' <Scott.M.Robertson@kp.org> ; emergency-rim@lists.oasis-open.org 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Rex Brooks Sent: Monday, July 13, 2020 7:05 AM To: elysajones@yahoo.com ; 'Scott M. Robertson' <Scott.M.Robertson@kp.org> ; emergency-rim@lists.oasis-open.org 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, elysajones@yahoo.com 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: emergency-rim@lists.oasis-open.org <emergency-rim@lists.oasis-open.org> On Behalf Of Scott M. Robertson Sent: Friday, July 10, 2020 6:57 PM To: emergency-rim@lists.oasis-open.org 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