Contacts: general functions, suppliers, staff, care homes and other contact roles (Kontakte)
1. Purpose and scope
The contacts module (Kontakte, reached from the desktop and from the "Beratung" menu) is the single store of every address and of every contact-related setting in IXOS. Other modules (POS, invoicing, goods logistics, prescription management, delivery management, blister management, reports) read from it.
This chapter covers:
- General contact functions: search and hit lists, the multi-role contact model, creating contacts, switching and splitting roles, status (active / inactive / deceased), locking and deletion under data-protection rules, consent-declaration versions, information texts (notes, hints, POS messages), the data-subject access report and its history, scanning documents into the DMS, contact-related printouts, and the function-key overview.
- Role-specific contact pages for every non-customer role: providers/manufacturers (Anbieter), doctors (Arzt), field representatives (Außendienst), branches and partner pharmacies (Filialen & Partner), care homes, outpatient care services and hospitals (Heim / Pflegedienst / Klinik) including their structure and invoicing settings, payers (Kostenträger), suppliers/wholesalers (Lieferant) including purchase-condition agreements, ordering/transmission parameters and contract data, and employees (Mitarbeiter) including user accounts, permission roles and role management.
The customer role itself (customer master data, medication management, sales data) is described in another chapter; it appears here only where the shared mechanics touch it.
2. Key concepts and terms
| German term | English | Meaning |
|---|---|---|
| Kontakt | contact | One stored person, company or institution. Stored once, can hold several roles. |
| Kontaktrolle | contact role | The function a contact has for the pharmacy (customer, doctor, supplier…). Each role has its own data pages and settings. |
| Adressbucheintrag | address book entry | Contact with no business meaning (tax adviser, tradesman); name, address and phone only. |
| Anbieter | provider | Pharmaceutical manufacturer or distributor; national list maintained by the data service, own entries possible. |
| Lieferant (Großhändler) | supplier / wholesaler | Party the pharmacy orders from. Manufacturers that deliver directly are set up as providers that also hold the supplier role ("direct supplier", Direktlieferant). |
| Außendienstmitarbeiter | field representative | Sales rep of a wholesaler or manufacturer. |
| Arzt | doctor | Prescriber / GP of customers. |
| Heim / Pflegedienst / Klinik | care home / outpatient care service / hospital | Institutions the pharmacy supplies; can have a unit structure with residents or patients. |
| Kostenträger | payer | Health insurer or other body that pays for prescriptions. |
| Mitarbeiter | employee | Own staff (or staff of a partner pharmacy). Can have a user account. |
| Filial- oder Partnerapotheke / Mandant | branch or partner pharmacy / tenant | Member pharmacy of a group; set up by the vendor. |
| Firmenstamm | company master data | The own pharmacy's master record. |
| Verbund / Filialverbund | pharmacy group | Group of branch and partner pharmacies that exchange data. |
| Kontaktaustausch | contact exchange | Replication of contact data between pharmacies of a group. |
| Laufkunde | walk-in customer | Temporary customer record, deleted once its open transactions are settled. |
| PÄD-gepflegt (also written "PAD-gepflegt") | data-service-maintained | Record supplied and updated by the price/change data service; read-only. |
| ABDATA | national drug/provider reference data | Source of provider, payer and article reference data. |
| Sperren / Entsperren | lock / unlock | Data-protection lock: the contact disappears from normal use and its data is anonymised in transactions; precursor to final deletion. |
| Sperrfrist / Löschfrist | lock period / deletion period | Configured periods after which contacts are locked or deleted automatically. |
| Löschvorbehalt | deletion reservation | Reason a contact may not be deleted (open pickups, substitution therapy). |
| Einwilligungserklärung | consent declaration | Customer's written consent to storage of personal data; versioned. |
| Informationstexte | information texts | Notes, hint, POS / invoicing messages, info text attached to a contact. |
| Auskunft über personenbezogene Daten | data-subject access report | GDPR report of all personal data held about a person. |
| Klassifikation | classification | User-defined tag that can be assigned to contacts of one or all roles. |
| Struktur | structure | Tree of an institution's units (houses, wards, rooms) with residents. |
| Bewohner / Patient | resident / patient | Customer assigned to a home or care-service unit. |
| Faktura | invoicing (accounts-receivable billing) | Module that creates delivery notes, invoices, receipts and dunning letters for invoiced customers. |
| Fakturamodell | invoicing model | Named template of payment info, print options and forms. |
| Sammelschein | collective slip | Summary document across many invoices or delivery notes. |
| Einzelaufstellung | itemised statement | List of the articles on an invoice. |
| Eigenbedarf | own consumption | Goods consumed by the institution itself, as opposed to residents. |
| Konditionsvereinbarung | condition agreement | Dated set of purchase terms agreed with a supplier. |
| Effektiver EK | effective purchase price | Purchase price after applying all supplier conditions; basis of "optimal supplier" choice. |
| Apo-EK / ABDA-EK | list pharmacy purchase price | Official list purchase price. |
| RAEP (rabattfähiger Apotheken-Einkaufspreis) | discount-eligible purchase price | The part of the Rx purchase price on which discounts may legally be granted. |
| Anbieterpreis | manufacturer price | Manufacturer's selling price. |
| Buchungs-EK | booked purchase price | Purchase price actually booked at goods receipt (may already include an offer discount). |
| Hochpreisschwelle | high-price threshold | Rx price above which an article counts as "high-price" (preset 1238.53 EUR). |
| Rx / Sichtwahl (SW) / Freiwahl (FW) | prescription-only / behind-the-counter OTC / open-shelf self-service | Dispensing classes (Abgabebestimmung) used to scope conditions. |
| Auftragsart | order type | Normal order, special order, batch order, etc. |
| Auftragskennung / Unterauftrag | order identifier / sub-order | Identifier that splits a supplier order into separately handled parts. |
| Warenkorb | basket | Accumulating order proposal per supplier and order time. |
| Warenkorbermittlungsmodell | basket determination model | Rules deciding which supplier's basket an article goes into. |
| Angebotsliste | offer list | Supplier's list of special-priced articles. |
| Verhandlungssache | negotiated offer | Offer-list entry without a price; terms settled after the fact. |
| Skonto | cash discount | Discount for early payment; applied after all other discounts. |
| MSV3 | wholesaler ordering web-service standard | Protocol for orders, availability enquiries and contract data. |
| IDF | supplier identification number | Supplier's identifier used in transmission. |
| Bestellzeit / Bestellschluss / Lieferzeit | order time / order cut-off / delivery time | Order window and promised delivery. |
| Spätauftrag | late order | Order time flagged as late; baskets can be handled with special rules. |
| Benutzerkonto | user account | Login of an employee. |
| Bedienerregister | operator register | Numbered, named, coloured operator slot for fast switching at POS. |
| Berechtigungsrolle / Recht | permission role / right | Bundle of rights / single permission. |
| Arbeitsplatzschutz | workstation protection | Module that switches on the permission concept and assigns roles to workstations. |
| Rollenverwaltung | role management | Creating, changing and deleting self-defined permission roles. |
| Leiter / Apotheker / PTA / PKA | manager / pharmacist / pharmaceutical technical assistant / pharmaceutical commercial employee | Predefined organisational permission roles. |
| IK-Nummer | institution identifier | German identifier for insurers and institutions; checked against the IK numbering rules on save. |
| BSNR / LANR | practice site number / lifelong doctor number | German doctor identifiers. |
| ELO | DMS product | Document management system connected to IXOS. |
3. Data model
3.1 Contact and roles
- Contact: one record per person/company/institution. Kind: natural person or legal entity (customers can be switched between person and company later).
- Contact role (many per contact). Roles: Address book entry, Provider, Doctor, Field rep, Home, Hospital (needs licence IXOS.Klinik / IXOS.Klinik Profi), Care service (handled like a home), Payer, Customer (Kunde (Person), Kunde (Firma), Laufkunde), Supplier, Employee, Branch/partner pharmacy (tenant). Each role has its own pages and its own status. Rules for combining roles:
- The role is fixed when the contact is created; more roles can be ticked later (e.g. doctor + customer; supplier + customer + provider).
- Any contact without the customer role can be given it. Homes, care services and hospitals receive the customer role automatically, and the two stay in sync (changes and deletion of the institution apply immediately to its customer contact).
- The role behind the currently open master-data window cannot be removed from that window. A role can be removed only if nothing relevant depends on it (e.g. open pickups); otherwise a warning is shown.
- Branch/partner pharmacies cannot be created by the user (vendor support sets them up), and they are not offered in the role chooser. Typical combination: tenant + customer (company) + supplier. The own pharmacy carries "Firmenstamm" instead of "Mandant".
- Status per role: Active; Inactive (hidden from standard search and evaluation lists, found by advanced search, can be reactivated); Deceased (natural persons only; e.g. excluded from the birthday list). Additionally Locked (data-protection lock; see 4.6) for customer (person/company), doctor and employee roles.
- Common master data (Stammdaten) on every role: name (mandatory), first name, salutation, title, birth date (persons), cost centre (company customers; written to the e-invoice field BuyerReference), standard address (street, postcode, city, district, PO box…; copied to the Addresses page), standard communication (phone / fax / mobile with a standard number and optional numbers for invoices and deliveries; e-mail addresses for standard / invoices / deliveries, homepage; per e-mail address an optional password and a "link" flag), contact-exchange block (exchange flag, origin pharmacy, changed on / by), audit fields (created on/by, changed on/by on supplier records).
- Detail pages vary by role; the full set across roles is: master data, specific data, medication management, risk management, sales data, payments, discount models, addresses, user account (employees only), plus role pages such as classifications, structure, conditions, send/delivery parameters.
- Addresses (Anschriften): standard address plus optional invoice and delivery addresses.
- Classification (Klassifikation): name, description, classification kind (the roles it applies to: one role or all). Many-to-many with contacts.
- Information texts: notes (many; title, description, created at/by, changed at/by, done flag), one hint (with "show at POS" flag), POS message (pop-up flag, validity from-to), invoicing message (pop-up-at-order-entry flag, "take from POS" flag, own validity), info text (free text).
- Change history (Änderungshistorie): logs status changes, locking, consent changes and info-text changes (except notes).
- Access-report history entry: date-time, operator, contact role, search criteria, selected data-category tree.
- Consent-declaration version: creation date (serves as version label), trigger, optional note, "consents under this version remain valid" flag; customers reference the version they signed.
3.2 Provider (Anbieter)
- Data-service flag (PÄD-gepflegt) → read-only; provider number (unique, only for data-service providers); "my customer number" (own account number at the provider; requires the supplier role as well); assigned field reps (many).
- ABDATA reference data (read-only): ABDA name, name, name 2, name 3, short designation, delivery address, wholesale licence and manufacturing licence (each: not specified / no / yes / not required).
3.3 Doctor (Arzt)
- Specialty (Fachrichtung, from a list; abbreviation filled automatically), practice site number (BSNR), lifelong doctor number (LANR).
- Portal access (Arzt.connect): active flag, password, URL.
3.4 Field representative (Außendienstmitarbeiter)
- Master data, addresses, appointments, classification.
- Assigned companies: many-to-many with supplier and provider contacts (assignable from either side).
3.5 Branch / partner pharmacy (Filiale)
- Manager name (Leitung), short code (Kürzel), flag "settlement from internal goods exchange" (Verrechnung aus internem Warenaustausch).
- Processing workstation for cross-pharmacy stock withdrawal.
- Rank in the list of preferred branches.
- Visibility settings for exchanged contacts (group-wide and per pharmacy; see 4.12).
3.6 Home / care service / hospital
- Institution kind: home, care service, hospital.
- Further data needed for receipts: district court (Amtsgericht), register number, VAT ID.
- Structure: tree. Root = the institution; units (houses, wards, rooms) nested to any depth; residents/patients are customer contacts attached to a unit (homes and care services only; hospitals have wards but no patients). A customer belongs to at most one unit at a time (implied, not stated).
- Per unit: name, "append name to sub-units" flag, addressee (defaults to unit name), contact data (inherited from the parent, overridable), optional own customer role (created automatically when "separate invoice" is ticked).
- Per element (institution / unit / resident): invoicing settings (see 3.7); contact persons (function label such as contact person, manager, carer/guardian; name; first name; contact details); medication (for blistering); prescription-request recipient; delivery/packing preferences (preferred delivery type, separate delivery with own delivery note); agreements (hospitals/wards: separate delivery and billing via an own price scheme).
- Portal access: Heim.connect, Rezept.connect (homes/care services), Klinik.connect (hospitals), each with active flag, password and URL.
- Bank accounts with a "receipt" flag (one or two must be flagged to print receipts).
3.7 Invoicing settings (Faktura) per structure element
- Control flags: separate invoice (Gesonderte Rechnung); own settings (Eigene Einstellungen). Both always on at the institution root.
- Invoicing mode: invoice = total / per customer; receipt count; collective invoice slip = no / total / per unit; itemised statement = no / total / per customer; bill own consumption separately; form a batch for invoice print; respect structure for invoice print; invoice sort order.
- Blistering (with blister module): billing article code per blister; combine billing positions; invoicing-order granularity (per blister order / per home unit / per resident).
- Payment info: payment method (transfer / direct debit); invoicing cycle (immediate, daily, weekly, half-monthly, monthly, quarterly; manual; not specified); payment-terms model; dunning-terms model; alternative pharmacy bank account; flat service fee (label + gross amount).
- Print options and forms (see 4.17).
- Optional invoicing model supplying payment info, print options and forms.
3.8 Payer (Kostenträger)
- Payer type: statutory insurer (with sub-type) / private insurer / other; IK number; contract payer number (Kassennummer); ABDA name.
- Specific data: postage limit (display only); billing route for care aids (via billing centre / direct with the care insurer).
- Discount-contract article lists (read-only, from data service; add-on RxAktuell).
3.9 Supplier (Lieferant)
- Master data: main-supplier flag, short code, my customer number, "manufacturer price" flag, assigned field reps, DMS-documents indicator.
- Condition agreements (many per supplier; dated): see 3.10.
- Offer-list links (many; linked in a separate module) with per-list and per-dispensing-class rules (see 4.25).
- Settings: auto-ready-to-send / auto-transmit, ignore in basket determination, hide in price tables (partners), return-slip sort, delivery-advice capture mode (MSV3 2.0), interim order at wholesaler and disposition-time shortening (direct suppliers), decentralised delivery (partners), sub-orders.
- Sub-order: order identifier (≤20 characters, no spaces or special characters), description, selection criteria (article query, customer query, dispensing class, back-order types), order type (normal / special / batch), active flag, priority; vendor sub-orders (e.g. narcotics, always priority 1) are fixed.
- Send parameters: protocol (MSV3), supplier IDF, default order type, default order identifier, MSV3 access (service provider and version V1/V2, branch ID, user ID, password), online enquiry (active, own column vs pooled, online user ID, "relevant direct supplier").
- Delivery parameters: dispatching warehouse, invoicing wholesaler (for direct suppliers), usual delivery duration, excluded delivery weekdays (default Sunday), order-time rows (order time, cut-off, delivery time HH:MM, weekdays, late-order flag, auto-create-basket flag, source = contract or manual).
- Contract data (supplier-reported): stored-since date; support/authorisation for normal, special, batch orders and take-back offers; substitution agreement; specific/unspecific response; free order identifiers per order type; regular order times and special days.
- Payments: account paid from, account for direct debit, creditor account number, "DATEV export of single invoices" flag, bank accounts.
- Preferred online-enquiry ranking (up to 10 wholesalers + provider group).
3.10 Condition agreement (Konditionsvereinbarung)
- Header (General page): created/changed on/by, valid from, remark, order types for optimal supplier, provider restriction list, invoice mode (collective / single invoice), Rx high-price threshold (basis + amount), minimum order value (basis + amount), minimum pack count (dispensing class + number), agreed average Rx pack price per month (basis + amount), monthly turnover target.
- Turnover-target settings: counted dispensing classes, order types, returns cut-off day, excluded articles, excluded offer lists.
- Article discount rules (ordered by priority): scope (Rx / SW / FW, order types, assortment groups, include-only / exclude tables of product-group keys, articles, article lists, providers) and value rows (value, reference type, price band, quantity band).
- Monthly discount rules: scope (as above plus Rx high-price) and a tier matrix (up to two criteria among turnover, pack count, average pack price) with the selected expected tier.
- Cash-discount rules: % value, dispensing classes, order types, assortment groups, include/exclude tables.
- Fees: postage and packaging, delivery, cool box, cold-chain articles, narcotics (per document or per order), returns (per document or per order), disposition order, special delivery/extra tour, below-minimum-order-value, below-minimum-pack-count; separately for "general" and "offer lists".
- Reusable article lists (from a saved report query or manual selection; imported lists).
3.11 Employee (Mitarbeiter)
- Master data as common, plus system-generated external employee ID (identifies the employee across the group).
- Specific data: personnel number (user-assigned, max 10 characters), hiring date, gross salary, job title (from list; "Bote" = courier), pharmaceutical-carer flag, qualifications (free text), commission points, commission amount, ELO user name.
- Payments: account salary is paid from; bank accounts with "salary account" flag.
- Message-type visibility: System / Pharmatechnik / Branches (on/off each).
- User account: active flag, operator register (position, name, colour; up to 500 operators in up to 50 levels), password, picture, fingerprints (max 10, one per finger), assigned roles, individually assigned rights.
- Permission role: name, description, contained rights, contained roles, kind (predefined organisational / predefined activity-related / self-defined), counts of employees and workstations holding it. Roles can be assigned to employees and to workstations.
- Right: belongs to a rights group; can be licensed/enabled or not ("freigeschaltet").
4. Features
A. General contact functions
4.1 Contact search and hit lists [GENERIC]
- Purpose: find any contact quickly in the role the user is working with.
- Behaviour:
- A navigation bar selects the role; the hit list shows only contacts holding that role (the customer tab shows both customers and walk-in customers). Navigation groups: Warenlogistik (providers, suppliers, field reps), Arzt, Klinik/Heim, Kostenträger, Mitarbeiter, Filialen & Partner, customers.
- Name search; the default mode is standard search, with phonetic search available as an alternative (its button appears only while standard search is the default). Typing starts a search even when the field has no focus.
- Advanced search (Erweiterte Suche): extra filter criteria; the last-used criteria are shown again. It is the only way to find inactive, deceased and locked contacts (locked ones are shown in red).
- If the selected role has no hits, the system offers to search the other roles.
- "All exchanged contacts" option: only visible when the pharmacy restricts visibility of contacts exchanged from other group pharmacies; ticking it adds the other pharmacies' exchanged contacts to the hits (optionally only after entering a birth date; see 4.16).
- Payer search always also matches the official data-service name.
- Hit lists can be sorted by any column (alphabetical, date or icon) and the columns can be configured per contact type (e.g. for employees: hiring date, operator-register position and name, personnel number).
- Indicators: info-text icon; field-rep icon on providers (tooltip lists names and mobile numbers of the assigned reps).
- Record switcher on detail pages: step through the contacts of the last search without going back to the list.
- Privacy notice: customer personal data may only be stored with written consent.
4.2 Multi-role contacts and role switching [GENERIC]
- Purpose: store a party once even though it plays several parts (a doctor who also buys practice supplies; a provider that is also a direct supplier and a customer).
- Behaviour: each role keeps its own data. Example: the doctor role holds the specialty; the customer role of the same person holds invoicing permission and sales statistics.
- To see another role's data: either select that role in the navigation and search again, or use "switch contact role" (Kontaktrolle wechseln) inside the details of a multi-role contact. This matters especially for suppliers/providers, and for homes, whose invoicing settings sit on the customer role.
- After one role of a multi-role contact has been deleted, it can be added back from a remaining role (e.g. give a supplier contact the provider role again; give a doctor contact the customer role again).
4.3 Create a contact (Neuen Kontakt anlegen) [GENERIC]
- Trigger: "New" in the contact module.
- Inputs: exactly one role chosen in a role-selection dialog; it defaults to the role active in the navigation bar. When "new" is used from inside an existing contact's details, the same role is used and the master-data page opens directly.
- Rules: only the name is required. First letters are capitalised automatically in title, first name (only for national contacts), name, street, city and country.
- Branch/partner pharmacies cannot be created by the user.
4.4 Change contact role (Kontaktrolle ändern) [GENERIC]
- Converts a walk-in customer or an address-book entry into a full customer.
4.5 Split contact roles (Kontaktrollen trennen) [GENERIC]
- Purpose: undo an unwanted combination of roles on one contact.
- Use cases: a contact was wrongly created as a direct supplier and should continue only as a supplier; an employee must be deleted but should remain a customer; clean-up while merging duplicates.
- Trigger: on the master-data page of a multi-role contact (offered from provider/supplier details).
- Rules: roles that coexist with the customer role can be split off, except home, hospital and branch. The user ticks the roles to move; a new contact is created holding those roles; unticked roles stay on the original.
- Permission: "Kontakte allgemein: Kontaktrollen trennen" (contained in role Leiter).
4.6 Status, locking and deletion (Kontakt sperren und löschen sowie Kontaktstatus ändern) [GENERIC — driven by EU data-protection law]
- Purpose: retire contacts in a way that respects data-protection duties: hide them, lock them (anonymise), or delete them permanently.
- Trigger: "Delete" in the contact list opens a choice: mark inactive, mark deceased, lock the contact (customer person/company, doctor, employee), or, for all other deletable roles, delete the contact completely.
- Inactive / deceased:
- Hidden from standard hit lists and evaluation lists, reachable only via advanced search; data kept; can be reactivated.
- Because data stays stored, a valid consent is still needed.
- Typical reasons. Inactive: long absence, hospital stay, living abroad. Deceased: open pickups remain, relatives may still want a copayment list.
- A customer cannot be set inactive if, in a branch group, the customer has access to the "Meine Apotheke" app in more than one branch (message shown).
- Setting a customer role inactive or deceased while the customer is assigned to a home asks whether to remove the home assignment (Yes = removed from the structure; No = stays, shown as inactive/deceased).
- Users cannot set their own status to inactive or deceased.
- An employee set inactive or deceased has their user account deactivated automatically: the operator register is hidden (no login possible) and "account active" is unticked and greyed. Reactivating the employee does not reactivate the account, but the checkbox becomes editable again.
- Lock (Kontakt sperren):
- Available for customer (person), customer (company), doctor and employee. It is the required step before final deletion. Typical reasons: no valid consent, or consent revoked.
- Effects: the contact disappears from standard search, is found only via advanced search with "show locked contacts" ticked and is displayed in red; it cannot be used in further processing; transaction and documentation data that reference it are shown anonymised.
- Blocked when the customer has unfinished transactions (open pickups) and/or a substitution therapy on file.
- Field reps and employees: a confirmation prompt appears before locking; the status change itself is still made in master data. A locked field rep's company assignments are hidden but kept, and come back on unlock.
- All status changes and locks are written to the change history.
- Unlock (Entsperren): the contact returns to standard search and its data is shown in clear again.
- Final deletion (manual): find the locked contact via advanced search, delete, confirm; this cannot be undone. If another contact uses this contact as an address, the system offers to convert that reference into a local address on the other contact first.
- Delete completely: for other deletable roles (address book, provider, supplier, payer…), deletion is immediate and permanent without locking. Address-book entries are always deleted immediately.
- Cannot be deleted: employees who hold the currently active operator register; customers with the branch or home role; supplier contacts maintained by the price/change data service.
- Permission (with the permission concept active): "Kontakte allgemein: Gesperrte Kontaktdaten bearbeiten" (in role Leiter) is needed to see locked contacts, to unlock them and to delete them finally. The data protection officer is the intended user.
4.7 Automatic lock and deletion periods [GENERIC — data-protection retention]
- Configuration parameters "Sperrfristen für personenbezogene Daten" (lock periods for personal data) and "Sperrfristen für Laufkunden" (lock periods for walk-in customers) lock contacts automatically.
- "Löschfristen für gesperrte Laufkunden" and "Löschfristen für Personenkunden" delete them automatically after the period, counted from the date of last use, unless a deletion reservation applies (unfinished transactions such as open pickups, or a substitution therapy).
- In a branch group: sales data (dispensing date) exchanged between branches restarts the lock period in all branches, so the contact is locked everywhere at the same time if the same period is configured. For deletion, the shortest period configured in the group applies to all branches.
- Walk-in customers are temporary by design and are removed once their transactions (back-orders, pickups, credit) are closed.
4.8 Merge duplicates (Dubletten bearbeiten) for suppliers and providers [GENERIC]
- Purpose: clean up providers/suppliers that were created twice.
- Inputs: up to 12 source contacts (to be removed) and one target contact. Only self-created contacts are offered; data-service-maintained contacts are excluded, and suppliers of data-service-maintained providers cannot be deleted.
- Behaviour: no contact data or settings are merged. Only goods-logistics transactions (baskets/order proposals, orders) move from the sources to the target; then the sources are deleted.
4.9 Consent-declaration versions (Aktualisierung der Einwilligungserklärung) [GENERIC — data-protection consent]
- Purpose: know which wording of the consent each customer signed, and force re-consent when it changes materially.
- Automatic new version whenever: the consent print form changes; the set of pharmacies in the group changes; the alternative text for the pharmacy list changes; the standard print form changes. A version can also be created manually, with an optional note.
- Management window (permission "Einstellungen Einwilligungserklärung pflegen"): shows the current version (creation date = label, trigger, note) and previous versions; versions not assigned to any customer are greyed out. For each previous version a checkbox says whether consents given under it remain valid. If unticked, all consents signed under that version become invalid and customers must sign the new version.
- Signalling: buttons in customer master data and in the hit list (if configured) show that an update is needed. At POS, when the customer is selected: if the notice is enabled, the consent window opens; otherwise, while "Nutzung der Einwilligungserklärung in IXOS" is on, a yellow warning triangle appears on the sales-data button.
- Revocation: record consent to data storage as "not granted", then lock the contact.
- The signed version is visible in the consent window and in the change history.
- Reports: queries "Einwilligungserklärung" and "customers with medication management but without consent for care-relevant data"; fields include consent for care-relevant data, consent granted, advertising consent (digital / post / phone), signature, version, handed out on. Mass changes and printing go through report result processing.
4.10 Information texts (Informationstexte) [GENERIC]
- Purpose: attach free-text knowledge to a contact and surface it at the right moment (POS, order entry).
- Availability: all roles; hint and messages only for the customer role.
- Opened from: search and details; automatically at POS when a message text is set to pop up; from "customer info at a glance" (licence IXOS.Kunde).
- Types:
- Notes (Notizen): unlimited running entries (advice notes, sales notes, supplier talks). Fields: title, description, created at/by, last changed at/by, done flag. Open notes sort first. Search also covers descriptions. Notes can be edited, set done or undone, and deleted (with confirmation).
- Hint (Hinweis): one text with "show at POS"; shown directly at POS when the customer is selected.
- Message texts (Meldungstexte): signalled by an info button at POS and at invoicing POS. POS variant: "pop up at POS" plus an optional validity period. Invoicing variant: "pop up at order entry", "take message text from POS", own validity period. The system writes messages automatically, e.g. on customer online registration for the "Meine Apotheke" app, and on stopping a medication with reason "inpatient stay" (if parameter "Info bei Med.-Abbruch Grund 'station. Aufenthalt'" is on).
- Info text (Infotext): plain free text.
- Delete: removes the text and its POS display flag; deleting the POS message also deletes the invoicing message if "take from POS" was ticked.
- Mass maintenance via report result processing: assign, adapt, append, overwrite, partially delete (words from the hint; whole lines containing a given text in messages/info texts). To mass-edit an invoicing message that is taken from POS, first unlink it (take-from-POS = No), then edit it in a second run.
- Display: hit lists show an info-text indicator; in sales an info button appears if any note, info text, hint or message exists. With "customer info at a glance", a pop-up message opens that window and appears in bold in the profile; notes can be created there at POS; empty pages are hidden.
- Changes (except notes) are tracked in the change history.
4.11 Data-subject access report (Auskunft über personenbezogene Daten) and history [GENERIC — GDPR right of access]
- Permission: "Kontakte allgemein: Auskunft über personenbezogene Daten erstellen" (role Leiter).
- Trigger: select the customer, then "personal data". The search-criteria window also allows "manual inputs" for a person not stored as a contact. A checkbox "consent declarations are managed in IXOS" drives the parameter "Nutzung der Einwilligungserklärung in IXOS"; if it is off, the report does not mention missing consent.
- Selection: a tree of personal-data categories; items can be ticked or unticked. Family members who appear on joint receipts (subtotals) are listed and can be deselected.
- Output: print preview; locked data is not included. Can be sent to printer, PDF, DMS or Excel.
- Group rule: in a branch group, each branch has to produce its own report for the answer to be complete.
- History (Auskunftshistorie): list of produced reports, newest first: date-time, operator, contact role (customer person/company, doctor, employee), search criteria; details show the category selection used. Locked or deleted contacts do not appear in the history.
4.12 Document scanning to DMS (Dokument scannen und in ELO übertragen) [GENERIC]
- Precondition: the ELO document management system is connected.
- Where: details of customer, employee and supplier contacts; also at goods-receipt booking and POS payouts (offered automatically if configured: just put the paper in the scanner).
- Trigger: "scan document", or feeding the scanner while details are open.
- Scan dialog: detected format; reorder pages; rotate 90° left/right; discard pages; apply an action to the current page, all pages or a custom selection; preview.
- Filing: category (main folder; default "Allgemein", which lands in the DMS inbox "Postbox" for manual filing) and area/document type, as configured in company master data > DMS > categories/document types.
- The supplier master data shows an indicator when DMS documents exist for the supplier and can jump to them.
- An employee's ELO user name links the employee to the folder of that name in the ELO inbox.
4.13 Classifications (Klassifikationen) [GENERIC]
- Same mechanism on every role page (provider, doctor, home/care service/hospital, payer, supplier, employee, field rep).
- The page lists assigned classifications (name, description, kind = roles it applies to). Classifications are assigned through a "manage classifications" window; only those defined for this role or for all roles can be chosen.
- "Delete classification" deletes the classification itself (after a warning) and removes it from every contact that still has it.
4.14 Address entry assistance [GENERIC]
- Works in master data, addresses and the quick creation of customers.
- After entering a postcode and moving to the city field, a list of matching cities opens (filled directly if the postcode is unique). Typing a city name suggests cities with postcodes; a postcode typed into the city field also works.
- Ranking: first the matching places from the pharmacy's own contacts, ordered by how often they occur; if there are few, further matches from the built-in address database are shown below in grey; if 10 or more come from the own contacts, none are added from the general database. At most 50 suggestions.
4.15 Standard communication and secure e-mail [GENERIC]
- Phone/fax/mobile numbers with one standard number and optional numbers for invoices and deliveries; international numbers allowed (noted for suppliers).
- E-mail addresses for standard, invoices and deliveries; homepage.
- Per e-mail address an optional password: attachments are then converted to PDF and sent encrypted. Alternative "link" flag: attachments go out as a download link; a password is mandatory and the content is always encrypted. The recipient must know the password.
- The pharmacy itself is responsible for encrypting health data sent to private persons (GDPR).
4.16 Contact exchange and visibility within a pharmacy group [GENERIC — multi-branch]
- Exchange flag on master data (group only): the whole master-data page is replicated to the other pharmacies; other pages are exchanged only in part (stated per page). Fields: origin (pharmacy that created the contact), changed on/by.
- Legal-entity contacts: exchange can only be excluded at creation, by unticking the flag before the first save; after that they are always exchanged. If a legal-entity contact also has a person role, changing the flag affects the other role too (a doctor who is exchanged makes the customer contact exchanged).
- Employees: exchange settings for employee contacts may differ from those of other contacts; the system shows notices when roles are managed.
- Permission roles and rights (and changes to them) are exchanged when contact exchange is enabled; the assignment of rights to employees is not.
- Visibility of exchanged contacts (Anzeige und Verwendung von Kontakten festlegen; permission "Massenbearbeitung von Kundendaten durchführen"): decides whether contacts from other group pharmacies appear in standard and advanced search and are considered by prescription scanning at POS. Useful before the first duplicate clean-up when branches are close together.
- Group-wide: "all exchanged contacts of other group pharmacies visible" (on = visible everywhere by default; off = none visible by default); "all exchanged contacts of the contact-exchange sub-group visible" (information only, always on inside a configured sub-group); sub-group name (only shown in a sub-group); "search non-visible exchanged customers only with birth date" (extending a search to all exchanged contacts then asks for a birth date).
- Per pharmacy: "use deviating settings" (off = group-wide rules apply); then one of: all exchanged contacts visible / only those of selected pharmacies (choose in a table) / none.
- Hidden contacts can still be pulled into a single search with "all exchanged contacts". Electronic capture (e.g. reading an insurance card) also considers hidden exchanged contacts and proposes one on an exact match of first name + name + birth date, or of the insurance number.
B. Providers, doctors, field representatives, payers
4.17 Provider contacts (Anbieter-Kontakte, ABDATA page) [DE-SPECIFIC]
- Purpose: view the nationally maintained list of manufacturers/distributors, mark providers you buy from directly as suppliers, and create own providers.
- Behaviour:
- Data-service providers carry the "maintained by data service" flag and are updated by the change service; their master data is read-only. Communication entries delivered by the service are read-only and marked; the user can add own entries and make one of them standard.
- Extra roles: customer (company), if the pharmacy supplies the provider; supplier, if the pharmacy orders directly.
- Provider number (unique, only for data-service providers); "my customer number" (own account number with the provider, enterable here or on the supplier data; needs the supplier role); one or more assigned field reps (pick or create).
- ABDATA page (read-only): official provider name, names 2/3, short designation, delivery address, wholesale licence and manufacturing licence (each: not specified / no / yes / not required).
- Idea underneath: a centrally maintained, read-only master list of manufacturers with regulatory licence flags, extendable with local entries.
4.18 Doctor contacts (Arzt-Kontakte) and doctor portal access [GENERIC core; identifiers DE-SPECIFIC]
- Purpose: keep prescriber data at hand for queries; doctors are linked to customers on the customer's medication-relevant data page (other chapter).
- Data: common master data; roles doctor and customer (person); specialty from a list (abbreviation filled in); practice site number (BSNR) and lifelong doctor number (LANR).
- Rules: with parameter "Autom. Arztzuordnung bei Rezeptscan" on, the BSNR lets prescription scanning match manually created doctors automatically; the LANR can be taken over from a scanned prescription.
- Portal access (Arzt.connect, paid add-on web portal): per doctor an active flag, a password (set via "assign password", agreed with the doctor; always displayed as ten asterisks so its length is hidden) and the URL. "Open page" only shows a notice: the pharmacy cannot log in with a contact's credentials; it uses its own pharmacy login to the Connect portal from the office menu.
- Idea underneath: prescriber registry keyed by national practitioner and practice IDs, used to auto-match scanned prescriptions; optional prescriber portal with per-prescriber credentials.
4.19 Field representatives (Außendienst-Kontakte) [GENERIC]
- Purpose: record reps of wholesalers/manufacturers and which companies they look after.
- Data: master data (name mandatory, address, phones), addresses, appointments, classification.
- Behaviour: once at least one rep exists, an "Außendienst" tab appears in contact search under goods logistics. The "Companies" page assigns supplier or provider contacts (picked from contact search) and removes assignments; providers and suppliers can also assign reps from their side (many-to-many).
4.20 Payer contacts (Kostenträger-Kontakte) [DE-SPECIFIC]
- Purpose: view data-service-maintained payers (read-only further data) and create own payers (name mandatory).
- Data: payer type (statutory insurer, with a second list for the sub-type / private insurer / other insurer); IK number, validated against the IK rules on save, with a warning on mismatch that the user confirms (does not block); contract payer number (Kassennummer); official ABDA name.
- Specific data: postage limit (amount up to which postage can be reimbursed; display only, no function yet); billing of care aids (Pflegehilfsmittel) via billing centre (like prescriptions) or directly with the care insurer. The page intro mentions special copayment agreements as an example, but no such field is described.
- Discount contracts page (Rabattverträge; paid add-on RxAktuell): which articles this payer has discount contracts for, filterable by article name. Two tables: (a) current contract articles, including those that will drop out with an imported but not yet activated data update; (b) articles newly added from the activation date of that update.
- Idea underneath: payer registry with identifiers and billing route, and payer-specific preferred-product lists that change on a known activation date.
C. Branches and partner pharmacies
4.21 Branch / partner master data (Filialen & Partner) [GENERIC — multi-branch]
- The list shows branches and, depending on the search, the chain head office.
- Master data is set up centrally by vendor support when the group is created; the pharmacy cannot edit the contact data. Its standard address is also copied to the company master data module (for the own pharmacy).
- Further data: manager name; short code within the group; "settlement from internal goods exchange":
- Off: the member is a separate company that is only partnered, so goods exchange with it is not internal.
- On: settlements for internal goods exchange between chain members are issued net without VAT; a separate invoice number range is used for these net invoices so that gross invoices keep a gapless sequence; also implicitly switches on "invoice with net prices" on the branch's customer master data.
- Addresses page shows the other branch's standard address from its customer role; delivery and invoice addresses are maintained there.
4.22 Cross-pharmacy stock withdrawal setting (Einstellungen (Filiale)) [GENERIC]
- For "cross-pharmacy stock withdrawal" (Übergreifende Lagerentnahme): choose the processing workstation in the public pharmacy that handles stock-transfer orders coming from the hospital-supplying pharmacy. If an automated picking system is attached, goods come out of the output chute configured for that workstation. Once set, the process runs fully automatically.
4.23 Preferred branches (Bevorzugte Filialen festlegen) [GENERIC]
- Order the group's branches by rank (move up/down). In the article search hit list, tab "Filialen" shows stock per branch: own pharmacy first, then the branches in this order.
D. Care homes, care services and hospitals
4.24 Institution contacts (Heim-, Pflegedienst- und Klinikkontakte) [GENERIC]
- Purpose: supply institutions with their own structure; attach customers as residents (homes) or patients (care services) to any unit; configure invoicing per unit.
- Data: master data like a doctor's but without personal fields; contact-exchange rules of legal entities; further data needed for receipt printing in invoicing: district court, register number, VAT ID.
- The institution role and its automatically created customer role are kept in sync (including deletion).
- Hospitals require the licence IXOS.Klinik / IXOS.Klinik Profi.
- Printouts from search or details: home-inspection protocol template, blister labels, blister plan, stock lists, range lists, prescription requests, weekly plan; hospitals: address labels only.
4.25 Structure (Struktur) [GENERIC]
- Purpose: model houses, wards and rooms; hold residents; carry invoicing settings read by the invoicing module; with the blister module, activate blistering for a home/care service and plan weekly blister production for all its residents.
- Tree: root = institution (icons distinguish home, care service, hospital). Filter starts at the first character; the term is split at spaces, commas and asterisks and every part must occur in the name (e.g. "in*ger" matches "Hinz, Gerhard" and "Gerber, Ingeborg"); umlauts match their two-letter spellings (Ö=OE, Ä=AE, ß=SS). The filter is cleared when moving to another institution. Expand/collapse all or the selection.
- Add unit: inserts a placeholder under the selected element ("new home/care unit" or "new hospital unit"). Enter the name; other contact data except the addressee is inherited from the parent and can be changed; the addressee defaults to the unit name. Focus stays on the new unit, so adding again creates a child; reselect the parent to create a sibling.
- Edit: select, change, save. Delete unit: removes the unit and all its sub-units after confirmation; only possible if no residents/patients are assigned anywhere below.
- Residents: create a new customer and assign it, or assign an existing customer ("assign resident"); remove an assignment. Homes and care services only.
- Name composition: each name has "append for sub-units" / "do not append". The resulting extended name is used as the addressee and shown in customer search for sub-units that have a customer role. Example: home "Pflegeheim am See" (append) > "Haus A" (do not append) > "Station 1" gives addressee "Pflegeheim am See Station 1".
- Detail tabs for the selected element: master data; invoicing (4.27); contact persons (rows with a function such as contact person, manager, carer/guardian, plus name and contact data); medication (for blistering); prescription request (recipient choice); delivery/packing (preferred delivery type; separate delivery with its own delivery note for a unit); agreements (hospitals/wards: separate delivery with own delivery note and billing via an own price scheme).
- Convert into a family ("Familie aus Patienten"): when a home structure was misused to manage a family, create a family from the residents; the home's customer becomes the family's contact person (changeable later). The home/care service is deleted; this cannot be undone.
- "Customer details" jumps to the customer-role page of the selected element (institution, separately billed unit, resident, separately supplied unit).
- The detail area can be collapsed and resized (display only).
4.26 Assigning residents and patients (Zuordnung von Bewohnern/Patienten) [GENERIC]
- From the institution side (Structure page): select the resident, "change assignment", pick the target institution or unit in a tree dialog, save. Within the same home, drag and drop in the tree. Remove: delete the assignment and save.
- From the customer side (customer pages "Medikationsmanagement" or "Faktura / Heim", "Faktura / Pflegedienst"): "assign home/care service" (if none yet) or "change home assignment", pick the unit, save; "delete home assignment" with confirmation.
- Setting the resident's customer role inactive/deceased prompts whether to remove the assignment.
4.27 Invoicing settings per structure element (Fakturaeinstellungen) [GENERIC]
- Purpose: decide, for an institution and optionally for each unit and each resident, how invoices, receipts and itemised statements are produced.
- Scope and sync: set on the institution, optionally overridden on units (wards) and residents. Settings are synchronised both ways with the invoicing settings on the corresponding customer contacts.
- Control flags per unit/resident:
- "Separate invoice" enables the invoicing-mode sub-tab; ticking it on a unit creates the unit as an independent customer contact automatically.
- "Own settings" governs payment info, print options and forms. If an invoicing model is selected these come from the model and are read-only; without a model (or after removing it) they are edited in the sub-tabs.
- Both are always on at the root and cannot be switched off.
- Automatic contact settings: creating a home, care service, hospital, unit or ward grants invoicing permission automatically. An existing customer assigned as resident keeps all its own settings (including preferred payment type and exchange flag) but always receives invoicing permission.
- Defaults: home: one total invoice, no receipt, no itemised statement, no separate own-consumption invoice. Care service: invoice per customer, no batch for invoice print. Hospital: total invoice, no receipt, itemised statement or own-consumption invoice.
- Inheritance: new units inherit the institution's settings; new or newly assigned residents inherit the settings (including invoicing model) of their home/unit. If the resident had deviating settings as a customer, they appear when "own settings" is ticked and can be saved. Assigning an invoicing model to residents through report mass processing ticks "own settings" automatically. Deleting an invoicing model that residents use makes them fall back to the parent unit's settings.
- Invoicing mode sub-tab:
- Invoice: "total" = one invoice for the whole institution or unit, except units/customers with separate invoices; "per customer" = one invoice per customer (institution, unit, resident, hospital, ward).
- Receipts: number printed at invoice creation; always that number per individual home customer, provided the resident has no separate invoice. Hospital receipts are not offered for automatic printing.
- Receipts and itemised statements are built from created invoices, so zero-sum options matter. If "print zero-sum delivery notes on invoice" is off, those delivery notes are missing from the invoice, receipt and itemised statement; if "create zero-sum invoices" is off, those invoices are missing from receipt and statement. To use them as evidence of medication supplied, switch both on; more reliable evidence comes from medication management, the collective delivery-note slip or the total-purchases list.
- Collective invoice slip: no / total (all invoices of the institution except separately invoiced units/customers) / per unit (one per unit directly below the institution or unit, provided invoices are per customer or ward; with a total invoice the slip contains just that).
- Itemised statement: no / total (all invoices) / per customer (if invoices are per customer).
- Bill own consumption separately: separate invoice for the institution's or unit's own consumption, for when its own administration is separate from residents' administration; possible even with a total invoice.
- Form a batch for invoice print; respect the structure for invoice print; invoice sort order (4.28).
- Blistering sub-tab (blister module only): billing article code per blister (an article that must exist in the article master; used to bill the blister fee); "combine billing positions" (on = blister fees summarised per blister unit on one invoice; off = listed per resident); invoicing-order granularity: per blister order / per home unit / per resident.
- Payment info sub-tab:
- Payment method: bank transfer or direct debit.
- Invoicing cycle: automatic with immediate / daily / weekly / half-monthly / monthly / quarterly (used by invoice runs, e.g. "all monthly customers"); manual (excluded from automatic runs and must be named explicitly); not specified (no preference).
- Payment-terms model and dunning-terms model (chosen from predefined models).
- Alternative pharmacy bank account for settlement (choice from the pharmacy accounts in company master data). Which account is used: 1) direct debit to the company account, 2) the alternative pharmacy account, 3) the standard account in company master data.
- Flat service fee: a label (needed for the line to appear on the invoice) and a gross amount (if empty, the line prints with 0.00). The line has no order or delivery-note position behind it, so it cannot be analysed in reports or transferred to MMR (external system, not explained). It can be removed from a single invoice in the invoice total screen.
- Print options sub-tab and forms sub-tab: see section 10.
4.28 Invoice print sorting for homes and hospitals [GENERIC]
- Default: one batch per home/hospital; inside it, invoices sorted by structure, and within a unit by invoice recipient.
- Settings on the institution: form a batch yes/no; respect structure yes/no; sort order (e.g. standard, by customer).
- No batch: invoices of the home's customers/wards are mixed in with all other customers in a general invoice run; when invoicing a single home, the structure is ignored and the standard sort applies (by invoice recipient, customer or document number, per global parameters). The sort cannot then be changed on the home.
- Batch without structure: all invoices in the batch sorted by invoice recipient regardless of unit (changeable, e.g. by customer). Recommended when no collective slip is printed (the slip itself is always ordered by structure).
- Print sequence without structure: (1) collective slip for home/hospital and units plus itemised statements; (2) the home/hospital's invoice; (3) invoices of residents/wards per the sort setting; (4) invoices for separately invoiced units; (5) invoices for separately invoiced residents.
- Print sequence without batches: (1) collective slip and itemised statements; (2) all invoices (homes, units, residents, separate units/residents, own consumption, other customers) sorted per global parameters.
- Global parameters: "Standardsortierung bei Rechnungsstellung", "Standardsortierung der Rechnungskopien", "Automatischer Quittungsdruck für Heime". If copies print at the end, they print in one block with end-printed receipts and itemised statements; blocks follow the invoice print order; per customer: invoice copy, receipt, itemised statement.
4.29 Institution bank accounts and receipts (Zahlungsverkehr Heim/Pflegedienst/Klinik) [GENERIC]
- Table of bank accounts with a detail editor (add, edit, delete with confirmation).
- "Receipt" flag: to print receipts for a home/care service from invoicing, at least one and at most two accounts must be flagged; flagged accounts appear in the receipt footer.
4.30 Institution portal access (Zugangsdaten) [GENERIC idea; product-specific]
- Three paid add-on portals: Heim.connect and Rezept.connect (homes/care services), Klinik.connect (hospitals). Each with active flag, password (set by the pharmacy as agreed with the institution; the password policy applies; displayed as ten asterisks) and URL.
- "Open page": Heim.connect / Klinik.connect show the notice that the pharmacy cannot log in with the contact's credentials (use the pharmacy's own Connect login in the office menu); Rezept.connect opens the support website.
4.31 Home inspection protocol template (Heimbegehungsprotokoll) [DE-SPECIFIC]
- Printed from home search or details. A dialog collects values printed onto the template: planned inspection date; home name and ward/unit name (editable); management (filled if a contact person with function "manager" exists); contact person; person responsible for ordering and accepting medicines; person responsible for removing and distributing medicines; date of last inspection; counts of defects from earlier inspections: total found, not remedied (open), not remedied (in progress), remedied (closed). Then preview and print.
- Idea underneath: periodic pharmacist inspection of medicine handling in supplied institutions, with defect follow-up counts.
E. Suppliers
4.32 Supplier master data (Lieferanten-Kontakte) [GENERIC]
- Name mandatory; common roles/status/address/communication; audit (created/changed on and by).
- Further data: main-supplier flag (Hauptlieferant); short code for quick selection (e.g. in goods logistics); my customer number at this supplier; "manufacturer price" flag (use the manufacturer price as basis when capturing an order); assigned field reps (one or more; can create new).
- DMS indicator and jump to the supplier's documents.
- Duplicate clean-up as for providers (4.8). Data-service-maintained suppliers cannot be deleted.
- F9 prints a blank condition-agreement form (4.45).
4.33 Condition agreements and optimal supplier (Konditionen) [GENERIC core; price bases DE-SPECIFIC]
- Purpose: record the purchase terms agreed with each supplier so the system can compute an effective purchase price per order line and pick the supplier with the best one (supplier optimisation).
- Permission: role Leiter or Konditionsverantwortlicher (conditions officer) to view and edit.
- Agreement list: outdated, currently valid (marked) and future agreements. Functions: new, details/edit, copy, delete. Recommended practice: change only copies (except typo fixes) so the history of terms is kept.
- What can be expressed:
- Percentage discounts on RAEP (the usual basis for Rx, since discounts on Rx may not be granted on the full list purchase price) or on the manufacturer price.
- Purchase at manufacturer price plus a fixed surcharge (direct orders at manufacturer price + 70 ct, the minimum a manufacturer may charge in direct business).
- Rx high-price threshold, preset to 1238.53 EUR on list purchase price, editable, alternatively on manufacturer price or RAEP.
- Discount exclusions and cash-discount exclusions for chosen articles, assortment/product groups and providers.
- Restricting a direct supplier's terms to the articles that supplier itself offers.
- Monthly discount tiers (turnover, pack count, average pack price, combinations) and their exclusions (e.g. whether high-price articles count).
- Use in ordering:
- Manual ordering: in the order query "offers", the option "optimal supplier" compares supplier A's special terms with supplier B's standard terms.
- Automatic ordering: follows the basket determination model's option "optimal/cheapest supplier" for back-orders and stock articles.
- Preconditions for conditions to be applied: (1) an agreement exists and on its General page at least one order type is selected under "order types optimal supplier"; the effective price is computed only for those order types and used only when ordering in one of them. (2) For special terms on articles of an offer list, the list must be linked to the supplier in the "manage offer lists" module, and its terms set on the supplier's offer-lists page.
- Agreement vs offer lists: if an agreement exists, offer lists are always considered too; the offer-lists page decides whether agreement and list exclude each other (and which wins), add up, or the cheaper effective price wins. Without an agreement, offer lists count only when the list's "optimisation" flag is ticked.
- The effective-price calculation per order line can be inspected in the goods-logistics archive.
- A schematic page exists that only says agreement and order-type settings drive the effective price; its diagram is an image (not captured).
- Idea underneath (DE parts): legally restricted discount bases on prescription drugs and a statutory minimum surcharge for direct manufacturer business; in another market, make the discount basis per dispensing class configurable.
4.34 Agreement — General page (Allgemein) [GENERIC]
- Audit fields filled automatically; valid-from date (lets you prepare future agreements); remark.
- Order types for optimal supplier. When several order types of one supplier give the same effective price, "Normal-Auftrag" is shown and the others are ignored; if the normal order type is not assigned, an arbitrary assigned one is used.
- Provider restriction: table of providers (name, number) to which the agreement applies.
- Invoice mode: collective invoice = conditions are applied when computing the effective price at goods booking (all rebates, including negotiated offers, arrive later as credit on the invoice); single invoice = conditions are not applied at booking because the invoice already carries the discounted price.
- Rx high-price threshold: basis (list purchase price or manufacturer price) and amount.
- Minimum order value per order: basis (list purchase price / manufacturer price / booked purchase price) and amount. Minimum pack count per order: dispensing class it counts for and number.
- Both are checked when a basket is ordered. If not reached, a notice appears on manual "set ready to send" and on active sending; the user may order anyway (conditions are still applied at booking) or add articles. On automatic ready-to-send, a message goes to the info centre.
- Agreed average Rx pack price per month: amount and basis (list purchase price or manufacturer price); a conversion table (trade margin in %) is provided.
- Calculation: all Rx packs booked in the current month plus those currently in orders or baskets; minus credits booked this month; high-price articles excluded; baskets without a call-off time that are not yet ready to send excluded.
- From the 15th of the month, the supplier's baskets in the basket overview are flagged when the computed average exceeds the agreed one (two flags: exceeded; exceeded and an order query is pending). The function "average pack price" shows the projected (approximate) value.
- Monthly net turnover target with this supplier; what counts toward current turnover is set in the turnover-target settings (4.39).
4.35 Agreement — Article discounts (Artikelrabatte) [GENERIC]
- Ordered list of rules; a new rule starts with standard terms; add, remove, copy (copy lands directly below), move up/down. Position = processing priority.
- Overview columns: priority; applies to Rx, FW (open shelf), SW (behind the counter); order types; assortment groups / exclusions.
- Scope tab: dispensing classes (Rx / SW / FW); order types (picker); assortment groups (picker); a "but not for" / "but only for" table of ABDA product-group keys, individual articles (via article search, saved article lists or imported lists) and providers (all their articles). "Delete article list" removes all excluded articles.
- Values tab: rows with value and reference type: % of list purchase price, % of booked purchase price, % of RAEP, % of manufacturer price, EUR per pack relative to booked purchase price, EUR per line, "EUR + manufacturer price = purchase price"; price band from/to (with selectable basis "price limits relative to"; an empty band has no effect); quantity band from/to (pack count).
- Price band dialog: "from"/"to" can be "high-price threshold" (uses the current Rx threshold, e.g. 1238.53 EUR) or an explicit amount.
4.36 Agreement — Monthly discounts (Monatsrabatte) [GENERIC]
- Discounts on the expected monthly purchasing volume. Same rule list as article discounts.
- Scope: Rx, Rx high-price (above the threshold on the General page), SW, FW; order types; assortment groups; include/exclude table of product groups, articles, providers; own article lists.
- Values: calculation basis ("discounts in", e.g. % of list purchase price, % of RAEP) and a tier matrix. Criteria: turnover, pack count, average pack price; up to two at once (one on columns, one on rows; they must differ).
- Rule: the user selects the cell matching the values expected for the current month. That discount is then applied to all in-scope purchases, whether or not the thresholds are actually reached at month end.
- Examples: expected turnover ≥ 1000 EUR → 2% of list purchase price. Average pack price 22.50–24.99 EUR and turnover 20,000–29,999 EUR → 0.70% of RAEP.
4.37 Agreement — Cash discount (Skonto) [GENERIC]
- Rules for the early-payment discount, applied after all other discounts (reduction of the purchase value after discounts).
- Rule fields: % value; dispensing classes (Rx preselected on new rules; Rx high-price, SW, FW); order types; assortment groups; include/exclude table for product groups, articles, providers. Rule list with priority, copy, delete, new.
- For offer-list articles, cash discount is applied only if the offer-list page has "cash discount per agreement is granted" ticked.
4.38 Agreement — Fees (Gebühren) [GENERIC]
- Agreed supplier charges, used at goods-receipt booking, separately for general orders and for offer lists: postage and packaging; delivery; cool box; cold-chain articles; narcotics (per document or per order); returns (per document or per order); disposition order; special delivery / extra tour; orders below the minimum order value; orders below the minimum pack count.
4.39 Agreement — Turnover-target settings (Einstellungen / Umsatzziel) [GENERIC]
- Defines what counts as "current turnover" against the monthly target: dispensing classes (Rx, Rx high-price, SW, FW); order types; "returns up to" = up to how many days before month end returns still count in the current month; exclusions: single articles, and offer lists linked to the supplier.
4.40 Order-type and assortment-group pickers [GENERIC]
- Multi-select of goods-logistics order types, used for optimal supplier, article discounts, monthly discounts, cash discount and the turnover calculation.
- Multi-select of assortment groups for a rule.
4.41 Article lists and import for conditions [GENERIC]
- Configure article lists: reusable lists built from a saved report query (adopted and named) or from a manual article selection. Usable in all discount tiers of the supplier. Tick a list to use it in an agreement rule (shown distinctly in the article table); untick to remove; "delete selection" removes the list entirely.
- Import articles: on article discounts, monthly discounts and cash discount, import low-margin lists (Niederspannen-/Minderspannenlisten) supplied by a wholesaler or cooperative as the rule's exclusion list.
- The import replaces the existing exclusion list completely, without asking, and cannot be undone.
- Formats: CSV or TXT. Either one article code per line, or semicolon-separated columns with a header row within the first three lines that contains the keyword "PZN"; at most the first three lines are headers.
- Imported articles appear with name and code under "and not for".
4.42 Supplier offer lists (Angebotslisten) [GENERIC]
- Purpose: decide how a wholesaler's special-offer lists combine with the condition agreement.
- Lists are linked/unlinked in the separate "manage offer lists" module (unlink when the offer ends).
- Supplier-wide rule for offer articles ordered below the offer quantity: either list purchase price minus condition discount, or list purchase price without condition discount.
- Per linked list: name; preferred list (only one; if an article is on several lists, the preferred list sets the price even if another is cheaper); optimisation flag (list counts in supplier optimisation even without an agreement; editable only when no agreement exists; otherwise read-only, reflecting whether at least one agreement has an order type for optimal supplier); contract-bound flag; negotiated-offers flag (list contains offers without a price).
- Per list and per class (Rx, Rx high-price, SW, FW), the rule for its articles:
- Offer discount (default): the list's offer discount is used; the booked purchase price, which already contains it, is the basis of the effective price.
- Condition discount instead of offer discount: list purchase price is the basis; choose condition type.
- Better discount: whichever is better for the pharmacy.
- Condition discount on top of offer discount: booked purchase price (with offer discount) is the basis; choose condition type.
- Condition type: "per agreement" (with "condition discount" this automatically ticks "cash discount per agreement is granted") or "special condition" (deviates from the agreement; basis list purchase price) with value and type: % of list purchase price (default), % of booked price, % of RAEP (Rx only), % of manufacturer price, EUR + manufacturer price = purchase price.
- "Cash discount per agreement is granted" checkbox.
- Negotiated offers: articles carried in the offer list at price 0 (minimum quantity 1) because the real terms are unknown. Enter an approximate average discount on list purchase price per class (Rx/Rx high-price, SW, FW); values up to 3 integer and 2 decimal digits. These are after-the-fact rebates: the basket's offer table shows a "negotiated offer" marker instead of a reduced price, the order line stays at list price, and only at goods booking is the discount factored into the effective price (the offer purchase price is taken as effective price).
4.43 Supplier settings (Einstellungen (Lieferanten)) [GENERIC]
- Some options appear only for certain supplier kinds (MSV3 2.0, partner/branch pharmacies, direct suppliers).
- Auto set orders ready to send: baskets for this supplier are released automatically per the goods-logistics parameter "Warenkorb (vor Abruf)". For group members it is "transmit orders automatically": orders go to the partner pharmacy at the stored order time, are set to "ordered", and the stock transfer is triggered.
- Ignore supplier in basket determination, except when: it is named as a specific supplier in the basket determination model; it is the fixed supplier in the article's details; it was chosen at POS (potential supplier); it is flagged main supplier and explicitly named as main supplier in the model; the article can only be ordered directly from it. Reasons: avoid a random fallback supplier when preferred ones report non-availability; avoid unintended orders with a provider whose baskets are created automatically with "next call-off"; protect a once-a-month special basket.
- Hide in price tables (partner/branch pharmacies only): hides their rows in all price tables (order queries, order offers, article details purchasing/offers); if set for all branches, the "available" column and the fixed-minimum-stock symbol are hidden as well.
- Return slip sorting: grouped by document number or alphabetical.
- Delivery-advice capture (MSV3 2.0 suppliers): "counter-scan delivery advice" (scan packs against the advice to confirm the actual quantity; default for MSV3 2.0) or "read in delivery advice" (take pack counts from the advice).
- Direct suppliers:
- "Allow interim order at wholesaler": an article is also ordered at short notice from a wholesaler even though enough sits in the direct supplier's basket. It is passed with the daily-need quantity to the basket of the wholesaler that delivers next (or, without delivery times, the one with the next order time). Quantities in the direct supplier's basket are ignored, quantities already ordered are counted, and basket-determination settings are ignored.
- "Deactivate disposition-time shortening": no reorder while the ordered quantity exceeds variable or fixed minimum stock; if insufficient, regular optimisation; back-orders always ordered; for POR articles (abbreviation not explained) ticking disables shortening and always uses regular optimisation.
- Joint purchasing (partner/branch pharmacies): "delivery to each pharmacy, invoice to own pharmacy" = decentralised delivery: each pharmacy receives its own order directly and does goods receipt and value booking; the ordering pharmacy receives the invoice.
- Sub-orders list: active sub-orders by priority (reorderable); the vendor sub-order "Betäubungsmittel" (narcotics) is always priority 1 and cannot be moved.
4.44 Sub-orders (Unteraufträge anlegen und verwalten) [GENERIC]
- Purpose: split a supplier order into separately identified parts (e.g. narcotics, robot-suitable articles, home supply).
- Vendor (standard) sub-orders are marked; they cannot be edited or deleted, only activated/deactivated. Mind the maximum number of free order identifiers the supplier honours (see contract data).
- New sub-order: unique order identifier (max 20 characters, no spaces or special characters); optional description; selection criteria: article selection via report query (e.g. articles suitable for the picking robot); customer selection via report query (the selected customers' articles, e.g. home supply); dispensing class (only prescription-only or only non-prescription); back-orders (all kinds active by default, individually deselectable: pickups, courier, post).
- New sub-orders are active at once; priority is set on the settings page. Order type per sub-order: normal, special or batch order. Own sub-orders can be edited and deleted.
4.45 Blank condition-agreement form [GENERIC]
- From the supplier's conditions page: a blank form/checklist for negotiating with wholesalers and spotting missing or vague terms; preview, then print.
4.46 Send parameters and online enquiry (Sendeparameter) [DE-SPECIFIC protocol]
- Transmission protocol: MSV3. Supplier IDF. Default order type (shown as a code). Default order identifier used when creating baskets, for separate delivery of all basket articles in a "remaining articles" sub-order.
- MSV3 access: service provider (searchable list of all providers; protocol version V1 or V2; several supplier contacts, e.g. branches with different credentials, can share one provider); branch ID at the provider; user ID; password; connection test. Saving validates the credentials automatically by a connection test; on failure a notice appears. After saving MSV3 credentials for a wholesaler, the contract data enquiry opens.
- Online availability enquiry: activate; at most 10 suppliers get their own result column; direct suppliers can share one pooled "Anbieter" column, so more than 10 can be active; "provider-specific column" (own vs pooled); user ID for online access; "relevant direct supplier (daily business)" (direct supplier with wholesaler character: no or low minimum order and prompt delivery; also makes it relevant for choosing the favoured article in prescription scan and for listing proposals in assortment control; only shown for direct suppliers).
- Setting a supplier with an MSV3 provider link to inactive deletes the link automatically.
- Online enquiry sorting (Bevorzugte OVA-Lieferanten): rank up to 10 wholesalers plus all configured providers (initially grouped under "<Anbieter>" at the end). The rank is the column order in the online enquiry/order window.
- Idea underneath: a standard wholesaler web-service for orders, availability and contract data, with per-supplier credentials and a ranked availability comparison.
4.47 Delivery parameters and order times (Lieferparameter) [GENERIC]
- Dispatching warehouse name; invoicing ("referring") wholesaler for direct suppliers, prefilled at goods-receipt booking.
- Usual delivery duration: for direct suppliers it pre-fills the delivery-date dialog when ordering; for wholesalers it is used to compute a basket's expected delivery time when a delivery time is set.
- Excluded delivery weekdays (default: Sunday), considered when computing delivery time.
- Order times table, per row:
- order time (start of the order window = automatic send time for everything collected since the last cut-off; also the "main order time" reported by the wholesaler; supplier-reported rows are marked differently from own rows);
- cut-off (contractual end of the window / of follow-up calls; after it, inclusion in the next delivery is not guaranteed);
- delivery time (promised, entered by the pharmacy, HH:MM);
- weekdays;
- late-order flag;
- "auto-create basket" (default on). Each order time with this flag creates a basket for the supplier in goods logistics.
- Rules:
- When the supplier reports a changed order time, the delivery time is carried over if the dropped time had one and the two times differ by at most ±30 minutes.
- Manual rows give extra baskets. Their cut-off stays empty; the cut-off of the next contract-reported time applies. Without a delivery time, baskets of that order time cannot be used to determine a "next delivery".
- Contract-reported rows cannot be changed, deleted or deactivated; manual rows can. Changes affect future baskets only. To remove a manual time: delete the row, clear the time or untick all weekdays; no new baskets are created afterwards.
- Late orders: baskets created for a flagged time are late orders and can be treated separately in the basket determination model (e.g. never order narcotics or cold-chain articles in a late order).
- Optional audible signal at order time; reminder before send time via parameter "Minuteneinstellung für bevorstehende Sendezeit".
- MSV3 contract data is fetched daily from wholesalers, with every change reported in the info centre; for direct suppliers it is fetched manually.
4.48 MSV3 contract data enquiry and contract data page (Vertragsdatenauskunft, Vertragsdaten) [DE-SPECIFIC protocol]
- Purpose: get the agreed main order times, cut-offs, substitution agreement and contract validity directly from the supplier.
- Wholesalers: checked and reconciled automatically every day and after each server start; changes applied to order times automatically and order times that no longer apply deleted. Direct suppliers: manual adoption. Every change is reported in the info centre and in Notes (internal messaging).
- Enquiry dialog: reported contractual order times plus own existing ones (own times that differ only slightly from contractual ones are not listed); reported main order times and cut-offs (only cut-offs if no main order times are reported; main order times are optional); order times currently stored on the supplier; substitution-agreement flag (supplier may replace unavailable articles with re-/parallel imports); number of additionally agreed sub-orders (order identifiers).
- Window semantics: from order time to cut-off, everything collected since the last cut-off is sent; orders sent in the window are delivered with the next tour if available.
- Unticking "auto-create basket" also deletes automatically created, empty baskets without a sub-order whose expected order time has passed.
- Providers/direct suppliers normally have no order times, so the pharmacy sends manually (e.g. to respect the minimum order value). When a provider is switched to MSV3 ordering, the dialog does not open automatically (to avoid adopting order times by accident). If viewing it, leave with cancel; if adopted by mistake, untick auto-create basket so no automatic orders bypass the minimum-order check.
- Contract data page: stored-since date; normal order supported (always, by default); special order supported and pharmacy authorised; batch order supported/authorised; take-back offer supported/authorised; substitution agreement; response type (unspecific = only "generally deliverable", no quantity, possibly no time; specific = also deliverable quantity and time). Free order identifiers (sub-orders) the supplier honours per order type (normal, special, batch). Order times: regular (order time, cut-off, weekdays; delivery times are not reported) and special days (movable or regional public holidays with deviating windows, tied to concrete dates; fetched automatically, manual fetch possible).
4.49 Supplier payments (Zahlungsverkehr (Lieferanten)) [GENERIC; DATEV link DE-SPECIFIC]
- "Transfer from account": pharmacy account used to pay this supplier. "Account for direct debit": pharmacy account the supplier collects from, if a debit authorisation exists.
- Creditor account number: under the DATEV chart of accounts it should lie in 70000–99999, up to 9 digits; digit count configurable in finance settings.
- "DATEV export of single invoices": untick when monthly collective invoices are booked instead, so the individual goods-receipt bookings are not exported (the collective invoice carries all turnover-dependent rebates).
- Bank accounts: add, edit, delete with confirmation.
- Idea underneath: map each supplier to an accounts-payable ledger account and choose whether to export per delivery or per monthly statement.
F. Employees, user accounts and permissions
4.50 Employee master data and specific data (Mitarbeiter-Kontakte, Spezifische Daten) [GENERIC]
- Employees are own staff; employees of a partner pharmacy can also be stored. Data: name (mandatory), address, birth date, phones, plus HR data.
- Common master-data rules apply (roles, status, address assistance, communication, encrypted e-mail, exchange). Status inactive/deceased deactivates the user account (4.6).
- External employee ID: generated by the system; identifies the employee across the group and for business evaluations.
- Specific data:
- Personnel number (self-assigned, max 10 characters), hiring date, gross salary.
- Job title from a list. Rule: if the title "Bote" (courier) is given to at least one employee, only couriers are offered when a delivery tour is created; if nobody has it, all employees are offered.
- "Pharmaceutical carer" flag; free-text qualifications.
- Commission: points (for a points scheme) and amount. Recorded only; no calculation is described.
- ELO user name: links the employee account to that folder in the ELO inbox.
- An employee used only as a courier can be kept without a user account and still counts as an employee (e.g. for the staff discount model).
4.51 Employee payments (Zahlungsverkehr (Mitarbeiter)) [GENERIC]
- "Transfer from account": pharmacy account used for payments to the employee, e.g. salary.
- Bank accounts table (add, edit, delete with confirmation); at least one account can be flagged as salary account, shown in a column.
4.52 Message types per employee (Nachrichtentypen) [GENERIC]
- Choose which message categories each employee sees in the info centre (menu bar) and in Notes (category "messages").
- Permission: role Leiter or Konfigurationsverantwortlicher, or right "Nachrichtentypen konfigurieren".
- Categories, each switchable:
- System: e.g. new data/change service installed, wholesaler offers updated, ordering error, appointment note passed to a basket, new joining information in OVP (not explained), Payback server communication failure.
- Pharmatechnik (vendor): sent by vendor staff or via IXOS.eCall: new software version, legal changes, tips, events, general information; subfolders IXOS Aktuell, Tipps & Tricks, Software, Veranstaltungen, Anforderungen, Online-Support, Allgemeines.
- Branches: events in branch pharmacies (e.g. a stock transfer was triggered); deleted automatically after 2 days.
4.53 User account and operator register (Benutzerkonto) [GENERIC]
- An employee may or may not have a user account. "Account active" = access to the system in principle; requires the employee contact to be active. Own account is also reachable via system maintenance > my profile.
- Operator register: a positioned, named, coloured operator slot shown at POS workstations for quick user switching. Assigning a free position and a name lets the user work at POS. Capacity: up to 500 operators on up to 50 levels.
- Users with an active account but no register can work only at back-office workstations (they appear there on the lowest level without colour); they cannot use the POS (till disabled) nor do till-related actions from sales administration or prescription management.
- Deactivate account: account and settings stay but access is blocked. The user's open POS sales move automatically to the user with the next-higher register. The register stays occupied internally (hidden, not reusable) — suited for temporary absence; if the employee will not return, free the register before deactivating. Do not deactivate a user who is currently working. Users cannot deactivate their own account.
- Remove register (position "none"): removes the register and deactivates the account; open sales are handed to another user; logged-in sessions are locked; the account is not deleted and must be reactivated manually to be used at back-office workstations.
- Password: if password protection is configured on at least one workstation, a password is generated on activation; it can be overwritten via "assign password" without knowing the old one.
- Who may edit accounts (independent of the permission concept): role Leiter, or one of the rights
- "Benutzerkonto bearbeiten" (activate/deactivate accounts, assign registers, set up authentication, merge employee duplicates, delete employees);
- "Benutzerkonto bearbeiten und nur Rollen zuweisen" (the same plus assigning any role);
- "Benutzerkonto bearbeiten und Rechte zuweisen" (the same plus single rights, and therefore all roles).
- With password protection the editor must authenticate ("log in") first; without the rights the page is locked. The vendor makes the initial assignment of these rights.
4.54 Permissions on the account (roles and rights) [GENERIC]
- Relevant only when the permission concept in workstation protection is fully or partly active; otherwise every user has unrestricted access.
- Roles table: every role with state assigned / active through another assigned role (not changeable) / not assigned. Kinds are distinguished: predefined organisational (Leiter, Apotheker, PTA, PKA), predefined activity-related, self-defined. Number of contained rights shown.
- Rights table: rights in alphabetically sorted groups (expand/collapse); state per right/group: active / partly / not; status column: right enabled (licensed) / not enabled / group with at least one enabled. Header shows active of total (e.g. 12/74) and number of manually assigned rights (not via a role). Select-all checkbox, search field, "only active" filter.
- Info area: definition and contents of the selected role, or definition of the selected right and the roles containing it; readable by anyone.
- Assigning a role ticks all its rights; further single rights can be added. Permissions apply to the user on all workstations for protected modules and functions.
4.55 Role management (Benutzerrollen verwalten, ändern, löschen) [GENERIC]
- Purpose: tailor permission bundles to the pharmacy's job split and document them.
- Possible policies: (1) single rights and all roles may be assigned; (2) only roles (predefined and own) may be assigned, never single rights; (3) only self-created roles are used.
- Access: "role management" from the workstation-protection module (system settings) or from an employee's user-account page.
- Rights:
- "Selbstdefinierte Rollen verwalten": create, edit and delete own roles.
- For each self-defined role, the system generates a right "Selbstdefinierte Rolle <Name> zuweisen" and grants it to the creator, who can then assign that role to others. It requires at least "Mitarbeiter: Benutzerkonto bearbeiten". New self-defined roles are not assigned to Leiter, who can anyway assign every right and role through "Benutzerkonto bearbeiten und Rechte zuweisen".
- Group exchange: roles, rights and their changes are exchanged between pharmacies with contact exchange enabled; which employee holds which rights is not exchanged.
- Role list: name, description, number of rights, number of employees, number of workstations holding it; tooltips list those employees/workstations and mark inactive/deactivated ones separately. Predefined roles are listed for information only.
- Detail area for a self-defined role: name, description, and the same roles/rights tables as on the account page (a role can contain other roles as well as rights).
- Create (new roles are shown in italics):
- From an employee's account: set the desired roles/rights on the employee, then "save as role" → a new row "<create new role>" appears; enter name and description; save. Example: PKA plus the right to see and edit narcotics documentation.
- From workstation protection: role management → new → tick rights and/or roles to include → name → save. The role is not yet assigned to anybody or any workstation; that is done on employee accounts or in workstation protection.
- Own-roles-only policy: Leiter or a holder of "manage self-defined roles" creates the roles and gives, e.g., the responsible pharmacist "edit user account" plus "assign self-defined role <name>". Example: a pharmacy without PTAs creates a role "PTA+PKA+BtM-Doku".
- Change a self-defined role: select it, tick/untick rights (header shows how many were added), save → a confirmation window lists the employees and workstations affected and the resulting changes → OK. A right removed from the role stays with an employee who also has it through another assigned role.
- Delete a self-defined role: select → delete → confirmation lists employees/workstations currently holding it → OK. Their rights stay assigned to them (as individual rights) and can be edited afterwards.
- Roles can be assigned to workstations (in workstation protection) as well as to employees.
4.56 Password, operator picture and fingerprints [GENERIC]
- Password (Mitarbeiter-Kennwort): needed when the protection concept is used. Dialog: operator-register name, new password, confirmation. Allowed for the employee themself, Leiter, or a holder of "Benutzerkonto bearbeiten und Rechte zuweisen"; authentication always required; possible at any workstation. Recommendation: not a shared password, at least 10 characters, with digits, special characters, upper and lower case. The system warns when these criteria are not met; parameter "Unsichere Kennwörter akzeptieren" suppresses the warnings.
- Operator picture (Bedienerbild): choose from a preinstalled set or load a photo (from disk/USB); stored with the profile on the server. Shown on the desktop, at POS workstations if configured, and in the team app (IXOS.team). With at least restricted password protection on any workstation, only Leiter and holders of "Benutzerkonto bearbeiten und Rechte zuweisen" may change it, after authenticating.
- Fingerprints (Fingerabdrücke verwalten): with a scanner connected, a fingerprint authenticates the user for login or for protected functions; without the permission concept it serves as a quick operator switch. Enrolment: choose a finger and place it five times in a row; the system checks that the print is not already stored for anyone; max 10 prints per person (one per finger). An indicator shows whether prints are stored; delete single or all. Allowed for the employee themself, Leiter, or a holder of "Benutzerkonto bearbeiten und Rechte zuweisen" (authentication required where password protection exists).
G. Function keys (Funktionstasten in der Kontaktverwaltung)
- Meaningful functions available in the contact module: search, new, delete, edit duplicates (suppliers/providers), open items (customers), info texts, change contact role, contact details, print / address label, visibility of contacts (for tenant contacts in "Filialen & Partner"), ranking (preferred branches), advanced search, print settings, consent settings, suggest families (Familien vorschlagen), personal data report, table settings.
5. Workflows
5.1 Create a non-customer contact
- Select the role in the navigation bar (or start "new" from an existing contact of that role).
- Confirm or change the role in the role-selection dialog (exactly one).
- Enter at least the name; use postcode/city assistance; enter communication data and mark the standard number/e-mail.
- In a group: decide on contact exchange before the first save (for legal entities this is the only chance to exclude it).
- Save; fill role-specific pages (specific data, classifications, payments, etc.); add further roles via the role checkboxes if needed.
5.2 Retire a person contact under data-protection rules
- Delete → choose inactive / deceased (data kept, still needs consent) or lock.
- Lock is refused if there are open pickups or a substitution therapy; settle those first.
- On lock: contact hidden, transactions anonymised, change history entry written.
- Either an authorised user (right for locked contacts) unlocks or deletes it finally via advanced search ("show locked contacts"), converting any address references held by other contacts into local addresses; or the configured deletion period deletes it automatically, unless a deletion reservation applies.
5.3 Respond to a data-subject access request
- User with the access-report right selects the customer (or enters the person manually).
- Confirm whether consents are managed in the system.
- Tick the data categories; deselect family members on joint receipts if appropriate.
- Preview and output (print, PDF, DMS, Excel). In a group, repeat in each branch.
- The report is logged in the access history.
5.4 Set up a care home with residents and invoicing
- Create the home contact (customer role and invoicing permission are added automatically).
- Enter district court, register number and VAT ID (needed for receipts); flag one or two bank accounts for receipts.
- On the structure page add houses, wards and rooms (child vs sibling by reselecting the parent); set name-append rules.
- Assign residents (new or existing customers); they inherit the unit's invoicing settings and receive invoicing permission.
- On the institution set invoicing mode (total vs per customer, receipts, collective slip, itemised statement, own consumption, batch/structure/sort), payment info (method, cycle, terms, alternative account, flat fee), print options and forms — or pick an invoicing model.
- Where a unit is billed separately, tick "separate invoice" (creates the unit's own customer contact) and, if needed, "own settings".
- Optional: blistering settings, contact persons, delivery/packing preferences, portal access, prescription-request recipient.
- Invoice runs pick up the institution according to cycle; printing follows the batch/structure sequence (4.28).
5.5 Maintain supplier purchase conditions and use them for ordering
- User with role Leiter or conditions officer opens the supplier's conditions page; copies the current agreement (to keep history) or creates a new one with a valid-from date.
- General page: tick the order types for optimal supplier; choose collective vs single invoice; set high-price threshold, minimum order value/pack count, average Rx pack price, turnover target; optional provider restriction.
- Add article-discount rules in priority order (scope, values, price/quantity bands; exclusions via product groups, articles, saved or imported lists).
- Add monthly-discount rules and pick the expected tier cell; add cash-discount rules; enter fees; set turnover-target counting rules.
- On the offer-lists page set how each linked list combines with the agreement, the preferred list, and averages for negotiated offers.
- When ordering, the system computes the effective price per supplier for the selected order types and proposes the optimal supplier (manually in the order query, automatically via the basket determination model). Minimum order value / pack count are checked when the basket is sent.
- At goods receipt, conditions are applied to the booked price (collective-invoice mode) and fees are applied; the calculation is visible in the archive.
5.6 Connect a wholesaler via MSV3
- Send parameters: protocol MSV3, IDF, default order type and identifier; choose the MSV3 service provider and version, enter branch ID, user and password; save (automatic connection test).
- The contract data enquiry opens: adopt the contractual order times and cut-offs.
- Delivery parameters: add delivery times (HH:MM) and any manual order times; flag late orders; keep "auto-create basket" where baskets should be created.
- Optionally activate online enquiry and rank the supplier in the online-enquiry sorting.
- From then on, contract data is fetched daily; changes are applied automatically and reported in the info centre and Notes.
5.7 Give a new employee system access
- Create the employee contact (status active); fill specific data (personnel number, job title — "Bote" for couriers).
- On the user-account page tick "account active"; assign a free operator-register position and name (needed for POS).
- Assign roles (and, if policy allows, single rights); a password is generated if password protection is in use; the employee or an authorised user sets a new password.
- Optional: picture, fingerprints, message-type visibility, bank account flagged as salary account.
- On departure: free the register, then deactivate the account (or set the contact inactive, which deactivates the account).
5.8 Create a self-defined permission role
- Either set up the rights on an employee and "save as role", or open role management and create a new role by ticking roles and rights.
- Name and describe it; save.
- Assign it to employees (account page) and/or workstations (workstation protection); grant "assign self-defined role <name>" to whoever should hand it out.
- Later changes show the affected employees/workstations before saving; deletion leaves the rights with former holders as individual rights.
6. Business rules and calculations
- Mandatory fields: name for every contact. IK number validation warns but does not block.
- Automatic capitalisation of title, first name (national contacts only), name, street, city, country.
- Role removal: not the role of the open master-data window; not while relevant relations exist (open pickups).
- Lock preconditions: no open pickups/unfinished transactions and no substitution therapy. Inactive is refused if a group customer has app access in more than one branch.
- Non-deletable: employee holding the active operator register; customers with branch or home role; data-service-maintained suppliers.
- Retention: lock and deletion periods by parameter; deletion period counted from last use; deletion reservation for open transactions or substitution therapy; in a group the lock period restarts everywhere when sales data is exchanged, and the shortest deletion period configured anywhere applies.
- Consent validity: a consent signed under a version that is not marked "remains valid" is invalid; the customer must sign the current version.
- Duplicate merge: max 12 sources; only self-created providers/suppliers; only goods-logistics transactions move.
- Address suggestions: own data first by frequency; general database added only if fewer than 10 own hits; max 50.
- Portal passwords always displayed as ten asterisks.
- Structure: unit deletion only without residents beneath; unit inherits parent contact data except addressee; addressee = composed name per append flags.
- Invoicing inheritance: institution → unit → resident; "own settings" overrides; invoicing model overrides sub-tabs; deleting a model reverts residents to the parent's settings.
- Receipt prerequisites: 1–2 bank accounts flagged; district court, register number, VAT ID entered.
- Bank account resolution for invoicing customers: direct debit to company account → alternative pharmacy account → standard company account.
- Flat fee line: needs a label; empty amount prints 0.00; not analysable in reports.
- Branch settlement: internal goods exchange invoiced net without VAT, own number range, forces "invoice with net prices".
- Effective purchase price = purchase price after applying all applicable condition rules (article-discount rules in priority order, the monthly discount of the selected tier, the offer-list rule; cash discount is always applied last, on the value after discounts). The help does not state how article and monthly discounts combine. Computed only for order types ticked for optimal supplier; applied at booking only in collective-invoice mode.
- Order-type tie-break: same effective price → prefer normal order; else any assigned type.
- High-price threshold: preset 1238.53 EUR on list purchase price.
- Direct-order minimum: manufacturer price + 0.70 EUR.
- Average Rx pack price: (Rx packs booked this month + Rx packs in orders/baskets − credits this month), excluding high-price articles and non-ready baskets without call-off time; flags from the 15th of the month when above the agreed value.
- Monthly discount: the discount of the chosen expected tier applies to all in-scope purchases regardless of the actual month-end result.
- Cash discount applies after all discounts; for offer articles only if granted on the offer-list page.
- Offer below offer quantity: list price minus condition discount, or list price without it (per supplier).
- Preferred offer list wins for an article on several lists even if not cheapest.
- Negotiated offers: average discount (max 3 integer + 2 decimal digits) applied only at goods booking.
- Low-margin list import replaces the exclusion list without prompt and irreversibly; header within first 3 lines must contain "PZN".
- Minimum order value / pack count: checked on sending; warning only; on automatic send → info-centre message.
- Order-time carry-over: delivery time kept if a reported order time moves by ≤ ±30 minutes.
- Manual order times have no cut-off (next contractual cut-off applies); without delivery time they don't count for "next delivery".
- Online enquiry: max 10 own columns; direct suppliers can pool into one column.
- Sub-order identifier: ≤ 20 characters, no spaces/special characters; narcotics sub-order fixed at priority 1.
- Creditor account (DATEV): 70000–99999, up to 9 digits.
- Operator registers: up to 500 operators on up to 50 levels; deactivation moves open sales to the next-higher register.
- Fingerprints: 5 placements to enrol; max 10 per person; duplicate check across the system.
- Password recommendation: ≥ 10 characters with digits, special characters, upper and lower case; warning unless insecure passwords are accepted.
- Role changes: removing a right from a role does not remove it from a user who holds it via another role; deleting a role leaves its rights with former holders.
- Courier selection: if any employee has job title "Bote", only couriers are offered for tours.
- Branch messages auto-deleted after 2 days.
7. Configuration and settings
| Parameter | Scope | Effect | Default |
|---|---|---|---|
| Sperrfristen für personenbezogene Daten | system | Period after which person contacts are locked automatically | not stated |
| Sperrfristen für Laufkunden | system | Lock period for walk-in customers | not stated |
| Löschfristen für gesperrte Laufkunden | system | Deletion period for locked walk-in customers | not stated |
| Löschfristen für Personenkunden | system | Deletion period for person customers (from last use) | not stated |
| Nutzung der Einwilligungserklärung in IXOS | system | Consent managed in the system; drives POS warning and access-report wording | not stated |
| Info bei Med.-Abbruch Grund 'station. Aufenthalt' | system | Auto-create a message text when medication is stopped for an inpatient stay | not stated |
| Autom. Arztzuordnung bei Rezeptscan | system | Match scanned prescriptions to manually created doctors via BSNR | not stated |
| Visibility of exchanged contacts (group-wide / per pharmacy) | group / pharmacy | Which other pharmacies' contacts appear in search and prescription scan; birth-date requirement for extended search | not stated |
| Contact exchange flag | contact | Replicate contact in group | not stated (legal entities: can only be switched off before first save, otherwise always exchanged) |
| Settlement from internal goods exchange | branch | Net invoices without VAT and own number range for internal exchange | not stated |
| Processing workstation (cross-pharmacy stock withdrawal) | branch | Workstation/picking-system chute that handles transfer orders | none |
| Preferred branches rank | pharmacy | Column order of branch stock in article search | not stated |
| Standardsortierung bei Rechnungsstellung | system | Default invoice sort (recipient / customer / document number) | not stated |
| Standardsortierung der Rechnungskopien | system | Sort/position of invoice copies | not stated |
| Automatischer Quittungsdruck für Heime | system | Automatic receipt print for homes | not stated |
| Institution invoicing settings | institution / unit / resident | See 4.27 | home: total invoice, no receipt/statement/own-consumption; care service: per customer, no batch; hospital: total invoice |
| Auto-generate invoices as PDF | institution / customer | Store PDFs in <documents>/<year>/<month>/ | not stated |
| Warenkorb (vor Abruf) | goods logistics | Governs automatic ready-to-send of baskets | not stated |
| Auto set orders ready to send / transmit automatically | supplier | Release baskets automatically | not stated |
| Ignore supplier in basket determination | supplier | Exclude supplier except listed cases | off (implied) |
| Hide in price tables | partner supplier | Hide partner price rows | off (implied) |
| Return slip sort | supplier | Grouped by document no. / alphabetical | not stated |
| Delivery-advice capture | MSV3 2.0 supplier | Counter-scan / read in | counter-scan |
| Interim order at wholesaler; deactivate disposition-time shortening | direct supplier | See 4.43 | not stated |
| Decentralised delivery (joint purchasing) | partner supplier | Each pharmacy receives goods; invoice to orderer | not stated |
| Excluded delivery weekdays | supplier | Excluded from delivery-time calculation | Sunday |
| Auto-create basket per order time | supplier order time | Create basket automatically | on |
| Minuteneinstellung für bevorstehende Sendezeit | system | Reminder minutes before send time | not stated |
| Rx high-price threshold | agreement | Separates high-price Rx | 1238.53 EUR (list purchase price) |
| Offer quantity shortfall rule | supplier | Price for offer articles ordered below offer quantity | not stated |
| Unsichere Kennwörter akzeptieren | system | Suppress weak-password warnings | not stated |
| Message types | employee | Visible message categories | not stated |
| DATEV export of single invoices | supplier | Export each goods-receipt booking | not stated |
| Creditor account digit count | finance settings | Length of creditor numbers | not stated |
| Consent print form / pharmacy list text | system | Changing them creates a new consent version | — |
8. Roles and permissions
- Permission concept is optional (module Arbeitsplatzschutz). When off, every user has unrestricted access; account editing rights apply regardless.
- Predefined organisational roles:
- Leiter (manager): contains all predefined organisational and activity-related roles.
- Apotheker (17 rights): PTA rights plus releasing manufacturing protocols and plausibility checks for compounding, deleting compounding with a released protocol, and access to the pharmacists' document folder.
- PTA (14 rights, list partial): optimise delivery tour; start hazardous-substances module; create/see/print shift receipt; create X receipt; create Z and S receipts; start Reports; document-directory access; see/edit goods-logistics archive; correction booking; handle support requests.
- PKA (11 rights, list partial): supplier-turnover evaluation; manage perpetual inventory; start Reports; document directory; goods-logistics archive; correction booking; support requests.
- Predefined activity-related roles:
- Umsatzverantwortlicher (turnover officer): configure controlling traffic light; evaluations IBV, supplier turnovers, self-declaration for emergency-service fund, prescription billing (ARZ); start Cockpit and see branch pharmacy in Cockpit; start DATEV and GDPdU export; J, M, shift and T receipts create/see/print; X create and see/print; Z and S create and see/print; start cash book; start Reports and run turnover-relevant queries; prescription management start and ARZ billing; document directory; see closing-receipt details in sales administration; goods-logistics archive; correction booking.
- Sortimentsverantwortlicher (assortment officer): edit stock, duplicates, article code of self-created/pre-captured articles, extend self-created article to group, edit status; annual inventory, stock valuation, perpetual inventory; start prices & calculation; start assortment control; document directory.
- Konfigurationsverantwortlicher (configuration officer): configure message types; DMS print settings; manage print forms; start system settings; document directory; start/edit order quantity optimisation and basket determination.
- Konditionsverantwortlicher (conditions officer): view/edit supplier condition agreements (referenced on condition pages).
- Self-defined roles: created via role management; each creates a dynamic right "assign self-defined role <name>".
- Rights named in this slice:
- Kontakte allgemein: Gesperrte Kontaktdaten bearbeiten (see/unlock/finally delete locked contacts; in Leiter).
- Kontakte allgemein: Kontaktrollen trennen (in Leiter).
- Kontakte allgemein: Auskunft über personenbezogene Daten erstellen (in Leiter).
- Einstellungen Einwilligungserklärung pflegen.
- Massenbearbeitung von Kundendaten durchführen (needed for contact visibility settings).
- Mitarbeiter: Benutzerkonto bearbeiten / … und nur Rollen zuweisen / … und Rechte zuweisen.
- Selbstdefinierte Rollen verwalten; Selbstdefinierte Rolle <Name> zuweisen.
- Nachrichtentypen konfigurieren.
- BtM-Dokumentation sehen und bearbeiten (example in role creation).
- Self-service limits: users cannot set their own status inactive/deceased or deactivate their own account; they may change their own password and fingerprints (with authentication).
- Authentication before editing accounts, pictures and fingerprints whenever password protection exists on any workstation.
9. Integrations, hardware and external services
- Price/change data service (ABDATA): supplies providers, payers, discount contracts and address reference data; read-only flags. [DE-SPECIFIC; idea: national master-data feed]
- MSV3 wholesaler web service: order transmission, online availability enquiry, delivery advice (MSV3 2.0), contract data (order times, cut-offs, special days, sub-orders, substitution agreement). [DE-SPECIFIC; idea: standard B2B ordering API]
- ELO DMS: document scanning, supplier documents link, employee inbox folder.
- Scanner (document scanning), fingerprint scanner, automated picking system (output chute for cross-pharmacy stock withdrawal).
- Connect portals: Arzt.connect, Heim.connect, Rezept.connect, Klinik.connect (paid web portals for doctors and institutions).
- "Meine Apotheke" app (customer app; registration forms and messages), IXOS.team (team app showing operator pictures), IXOS.eCall (vendor messages), Payback (server status messages).
- E-mail with PDF encryption or password-protected download links.
- DATEV (accounting export) and GDPdU export (rights only). E-invoice XML (cost centre → BuyerReference).
- RxAktuell add-on (payer discount contracts).
- Blister management module and external blister centres (delivery notes "delivery made separately").
10. Printouts, reports and exports
- Customers (from contacts; details in customer chapter): address labels (standard / invoice / delivery address — the latter two only if the address exists); care-aid forms (receipt confirmation; approval/cost-coverage application), each in versions for dispensing before and from 01.06.2025, prefilled with customer (name, address, phone, insurance number, birth date) and pharmacy (name, address, phone, IK), care-insurer fields left blank; copay list; prescription list; total-purchases list; "Meine Apotheke" registration/privacy form with access data; federal medication plan, medication plan, range list; SEPA mandate blank or prefilled without bank details and mandate reference (full print only when creating/updating the mandate); Connect access data. From medication management only the three medication-related prints are offered.
- Homes and units: address label; inspection protocol template (4.31); weekly plan; prescription requests for medications without / with doctor assignment; range list; stock list; blister labels and blister plan; Connect access data for Rezept.connect. Hospitals: address label only.
- Doctors: address label; prescription request (opens the prescription-request module); Arzt.connect access data.
- Suppliers: blank condition-agreement form.
- Other roles (walk-in customers, payers, providers, field reps, address-book entries, employees): address label.
- Output: label printer, standard printer or PDF; optional preview.
- Invoicing documents (configured per institution/customer):
- Print options: number of delivery notes (first original, rest copies); number of back-order notes (list all outstanding items of partly or undelivered positions); number of invoices (first original printed or e-mailed, rest copies); label print with delivery note (after closing the order, asks for the count; not repeated after later changes or pickup resolution); automatic delivery-note print: always (even for external-partner delivery such as a blister centre, then marked "delivery made separately") / always except purely separate deliveries (pharmacy goods printed; contract-blistered goods created with remark but not printed) / only if the delivery contains pharmacy goods; print zero-sum delivery notes on invoice; print zero-sum receipts; create zero-sum invoices; print/dispatch zero-sum invoices (if off, the invoice gets status "Intern"); automatic print/dispatch of invoices (preview offered before print by default and always before e-mail); automatic invoice PDFs in <documents>/<year>/<month>/<name and date>.pdf with invoice number and date in the file name, copies suffixed "-Kopie", independent of printing; automatic dunning print/dispatch.
- Forms (default form if unset): delivery note (options: print all outstanding back-orders; show prices and totals); invoice (position sort); dunning letter; collective delivery-note slip (sort); collective invoice slip; label (customer/home/hospital); receipt (also used for itemised statements; sort).
- Data-subject access report: print, PDF, DMS, Excel; history list.
- Reports queries: consent declarations; customers with medication management lacking consent; mass maintenance of info texts and invoicing models via result processing; report queries also define condition article lists and sub-order article/customer selections.
11. Dependencies on other modules
- Customer contacts (master data, medication management, sales data, invoicing pages, families) — customer chapter.
- POS / sales (info texts, consent warning, operator registers, customer selection) — POS chapter.
- Invoicing (Faktura): invoice runs, receipts, dunning, invoicing models, payment and dunning terms models.
- Goods logistics: baskets, basket determination model, order quantity optimisation, order queries, online enquiry, goods receipt booking, archive, offer-list management, returns.
- Prescription management and prescription scanning (doctor matching, contact visibility); prescription requests module.
- Blister management; delivery management (tours, couriers).
- Company master data (Firmenstamm): pharmacy bank accounts, DMS categories, own pharmacy record.
- Workstation protection (Arbeitsplatzschutz): permission concept, workstation roles, password protection.
- Reports module (queries, result processing); Notes / info centre (messages); system settings (configuration parameters); finance settings (creditor account length).
12. Portability notes
- Generic and directly reusable: multi-role contact model; per-role status; lock → anonymise → delete lifecycle with retention periods and deletion reservations; consent versioning; info texts surfaced at POS; data-subject access report with history; DMS scanning; classifications; address suggestions; encrypted e-mail; multi-branch contact exchange with visibility control; branch stock ranking; institution structure with residents and hierarchical invoicing inheritance; invoice batching/sorting; supplier condition engine (priority-ordered discount rules with scopes, bands and exclusions, expected-tier monthly discounts, cash discount last, fees, offer lists, negotiated offers, minimum order checks, average pack price monitoring); order times/cut-offs/late orders and automatic baskets; sub-orders; employee HR fields; user accounts with operator slots, role/right model with self-defined roles and delegated assignment rights, fingerprints.
- Germany-specific, with the idea underneath:
- ABDATA provider/payer data and "data-service maintained" flags → a national or vendor-maintained master-data feed that local users may extend but not edit.
- RAEP, Rx high-price threshold (1238.53 EUR), manufacturer price + 70 ct → legally constrained discount bases and minimum direct prices; make the basis and thresholds configurable per dispensing class.
- MSV3 protocol, IDF, contract data, special days → a standard supplier ordering/availability API with machine-readable delivery windows.
- IK number, BSNR, LANR, statutory/private payer types, care-aid billing route, discount contracts (RxAktuell) → payer and prescriber identifiers, payer-specific billing routes and preferred-product lists.
- DATEV creditor accounts, GDPdU → mapping suppliers to ledger accounts for accounting export.
- Home inspection protocol → periodic pharmacist audits of institutions with defect tracking.
- GDPR rules (consent, access report, retention) → privacy-law compliance features; Syria's rules may differ, but the mechanics carry over.
- VAT-free internal settlement between branches with own number range → intra-group transfer invoicing that keeps external invoice numbering gapless.
13. Open questions
- Default lengths of the lock and deletion periods, and whether they differ by role, are not given.
- Whether doctor and employee contacts are also deleted automatically (only person customers and walk-in customers are named).
- A customer belongs to at most one home unit at a time — implied by "change assignment", not stated.
- The complete list of rights is not given; role contents are marked as partial ("among others").
- Role management intro says rights can be added to predefined roles, but the change page allows editing only self-created roles; which is correct is unclear.
- Exact formula order when several article-discount rules match (first matching by priority vs cumulative) is not stated.
- How monthly discount tiers interact with article discounts (additive or sequential) is not stated.
- The postage limit on payers has "no function yet"; the special-copayment field mentioned on the payer page is not described.
- The meaning of abbreviations MMR, POR and OVP is not explained in these pages.
- The schematic diagram of condition logic is an image and was not available.
- Commission points/amount: no calculation or payroll use described.
- Which contact fields are exchanged on pages other than master data is only described as "restricted".
14. Source pages
- Kontakte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/01_kontakte_start.htm
- ABDATA — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Anbieter-Kontakte/anbieter_abdata.htm
- Klassifikationen (Anbieter) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Anbieter-Kontakte/anbieter_klassifikationen.htm
- Anbieter-Kontakte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Anbieter-Kontakte/anbieter_stammdaten.htm
- Zugangsdaten (Arzt) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Arzt-Kontakte/arzt_connect-zugang.htm
- Klassifikationen (Arzt) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Arzt-Kontakte/arzt_klassifikation.htm
- Arzt-Kontakte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Arzt-Kontakte/arzt_stammdaten.htm
- Außendienst-Kontakte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Aussendnst/aussendienst_stammdaten.htm
- Unternehmen (Außendienst-Kontakte) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Aussendnst/aussendienst_unternehmen.htm
- Filialen & Partner — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Filialverwaltung/01_filiale.htm
- Anschriften (Filiale) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Filialverwaltung/filiale_anschriften.htm
- Einstellungen (Filiale) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Filialverwaltung/filiale_einstellungen.htm
- Bevorzugte Filialen festlegen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Filialverwaltung/filiale_einstufung.htm
- Anzeige und Verwendung von Kontakten festlegen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Filialverwaltung/filiale_sichtbarkeit_kontaksuche.htm
- Stammdaten (Filial- oder Partnerapotheke) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Filialverwaltung/filiale_stammdaten.htm
- Heim-, Pflegedienst- und Klinikkontakte in IXOS — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/01_heime_kliniken_start.htm
- Heim-, Pflegedienst- oder Klinikstruktur anlegen und bearbeiten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heim_klinikstruktur_anlegen_aendern.htm
- Formular für ein Heimbegehungsprotokoll drucken — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heime_drucken_formular_heimbegeh.htm
- Klassifikationen (Heim/Pflegedienst/Klinik) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heime_klassifikation.htm
- Zugangsdaten (Heim/Pflegedienst/Klinik) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heime_klinik_connect-zugang.htm
- Struktur (Heim/Pflegedienst/Klinik) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heime_klinik_struktur.htm
- Anzeigebereiche der Heim-/Pflegedienst-/Klinikstruktur anpassen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heime_klinik_struktur_anpassen.htm
- Fakturaeinstellungen vorgeben (Heim/Pflegedienst / Klinik) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heime_klinik_struktur_faktura.htm
- Sortierung des Rechnungsdrucks einstellen (Heim / Klinik) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heime_struktur_faktura_rechnungsdruck_sortier.htm
- Zuordnung von Bewohnern/Patienten zu Heim/Pflegedienst verwalten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heime_struktur_heim_zuordnen.htm
- Zahlungsverkehr für Heime, Pflegedienste bzw. Kliniken — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Heim-Kontakte/heime_zahlungsverkehr_bankverbindung.htm
- Klassifikationen (Kostenträger) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Kostentraeger-Kontakte/kostentraeger_klassifikation.htm
- Rabattverträge (Kostenträger) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Kostentraeger-Kontakte/kostentraeger_rabattv.htm
- Spezifische Daten (Kostenträger) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Kostentraeger-Kontakte/kostentraeger_spezifische_daten.htm
- Kostenträger-Kontakte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Kostentraeger-Kontakte/kostentraeger_stammdaten.htm
- Konditionen (Lieferant) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/01_lieferant_konditionen_start.htm
- Konditionsvereinbarungen pflegen und einsehen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_allgemein.htm
- Konditionsvereinbarungen - Artikellisten konfigurieren — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_artikellisten_konf.htm
- Konditionsvereinbarungen - Artikelrabatte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_artikelrabatte.htm
- Konditionsvereinbarungen - Artikel importieren — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_artikelrabatte_artikelliste_import.htm
- Auftragsarten auswählen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_auftragsarten.htm
- Einstellungen für Lieferanten-Konditionen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_einstellungen.htm
- Konditionsvereinbarungen - Gebühren — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_gebuehren.htm
- Konditionsvereinbarungen - Monatsrabatte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_monatsrabatte.htm
- Preisspanne hinterlegen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_preisspanne.htm
- Schematische Darstellung der wichtigsten Zusammenhänge — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_schaubild.htm
- Konditionsvereinbarungen - Skonto — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_skonto.htm
- Sortimentsgruppen auswählen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/Konditionen/lieferant_konditionen_sortiment.htm
- Angebotslisten (Lieferant) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_angebotslisten.htm
- Anbieter und bevorzugte Lieferanten sortieren — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_bevorzugte_ova_lieferanten.htm
- Drucken eines Blankoformulars zum Eintragen von Konditionsvereinbarungen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_drucken.htm
- Einstellungen (Lieferanten) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_einstellungen.htm
- Unteraufträge anlegen und verwalten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_einstellungen_unterauftraege_verw.htm
- Klassifikationen (Lieferanten) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_klassifikationen.htm
- Lieferparameter — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_lieferparameter.htm
- Vertragsdatenauskunft für MSV3 — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_lieferparameter_vertragsdaten.htm
- Sendeparameter (Lieferant) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_sendeparameter_akt.htm
- Lieferanten-Kontakte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_stammdaten.htm
- Vertragsdaten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_vertragsdaten.htm
- Zahlungsverkehr (Lieferanten) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Lieferanten-Kontakte/lieferant_zahlungsverkehr_bankverbindung.htm
- Benutzerkonto (Mitarbeiter) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/mitarbeiter_benutzerkonto.htm
- Bedienerbild auswählen oder ändern — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/mitarbeiter_benutzerkonto_bedienerbild.htm
- Fingerabdrücke verwalten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/mitarbeiter_benutzerkonto_fingerabdruck.htm
- Mitarbeiter-Kennwort neu vergeben oder ändern — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/mitarbeiter_kennwort_neu.htm
- Klassifikationen (Mitarbeiter) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/mitarbeiter_klassifikation.htm
- Nachrichtentypen (Mitarbeiter) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/mitarbeiter_nachrichtentypen.htm
- Spezifische Daten (Mitarbeiter) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/mitarbeiter_spezifische_daten.htm
- Mitarbeiter-Kontakte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/mitarbeiter_stammdaten.htm
- Zahlungsverkehr (Mitarbeiter) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/mitarbeiter_zahlungsverkehr_bankverbindung.htm
- Benutzerrollen verwalten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/rollenverwaltung.htm
- Benutzerrolle ändern — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/rollenverwaltung_rolle_bearb.htm
- Benutzerrolle löschen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/Mitarbeiter-Kontakte/rollenverwaltung_rolle_loeschen.htm
- Aktualisierung der Einwilligungserklärung — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/einst_ewe_verwalten.htm
- Funktionstasten in der Kontaktverwaltung — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/f-tasten_kontakte_popup.htm
- Informationstexte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/informationstexte_bearbeiten.htm
- Kontaktrolle wechseln — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/kontakt_kontaktrolle_wechseln.htm
- Kontaktrollen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/kontakt_kontaktrollen.htm
- Kontaktrollen trennen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/kontakt_kontaktrollen_trennen.htm
- Kontakt sperren und löschen sowie Kontaktstatus ändern — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/kontakt_loeschen.htm
- Neuen Kontakt anlegen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/kontakt_neu_anlegen.htm
- Auskunft über personenbezogene Daten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/kontakte_ausdruck_personenbez_Daten.htm
- Auskunftshistorie — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/kontakte_ausdruck_personenbez_Daten_Historie.htm
- Dokument scannen und in ELO übertragen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/kontakte_dokument_scannen.htm
- Kontaktbezogene Ausdrucke erstellen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT4_Beratung/Kontakte/kontakte_kunden_drucken.htm