Medivis connects AI imaging preparation with surgical planning and navigation

Medivis connects medical imaging, AI-assisted segmentation, surgical planning and navigation. Studio prepares and organizes a case; navigation systems bring relevant imaging and plans into an operative workflow, with conventional displays and augmented reality options. The company also presents Frontier agent and robotics research. Those future-facing programs need to remain separate from the products currently described as cleared, because a shared platform does not give every feature the same clinical status.

01 / ProductStudio prepares the case and navigation carries it forward

Medivis Studio is presented as an FDA-cleared, CE-marked platform for imaging, segmentation, reconstruction and planning. Its public description includes PACS connectivity, automatic and interactive segmentation, saved trajectories and multi-planar views. The point is continuity around a case: the imaging and work performed during preparation should remain available when the team moves into another environment.

The Spine Navigation page describes conventional navigation and AR guidance, with tracking of instruments relative to imaging and the patient. The page explicitly limits its current FDA-cleared spine scope to thoracolumbar procedures and identifies cervical spine and 2D–3D fluoroscopic registration as pending. Those details matter more than a broad claim that a platform supports spine surgery.

Cranial Navigation addresses a separate set of workflows, including cranial procedures and catheter-related guidance. Medivis describes both operating-room and portable bedside configurations. The company markets speed and accuracy benefits, but this blueprint does not treat those claims as independently reproduced findings. The procurement unit is a specific product configuration and intended use, rather than an undifferentiated AR headset.

The platform overview also distinguishes Body Navigation and Frontier research from the cleared offerings. Body Navigation is under investigation, and the contact page says it is not available for sale. Frontier includes agents and robotics research. These programs explain the company's direction, but they should not be included in a description of ordinary available clinical functionality without their current status attached.

02 / AudienceClinical programs and imaging IT need a shared scope

Medivis is relevant to institutions evaluating imaging preparation and surgical navigation, with surgeons, imaging teams, operating-room staff and IT involved. A department might begin with planning software, while another evaluates an integrated navigation configuration. Those are materially different projects. A good evaluation states which workflow is changing and which parts of the existing setup the institution expects to retain.

NVIDIA supplies a broader view of AI and visualization infrastructure, while Aidoc illustrates AI applied to clinical imaging analysis and orchestration. Medivis is closer to the interaction between a prepared image, a spatial plan and physical guidance. The comparisons help explain the layer being purchased; they do not imply that compute infrastructure, imaging triage and navigation are direct substitutes.

A consumer seeking an automated interpretation or a developer seeking unrestricted access to a medical agent would be outside the main offer described here. The site's usage notice identifies trained healthcare practitioners as users of Studio and the navigation products. A hospital should also avoid treating an attractive immersive display as the whole purchase. The applicable software, tracking, instruments, installation and training determine the actual supported workflow.

03 / WorkflowA proposed evaluation tests continuity without conducting surgery

A proposed operational evaluation can begin with an institution-approved demonstration case or training environment. Identify the exact Studio and navigation versions, hardware and intended workflow. Have the relevant clinical team define what the demonstration must preserve between imaging preparation and the receiving environment. This is an evaluation of product fit and information continuity, not a set of instructions for performing a medical procedure.

First, load the permitted imaging through the proposed connection and confirm the correct case and series are selected. Inspect whether staff can find the same case when changing workstations or access methods. A compelling rendering is of limited practical value if the receiving team cannot establish which source examination it represents or whether it reflects the latest approved preparation.

Next, ask a qualified user to demonstrate segmentation and planning features on the approved material. Review how automatic results can be inspected and modified, and how the system saves that work. The useful question is whether the team can distinguish a proposed automated output from the clinician's reviewed plan. Do not assume a generated anatomical boundary is correct simply because its visualization appears coherent.

For a navigation demonstration, use the supported training setup and have the vendor show how the planned case is connected to the relevant physical configuration. Inspect the displayed status when tracking or registration is incomplete. The institution needs to understand the system's failure and recovery behavior before any clinical deployment. This article does not prescribe registration methods or substitute for the product's controlled instructions and training.

