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.
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.
Search, add to basket, submit for approval: four components behind three steps.
Smart catalogue search
Recognises synonyms, product codes and barcodes. The catalogue learns the nurse's language, rather than the nurse learning the catalogue's.
Hospital-specific prices
Each hospital sees its own contract prices in the catalogue. There is no need to call a representative for pricing.
Repeat orders and surgical kits
Repeat last week's order with one tap. Order the materials for an operation as a kit.
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
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 conceptThis is an example, not a limit; we apply the same approach to similar processes in other industries.