Reponses to written questions for RFO C16-046 Patient Unified Lookup System for Emergencies (PULSE) Operator

RFO C16-046 Patient Unified Lookup System for Emergencies (PULSE) Operator, Reponses to written questions submitted to EMSA by October 19, 2016 by 5:00pm deadline:

Date Requested: 10/17/2016 @ 2:17pm

Requestor: Raja Krishnan

Entity: Agile Global Solutions, Inc

Email address: raja@agileglobal.com

Question: Is there an incumbent for this work? Please let me know. Thx.

Answer: No there is not an incumbent working as the PULSE Operator.

 

Date Requested: 10/18/2016 @ 9:13 am

Requestor: Jonathon Feit

Entity: Beyond Lucid Technologies, Inc.

Email address: Jonathon.Feit@beyondlucid.com

Question: And what happened with the other one — why was it cancelled?

Answer: Items were added to the scope of work.

 

Date Requested: 10/19/2016 @ 2:03 pm

Requestor: Ajay Prashar

Entity: Physicians Medical Group of Santa Cruz

Email address: aprashar@pmgscc.com

Questions:

  1. Do you have a document that displays the interactions between the PULSE servers (Web, Application, and Database) within the PULSE Operator environment for RFO #: C16-046?
  2. With respect to system requirements as defined in “Attachment A – Scope of work”, (A)(4) on page 13 of 40:
  3. Can you confirm that the PULSE Vendor will provide preconfigure virtual machines for PULSE Operators that are using cloud environments?
  4. If use of VM’s is confirmed, do you have any details as to the:
  5. Platform of the virtual machines? (Citrix, VMware, or Hyper-V hypervisor)
  6. Resource requirements of each VM? (disk space, processor, RAM, operating system)
  7. How will the virtual machines be securely obtained by the PULSE Operators? (physical exchange of hard drive, secure download, etc.)

Answers:

  1. We do not have a document that displays the interactions between the PULSE servers at this time. By the time of the hand-over from the Software Developer to the Operator, there should be a System Design Document available for the Operator that would describe these interactions.

2. a. The PULSE Vendor can provide preconfigured virtual machines for PULSE        Operators if they are using the same cloud service as the PULSE Vendor.

 

  1. The PULSE Vendor is using Amazon Web Services (AWS) Elastic Compute Cloud (EC2) for cloud services, which in turn uses Xen Hypervisor for virtualization.

 

  1. The PULSE Vendor has deployed the testing environment on three virtual Ubuntu Linux machines, each an AWS T2.large instance (2 virtual 64-bit CPUs, 8GB RAM) with an attached 128 GB virtual filesystem. It will be the responsibility of the PULSE Operator to determine whether this hardware configuration is sufficient for the PULSE Drill after it has been deployed.

 

  1. The PULSE Vendor can provide an AWS AMI to PULSE Operators using AWS EC2. If PULSE Operators choose to deploy on some other environment, the PULSE Vendor can support their configuration on a separate environment in a limited way. In addition, the software implementing PULSE will be made available on GitHub.

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s