Aggregations are sub-forms of groupings. Aggregations have all the attributes of groupings but no user-assigned name and they can be used more flexibly.
Groupings always have a primary key (unique name). In medAspis, the primary key is a 64bit long unique identifier in base-64 notation. In this notation, the primary key is formed from letters, numbers and common special characters. medAspis uses the characters: A-Z, a-z, 0-9, + and -. Prefixed with a “K!”, an example is “K!E9j-I9S4TVI”.
Each grouping – no matter what name the user assigns – has a primary key formed in this way. The reason: Within the medAspis system, all groupings must be clearly identifiable. However, it may be that different customers use the same delivery note numbers for their grouping, for example. To be sure that all groupings can always be reliably identified and assigned in the system, the primary key is the aggregation code automatically generated for each grouping. This can never be changed or manipulated.
Using the aggregation codes as primary keys, groupings can be organised hierarchically. Aggregations can be part of a super-aggregation. This hierarchical relationship can take place in as many levels as required.
Aggregations can be made visible to third parties. If the status of an aggregation is set to EXPORT, the aggregation is visible for others and can be taken over into the own data structure. Aggregations are passed on, for example, by sticking the aggregation code on an aggregated box. The receiver sees the code, scans it and has taken the data into its own data structure.
For easy processing of aggregations, medAspis provides lists with aggregation numbers to its customers.