Electronic orders

Documents travel in both directions. The customer orders electronically, but the supplier's warehouse system often cannot read the order — so somebody retypes it. We take the order, convert it into a format your system understands, or hand it over directly to its API.

Where we take orders from

• A structured order by e-mail — typically an XML or CSV attachment.
• The MEDIDATA server — the same infrastructure that carries delivery notes in the opposite direction through MEDIDATA e-kurýr.
• An EDI ORDERS message — see EDI.
• Shared storage or an API — whatever the customer can offer.

What we do with it

• Validate it and split it into header and lines.
• Convert it into a format your warehouse or accounting system can import.
• Or deliver it straight into your API — no file, no manual handling.
• Keep its link to the documents that will later arise from it.

Departments and cost centres

Hospitals order per department and account per cost centre. We hold the customer's code list in the gateway and map your internal identifiers onto it, so the order number, department and cost centre travel onward on the delivery note and the per-department breakdown follows from that.

The mapping is set up once, through a straightforward web administration interface. Our technical support can also do the setup for you from the code list you supply.

How the integration runs

The same way as for delivery notes: send us a sample of a real order and the specification of the target system or its API, and the mapping is on us. The data scope is described under Accepted formats.

Sign up