Finally, compare the conventional and immersive presentation of the same permitted case. Observe whether each user can identify the information and system state they need, and document any practical constraints. The Studio page specifically says images viewed on a head-mounted display are informational and not intended for primary diagnosis. Keep that limitation attached to the relevant viewing use, even when another navigation product has a different authorized purpose.

04 / PricingStudio access and navigation scope require a written proposal

The commercial contact page routes Studio, navigation, research and partnership inquiries to the company. Studio invites requests to try it for free, but the reviewed pages do not specify a universal free entitlement or a public standard price. An institution should establish the duration, scope and permitted data for any evaluation before treating the invitation as access to its full planned deployment.

The Studio page describes both software deployment and optional hardware additions. It also lists enterprise capabilities such as identity-provider integration, PACS and DICOMweb connectivity, and Azure or on-premises deployment. These are useful scope markers for a proposal. They do not establish that every deployment option, interface or device is included in one price or supported in the same configuration.

Navigation combines software with hardware and associated workflow requirements. Obtain the exact configuration and product documentation rather than comparing it to the price of a standalone display. Ask which installation, support, training and equipment responsibilities the agreement covers. The public pages do not establish a single subscription unit or capital-purchase amount, so this blueprint does not invent one.

Research engagement must remain a separate commercial discussion. A Frontier collaboration is not the same as buying a currently cleared clinical navigation system, and Body Navigation's appearance in the contact form does not make it available for sale. Keep the statement of work explicit about whether it concerns product evaluation, clinical deployment within the available scope or co-development research.

05 / DistinctionsCase continuity is the central product proposition

The meaningful distinction is how Medivis connects preparation to the environment in which imaging and a plan are used. A standalone three-dimensional viewer can be useful, but continuity across data, segmentation, planning and guidance is a broader organizational proposition. The editorial inference is that retaining a coherent case state can reduce avoidable rework, provided the institution verifies versioning, review and access in its actual workflow.

The navigation pages also make conventional displays and AR part of the same discussion. That can matter to teams with different preferences and physical constraints. The relevant evaluation is whether each supported presentation makes the same necessary information and status clear. An immersive view should be assessed against the specific task rather than assumed to be better because it is visually impressive.

Medivis' Frontier agents page describes Maia as an orchestration layer that assembles case context for models and invokes tools. This is a research direction, not a currently cleared autonomous surgical agent. Its inclusion makes the company's broader AI ambitions visible while preserving the practical distinction between documented commercial products and work under development.

06 / QuestionsClearance, display purpose and research status differ

The first question is the exact current intended use for the configuration under consideration. The spine page's pending cervical and fluoroscopic features demonstrate why a broad product label is insufficient. Confirm the applicable version and jurisdiction with the controlled instructions. A clearance attached to one function does not automatically extend to every workflow illustrated elsewhere on the same website.

The second question is how the organization manages changes to a prepared case. If imaging, segmentation or a plan is revised, the receiving team needs to know which version it is using. Ask the demonstration team to show that transition and how the relevant user reviews it. This is an information-management issue as much as a visualization issue, and it cannot be settled by a product screenshot alone.

The third question concerns deployment responsibilities. Enterprise access, local compute, tracking hardware and clinical equipment introduce different support boundaries. Establish who owns each boundary and what happens when a dependent system is unavailable. The public descriptions establish available approaches, but they do not demonstrate the institution's network, identity integration or operating-room readiness. Those details belong in the scoped evaluation and implementation plan.

07 / DecisionChoose the available product that serves the program

Medivis is a substantive AI-related company because it applies segmentation and spatial computing to medical imaging and surgical workflows. A useful starting point is either a defined Studio planning requirement or a specific currently supported navigation configuration. Demonstrate the complete case path, including review and system status, with the qualified teams who would use and maintain it.

Keep the company's research programs visible as research and evaluate them under a separate purpose. For present deployment, make the purchase depend on the configuration that can be documented, demonstrated and supported today. That gives Medivis' integration proposition a fair assessment without allowing a future agent, investigational product or pending feature to fill a gap in the current workflow.