Question: Who is contracting party? Is NETC and MaineHealth signatories to the agreement or just NETC?
Answer: MaineHealth

Question: The project may require that the work be done in phases. Will the contracting parties consider a phased approach to the RFP response?
Answer: Yes, but prefer to maximize the funding opportunity, ensure we’re meeting the Connected Care Pilot Program requirements/timelines, and balance other organization priorities and activities.

Question: The RFP requires a 36-month agreement. Will NETC and MaineHealth agree to a portion of the agreement being 36 months (to comply with the Pilot Program) with another portion extending beyond 36 months to 60 months.
Answer: Although a 36 or 60 month contract is acceptable for portions of the project, it is important to note that Connected Care Pilot Program (CCPP) funding is only available through December 31, 2025. To remain compliant with the program’s requirements and justify any eligible one-time costs (e.g., for Distributed Antenna Systems or equivalent), some portion of the associated patient-facing telehealth services must be operational no later than December 31, 2025. For purposes of contracting Managed, Recurring, or Capital (MRC) services, NETC and MaineHealth are open to a combination of contract terms, including 36-month, 60-month, or hybrid structures.

Question: Are the health care providers listed in the RFP separate legal entities or are they owned by MaineHealth? If they are separate legal entities, what is the intended relationship between the vendor and each entity? 
Answer: MaineHealth is one legal entity. All of the hospital locations in scope for this effort are one entity.

Question: Will NETC and MaineHealth allow subcontractual arrangements for the vendor to fullfill the RFP requirements?
Answer: Yes, MaineHealth will allow subcontractors to perform work as needed. There are no rules against using subcontractors in the Connected Care Pilot Program. 

Question: It is important for the hospital component of the 5G network to be completed for the remaining connectivity requirements to be instituted in the community. Can the NETC funding for MaineHealth cover the initial build for the hospital properties with a secondary contractual arrangement for the remaining portions of the RFP?
Answer: It is preferred that there is an initial build-out (one-time charge) and secondary contractual arrangements for the remaining portions of the RFP.

Question: SLAs can be provided where the vendor can ensure QoS and other network reliability. SLAs cannot be provided when services are provided over generic internet connections, including satellite. Is that arrangement acceptable in an RFP response? 
Answer: Yes, that is acceptable. What specific use cases, locations or examples, would satellite be utilized?

Question: Would NETC prefer to have a Confidential response and a non-confidential response (redacted) or just a single response with confidential material marked as such in the response?
Answer: A single response with confidential material marked is preferred.

Question:• What specific telehealth, telemedicine, and remote patient monitoring functions are expected of the patient device (e.g., video visits, data submission, messaging, app access, etc.)?
Answer: Yes, all of those are possible use cases.

Question: • Are there any required integrations with MaineHealth or third-party Electronic Health Record (EHR) platforms that the device must support?
Answer: Yes, primarily at the application level rather than the device itself.

Question: Who retains ownership of the device after deployment: NETC, MaineHealth, or the patient?
Answer: MaineHealth

Question: Is the device to be used only for the duration of care, or will patients keep it permanently?
Answer: Only used for the duration of care. The patient will not keep the device.

Question: What is the process for device retrieval, replacement, or recycling if a patient graduates from or leaves the program? 
Answer: Devices will be returned to MH for use with future patient care.

Question: Who is responsible for device onboarding, provisioning, and zero-touch configuration—MaineHealth, the vendor, or both?
Answer: MaineHealth initially, maybe the vendor as well if process changes.

Question: • Will device management—including software updates, security patching, and remote troubleshooting—be handled by the vendor or MaineHealth IT?
Answer: MaineHealth initially, maybe the vendor as well if process changes. All changes must be approved and follow MaineHealth change polices for change management.

Question: Is there an established Mobile Device Management (MDM) protocol or platform required for compliance? 
Answer: Yes, Microsoft Intune.

Question: Does the device require support for configuration changes post-deployment (e.g., adding apps, updating Wi-Fi/cellular profiles)?
Answer: Yes. Depending the device use case there may be variation on the applications available on phones or tablets. MaineHealth sets up devices by profiles for access: Clinical, patient facing, shared or individual assigned.

Question: • What minimum hardware and software specifications are expected for the device (processor, RAM, OS version, camera, sensors, battery life, etc.)?
Answer: Some specifics based on use case, but newer / current hardware platforms preferred. Varies by need. Example: Epic Rover wound care photos have minimum camera requirements. iPhone 16e phones do NOT meet all wound measurement specifications. 

Question: Is there a preferred form factor (smartphone, tablet, dedicated medical device) or are multiple device types anticipated depending on use case?
Answer: Smartphone primarily, potentially tablets or other medical devices depending on use case.

