RED CROWNINTERACTIVELET'S BUILD
EN
Menu

Feasibility and user experience testing

Software prototypes
for medical products

Software prototypes for medical product and engineering teams. We focus on user interfaces, information and 3D visualization, and a working scenario that professionals can evaluate.

CODEX EPD · PHILIPS
CODEX EPD interface from the founder's development experience at Philips
Founder experience before Red Crown
Founder experience at Philips3D visualizationA prototype to try↓

Founder experience and projects

TechnionPhilipsPlaytikaTel Aviv UniversityIsraeli Navy

From the founder's experience

Medical software development experience

Before founding Red Crown, our founder participated in developing CODEX EPD at Philips. This is prior professional experience in medical 3D software.

CODEX EPD interface from the founder's development experience at PhilipsCODEX EPD · PHILIPS

Founder experience before Red Crown

CODEX EPD at Philips

The founder's experience developing a medical 3D system at Philips, combining anatomical information and interactive visualization. The work connected software components, spatial displays and a professional interface.

  • Medical 3D Information and interface together
  • Founder experience Developing at Philips

Service scope

What the prototype can test

Define one or a few product questions: which data users need, the sequence of actions and how information appears in the interface.

01 / EXPERIENCE

Interface and workflow

Implement a use case with navigation between screens and core actions. The version supports presentations and feedback from professionals.

02 / VISUALIZATION

Medical 3D visualization

Integrate anatomical models and information in an interactive display. Evaluate navigation, component selection and the relationship between the model and displayed information.

03 / INTEGRATION

Software feasibility testing

A focused test connecting software components, data and interface. Document what was implemented, the testing conditions and what is needed for the next development stage.

Yulia Pavlov, founder and lead engineer at Red Crown Interactive
Yulia PavlovFounder and lead engineerLinkedIn ↗

Professional leadership

Management and development
Led by Yulia Pavlov

More than a decade of software and real-time 3D development in industry and research.

Yulia leads planning, design and development. Specialists join as the project requires, with one clear point of contact for you.

B.Sc Software engineering, TechnionMBA Tel Aviv University

Project stages

How we work

01

Define the test scenario

Focus on the user, scenario and question to test.

Deliverable: prototype scope
02

Implement an initial interface

Build the main interaction or visualization.

Deliverable: a version for professional feedback
03

Refine with professional feedback

Incorporate findings and connect software components.

Deliverable: a functional prototype
04

Handover and limitations documentation

Document capabilities, limitations and next decisions.

Deliverable: a foundation for further development

Before we start

Frequently asked questions

What does a medical prototype include?

A defined use case, interface and software or 3D components needed to evaluate it. Scope follows the question to test with professionals.

Is a prototype approved for clinical use?

No. A prototype is for evaluating and demonstrating an idea. Clinical product requirements, validation, information security and regulation are defined separately with the appropriate professionals.

Can we start with sample data?

Yes. A prototype can use suitable sample data. Data requirements and system connections are assessed during project planning.

Does the service include medical hardware development?

The focus is a software prototype: interface, application logic and interactive visualization. If a device or existing system connection is needed, we review interfaces and responsibilities with your engineering team before agreeing the scope.

The next step

Let's discuss
your project

Tell us what professionals need to do and what you want to test in the first prototype.

  • Focus the scenario and workflow
  • Choose visualization and software components
  • Define prototype deliverables and limitations

We usually reply by email within one business day.

Your details are used only to contact you about the project.