Structure of our Forms

Here we provide an illustration of the individual levels using the AQC family as an example:

• 1st dimension, 1st level A0: e.g. clinic section: Normally includes all entry and exit information. Diagnoses of a patient collected during a hospitalization.
• 1st dimension, 2nd level A1: e.g. operation part: On level A1, for example, all operations performed on a patient during his hospitalization are recorded. This level can include 0 – n operations.
• 1st dimension, 3rd level A2: e.g. procedure part: On level A2, for example, all procedure parts during an operation are recorded. An operation may consist of several procedures or parts of procedures. This is the case, for example, if a change of surgeon has taken place during an operation or if a complication occurs during an operation which one wants to assign to a specific part of the operation.
• 2nd dimension, 2nd level B1: e.g. children: In the first dimension the case with the operations (e.g. caesarean section and additional operation on the following day) is handled, in the second dimension the twins which were born in that caesarean section.

Each case in the Adjumed system represents the complete hospitalization of a patient. This means that there is always exactly one case per patient and hospitalization. The patient is uniquely identified in the system per clinic / center by the patient number (PID) and the admission date / case start date. Multiple cases can be assigned to a patient using the PID.

For the identification of a specific case, an entry date and a PID are required. (Exception: for web service import only one case identification number (CID) is sufficient).

You as the customer determine with your recording and evaluation requirements which dimensions and levels your register consists of and which fields and codes you want to use.

We will be happy to advise you on setting up or making changes to your register. In the process of this dialog, you as the customer contribute your requirements and we contribute our experience as to which fields and codes it is useful to collect, when and where.