Question: Should the device be compatible with third-party peripherals such as Bluetooth-enabled blood pressure cuffs, glucometers, or pulse oximeters?
Answer: Yes, if possible. MaineHealth already utilizes several of those listed and stethoscopes, weight measurement pads and more.

Question: Are there any requirements or restrictions regarding device brand, model, or allowed operating systems?
Answer: Yes, Apple iPhone hardware preferred. Exceptions must be reviewed with EUC and Collaboration Systems. Newer platforms preferred.

Question: What level of data encryption and security is required for data at rest and in transit on the device? 
Answer: AES265 for at rest in motion TLS 1.2 min (with aes256 as the minimum crypto being used)

Question: Are specific regulatory standards (such as HIPAA or HITECH) required at the device level for configuration and encryption?
Answer: HIPAA

Question: Should devices be enrolled in a corporate VPN or private APN, and does this require pre-configuration? 
Answer: Yes, no pre-configuration is required to start. Process may evolve over time.

Question: Are role-based access controls required on the device for patients, caregivers, or clinicians?
Answer: Yes, primarily at the application level rather than the device itself. In some cases MaineHealth does have role-based controls especially if a device is used by a patient to complete an activity whether within the EMR or not.

Question: Should the device support fallback between Wi-Fi, 4G/5G cellular, and satellite (e.g., Starlink Direct-to-Cell) with no user intervention?
Answer: Yes

Question: Are there minimum performance standards for uplink/downlink speeds, latency, and jitter for the device’s telehealth functionality?
Answer: Yes, it will vary depending on the application.
Examples:
-Video Calls via Zoom – 3.0mbps for video calls
-Virtual Care (Inpatient with clinical provider remote): Varies by inbound or outbound connection and number of participants on video or telephony connection.

Question: • Will SIM/eSIM cards be managed by the vendor, and are device models required to be “unlocked” for multi-carrier compatibility?
Answer: Yes, unlocked is preferred.

Question: What are the expectations for device support, repair, and replacement (e.g., hotline, on-site, mail-in, loaner devices)?
Answer: Open for discusion, all options are possible.

Question: Is remote device wipe or lock capability required in cases of loss or theft?
Answer: Yes, the MaineHealth MDM can perform this function.

Question: Are there user training or onboarding materials required for patients receiving the device, and who is responsible for their creation and delivery?
Answer: Yes, MaineHealth created and delivered.

Question: Can NETC clarify expectations around SIM lifecycle management, including provisioning, activation, suspension, and deactivation workflows? • Can NETC clarify expectations around SIM lifecycle management, including provisioning, activation, suspension, and deactivation workflows? Is a centralized portal required for these functions? 
Answer: Yes, a centralized portal is required. 

Question: Will NETC require real-time visibility into SIM usage, data consumption, and device connectivity status across all endpoints? Is historical usage reporting a desired feature?
Answer: Reports containing baseline historical data, expected usage, data consumption and common connection issues are always useful. Real-time access is additionally desired in the event of outages or degraded service and can support troubleshooting and issue resolution in addition to setting clear end user expectations.

Question: Is HIPAA-compliant traffic routing via private APN or VPN mandatory for all SIM-connected devices?
o Would NETC prefer a platform that enforces policy-based access and segmentation?
Answer: HIPAA-compliant traffic routing is required.

Question: Will NETC require remote diagnostics or alerting for SIM-connected devices (e.g., offline status, abnormal usage, roaming events)?
Should the platform support automated alerts and escalation?
Answer: Please include pricing for automated alerts and escalation. 

Question: Does NETC anticipate scaling beyond the initial 500 SIMs?
Should the platform support bulk provisioning, configuration, and reporting for large device fleets?
Answer: Yes, please include pricing for scaling beyond 500 SIMs

Question: • Is integration with external systems (e.g., EHR, device management platforms) via APIs a requirement or preferred capability for SIM management? 
Answer: API requirements will be discussed during contract negotiations with the selected vendor. 

Question: Based on these requirements, is this geared towards Internet Service Providers and/or product manufacturers only or also technology partners like ourselves? 

4.17 Each Responding Vendor must have a current FCC Registration Number (FRN).
More information about obtaining an FRN can be found at
https://apps.fcc.gov/coresWeb/publicHome.do.

4.18 Each Responding Vendor must have a current USAC 498 ID (also known as a Service
Provider Identification Number (SPIN)). More information about obtaining the 498
ID can be found at http://www.usac.org/sp/about/obtain-498ID/default.aspx.
Answer: All proposals will be considered, provided that the responding vendor has, at minimum, an active USAC 498 ID (SPIN) and FCC Registration Number (FRN). These are required under the FCC’s Rural Health Care Program rules for any entity receiving program disbursements as a service provider.
This means participation is not limited to Internet Service Providers or product manufacturers. Technology partners and other entities may respond, so long as they are properly registered with the FCC and USAC and can meet the program’s invoicing and compliance obligations.