1000 Possibilities: Lean FMD's Data Structure

medAspis makes no secret of the data structure of Lean FMD. The data are yours. So you should be able to do with them as you please. The data are stored securely on German servers.

Our Recommendation: Outsource FMD Data

We make it easy to access FMD data at any time. And for over five years. This opens up the possibility for our customers not to burden their highly efficient materials or merchandise management systems with these data, but to simply outsource them to us. This saves effort and storage space. And when the data are actually needed, they can be accessed.

medAspis API: Access to Internal Data Structure

medAspis provides its customers with a powerful WebService access via API interface. This makes access to the data as simple as possible.

You can see how powerful the interface is just by taking a look at the Lean FMD Control Panel. Everything you can see and address here is also accessible via the API. Typically, the captured data are assigned to existing business transactions via a key:

Using this key, the data can be saved and easily retrieved later. We would be happy to send you our API tutorial. Drop us a line.

Behind the Scenes: medAspis Data Structure

To enable you to work with the data in the best possible way, medAspis has opted for a very powerful data structure.

Data Structure in Detail

Each data record contains all relevant data for each individual scan that is carried out.

Scan time: Time and date of the scan. It is not the time on the FMD Speed Scanner that is recorded, but the server time of the medAspsis FMD Server. This cannot be manipulated.
Pack data: Each capture includes all relevant pack data. The unique identifier is also retained. This unique identifier is required if you want to process the data yourself.
FMD operation: Together with the result of the NMVS, the FMD operation selected by the user is also stored. In addition, the full JSON response of the NMVS and the response time is captured – in case someone wants to know exact details.
Additional information: If an alert occurs, an extended error description and the error handling performed is stored.

Groupings: Bundle Data as Required

With Lean FMD from medAspis, data can be bundled into groupings. This makes it possible to link your company data with serialised medicine packs.

Structure of a Grouping

What exactly does it mean? Technically described, groupings are lists of packs that are stored under a generic term (key). This can be a delivery note number, for example. With the help of this key, you can create groupings and retrieve them at any time. All groupings are displayed in the Lean FMD Control Panel. They can also be read out via the API and processed further via your IT systems.

Create a Grouping in No Time

As a rule, a grouping is created via the FMD Speed Scanner:

Name the grouping by scanning a barcode, e.g. a delivery note number.

Codes are scanned either directly from the screen or from a printed document (e.g. delivery note). You can create such barcodes using your ERP system.

Import data into the system

If required, import data from an external source directly into the medAspis system. A simple XML format is available for this purpose, which structures the pack data. The data can be coded according to GS1 as well as PPN.

Are your data available as an Excel list? No problem, these can also be easily imported into the medAspis system for further processing.

Retrieve Groupings Hassle-Free

Would you like to use the recorded FMD data within your IT infrastructure and your ERP system? With medAspis and Lean FMD this is very easy. If the data were previously stored in the system with a certain key, they can be retrieved with the very same key. To obtain the content of a list, you only need a one-line IT request specifying the key (in the example: PRIMARY_KEY). The medAspis system responds immediately and outputs the associated pack data in a structured form. In our example, just the pack information is retrieved. If required, all other elements of the data structure are also available to you.

Example: Save Serial Numbers for a Delivery Note

Learn how to use groupings in a typical situation now. The task: Record all serial numbers for an existing delivery bill.

The delivery note number is read in with the FMD Speed Scanner.
With the reading process, the 2D matrix codes of the packs are assigned to the delivery note number.
You complete the process by pressing a button on the FMD Speed Scanner. The scanner is immediately available for the next delivery note.
After all delivery notes have been scanned, the complete data records are available to you, structured and counted.
Use theLean FMD Control Panel to view the grouping or apply as many FMD operations to it as required. Alternatively, you can transfer the data to your IT by specifying the delivery note number.

Full-Fledged, Multi-Level Aggregation Concept

Aggregation refers to a grouping of serialised individual packs identified by a unique aggregation code. Via the aggregation code, all serial numbers contained in the aggregation can be retrieved at once.

An example use of aggregation: a carton or a complete pallet is to be deactivated or marked as export without the need to scan the packs individually. This example shows the amount of time which can be saved using this function.

Structure of an Aggregation

medAspis not only provides the aggregation system, but also the associated aggregation codes.

Pure code or sticker for direct labelling of cartons, pallets or other packaging units? The choice is yours.

Organise aggregation hierarchically

Parallel to the actual requirements, serial numbers can be hierarchically aggregated. This means, for example, that pharmaceutical packs can be aggregated into cartons and cartons in turn into pallets.

If only the top code is read, the hierarchy of aggregations below can be triggered automatically. In other words, all packs included can be verified, deregistered or exported at once. This means much less manpower in your FMD processes.

Use the hierarchical medAspis system to structure your own data according to known data (e.g. according to GS1) or to set up your own system of keys.

And this is what it looks like in practice

Export Aggregations

All data sets are, of course, only visible to you. However, you can make your aggregations – also hierarchically – available for use by external parties. If you set your data to export status, your customers can benefit from your aggregations as well.

You make your customers’ lives easier when you relieve them of the tedious scanning in goods receipt.

Higher Productivity: Examples of Aggregation

Example 1: A supplier (manufacturer, logistics specialist, wholesaler) delivers aggregated goods to a hospital. Now all it takes is reading in the code on the delivery box – and all the goods are cleared on behalf of the hospital.
Example 2: An exporter verifies complete boxes in goods receipt and at the same time aggregates them. For the prescribed change of status to export for this carton, it is enough to scan the aggregation code applied to the carton. Immediately, all contained packs are set to export without any further scanning process.
Example 3: A pharmaceutical distributor buys large tranches of medicines. If wholesalers buy directly from the manufacturer instead of from him, they do not need to scan – they do, however, if they buy from the distributor. To increase competitiveness, the pharmaceutical retailer aggregates all deliveries. For customers, it no longer makes a difference whether they buy from manufacturer or retailer. In both cases, there is no need for scanning.
Example 4: A parallel trader operating throughout Europe ships goods from one warehouse to the next. Since both warehouses are located in different countries, the goods must be verified at the recipient’s place. To make this work easier, goods are aggregated when they are sent and verified by aggregation code upon receipt.

Contact form

Your Quick Contact to medAspis