X Medikal Product concept

Reducing hospital supply orders to three steps.

Catalogue, contract prices and ERP in one portal; nurses find products in their own words and submit them for approval.

X Medikal product concept with sample data: searching the portal catalogue for “surgical gloves” returns 48 synonym-matched results and contracted product cards; in front, an iPad shows the Laparoscopic Cholecystectomy surgical kit.
Repeating a previous orderFull screen ↗
Product concept: a solution study presented through screen designs, not an interactive demo. X Medikal is fictional; screen data is illustrative.
Industry
Healthcare & Medical
Capabilities
Product Strategy, Experience Design, Software Engineering
Platform
Web, iPad

Problem and approach

Problem

Hospital procurement orders still often begin with a phone call.

In a catalogue of 14,000 products, one hospital asks for “surgical gloves” and another for “sterile gloves”; prices differ by hospital contract. Urgent requests get lost among telephone notes, orders are entered into the ERP manually and live stock is not visible.

Approach

We look for the problem in hospital corridors, not just on screen.

In a two-week discovery sprint, we observe nurses and procurement teams at work, collect the names they use for products, and test a prototype with actual users in week three. The jointly scoped first phase, such as catalogue search and ordering at one pilot hospital, targets a launch in 6–12 weeks; the iPad app and other hospitals follow in later phases.

Solution

Search, add to basket, submit for approval: four components behind three steps.

The X Medikal concept's Orders screen, with sample data: open orders, monthly spending, contract compliance and average delivery time cards; orders by department and a status timeline for order SİP-04871 from creation to delivery.
Order status stepsFull screen ↗
The procurement team and nurse share the same view: open orders, spending and contract compliance, with the selected order's journey to delivery on the right.
The X Medikal concept's iPad app showing a new request for Operating Theatre 3, with sample data: Search, Basket and Approval steps, reorder cards, frequently used products and a barcode-scanned notification.
Requesting contracted productsFull screen ↗
iPad app: repeat orders and add items by barcode.
  1. Smart catalogue search

    Recognises synonyms, product codes and barcodes. The catalogue learns the nurse's language, rather than the nurse learning the catalogue's.

  2. Hospital-specific prices

    Each hospital sees its own contract prices in the catalogue. There is no need to call a representative for pricing.

  3. Repeat orders and surgical kits

    Repeat last week's order with one tap. Order the materials for an operation as a kit.

  4. Real-time ERP integration

    Approved orders are transferred to the ERP immediately, with live stock visibility.

Scenario and scope

Example users

Hospital department manager, procurement specialist, approver and the supplier's order team.

Example workflow

The department finds what it needs in the catalogue, adds it at the contract price, and an authorised person approves it for transfer to the ERP. Delivery and document status are tracked in the portal.

Decisions for a real project

Define the product dictionary, contract price source, hospital and department permissions, stock freshness, ERP access and pilot hospitals. The scope here is procurement operations, not clinical decisions or patient-record management.

Related service: B2B portal development. You can list your own users and systems in the project brief tool.

Timelines, teams and technologies in this scenario are illustrative planning choices; actual scope, schedule and team are defined during discovery. Product names do not imply partnerships.

What we measure

%30Target: reduction in time spent per order
%50Target: share of orders placed through the portal
%25Target: reduction in requests received by phone and email
%95Target: share of orders placed at contract prices

These targets are example measures defined for this scenario; actual results vary by project.

Technology and team

Technology

  • Next.js
  • TypeScript
  • Node.js
  • Elasticsearch
  • PostgreSQL
  • SAP S/4HANA integration
  • Azure

For customer and supplier portal scope, integrations and delivery terms, see the B2B portal development page.

Suggested team 7 people

  • 1 product strategist
  • 1 product designer
  • 4 software engineer (web, iPad, integration)
  • 1 QA engineer

Your process

Do you manage a similar operation? Let's schedule a 30-minute conversation about moving hospital orders from phone calls to a self-service portal.

Let's discuss this concept

This is an example, not a limit; we apply the same approach to similar processes in other industries.