Home/Solutions/Healthcare

Screen sharing for healthcare meeting and teaching rooms

Bring staff presentations, teaching materials and remote colleagues into a shared room workspace. Choose the hardware for the room, manage it in Polaris Cloud, and give IT and security reviewers a clear place to start.

Polaris requires access to Mersive’s cloud. Include that connection in your deployment review.

The rooms your teams use

Plan for the meeting, the network and the review

Department meetings, teaching sessions and hybrid discussions have different room needs. Start with how people share, then check the network requirements and security evidence.

✕Presentations from several devices

Staff and visiting speakers bring their own laptops and material. Switching presenters should be part of the room plan.

✓ Share presentations and approved teaching material in the Polaris workspace. Test the devices and sharing methods your teams use before rollout.
✕Staff and guest networks

Network segmentation affects how a presenter reaches the room display. Your access policy needs to be part of the evaluation.

✓ Polaris supports cross-network sharing on Pro and Essentials. Confirm the required ports, endpoints and cloud access with your network team, then test your intended configuration.
✕Evidence for the security review

IT, security and procurement need the scope and dates behind a vendor’s claims.

✓ Start with the public Trust Center. Request the SOC 2 Type 2 and full penetration-test reports under NDA when your reviewers need the detailed evidence.
✕Different rooms across the health system

An administrative meeting room and a teaching room may need different displays or conferencing equipment.

✓ Choose the hardware for each room and manage both products in Polaris Cloud. Pro and Essentials run the same software and share the same security posture.
Choose your room hardware

The same platform, sized for the room

Essentials runs the same Polaris software as Pro: the same workspace, the same cloud, the same security posture. The differences are the chassis, not the platform.

Polaris Pro
Rooms that need the room’s camera and microphone in a laptop-hosted meeting
  • Share presentations and teaching material in the Polaris workspace.
  • Use wireless BYOM to connect the room’s camera and microphone to the presenter’s laptop call.
  • Link is a software bridge between the laptop in BYOM and the Pro, and the Pro is what controls the room's cameras and peripherals. That is why Link needs a Pro.
  • Check display, wired-input and peripheral requirements on the Pro product page.
Explore Polaris Pro →
Polaris Essentials
Rooms focused on wireless presentation and shared content
  • Use the same Polaris workspace, browser sharing and cross-network capabilities as Pro.
  • Manage the room in the same Polaris Cloud portal.
  • Use the same software security controls as Pro.
  • Choose Pro when you need wireless BYOM or Polaris Link. Those depend on Pro’s room-peripheral connection.
Explore Polaris Essentials →

Compare specifications and current buying options on the product pages. Room hardware determines the fit; a software license does not turn Essentials into Pro.

For IT, security and AV teams

Build the review around the intended use

Start with the rooms you plan to equip and the information people will share. Review the evidence, network requirements and operating controls together.

HIPAA safeguards and HITRUST mapping

The SOC 2 Type 2 report dated 15 July 2025 includes an opinion on controls implemented to meet 45 C.F.R. §164.308, the HIPAA Security Rule administrative safeguards. It also maps controls to HITRUST CSF v11.5. The attested system is the Polaris cloud management console. The HITRUST mapping is not a HITRUST certification, and neither statement establishes HIPAA compliance for your deployment. Request the report under NDA to review its scope and findings.

Review the security evidence →

Review the data path for your use

Include the sharing method, network connections and cloud dependency in your security review. For case discussions or telehealth workflows, agree on the permitted content and use with your clinical and security teams before deployment.

Open the Trust Center →

Test sharing across your networks

Test staff and guest devices on the network segments they will use. Pro and Essentials support the same cross-network sharing software. Confirm the access rules and connectivity needed for your configuration with your network team.

Review cross-network sharing →

Manage rooms across sites

Use Polaris Cloud to review device health, configuration, firmware and usage across your meeting and teaching rooms. Manage Pro and Essentials together as the fleet grows.

Explore Polaris Cloud →

Plan configuration and updates

Apply configuration templates and stage firmware updates across selected rooms before expanding the rollout. Editing a template re-applies it to every device assigned to it, so a room that was changed locally comes back to the approved profile.

Explore fleet management →
Security evidence and deployment requirements

Know what each document covers

Architecture documentation, management-system certification, cloud attestation and device testing answer different questions. Keep the scope attached to each piece of evidence.

Public architecture, detailed reports on requestRead the security architecture and published summaries in the Trust Center. The SOC 2 Type 2 and full penetration-test reports are available under NDA. Use the relevant documents for your review. Open the Trust Center →
Secure boot and signed updatesThe room devices use secure boot. Firmware updates are checked for authenticity and integrity. The device refuses a downgrade to an earlier version. The pod keeps two firmware partitions: a new image installs beside the running one, and a pod that fails to come up on the new version returns to the last known-good one. Review firmware and updates →
A purpose-built Linux devicePolaris Pro and Essentials use a hardened Linux image for the room appliance. Review the device architecture and network requirements as part of your deployment assessment. Review device security →
Defined audit and certification scopesMersive’s ISO/IEC 27001:2022 certification covers the ISMS supporting the Mersive Collaboration Suite (Solstice Cloud System). The surveillance record reports no nonconformities at the June 2026 surveillance audit. The SOC 2 Type 2 report covers the Polaris cloud management console for security, confidentiality and availability. Room appliances are outside that attested system boundary and have separate testing evidence. Review scopes and reports →
Separate application and device testingIndependent testing includes a July 2026 application assessment and a May 2025 physical assessment of the Gen 4 Pod and Pod Mini. These are different engagements with different scopes. Request the full reports under NDA to review the methods, findings and limitations. Review the testing record →
A cloud connection is requiredPolaris depends on Mersive’s cloud for activation, licensing, configuration, sharing and updates. Confirm the required connectivity with your network team before deployment. On-premises and air-gapped operation are not currently available. Review network requirements →
Your evaluation

Test a room your teams will use

Choose a representative meeting or teaching room. Agree on the permitted test content, devices and network connections, then evaluate the workflow with the people who will use and support it.

  1. Share from staff and guest devices. Test the laptops, browsers and network segments you expect to support.
  2. Run a teaching session. Switch presenters and share approved training material using the room’s intended setup.
  3. Check a hybrid discussion. In a Pro room, test the selected camera, microphone and meeting service with both local and remote participants.
  4. Review operations. Check room health, apply a configuration template and plan a staged firmware update with IT.
  5. Record the result. Document access requirements, unresolved questions and the use cases your team approves for rollout. Use non-sensitive sample content until your team approves any use of patient information.

Start a trial →

Plan your evaluation
Trust CenterReview the architecture, audit scopes and testing summaries. Detailed SOC 2 and penetration-test reports are available under NDA.Network requirementsReview the deployment guidance with your network team and confirm the requirements for your configuration.Get a demoBring your room requirements and see the Polaris workspace in use.

See Polaris in your own rooms

Test Polaris with your devices, network and approved meeting material. Include your IT, security and AV teams in the evaluation, then decide which rooms fit your rollout.

Start a trial