Skip to main content

Customer contacts: records, search, duplicates, walk-ins and the customer file (Kontakte – Kunden-Kontakte, Laufkunden, Kontaktsuche, Dubletten)

1. Purpose and scope​

The Contacts module (Kontakte) is the pharmacy's master register of everyone it deals with. This chapter covers the customer side of it:

  • Finding contacts: standard and phonetic name search, wildcard rules, advanced search with role-specific criteria, configurable hit lists, the contact picker used by other modules, scanning a customer card or reading an insurance card to open a customer.
  • The customer file (contact details, Kontaktdetails): master data, addresses, communication channels, customer-specific data (payment preference, customer card, family and guardian links, delivery, health and long-term-care insurance), invoicing terms (Faktura), payment transactions (credit limit, debtor account, bank accounts, SEPA mandates), discounts / coupons / price schemes, loyalty bonus accounts, consent management (data protection), classifications, customer-app access, change history, sales history.
  • Clinical parts of the customer file: risk management (CAVE profile: allergies, diseases, weight, creatinine/GFR; documented interaction and CAVE risks), medication-management enrolment, the medication plan page, the federal medication plan (Bundesmedikationsplan, BMP) read-in and comparison, the change history of medication-relevant data, sample articles (medicines obtained elsewhere).
  • Lightweight contact types: walk-in customers (Laufkunden — temporary records that are locked and deleted automatically) and address-book entries (Adressbucheintrag — contacts without a role), and how both are promoted to full customers.
  • Data quality in a pharmacy group: contact exchange between branch and partner pharmacies (Kontaktaustausch) and duplicate search and merge (Dubletten).

Users: counter staff (search, quick creation, walk-ins, sales history, handing articles to the till), pharmacists (CAVE data, medication management, BMP), back office / managers (invoicing terms, bank data, duplicates, consent clean-up, permissions).

Out of scope here (other chapters): supplier, doctor, staff and care-home contacts in depth; the medication-management module itself; invoicing runs and dunning; the payment-transactions module and SEPA file export; reports; bonus and discount model administration.

2. Key concepts and terms​

German termEnglishMeaning
KontaktContactAny record in the contact register; carries one or more roles.
KontaktrolleContact roleWhat a contact is to the pharmacy: customer, walk-in customer, doctor, supplier, payer, employee, care home, clinic, nursing service, branch/partner pharmacy, etc. A contact can hold several roles.
Kunde (Person / Firma)Customer (person / company)Customer role; type person (natural person) or company (legal entity).
LaufkundeWalk-in customerTemporary customer record created only so a one-off process (order, credit, service) can be tied to a person; locked and deleted automatically after the process closes.
AdressbucheintragAddress-book entryLightweight contact with no real role; can be promoted to any role.
KontaktdetailsContact detailsThe customer file: a set of pages (master data, addresses, specific data, etc.).
StammdatenMaster dataName, type, status, default address, communication, customer number, consent, invoicing permission, VAT handling.
Spezifische DatenCustomer-specific dataPayment preference, flags (back-office, analysis-neutral, cooperation partner…), blistering, customer card, relationships, delivery, insurance.
AnschriftenAddressesAll addresses of a contact, typed default / invoice / delivery.
FakturaInvoicing (account sales)Per-customer terms for selling on account and issuing invoices / delivery notes.
FakturamodellInvoicing modelReusable bundle of invoicing terms assigned to customers.
Faktura-ErlaubnisInvoicing permissionFlag that allows account sales to the contact.
ZahlungsverkehrPayment transactionsCredit limit, debtor account, direct-debit target account, bank accounts.
SEPA-LastschriftmandatSEPA direct-debit mandateStored debit authorisation (reference, granting date, sequence type).
ForderungslimitReceivables limitMaximum open credit granted to the customer.
DebitorenkontoDebtor accountCustomer's account number in bookkeeping (DATEV export).
KundenrabattmodellCustomer discount modelDiscount scheme assigned to the customer.
SofortrabattInstant discountPercentage taken off at the moment of sale, limited to an assortment scope.
PreisschemaPrice schemeWholesale price scheme (licence-bound).
BonuskontoBonus accountLoyalty-points ledger for an account-based bonus system.
EinwilligungserklärungConsent declarationCustomer's (data-protection) consent with scopes: data storage, advertising channels, care-relevant data, contact exchange.
Familie / AnsprechpartnerFamily / contact personHousehold grouping of customers; the contact person is the family's lead member and can be the joint invoice debtor.
Gesetzlicher BetreuerLegal guardianContact who legally represents a customer; can be the invoice recipient.
KlassifikationClassificationTag / segment assigned to contacts.
KontaktaustauschContact exchangeSharing of contact master and sales data across the pharmacies of a group (Verbund) or sub-group (Teilverbund).
Dublette / Kontakte mischenDuplicate / merge contactsTwo or more records for the same real contact; merging creates one new record and deletes the sources.
HerkunftOriginPharmacy (branch) where the contact was created.
Phonetische SuchePhonetic searchSound-alike name search, alternative to the standard pattern search.
Erweiterte SucheAdvanced searchSearch with role-specific criteria, status filters, former names / numbers.
TrefferlisteHit listSearch result list with configurable columns.
SchnellanlageQuick creationMinimal create dialog launched from a picker (e.g. at the till).
Offene PostenOpen itemsCombined list of a customer's unfinished advance deliveries, missing prescriptions, back-orders, pickups and unpaid invoicing documents.
RisikomanagementRisk managementCustomer page with the CAVE profile and documented risks.
CAVE-CheckCAVE (contraindication) checkAutomatic check of each dispensing against the patient's allergies, diseases and parameters.
Erweiterter CAVE-CheckExtended CAVE checkCAVE check that also uses body weight and kidney function (creatinine / GFR).
MIV-SchlüsselPatient-characteristic codeCode from the German drug-data provider's catalogue of allergies and diseases.
Hauptbegriff / Folgebegriff / EinzelbegriffMain / subordinate / single termHierarchy levels of disease characteristics.
Diathese (allergische)Allergic diathesisDisease characteristic "tendency to allergies"; proposed automatically when many allergies are stored.
Interaktion / CAVE-DokumentationInteraction / CAVE documentationRecord of a risk the user consciously accepted in a sale, with reason and optional expiry.
Medikationsmanagement (MM)Medication managementPharmacist-led management of a patient's medication; enrolment flag on the customer.
MedikationsverlaufMedication courseOne medication used over time with dosing sections, stock and range.
Dauermedikation / BedarfsmedikationLong-term / as-needed medicationClassification of a course; controls whether it stays on the printed plan after its supply range ends.
Bundesmedikationsplan (BMP) / eMPFederal medication plan / electronic medication planGerman standardised patient medication plan with 2D code / its electronic form.
MedikationsplanvergleichMedication plan comparisonLine-by-line reconciliation of a read BMP against the system's medication record.
KundenparameterCustomer parametersPharmaceutically relevant patient values printed on the BMP (allergies, weight, creatinine, pregnancy, etc.).
Mustereintrag / MusterartikelSample entry / sample articleRecord of a medicine the customer has but did not buy here (e.g. from the doctor).
Pharmazeutische Dienstleistung (PDL)Pharmaceutical serviceBillable clinical service (e.g. polymedication review).
VerkaufsdatenSales dataCustomer's purchase history page.
PauschalenFlat ratesAids supplied under a periodic flat-rate reimbursement.
PflegehilfsmittelConsumable care aidsMonthly-capped care supplies billed to the long-term-care insurer.
Kostenträger / IKPayer / institution identifierHealth or care insurer and its institution identifier (IK).
KassenstatusInsurance statusPatient's co-payment status code.
ZuzahlungsbefreiungCo-payment exemptionPeriod in which the patient is exempt from statutory co-payments.
ÄnderungshistorieChange historyField-level audit trail of contact data.
Zugangsdaten / "Meine Apotheke"Access data / customer appCustomer's login to the pharmacy's patient app and web portal.
LeiterManager roleBuilt-in role holding most sensitive rights.
ArbeitsplatzschutzWorkstation protectionUnder the sensitive-data permission concept, certain functions are allowed only on approved workstations.

3. Data model​

3.1 Contact (Kontakt) — the core record​

  • Identity: name (the ONLY mandatory field), first name, salutation, title, date of birth, sex; for companies a cost centre (Kostenstelle; written into the buyer-reference field of electronic invoices).
  • Roles: one or more contact roles; type person / company (type selectable only when the contact holds the customer role exclusively).
  • Status: Aktiv | Inaktiv (not currently used; excluded from standard search, findable in advanced search, can be reactivated) | Verstorben (deceased; natural persons only; excluded e.g. from birthday lists). Separate locked state (gesperrt): result of consent withdrawal or automatic walk-in lock; locked contacts are hidden from standard search, shown red in advanced search, cannot be taken into other modules.
  • Customer number: two parts — short code of the creating branch (when the contact comes from another branch) + number. Auto-assigned on creation.
  • Origin (Herkunft): pharmacy where created. Changed on / by: last change date and employee.
  • Exchange flag (Kontakt austauschen) + scope (whole group / sub-group).
  • Info texts: free information texts attached to the contact (shown via info icon; also till hints from information/tasks/questions).
  • Default address and default communication (mirrored on the addresses / communication sub-structures).
  • Consent status (see 3.9).
  • Invoicing permission, invoice preferred as (printout | e-mail), VAT display mode, VAT ID + VAT-ID check state, separate statistics flag.
  • Geo-coordinates of the default address (determined after a courier sale; manually adjustable).

3.2 Walk-in customer (Laufkunde)​

  • Same contact entity with role "walk-in"; reduced set of pages and fields; change history available.
  • Lifetime: until the related process (pickup, credit, invoicing) is finally closed, then automatic lock after a configured period, then final deletion after a further configured period.
  • Consent status additionally has the state "consent not granted" by default; signing consent turns the role into customer (person) automatically.

3.3 Address-book entry (Adressbucheintrag)​

  • Contact without a real role; all fields exchanged in a group; promotable to any role.

3.4 Address (Anschrift)​

  • Unlimited per contact. Fields: salutation, title, surname, first name, free addressee line, two additional lines, district (Ortsteil), PO box, street/no., postcode, city, country, remark.
  • Type: blank | Standard (default) | Rechnung (invoice) | Lieferung (delivery); at most one of each of the three named types.
  • Origin: own address, or reference to another contact's address (synchronised from the source); markers "comes from another contact" / "used by other contacts".

3.5 Communication entries​

  • Per contact role: phone, mobile, fax, e-mail(s), homepage; each optionally typed by usage: default / invoices / deliveries.
  • E-mail address may carry a password (attachments sent as encrypted PDF) or a "link" mode (download link, always encrypted, password required).
  • If the customer uses the app: an auto-generated app mailbox address (…@meine-apotheke) shown instead of the homepage.

3.6 Customer-specific data​

  • Preferred payment method; flags back-office customer, analysis-neutral, cooperation partner, wholesale partner, batch documentation for medicines, enter batch/expiry for blister articles, duplicate-medication check, additional recommendation (cross-selling), stock-neutral delivery.
  • Blistering participation: No | with stock keeping | without stock keeping (contract blistering) | third-party system with stock keeping | third-party system without stock keeping.
  • Preferred tour, delivery note text, robot output chute number, EDI partner (person: one eye-clinic system; company: that system or EDIFACT with recipient ID and sender ID).
  • Customer card number (may be shared by several customers).
  • Relationships: family link (via family entity), legal guardian link (+ "guardian is invoice recipient").
  • Health insurance: payer, payer IK, insured number, insurance status, co-payment exemption from/to, addition (free text). Not for companies.
  • Long-term-care insurance: care-fund payer, payer IK, billing address of the care fund, insured number, approval state for consumable care aids (granted / requested / none), legacy free-text care fund field. Not for companies.

3.7 Invoicing settings (Faktura)​

  • Separate invoice flag; own settings flag; invoicing model OR individual settings; "settings from" (inherited source unit); invoice recipient address.
  • Payment info: payment method (transfer | direct debit), invoice issuing (automatic with cycle immediate/daily/weekly/half-monthly/monthly/quarterly | manual | none), payment-terms model, dunning-terms model, alternative pharmacy account, service flat fee (label + gross amount).
  • Print options: counts of delivery notes, back-order delivery notes and invoices; label printing; automatic delivery-note print rule; zero-total handling flags; automatic print/delivery of invoices and reminders; automatic PDF creation.
  • Forms per document type (delivery note, invoice, reminder, collective slips, label, receipt) with sort orders and options.
  • For care-home structures: inherited from the superior unit unless own settings; synchronised with the home contact.

3.8 Payment transactions​

  • Receivables limit, open receivables (display), debtor account number, "direct debit to company account".
  • Bank accounts (n per contact): account holder, IBAN, BIC (live-validated, auto-generated), bank name, bank code, account number; usage flags Default and Direct debit (exactly one account each).
  • SEPA mandate per debit account: reference, granted-on date, sequence type first / recurring, signature (digital or printed), revoked state.
  • Consent to data storage granted / not granted; handed out on (date); version (date of version + short code of managing branch); signed flag; signed by legal representative (+ representative contact or typed name); advertising (all channels or selected channels: digital, phone, post); care-relevant data consent; contact exchange (+ group / sub-group).
  • Derived status: signed | handed out, not signed (pending) | not granted / revoked | needs update / re-signing | (walk-ins) not granted.
  • Signed document stored in the document management system (DMS) / as PDF.

3.10 Family and guardianship​

  • Family: members (customer contacts), contact person (first member by default), invoicing mode (per member | per member with collective slip to contact person | total to contact person).
  • Guardian relation: guardian contact ↔ ward contacts (many wards per guardian; one guardian per ward is implied by merge rules).

3.11 Classification assignment​

  • Classification (name, description, kind = contact roles it applies to, exchange marker, number of assigned contacts) ↔ contacts (n:m).

3.12 Loyalty​

  • Bonus account per customer per bonus system (one shared account group-wide when contacts are exchanged).
  • Booking: date, pharmacy, units awarded/redeemed, reason, booking type (sale | reward redemption | manual correction | account transfer), units already redeemed, expired, available, expiry date.
  • Personalised coupons: coupon model, barcode, coupon type, valid from/to, redeemed flag (+ date and branch when redeemed elsewhere).
  • Discount model assignment: model, valid from, "prefer model price" (stored on the model), purpose. Instant discount: percentage + assortment scope + "further discounts" allowed/restricted. Price scheme (licence-bound).

3.13 Clinical profile (CAVE data)​

  • CAVE check on/off; extended CAVE check on/off; age (derived from DOB), sex; weight + last-update date; creatinine + last-update date; GFR (computed from creatinine).
  • Allergy list: MIV code, designation, how assigned (via which finished medicine and/or substance), edited on.
  • Disease list: MIV code, designation (sex-specific where relevant), edited on, status statisch | temporär | deaktiviert, end date.
  • Inactivated characteristic handling: processed flag per inactivated item.
  • Risk documentation: documented interactions and documented CAVE risks, each with reason and optional expiry date (expired entries greyed).

3.14 Medication management enrolment​

  • MM participation flag + since date; BMP/eMP auto-print option; data capture complete; last counselling; next counselling; number of open drug-related problems.
  • Treating doctors (doctor contact, specialty, family-doctor flag, remark) — a family doctor is required.
  • Pharmaceutical services: kind, date, contract document marker, results marker, billing voucher marker; complete when all columns are filled.
  • Medication courses (owned by MM module): article, dosing sections, stock, long-term vs as-needed, stops (pause / discontinuation), deviating free texts per PZN.
  • Change history of medication-relevant data (category, reference, change type, old/new value, difference, user, markers).

3.15 Sales data​

  • Read view over the customer's sales lines: sale type, date, markers (split pack, blistered, special code / e-prescription billing note), designation, dosage form, unit, quantity, price, co-payment, extra cost, customer-paid total, open back-order marker, dispensing branch; flat-rate and care-aid groupings.
  • Sample articles are stored as special sales lines (quantity ≥ 1 from sales data; from MM may be 0).
  • Per-customer "anonymise sales data" flag.

3.16 Customer-app access​

  • Active flag, registration date, last login, last order, login ID / e-mail, password (one-time printable), login QR code, list of other group pharmacies where registered.

3.17 Change history​

  • Per historised field change: area (page), category, property, original value, new value, change date, operator. Includes info-text changes and blistering participation changes.

4. Features​

4.1 Contact search in the Contacts module (Kontaktsuche) [GENERIC]​

  • Purpose: find a contact quickly by name.
  • Trigger: open a navigation entry of the Contacts module (entries group roles, e.g. "Kunde" for customers; "Warenlogistik" for suppliers, vendors/manufacturers (Anbieter) and field reps) and start typing — typing anywhere on the screen starts a search, focus does not need to be in the search field; typing again after a search replaces the previous term.
  • Matching: always against the stored name, within the roles of the selected navigation entry.
    • Implicit trailing wildcard. Leading * for an unknown beginning (*mann); ? for exactly one unknown character (Ho??mann).
    • "Surname, first name" pattern: Muster, He; *, th searches by first name only.
    • Standard search can be widened to phonetic search (sound-alike). The phonetic button is visible only while standard search is the default; parameter "Automatik" (system settings Contacts, page phonetic search) makes phonetic search the pharmacy-wide default.
    • Supplier / vendor search is tolerant: umlaut variants match (ä = ae), punctuation, spaces, hyphens, plus signs, brackets, slashes and apostrophes are ignored; second and third name fields are searched too, so a hit may not visibly contain the term. Search from article management is exact.
  • Rules: inactive and deceased contacts are excluded (and, with the sensitive-data permission concept, locked contacts). If the selected role yields nothing, the user is offered to repeat the search across all roles.
  • Group visibility: toggle "all exchanged contacts" (visible only if the pharmacy has hidden or restricted other pharmacies' exchanged contacts) adds exchanged contacts of all other group pharmacies to the hit list.
  • Card-based opening: scanning the customer card with a hand scanner opens the customer immediately. Reading the health-insurance card with a chip-card reader opens the customer immediately if card and stored data agree; if they differ, a "reconcile customer data" (Kundendaten abgleichen) dialog appears first.
  • The same standard search drives the customer suggestion list at the till (Kundenvorschlagsliste).

4.2 Contact picker in other modules [GENERIC]​

  • Many modules need a contact; a picker window (titled by contact type) offers the same standard / phonetic search.
  • Customer pickers have separate tabs for customers and walk-in customers (unless walk-ins are configured to appear in the customer tab, see 4.25).
  • Payer pickers accept payer name or payer number.
  • Vendor / field-rep pickers allow multi-select with checkboxes; selected items stay on top, the rest alphabetical; a tooltip lists the selection.
  • Quick creation (Schnellanlage) can be launched from the picker (used for walk-ins at the till).

4.3 Advanced search (Erweiterte Suche) [GENERIC]​

  • Where: Contacts module; till customer picker; till payer picker (pre-filtered to role payer with filters statutory / private / long-term-care funds).
  • Inputs: contact role ("no selection" = all roles) — the available criteria change with the role (different sets for customer person, customer company, payer); status inactive / deceased; street and other fields. Some criteria only become editable after ticking their checkbox. Checkbox "show locked contacts too".
  • Former identities: for customers (person/company), checkboxes "include former names" and "include former customer numbers" search the history of contact details. Standard search no longer matches old customer numbers; an old customer card can be scanned into the customer-number criterion.
  • Rules:
    • If the result contains inactive or deceased customers, a message offers to change their status.
    • Locked contacts appear only with "show locked" ticked; under the sensitive-data permission concept they are visible only with the right "Contacts general: edit locked contact data" (part of role Leiter); the same right is needed to unlock or finally delete them.
    • Display: inactive / deceased in grey, locked in red. Locked contacts cannot be transferred into other modules.
    • Criteria persist until changed, cleared ("Eingaben löschen") or until the Contacts module or till is closed; the active criteria are shown above the hit list.

4.4 Hit lists (Trefferlisten) [GENERIC]​

  • Columns are user-configurable (list-view configuration); context menu jumps to functions of the selected contact.
  • Available information: title, salutation, name, first name, type (person/company), specialty (doctors), job title, date of birth, short code and vendor number (suppliers), branches where active, payer type, IK, pharmacy short code; default street, postcode, city, phone, fax, mobile, e-mail, homepage of the role; customer number (prefixed by creating branch's code); customer card number; payer, payer IK, insured number, insurance status, exemption from / until; last sale date; care home and home unit names; additional info (customer hint + till hints from information/tasks/questions); origin; direct-debit BIC / IBAN; "has at least one bank account"; "my customer number" at a supplier; personnel number, hire date, operator register (employees).
  • Icon columns: supplier is also vendor (direct supplier); supplier is a branch/partner pharmacy; info text present; customer card; documents in DMS (click opens them); medication management / blister (click opens MM page or blister management); care-home resident / nursing-service patient (tooltip shows assignment; click opens Faktura/home page); bonus/discount model (click opens discount page); sales data present (may be locked; click opens sales data); CAVE check active; consent status (4 states: current signed consent / form handed out / no signed consent / consent outdated; click opens consent dialog); walk-in customer; family member; further roles (customer is also employee or doctor); registered in the customer app (shown in duplicate hits when licensed).

4.5 Contact details frame (Kontaktdetails) [GENERIC]​

  • Opens on the master data page; a header shows key data and an info icon (opens the contact's information texts). A selector switches between the contacts of the last search; for care-home residents, next/previous resident of the same home structure.
  • Status icons on master data, specific data and MM pages: electronic medication list (eML) can be opened [DE]; has customer card; medication management and/or blistering; care-home resident (tooltip: which home); nursing-service patient; family link; open items exist; DMS documents exist; has customer-app access; app registration not yet completed.
  • Open items (Offene Posten) for customers and walk-ins: one combined list of advance deliveries (Vorablieferungen), missing prescriptions (Fehlende Rezepte), pickups and back-order deliveries (Nachlieferungen), and receivables / invoicing documents not yet completed.
  • Propagate to family: when saving changes that typically concern the whole household (address, health insurer, discount model, landline number, etc.), a dialog lets the user tick which family members receive the same change.
  • On opening the contact details, the system checks expired temporary diseases (4.19.5) and unprocessed inactivated CAVE characteristics (4.19.6).

4.6 Master data page (Stammdaten) [GENERIC]​

  • Purpose: basic identity and contact data plus overarching settings (invoicing permission, VAT handling). Branch/partner-pharmacy contacts have a different master-data page.
  • Data-protection notice: store customer data only with written consent (see 4.16).
  • Role: set at creation; further roles can be added to an existing contact (e.g. a doctor also becomes a customer).
  • Status changes: setting a customer that is assigned to a care home to inactive or deceased asks whether to remove the home assignment.
  • Type person ↔ company: allowed only when the contact has no other roles and does not take part in medication management (notice otherwise). Person → company removes an existing consent declaration; company → person opens the consent dialog if the missing-consent parameter is on.
  • Default address (copied automatically to the addresses page as default). Parameter "prefill postcode and city when creating customers" fills in the pharmacy's own postcode/city. A country other than Germany shows that country's flag in hit lists (if configured), in sales and in the customer-info overview.
  • Address entry assistance (master data, addresses, quick creation): entering a postcode and moving to the city field lists matching cities (unique match is prefilled); typing a city suggests city + postcode; a postcode may be typed into the city field. Suggestions come first (black) from the pharmacy's own contacts ordered by frequency, then (grey) from a built-in general address database if fewer than 10 own matches exist; maximum 50 suggestions.
  • Geo-coordinates for courier delivery: after a sale completed with completion type courier (Bote), the address is geocoded; a marker shows success on master data and addresses; the point can be shown on a map and moved manually (confirm, locate, double-click, OK).
  • Communication (see 4.7). Customer number (see 4.8). VAT ID (companies only; 4.13). Consent status with button to the consent dialog.
  • Invoicing permission (Faktura-Erlaubnis): allows account sales. If missing, invoicing a sale shows a notice and the permission can be granted on the spot. Set automatically for customer contacts of care homes, home units and residents (for residents only if their address equals that of the superior unit / home).
  • Invoice preferred as: printout (default) or e-mail. Takes effect only when "print/deliver invoices automatically" is on in the invoicing settings; manual reprints default to print but the channel can be switched in the print preview. If e-mail is chosen but neither the customer nor the invoice recipient has an e-mail of usage default or invoice, a warning marker appears and invoices go out as printouts. A legal guardian who is the invoice recipient uses the guardian's preference. Care-home residents: by default the home's setting; units with separate invoicing use the unit's; residents with separate invoicing their own. In cross-invoicing groups with exchange the setting propagates to the other pharmacies.
  • VAT display on invoice (editable only with invoicing permission) [DE/EU-SPECIFIC; idea: per-customer tax treatment of invoices]: normal invoice with gross unit prices (private customers); invoice with net unit prices (businesses); VAT-exempt for sea-going ships (needs licence "Faktura Profi" and type company, else warning); VAT-free intra-EU business supply (needs that licence and a VAT ID on the contact, else warning); VAT-free other reasons (export outside the EU, sales to NATO forces, special permits) — no reason is printed, the user must add it to the invoice footer.
  • Separate statistics (Getrennte Statistik): sales to this customer are kept out of normal sales statistics and out of purchase-order optimisation (demand calculation). Not retroactive. Automatically the case with stock-neutral delivery. Example: goods bought on behalf of a partner pharmacy outside the group and passed on by invoiced order.
  • Exchange block (groups only): exchange checkbox + group / sub-group scope; origin; changed on / by. All master-data fields are exchanged; other pages as noted per page.

4.7 Communication channels and secure e-mail [GENERIC]​

  • Phone, mobile, fax, e-mail, homepage per contact role; a sub-dialog (tabs telecommunication / internet) assigns which number and which e-mail address is the default, which is used for invoices and which for deliveries; several e-mail addresses allowed.
  • Password per e-mail address: attachments are converted to PDF and sent encrypted; the recipient must know the password. Alternative "link" mode sends a download link — always encrypted, so a password is required. Rationale: documents to private persons contain health data and must be protected.
  • Compose a new e-mail from the field (default address prefilled).
  • Customer-app users: an auto-generated app mailbox address replaces the homepage field; messages can be sent to the app inbox. "New message" uses the app if the customer uses it, otherwise (no app or registration incomplete) the default e-mail.

4.8 Customer number assignment [GENERIC]​

  • On creation the next free number after the last one assigned in the pharmacy is given automatically.
  • Among pharmacies that exchange customers, a number is used only once.
  • Per-pharmacy number ranges: assign a start value manually once (e.g. pharmacy A 1,000,000 → next automatic 1,000,001; pharmacy B 2,000,000 → 2,000,001); leave gaps large enough to avoid overlap.
  • Number displayed as branch short code + number when the contact originates from another branch.
  • Customer number, family doctor and payer cannot be typed freely during a merge (4.27).

4.9 Addresses page (Anschriften) [GENERIC]​

  • Unlimited own addresses and references to other contacts' addresses; type blank / default / invoice / delivery, at most one of each named type.
  • Markers: address originates from another contact; address is used by another contact (customer contacts only); customer prefers invoices as printout vs e-mail.
  • Referencing another contact's address (customer contacts only): use a registered contact's name + address as default, invoice, delivery or untyped address — e.g. same household, or invoices go to a relative / carer who is a customer. Tooltips name the source contact (on the target) and list the users of the address (on the source). Changes at the source are synchronised to the target.
  • Use locally (Lokal verwenden): breaks the reference; the address becomes a plain copy that no longer updates (a notice says so).
  • Group behaviour: if the source contact is exchanged, the reference marker also appears at the target in other pharmacies. If the source is not exchanged, only the address text is exchanged with the target; no marker elsewhere; exchanging the source later does not restore the link or synchronisation.
  • Deletion: the default address can never be deleted; deleting an invoice or delivery address always asks for confirmation.
  • All addresses of a contact are exchanged within the group.
  • A default address entered on master data appears here automatically as default.

4.10 Customer-specific data page (Spezifische Daten) [GENERIC unless tagged]​

  • Preferred payment method: prefilled when closing a sale for this customer; overrides a per-workstation preset. If a sale involves several customers with different preferences, nothing is prefilled and a notice says so. Pickups cannot be settled through invoicing even if the preference is later changed to account sale; they must be settled at the till with another method (e.g. cash), even with zero remainder. Care homes and home units are automatically "account sale".
  • Back-office customer: all sales count as back-office sales (excluded e.g. from staff deployment planning).
  • Analysis-neutral: customer ignored in analyses.
  • Cooperation partner: customer is a partner pharmacy in the group that belongs to a different trading company (different VAT ID); its revenue and units are filtered out of reports, the cockpit and the "IBV" analysis.
  • Wholesale partner (company customers): also sets cooperation partner, batch documentation and stock-neutral delivery automatically.
  • Blistering participation: No / with stock keeping (manual or machine blistering in the pharmacy) / without stock keeping (contract blistering) / third-party system with or without stock keeping. With the vendor's own blister system: yellow warning if not configured, red if no valid licence.
  • Enter batch and expiry for blister articles: prompts for both on dispensing blister articles to this customer.
  • Batch documentation for medicines [DE-SPECIFIC; idea: mandatory batch traceability for inter-pharmacy supplies]: prompts for the batch on every medicine dispensing to this customer (German pharmacy operating regulation requires documenting and passing on batches in goods exchange between pharmacies).
  • Duplicate-medication check: warns in customer-related sales about possible duplicate medication; editable only if the global parameter "duplicate-medication check active" is on; default for new customers from parameter "duplicate-medication check on customer creation".
  • Additional recommendation: with the cross-selling module, show stored cross-selling recommendations for this customer by default.
  • Preferred tour (delivery-management licence): only regular tours; proposed when setting delivery modalities; a tour on a care-home contact applies automatically to all its residents that have none. Delivery note text (Lieferhinweis): shown (editable) at the till in the pickup/delivery dialog and printed under customer/delivery data on the digital courier list.
  • Stock-neutral delivery: articles of the sale (usually an account sale) are not taken from stock, only from the special delivery.
  • Robot output chute: number of the picking machine's chute used for this contact (for care homes set in the home structure).
  • Electronic data interchange: person customers can be linked to one eye-clinic partner system (licence); company customers to that system (delivery-note data sent electronically) or EDIFACT (orders, delivery notes and invoices exchanged electronically; recipient ID and sender ID enterable only with EDI on).
  • Customer card: scan or type the number. A number may be shared by several customers: on save a warning says it is already assigned (to catch typos) but it is saved; scanning such a card offers a choice of the customers.
  • Family (relationship field): pick customer contacts (picker proposes customers with the same surname) to link; the currently open contact becomes contact person. If already in a family the field shows the contact person and opens family details (4.17). A trash icon detaches the contact; if only one member would remain, the family is deleted automatically. Advice: coordinate with the data-protection officer.
  • Legal guardian: assign via contact picker or create a new contact. A guardian contact shows "customer is guardian" and lists its wards. "Is invoice recipient": invoices are addressed and delivered to the guardian using the guardian's address and preferred channel.
  • Health insurance [DE-SPECIFIC; idea: payer link, member number, co-payment status and exemption period on the patient] (not for companies): payer from list; IK filled automatically; insured number plausibility-checked (warning marker on leaving the field and message on save if invalid); insurance status (default derived from age at creation); co-payment exemption from/to; free-text addition. Rules in section 6.
  • Long-term-care insurance [DE-SPECIFIC; idea: second payer for home-care consumables with an approval state] (not for companies): care fund payer, IK (auto), billing address of the care fund (maintained as invoice address on the payer contact), insured number (may be missing while approval is incomplete; mandatory when billing through a particular clearing centre, "DRZ"), approval state for consumable care aids: approval granted (approval period entered for at least product groups 51 and 54) / approval requested (payer or approval period missing for one of the two groups) / no approval (neither payer nor period for one of the groups). Button opens the cost-coverage application form for the care fund. Legacy free-text care-fund field (pre-2018) is mapped to a payer where possible and can be deleted after checking.
  • Group exchange: everything on this page is exchanged except preferred tour, robot output chute and long-term-care insurance data.

4.11 Invoicing page (Faktura) [GENERIC: per-customer account-sale terms, inheritable through an organisational hierarchy]​

  • Scope: customer contacts and branch/partner-pharmacy contacts (for a branch as customer: payment-relevant data; the internal goods-exchange settlement setting sits on the branch contact's master data). Ordinary customers: pick an invoicing model OR maintain individual payment info, print options and forms. Care-home / nursing-service units, residents / patients and clinic wards: page titled "Faktura / Heim" or "Faktura / Pflegedienst", with separate-invoice and own-settings options; resident-of / unit information shown only for assigned customers. If a unit or ward has separate invoice or separate delivery, it becomes visible as a customer contact. Invoicing settings of home/nursing customers and units are synchronised with the home/nursing contact.
  • Separate invoice: default off = resident invoiced with the superior unit. On = own invoice that the run for the whole home does not create automatically; the contact must be named explicitly or the run option "additionally create separate invoices" used; receipts (Quittungen) for such residents are never created.
  • Own settings: on = resident has own settings; initially inherited from the superior unit and shown read-only. Invoicing model selectable for residents only with own settings on; assigning a model to residents by bulk processing in Reports switches own settings on; deleting a model that residents use makes them fall back to the superior unit. "Settings from" shows the source unit or "own settings".
  • Invoice recipient: from the addresses page.
  • Lower tabs are editable only without invoicing model (and, for residents/wards, with own settings); otherwise the model's values are shown read-only.
  • Payment info tab: payment method transfer / direct debit; invoice issuing automatic with cycle (immediate invoice, daily, weekly, half-monthly, monthly, quarterly — used by invoicing runs, e.g. "all monthly customers"), manual (excluded from automatic runs, must be named explicitly), none; payment-terms model; dunning-terms model; alternative pharmacy account (any of the pharmacy's bank accounts from company master); service flat fee (label required for the fee line to appear; gross amount, empty prints 0.00; the fee line has no order/delivery-note line behind it so it cannot be analysed in reports or transferred to "MMR"; removable from a marked invoice in the invoice total).
  • Print options tab: number of delivery notes (first original, rest copies), number of back-order delivery notes (list all outstanding quantities of partly and not delivered lines), number of invoices (first original or e-mailed, rest copies); label printing (on = labels printed automatically after closing the order with delivery-note creation, after asking for the count; no reprint after changing a transaction or resolving a pickup slip if labels were already printed; off = manual; printer/format via the default label form); automatic delivery-note printing: always (even if delivered by an external partner such as a blister centre — printed with a "delivered separately" remark) / always except notes containing only separately delivered goods (those are created with the remark but not printed) / only if the delivery contains goods from the pharmacy; print delivery notes with total 0 on invoice; print receipts with total 0 (home/nursing); create invoices with total 0; print/deliver invoices with total 0 (if off such invoices get status Intern); print/deliver invoices automatically (preview offered before print, always before e-mail); create invoices automatically as PDF (document directory with year/month subfolders; filename has invoice number and date; copies suffixed "-Kopie"; independent of printing); print/deliver reminders automatically.
  • Forms tab: per document type a print form or the default: delivery note (+ print all outstanding back-orders, show prices and totals), invoice (+ line sort order), reminder, collective slip for delivery notes (+ sort), collective slip for invoices, label (sub-dialog: form for home/clinic label and for customer label; clear button), receipt (receipts and itemised statements; only for invoicing models and home/clinic structures; + sort).
  • Invoicing model picker: models maintained in the module for invoicing conditions; list shows name, description, number of linked customers.
  • Payment-terms picker: list of terms models with name, info text, default flag (the default model applies automatically to every customer without a manual assignment); type-ahead; opens payment-terms administration to create / change.

4.12 Payment transactions page (Zahlungsverkehr), bank accounts and SEPA mandates [GENERIC credit limit and bank data; DE/EU-SPECIFIC SEPA and DATEV]​

  • General tab: receivables limit (maximum credit granted); open receivables (display); debtor account for bookkeeping — under the DATEV chart of accounts between 10000 and 69999, up to 9 digits; other numbers only after agreement with the tax adviser; automatic debtor-account assignment and digit count can be configured in the DATEV / finance settings. "Direct debit to company account": which of the pharmacy's own bank accounts this customer's debits are collected into. To stop direct debit, set it to none and save.
  • Accounts tab: list + editor of the contact's bank accounts; add, delete (with confirmation). Usage flags Default and Direct debit — exactly one account each. Invoicing by direct debit also needs payment method direct debit on the Faktura page, and a SEPA mandate must be stored. BIC validated while typing — on failure saving is still allowed but a warning marker remains; BIC generated automatically on customer creation or first entry of legacy account data. "Generate IBAN" derives the IBAN from bank code + account number using the standard method. All account data are exchanged within the group.
  • SEPA mandate [idea: stored, signed recurring-debit authorisation with reference, date and sequence type]:
    • No one-off mandates. Blank mandate forms can be printed in advance (contact-related printouts) and the mandate recorded later.
    • Fields: mandate reference (generated, or overwritten with a reference the customer already granted); granted on (actual confirmation date, or expected date while the signature is pending, corrected later); usage first (Erstmalig) or recurring (Folgend — re-use of a manually entered existing reference).
    • Preconditions: valid IBAN and account holder saved; pharmacy's creditor identifier stored in company master (checked on creation; mandatory for SEPA core debits).
    • Signature: digital signature on a signature device, or print (preview, print). After OK the reference is shown as the account's SEPA mandate and the function becomes "edit mandate"; save the customer.
    • Edit: correct the granting date, adjust usage. Revoke: in the edit dialog, with confirmation that the account will no longer be debited. Implicit revocation: if a returned debit is re-submitted in the payment-transactions module with sequence type "last direct debit", the mandate is revoked with the next SEPA file export.

4.13 EU VAT ID verification [DE/EU-SPECIFIC; idea: validate a business customer's tax ID against a government web service before zero-rating]​

  • Intra-EU B2B supplies to a company in another EU country carry no German VAT, provided the customer (type company) has an EU address outside Germany and an EU VAT ID, and the pharmacy's own VAT ID is registered for EU trade. The pharmacy is liable if the exemption was wrongly applied, hence verification is recommended.
  • A check button next to the VAT ID calls German and EU online services. German VAT IDs cannot be checked.
  • States: not checked (also after the contact name or VAT ID changed since the last check); checked and invalid (notice); valid with qualified confirmation (address confirmed too); valid but address not confirmed (simple confirmation, or a value changed after a qualified check). Tooltip shows state and time of last check. Country-specific notations are accepted (e.g. with spaces or dots).

4.14 Discounts, coupons and prices page (Rabatt/Coupons/Preise) [GENERIC]​

  • Instant discount: percentage applied immediately when selling; scope: none (no discount), free-choice (self-service OTC shelf) articles, or free-choice + behind-the-counter display articles. "Further discounts": allow or restrict other discounts (bonus points, check-out coupons) on top.
  • Discount model: pick (or create/change from the picker); validity start; "prefer model price" (always use the model price instead of a calculated price, whichever is cheaper; stored on the model; recommended for purchase-price-based models such as employees or branch pharmacies — guarantees the model applies and avoids a zero price when no sales price exists); purpose text from the model. Removing the assignment shows a safety notice, then save.
  • If a discount would make a sale loss-making, the price-control / price-correction dialog appears and the user decides the final price.
  • Group: discount models and assignments are exchanged among all pharmacies if centrally enabled; any pharmacy may create, change or delete them; changes propagate promptly; a customer has the same model everywhere; all pharmacies share the default model for new customers.
  • Coupons: all personalised coupons issued to the customer; filter by validity; model name, barcode, type, valid from/to, redeemed (grey). Issue a coupon; delete a not-yet-redeemed coupon (context menu "delete barcode"). In a group a tooltip shows redemption date and branch if redeemed elsewhere. Personalised coupons are included in the data-subject access report.
  • Price scheme: only with the professional invoicing licence or clinic licences, for wholesale business; pick / remove. NOT exchanged in the group (everything else on the page is).

4.15 Bonus accounts (Bonuskonten) [GENERIC loyalty-points ledger]​

  • Visibility: only if an account-based bonus system is used AND the customer falls under the customer selection of a usage (Verwendung) of that bonus model, or has already received units through another (possibly expired) usage.
  • Group: with exchanged customers, ONE shared bonus account across the group.
  • Header: bonus system (from systems assigned to the customer); current available units; "in the next N days X units expire" (N default 30, changeable to query).
  • History: bookings from sales, reward redemptions, account transfers, manual corrections. Filters: date range and checkboxes — from sales; manually awarded; reward redemptions; account transfers (bonus accounts moved after a merger of branch/partner pharmacies); already redeemed or expired. Columns: date, pharmacy, count awarded / redeemed, reason, booking type, redeemed, expired, available, expiry date. Fully consumed awards are greyed.
  • FIFO rule: redemptions always consume units from the oldest awards first; on an award row "count" = units received, "redeemed" = units of that award consumed so far.
  • Manual correction (Bonuskonto bearbeiten): requires role Leiter or the right "customer bonus accounts" (+ workstation protection). Dialog: current balance; plus or minus; number of units; resulting total; reason; expiry date for credited units (default = the bonus system's expiry period).
  • Scopes in one tailored declaration: (1) storing personal data including health data used for the CAVE check, only within the pharmacy / group as consented, plus accept/decline advertising by digital channel, phone or post; (2) contact exchange in the group or sub-group (participating pharmacies listed unless replaced by free text); (3) medication management — separate consent because care-relevant data go to third parties (doctors, hospitals), including authorisation for automatic prescription requests to the treating doctor.
  • The shipped print template is a non-binding sample; the pharmacy owner is the data controller and must have it reviewed.
  • Automatic prompt: when creating a customer or changing personal data without consent on file, the dialog opens automatically; can be switched off via parameter "notice on missing consent" (for pharmacies that manage consent outside the system).
  • Opening points: master-data function or consent button; "take over customer data" dialog (BMP / prescription); consent icon in hit lists.
  • Fields: consent to data storage (documents that the declaration was given to the customer to read) / consent not granted; handed out on; status icon; version (date + managing branch code); signed; by legal representative (picked from contacts or typed surname + first name); advertising — all channels or "only" with ticked channels; care-relevant data; exchange contact (+ group / sub-group). For person customers exchange is initially off (default via parameter "allow contact exchange automatically"); exchange can only be undone for customers without other roles and for homes / clinics.
  • Signing: digital signature (document then viewable via DMS/PDF icon) or printout covering all granted scopes. After printing a prompt asks whether it was just printed or already returned signed; status updates accordingly. Printing from hit lists or Reports records the print date as hand-out date automatically. If only adjusted (not handed out), save and close.
  • Withdrawal: set "consent not granted" and save → (outside sales transactions) the system offers to lock the contact: Yes = lock now; No = lock later; Cancel = discard. Recommended: regularly query customers without consent in Reports (predefined query "Einwilligungserklärung") and lock them in bulk.
  • Settings warning: "check data-protection settings" appears when at least one data-protection parameter is at its maximum value and/or no data-protection officer is recorded in company master.

4.17 Family details, family suggestions and guardianship [GENERIC household grouping]​

  • Family details dialog: assign members, check consent of every member (marker per member without signed consent; click to process), define the contact person (first member by default; "set contact person"), choose invoicing mode:
    • per family member (each gets own invoice);
    • per family member with collective slip to the contact person (separate invoices bundled under a collective slip when several are created in one run; each recipient's preferred channel respected);
    • total to the contact person (one joint invoice; contact person is the debtor).
  • Customers holding the doctor role are meant for practice supplies and are excluded from joint family invoicing: info marker "doctors are not considered"; warning if the doctor is the contact person (joint invoicing unusable).
  • Guardian markers (is guardian of / has a guardian); click shows the guardian's contact data and wards.
  • Migration: families previously modelled only by a shared customer card number can be converted into real families with one function.
  • At the till or in invoicing, when switching the customer in a sale, family members are offered automatically.
  • Family suggestions (Familien vorschlagen) (licence for the customer add-on): proposes possible families from matches in existing master data (criteria not documented); each proposal expandable; system proposes a contact person (changeable); user ticks reviewed proposals and creates the families. Advice: check and consult the customers.

4.18 Classifications (Klassifikationen) [GENERIC tagging / segmentation]​

  • Lists the customer's classifications: name, description, kind (roles it applies to). Only classifications for customers or for all roles can be assigned.
  • Assign via picker (name, description, exchange marker, number of assigned contacts); the classification administration module can be opened from the picker. Assigning / removing is also possible from that module.
  • Delete: after a notice the classification is deleted and removed from all contacts still assigned (see open questions).
  • All data exchanged in the group.

4.19 Risk management and CAVE profile (Risikomanagement) [GENERIC: patient risk profile driving contraindication checks; the code catalogue is DE-specific data]​

4.19.1 Page structure​

  • Three tabs: documented interactions, documented CAVE risks, CAVE data. The same CAVE data appear read-only in the MM module under "objective impression".

4.19.2 CAVE data tab​

  • CAVE check flag: when set, every dispensing for this contact is automatically checked for contraindications against the profile, plus a cross-reaction check.
  • Extended CAVE check: additionally uses body weight and creatinine / GFR.
  • Values: age (only if DOB stored), sex (only if stored), weight + date of last update (system-maintained), creatinine + date (entering creatinine converts it into GFR), GFR.
  • Activating the CAVE check without age and sex prompts for date of birth and sex.
  • Allergy list (code, designation incl. via which medicine/substance assigned, edited on) and disease list (code, designation, edited on, status, end date); add via assignment functions; delete with confirmation.
  • When three or more allergies are stored, the system asks whether to add the disease characteristic "allergic diathesis"; Yes adds it automatically (one page says "more than three").
  • Disease status: static / temporary (end date, default today + 6 months) / deactivated (stores today as end date; kept on file but ignored by the check).

4.19.3 Assign allergy (Allergie zu Kontakt zuordnen)​

  • Search modes: by allergy name (with option "only environmental allergies", available only in this mode); by finished medicine that triggers the allergy; by substance (default).
  • Hit lists: by name — stored marker, code, designation, synonym flag, preferred term, short definition; by medicine — stored marker, product name + manufacturer + dosage form, marker whether it can serve as CAVE criterion "allergy"; by substance — stored marker, substance name, synonym, homeopathic and anthroposophic flags, usable-as-criterion marker. Synonyms can be hidden (otherwise one hit appears under several names).
  • Definition used: "allergy" = restrictions on using a medicine that stem from a hypersensitivity to a substance, immunological (allergic) or non-immunological (pseudo-allergic). Cross-reaction = sensitisation to a substance caused earlier by a chemically different substance.
  • After choosing a substance: all allergies linked to it are listed pre-ticked; untick non-applicable ones; details of the selected allergy shown; confirm stores the ticked ones.
  • After choosing a finished medicine: shows medicine and its ingredients; per ingredient: already-stored marker, checkbox (pre-ticked where the ingredient has documented allergies; disabled where it has none), name, "has allergies" and "info available" markers; lower list shows the allergies of the selected ingredient; an info function pages through the definitions of that ingredient's allergies.

4.19.4 Assign disease (Erkrankung zu Kontakt zuordnen)​

  • Search by term; hit list: stored marker, code, designation (sex-specific), hierarchy marker H (main term — fairly unspecific condition recognisable from the medication), F (subordinate term — more specific, learned by asking patient/doctor, avoids false alarms), blank (single term — outside the hierarchy, already precise enough), synonym, preferred term, definition text.
  • Choosing a main term opens a follow-up list of its subordinate terms; the user stores the correct subordinate term.
  • Inputs: status static or temporary; edited on; end date (temporary: default today + 6 months).
  • Scope of "disease": illnesses, chronic conditions, past events (stroke, embolism), anatomical changes, age ranges (menopause, man of reproductive age), abnormal lab values, special susceptibilities, non-drug treatments (dialysis), circumstances and behaviours (smoker, pregnancy, competitive athlete).

4.19.5 Review of expired temporary diseases (Krankheitsstatus prüfen) [GENERIC]​

  • Trigger: among other moments, when the contact details are opened and a temporary disease's end date has passed. A dialog lists them (code, designation, edited on, status, end date).
  • Per disease: set static (no end date needed); keep temporary (a new future end date is mandatory); set deactivated (kept on file but no longer checked; no end date needed).

4.19.6 Inactivated CAVE patient characteristics [DE-SPECIFIC data source; idea: handling retired codes in a maintained clinical catalogue with successor references]​

  • The drug-data provider maintains the characteristic catalogue and can inactivate entries; inactivated entries are no longer checked. The system notifies automatically when a customer has inactivated characteristics and lists them: code, preferred designation, disease status (empty for allergies), end date (temporary diseases), reference flag (alternatives offered). Info area and full-definition function.
  • With references: shows the inactivated item, the provider's explanation and a list of alternative characteristics (already-stored marker; checkbox, not tickable if already stored; code; designation; status; end date); "mark all"; checkbox "adopt and mark as processed". OK removes the inactivated item from the CAVE data, adds all ticked alternatives and marks the item processed (no further notices); returns to the list if more remain. With a single proposed alternative: tick "adopt and mark processed" to swap; if not adopting, the user must remove the item manually in CAVE data and choose an alternative.
  • Without reference: shows the item, the explanation and a "no reference" notice; checkbox "mark as processed"; function "edit CAVE data" jumps to the CAVE data tab for manual update.

4.19.7 Documented risks [GENERIC]​

  • CAVE documentation tab: application risks the user consciously accepted in sales, each with a reason and optional expiry date of the suppression period (e.g. tied to a temporary disease); detail tab shows the documentation. Expired entries are grey and listed last. "Edit documentation" changes or re-activates an entry.
  • Interaction documentation tab: same pattern for documented interactions.

4.20 Medication management page, medication plan page and medication change history​

4.20.1 Medication management page (Medikationsmanagement) [GENERIC enrolment record; DE: pharmaceutical services billing, BMP/eMP]​

  • Purpose: enrol the customer in MM; switch on automatic offering of an updated medication plan (BMP / eMP); store care-relevant data; manage pharmaceutical services; show counselling state. "Extended functions" opens the MM module (paid add-on).
  • General: MM participation + since; BMP/eMP option (after sales that changed medication data, printing the plan is offered automatically); sex and DOB.
  • Activities: data capture complete; last counselling date; next planned counselling; count of open drug-related problems.
  • Treating doctors: add doctor contacts via search (specialty copied if stored); family-doctor flag per row; remark; remove. A family doctor is required for MM participation. Doctor contact data are exchanged in the group.
  • Pharmaceutical services list [DE-SPECIFIC; idea: billable clinical services with contract, result and billing evidence]: kind, date, contract (printed / digitally signed in DMS / PDF without DMS), results (DMS/PDF marker when results are scanned or saved from the polymedication review tool, or a simple "rendered" tick), billing voucher (marker once an e-prescription billing voucher was generated). The row turns grey (complete) only when all columns are filled. Actions: hand over to till for billing; open the polymedication review tool; scan documents; add; refresh; delete.
  • Enrolment: tick MM and save; if consent for care-relevant data is missing, a notice asks to obtain it but enrolment proceeds. Bulk: mass processing in Reports activates / deactivates MM and with it the BMP option.
  • Care-home assignment functions (open home details, assign, change, delete with confirmation) — see homes chapter.
  • MM activation is NOT exchanged between branches; MM data are not synchronised even if enrolled in several.

4.20.2 Medication plan page (Medikationsplan)​

  • Shows the customer's current plan: which medication courses are current and which inactive; offers the main functions of the MM medication overview.

4.20.3 Change history of medication-relevant data [GENERIC audit trail for the medication record]​

  • Records all changes to MM data, including blister management. Opened from the medication plan page or MM "objective impression" (all courses of the customer), from course details (one course), or from blister release history (extra columns resident, released by, long-term marker).
  • Filters: from/to (default last 14 days); category: dosing, prescription request, stock, blistering, medication stop, batch/expiry, course, federal medication plan; "with comments".
  • Columns: date+time; reference (course/article); change type (e.g. deletion, split, sample entry, correction, sale, new stop, changed stop); old value; new value; difference (stock); changed by; markers (newly created BMP attached as PDF; blister change undone later / release done).
  • Stock corrections happen in course details: correct remaining stock; "do not use remaining stock" = discontinue at medication level — the dispensing remainder becomes 0.00 and no longer counts toward the course's total stock; reversible.

4.21 Federal medication plan read-in and comparison (Bundesmedikationsplan) [DE-SPECIFIC; idea: standardised machine-readable medication plan exchanged between doctor and pharmacy, reconciled against the pharmacy's own record]​

4.21.1 Background​

  • Since late 2016 doctors must issue the standardised plan to entitled patients; a patient taking at least three prescribed medicines has a legal claim to it. It lists medicines with active ingredient, form and strength, plus patient parameters, and carries a 2D code. The same logic applies to the electronic plan (eMP).
  • The code is scanned with the prescription scanner (one scanner model unsupported) at the till or in Contacts.

4.21.2 Read-in flow​

  1. Scan the code; it is validated. A multi-page plan requires all pages to be scanned, otherwise a notice.
  2. Customer matching:
    • unique match = surname, first name, DOB and insured number identical → no take-over dialog;
    • exists, already in MM, identical → comparison opens directly;
    • exists, not in MM, identical → MM activated automatically, consent print preview shown;
    • exists, data differ → "take over customer data" dialog;
    • exists but not yet saved and/or no doctor stored → doctor selection;
    • unknown → create the customer directly in the take-over dialog, MM activated automatically.
  3. MM and CAVE check are activated automatically if not yet active; MM requires consent for care-relevant data, printable during the flow. (Within the telematics infrastructure, MM is available licence-free with reduced scope for reading/editing plans.)
  4. Comparison window: edit; import plan data into MM; write medication of the current sale from MM onto the plan.
  • Take-over dialog: offers all customer data from the plan for import. By default offers a consent declaration — for walk-ins / new customers consent to personal AND care-related data; for stored customers consent to care-relevant data. Option "print federal medication plan": after a sale with changes, printing the updated plan is offered automatically (same as the option on the MM page).

4.21.3 Customer parameters​

  • Pharmaceutically relevant values printed on the plan, agreed with the customer; editable from the comparison window and from the plan print preview.
  • Per field colour: green = match; yellow = no value in the customer file; red = differs. Take individual values, take all filled values at once, or type into the customer-file column (only manual entry is possible from the print window).
  • Allergies on the plan are free text and cannot be imported; the user selects allergies by substance; they are then stored in CAVE data. A delete function clears the allergy field.
  • Per parameter a print toggle; preview shows the truncated (space-limited, "…") real output; order fixed by the specification.

4.21.4 Comparison window​

  • Header: notices on differences; name, first name, DOB, insured number; creator (pharmacy or doctor — doctor data can be reconciled); customer parameters (yellow = not reconciled); move lines up/down (headings, text lines, prescriptions).
  • Per line: take-over checkbox (only for new lines, initially ticked); match status — identical / new for the system (on the plan, or added here as sample entry) / only in the system / in both but differing (yellow); active ingredient (> 3 ingredients shown as combination product), strength, form, dosing morning/noon/evening/night (inline editable), unit, notes (only deviations shown; editable), reason (editable), stop marker (shown only if plan and system agree or the system's discontinuation began no more than 3 months ago, or for pauses; tooltip lists all stops), info icon (duplicate medication, CAVE risks, interactions), print toggle, open course details / sample-entry window / compounded-preparation marker, details of differences.
  • Switching between standard and as-needed / free / complex dosing is done in course details.
  • Lines the doctor's software listed several times become free-text lines at the top (PZN, ingredient, name, strength, form, dosing, notes) — usually complex dosings to be combined in course details; the duplicates should then be deleted.
  • Sample entry: turn a free-text line into a medication article; the sample replaces the free-text line. Booking a sample here is only possible if the plan does not already contain an article with the same active-ingredient key; otherwise clarify with the doctor.
  • Medication stop create / edit jumps to the MM stop page.
  • Pharmacy-own articles (own article numbers): can carry deviating free texts (ingredient, strength) stored with the number in the code so they can be read back (the own number is known only within the pharmacy / group); not written to the article master; shown in red.
  • Auto-generated notes: the system generates notes for therapy start, end of supply range and stops within the next 28 days; on re-reading these are recognised and filtered so only real differences show. Tooltip line 1 = actual note (may be empty); line 2 = generated + actual = what is printed.
  • Take-over rules: checkbox only for new lines and stays after editing; once a changed line is saved (e.g. course details entered or free-text booked as sample) it is always booked and the checkbox disappears; differing lines (already in MM) are taken over by default without checkbox.
  • Release & take over checks: a doctor is stored (else doctor selection); all required data present — unknown current stock or missing long-term flag opens "complete missing data"; formal plan checks: last printable line must not be a heading; two headings must not follow each other (also if lines between are not printed); a heading needs at least one character. Violations → notice, fix, save.
  • Booking of courses by stock: stock empty → no article booked into the course (course without article created if none exists); stock 0 → sample with stock 0 / new course with article stock 0; stock > 0 → sample with stock x / new course with article stock x. Samples created in MM also appear in article details and the sales data page; batch and expiry of auto-created samples must be maintained manually.
  • Afterwards customer-related interactions and application risks are shown; if the plan was scanned at the till, a prompt offers to start a sale for the customer.
  • Deviating free texts: the specification allows pharmaceutical statements that deviate from the drug database per medication line (vendor recommends keeping database values). Dialog lists all ingredients, editable; applies to all medicines with the same PZN in the course; appears in print window, printout and next read-in; "reset to standard" restores database values; shown in red.
  • Complete missing data: lists courses without long-term flag and courses taken over from the comparison (incl. those with a pause or discontinuation) without long-term flag. Tick long-term vs as-needed; enter current stock if known (basis for supply-range calculation). An as-needed medication with stock 0 does not appear on the new printout.
  • New lines (comparison and print window): intermediate heading (own text or predefined; editable any time); free-text line (general note); additional line (bound to the marked medication / compound and moves with it; moved alone it becomes a free-text line and loses the binding); compounded-preparation free-text line. Free-text lines can later be replaced by a sample entry.

4.22 Sales data page (Verkaufsdaten) [GENERIC purchase history]​

4.22.1 Sales tab (Abverkäufe)​

  • Evaluates all sales in a period (default 1 January of the current year to today; default via parameter "sales data period"; changeable by filter); article filter by name or article number. Not-yet-billed advance deliveries are excluded from totals.
  • Totals: customer-paid; revenue; normal (cash) sales; private prescriptions; green prescriptions (Grünes Rezept); co-payment; extra costs; prescription debt (value of packs whose prescription is still missing or stored as advance delivery, at the pack value valid at entry time).
  • Lines: sale type (normal, statutory prescription, private prescription, green prescription, narcotics prescription, care aid; cancelled variants; sample article; advance delivery; "F" = prescription sale with missing prescription); date (start of subtotal); markers split pack / blistered / split-blistered; special code or e-prescription billing note (tooltip); designation; form; unit; quantity (advance deliveries: unbilled quantity); price; co-payment + extra cost; customer total; open back-order; dispensing branch (blank = own; sample articles from other branches not shown). Sortable. For invoiced orders (also back-dated) a tooltip shows entry and order date. Details: co-payment, extra costs, article number, manufacturer.
  • Anonymise sales data: under the sensitive-data permission concept a per-customer checkbox hides the sales history; requires right "anonymise sales data". A user who sees the box ticked but no sales lacks that right.
  • Functions: open sales administration for the customer (date range and article carried over); drug-database info for selected lines (multi-select); risk check on selected lines (choose check type; e.g. customer phones to ask whether yesterday's purchase fits; look-back for interaction checks = till parameter "number of days for the check"); filter period; shopping cart / order (reorder from history without a sale; cart/back-order dialog with "procure for pickup" option, customer prefilled, flagged as pickup); telephone reservation; hand over to till; show prescription image.

4.22.2 Hand an article from history to a sale or quote​

  • Start from a running sale, a quote (Kostenvoranschlag) or the Contacts module. In a sale: assign the customer, open the sales data (customer info icon, or pressing the customer key again → view customer details / remove assignment / change customer), select article(s), then:
    • "hand over to till" (customer present) — article becomes a new line in the sale or quote;
    • "telephone reservation" — creates a sale with phone reservation for the marked articles or adds them to the current sale; the whole sale becomes reserved; no pickup slip is printed because the customer is absent.

4.22.3 Book a medication from history (Medikation einbuchen)​

  • For an MM customer, previously bought articles (medicines or not) can be added to MM afterwards — e.g. purchases before enrolment (otherwise no range calculation) or when medication detail entry was cancelled at the till.
  • Preconditions: MM licence; customer enrolled; all medicines except veterinary ones count, including those outside the main medicine class (notably homeopathics).
  • A medication = use of an article over time with fixed dosing, possibly split into dosing sections separated by pauses or differing doses.
  • Flow: mark article → "book medication" → course details. For a follow-up prescription with the same article / finished-medicine number as before, the dialog is skipped when parameter "hide medication details for the same medication" is on, and a success notice is shown.

4.22.4 Sample articles (Musterartikel erfassen) [GENERIC: externally obtained medication recorded in patient history]​

  • Records articles the customer did not buy here (e.g. from the doctor) so that CAVE, interaction checks and MM are complete.
  • From the sales data page: medicines or other articles, always with quantity ≥ 1. From MM (medication plan, medication overview, course details): medicines only; course details and/or dosing may be kept (dosing only without course details: quantity 0).
  • Fields: date received (default now); article (form, unit, number, partial quantity shown); packs; from MM only: partial quantity on hand (default full pack; e.g. "brown bag" review of opened packs), batch, expiry; prescribing doctor (optional; shown as prescriber in MM); checkbox "reset this course's total stock to 0 at this time and continue with the entered partial quantity" (only in MM and only if a course with stock exists).
  • After entry: interaction and CAVE checks against the customer's other articles, results shown; for MM customers and medicines, course details open; if long-term flag missing, a prompt explains that long-term medications stay on the printed plan after the range ends while as-needed ones disappear.
  • Counted in CAVE and interaction checks as if dispensed by the pharmacy or a connected branch; not listed on co-payment lists. Deletable from the sales list with confirmation.

4.22.5 Flat-rates tab (Pauschalen) [DE-SPECIFIC; idea: aids supplied under a periodic flat-rate reimbursement with margin tracking]​

  • All aid dispensings billed on flat rates, grouped per flat rate and month (also shown ungrouped on the sales tab). Period default as above. Revenue = gross of all billed flat rates in the period.
  • Columns: expandable month rows → articles; designation; dispensing date; flat-rate billing price; unit; quantity (advance deliveries: unbilled); purchase price gross; dispensing price from the flat-rate calculation; yield = billing price − dispensing price of the aids.
  • Details: per flat rate — co-payment (month total), difference amount (monthly sum; flat rates may cover more than one month), remaining term, remaining amount = billing price − sum of dispensings; per article — number, manufacturer.
  • Hand over to till only for an article (not a flat rate): goes into a normal sale; to record it as a follow-up dispensing, create a prescription subtotal and drag the article into it, which opens the aids-contract database to choose the flat rate and take its billing price.

4.22.6 Care-aids tab (Pflegehilfsmittel) [DE-SPECIFIC; idea: monthly-capped consumable care supplies billed to the care insurer]​

  • Dispensings of consumable care aids grouped by month and product group; gross revenue for the period.
  • Columns: designation; date; purchase price gross (average purchase price + VAT); unit; quantity; count; billing price with the payer (gross); yield = sum of dispensings − gross purchase prices.
  • Details: per billing month — co-payment, own share for the civil-servant aid scheme, difference amount; per product group — contractual maximum price, product group; per article — co-payment, own share, number, manufacturer.
  • Hand over to till: month, product group or articles.

4.23 Customer-app access data (Zugangsdaten) [GENERIC: patient app account linked to the customer record]​

  • Visible depending on the licensed connect product (paid add-on); shows contact data from master data.
  • Active (enables app / web access; set automatically after the first successful simplified connect); "connect" (customer scans a QR code to download the app and links to the pharmacy with a verification code); registration date; last login; last order (app/web); login ID or e-mail (system login ID until the customer logs in, then the customer's e-mail); password ("assign password" generates a one-time password, printable exactly once right after assignment; always displayed as 10 asterisks); login code (QR for download + simplified connect; system-assigned credentials handed over or printed; must be changed at first login); "also registered in" (other group pharmacies, only with the cross-pharmacy feature).
  • Deactivating and reactivating access requires the customer to reinstall the app before reconnecting.
  • Data are available within the group.

4.24 Change history of contact data (Änderungshistorie) [GENERIC audit trail]​

  • Field-level history for customers (incl. walk-ins) and also care homes, clinics, doctors, suppliers, employees.
  • Permission: right "Contacts general: show change history" or role Leiter; plus workstation protection under the sensitive-data concept.
  • Filters: date from/to; area (each contact-details page with at least one historised field, plus "information texts" = info texts entered via the info function, excluding notes); category (group on the page); property (single field).
  • Table: original value, new value, change date, operator. With the blistering licence also all changes to blister participation. Printable (preview, save as PDF).

4.25 Walk-in customers (Laufkunden) [GENERIC: temporary customer record for a one-off transaction that needs an identity]​

  • Use: capture a person's data temporarily when an article must be ordered for them, credit granted, or a pharmaceutical service / vaccination provided — without creating a permanent customer.
  • Retention: kept until the related process (pickup, credit, invoicing) is finally closed AND the configured interval elapsed; parameters "lock periods for walk-ins" (automatic lock after N) and "deletion periods for locked walk-ins" (final deletion relative to the lock date). While stored and not locked they are searchable.
  • Search: customer search shows two tabs, customer and walk-in, and searches both. Parameter "show customers including walk-ins" = Yes removes the separate tab; walk-ins appear in the customer tab with an icon.
  • Details: reduced set of pages/fields; master data shows role walk-in; editable; change history available; open items available.
  • Creation from prescription data (prescription scan or e-prescription dialog): "add" → "take over customer data" → option "as walk-in customer" (or as customer). Consent defaults to "no consent declaration" and can be recorded later on the walk-in's master data. When the walk-in signs consent, the role changes automatically to customer (person); if consent is only printed / handed out the status shows pending (yellow). Parameter "automatic walk-in creation in prescription scan" creates walk-ins automatically from prescription data. The insured number is validated: invalid format → warning and the record cannot be saved until corrected.
  • Creation in a sale (till or invoicing): customer key → contact picker → quick creation, preselected with role walk-in; minimum = name; first letters of title, first name (domestic contacts only), name, street, city and country are capitalised automatically; OK creates and assigns to the sale.

4.26 Promoting walk-ins and address-book entries (Kontaktrolle ändern) [GENERIC]​

  • Walk-in → customer: from the hit list or contact details (also during a sale via customer details → master data). Choose customer (person) or customer (company). On conversion the contact receives the default customer discount model (unless it already had one) and the invoicing model flagged as default for customers. If the missing-consent parameter is on, the consent dialog opens. In groups the master-data window opens so the user decides via "exchange contact" whether the role change applies in all branches (default from "allow contact exchange automatically"); after saving the consent dialog appears per setting.
  • Address-book entry → full contact: select entry, "change contact role", choose ANY available role (customer, supplier, payer, …), confirm. If it becomes a person customer and data-protection settings require it, the consent dialog opens.

4.27 Duplicates: search and merge (Dubletten) [GENERIC]​

  • Why: customers get created more than once, especially after contact exchange across branches; also to merge walk-in and customer records in one pharmacy. Only after merging are all of a customer's sales across branches in one record.
  • Roles that can be merged: customer, doctor, care home, employee, supplier. Merging employees needs right "edit user accounts and assign rights" or role Leiter. Person and company contacts can never be merged together. (Duplicate processing also exists for articles and invoicing models elsewhere.)
  • Recommended approach for large volumes: stage the work — filter by role (e.g. persons only), go alphabetically or by identical surname + first name; afterwards review the group visibility restriction.
  • Search ("Dubletten bearbeiten" → select duplicates): needs workstation/user permission if the sensitive-data concept is on. Criteria: name pattern (surname, optionally ", first name", e.g. muster*, ma*); match attributes, all ON by default and individually switchable: surname, first name, postcode, street, date of birth — enabled attributes are AND-combined (hits must share all of them). Results only if at least two hits. Details of a marked hit can be opened; an icon shows customer-app registration (if licensed).
  • Merge wizard (Kontakte mischen): mark up to 8 duplicates → step 1 master data, then role-specific pages (customer, doctor and/or care-home data) → "merge". A NEW contact is created and the sources are deleted; the new one carries all sales data, advance deliveries, back-order deliveries etc. of the sources. Irreversible. The merged contact is visible immediately in all branches; the old ones disappear group-wide.
    • Per attribute row: status (all values identical or manual choice made / optional attribute without value / optional attribute differs or prefill was deleted / mandatory attribute differs); one column per source contact headed by pharmacy short code; "selection" column. Selection is prefilled when only one source has a value or all agree; empty when they differ → pick a source value, type a new value, or clear the manual choice.
    • Family doctor, payer and customer number cannot be typed freely (must be picked / newly assigned). Only centrally maintained payers are offered; a payer created locally by one branch is not shown.
    • Taken over without choice: from the FIRST (leftmost) contact — delivery, invoice and default address; bank name, bank code, account number. From ALL sources — customer card numbers; allergies, diseases and other patient characteristics; family membership and contact-person role; guardian / ward relations.
    • Refused when: another workstation is editing contacts (change, duplicate processing, deletion) at the same time; sources belong to different families; a family would be left with one member and would have to be dissolved; two or more sources have different legal guardians; a guardian and their ward are to be merged together.
    • Guardianship: if a source has a guardian the new contact inherits it; if a source is a guardian, the new contact inherits the wards.
  • What: shares contact data AND the contact's sales data among the pharmacies of the group. Benefits: no re-entry, consistent data, see purchases in other branches, cross-branch interaction checks, group-wide discount models.
  • Prerequisite: exchange enabled centrally for the group or between specific pharmacies.
  • Per customer: checkbox "exchange contact" on master data / in the consent dialog. Set only with the customer's consent and only if the contact has no other roles — or for care homes, nursing services, clinics. Activating it for a care home activates it for all its residents, including future ones. Person customers start with exchange off (parameter "allow contact exchange automatically" changes this default). A change always affects the whole contact with all roles.
  • Sub-groups (Teilverbünde), if configured centrally: (1) visibility setting (Contacts > branch & partner > visibility): with permission, adopt the group-wide visibility for exchanged contacts of other pharmacies or deviate (e.g. only certain pharmacies); (2) a dropdown next to the checkbox chooses whole group vs sub-group; (3) a Reports query sets exchange in bulk.
  • Not exchanged: MM activation and MM data; preferred tour, robot chute and long-term-care insurance data; price scheme. Everything else noted per page is exchanged (master data, addresses, bank accounts, specific data, discounts/coupons, classifications, consent, app access, address-book entries).
  • Deactivation (only person customers without other roles): untick per customer, or in bulk via a Reports query "contact exchange = yes" → process result → set.
  • After switching exchange on, running duplicate processing is recommended.

5. Workflows​

5.1 Create a regular customer​

  1. In Contacts (or from a picker), create a contact with role customer; choose type person or company (only if no other roles).
  2. Enter name (only mandatory field), first name, DOB, sex, default address (postcode/city assistance; optional prefill with the pharmacy's own postcode/city) and communication data.
  3. Customer number is assigned automatically (next free number; per-pharmacy ranges if start values were set).
  4. On save, if no consent is on file and the missing-consent notice parameter is on, the consent dialog opens: record scopes (storage, advertising channels, care-relevant data, exchange), print or capture a digital signature, record hand-out/signature status.
  5. Optionally: specific data (payment preference, card, insurance, family/guardian), invoicing permission and Faktura terms, bank account + SEPA mandate, discount model, classifications, CAVE data, MM enrolment.
  6. In a group: decide "exchange contact" (only with consent; default per parameter).

5.2 Find and open a customer​

  1. Type the name (wildcards / "surname, first name"), or scan the customer card, or read the insurance card.
  2. Insurance card with differing data → reconcile customer data first.
  3. No hit in the role → accept the offer to search all roles; still nothing → phonetic search or advanced search (status inactive/deceased, locked, former names/numbers).
  4. Inactive/deceased hits → optionally reactivate; locked hits need the locked-data right.
  5. Open contact details; system checks expired temporary diseases and inactivated CAVE characteristics and prompts if needed.

5.3 Walk-in customer lifecycle​

  1. Create: from prescription scan / e-prescription ("take over customer data" → as walk-in; or automatically per parameter) or at the till via quick creation (name minimum).
  2. Use for the order / credit / service; the walk-in is searchable in the walk-in tab.
  3. Either: walk-in signs consent → role becomes customer (person) automatically; or user changes role to customer (person/company) → default discount model and default invoicing model assigned, consent dialog, exchange decision in groups.
  4. Otherwise: process closed → automatic lock after the lock period → final deletion after the deletion period.

5.4 Find and merge duplicates​

  1. Ensure no other workstation is editing contacts.
  2. Open duplicate processing; enter a name pattern and choose match attributes (surname, first name, postcode, street, DOB — AND-combined).
  3. From the hit list (≥ 2 hits) mark up to 8 contacts of the same kind (not person + company).
  4. Wizard: master data → role pages; resolve every row (pick a source value, type a new value; family doctor, payer and customer number must be picked/assigned).
  5. Merge → new contact created, sources deleted group-wide; addresses and bank data from the first contact; card numbers, CAVE characteristics, family and guardian relations from all; all sales and open processes combined. Irreversible.
  6. If refused (different families, family would dissolve, conflicting guardians, guardian + ward) → resolve the relations first.

5.5 Read a federal medication plan​

  1. Scan all pages of the plan's code (till or Contacts).
  2. Match or create the customer (take-over dialog; consent offer; option to auto-offer plan printing).
  3. MM and CAVE check are auto-activated if needed; doctor selection if none stored.
  4. Reconcile customer parameters (green/yellow/red); choose allergies by substance.
  5. In the comparison, review each line; edit dosing / notes / reasons; convert free-text lines into sample entries; tidy duplicates; set print toggles.
  6. Release & take over → complete missing data (long-term vs as-needed, current stock) → formal heading checks → courses booked by stock rules.
  7. Review displayed interactions / CAVE risks; optionally start a sale for the customer.

5.6 Maintain the CAVE profile​

  1. Risk management → CAVE data → switch on CAVE check (enter DOB/sex if prompted); optionally extended check with weight and creatinine (→ GFR).
  2. Assign allergies by substance, finished medicine or allergy name; untick non-applicable allergies; at three or more allergies accept "allergic diathesis".
  3. Assign diseases; for a main term pick the subordinate term; set static or temporary (default end today + 6 months).
  4. When prompted, review expired temporary diseases (static / new end date / deactivate) and process inactivated characteristics (adopt alternatives or edit manually).

5.7 Set up direct debit for an invoice customer​

  1. Master data: grant invoicing permission.
  2. Faktura page: payment method direct debit (or via invoicing model).
  3. Payment transactions → accounts: add account (IBAN/BIC; generate IBAN from legacy data if needed); flag as direct-debit account.
  4. Create SEPA mandate (pharmacy creditor ID must exist): reference, granting date, first/recurring; digital signature or print; save.
  5. Optionally choose the pharmacy account to collect into ("direct debit to company account").
  1. Consent dialog → "consent not granted" → save.
  2. Outside a sale the system offers to lock now / later / cancel.
  3. Periodically: Reports query on missing consent → lock in bulk.

5.9 Use the sales history at the counter​

  1. In a sale assign the customer and open sales data (or open from Contacts).
  2. Select articles → hand over to till (or quote) / telephone reservation / reorder into cart as pickup / risk check / drug info.
  3. For MM customers: book a past purchase as medication; record sample articles for medicines obtained elsewhere.

6. Business rules and calculations​

Identity and search

  • Name is the only mandatory field of a contact.
  • Standard search excludes inactive, deceased and (with the permission concept) locked contacts; advanced search can include them; locked contacts can never be transferred into other modules.
  • Wildcards: implicit trailing *; leading *; ? = exactly one character; "surname, first name".
  • Customer numbers: next free after the last assigned; unique across exchanging pharmacies; manual start values create per-pharmacy ranges.
  • A customer card number may belong to several customers (warning on save; selection on scan).
  • Person ↔ company switch only without other roles and without MM; person → company deletes consent.

Addresses and communication

  • At most one default, one invoice, one delivery address; default can never be deleted; deleting invoice/delivery addresses requires confirmation.
  • Referenced addresses synchronise from the source until "use locally"; in groups the link survives only if the source contact is itself exchanged at the time of referencing.
  • City suggestions: own-contact matches by frequency first; general database only if fewer than 10 own matches; max 50.
  • E-mail invoices fall back to printout when no default/invoice e-mail exists; password-protected addresses get encrypted PDFs.

Invoicing and payment

  • Account sales require invoicing permission (can be granted at the moment of invoicing). Auto-granted for care homes, units and residents whose address equals the home's.
  • Faktura tabs are read-only while an invoicing model is assigned; residents/wards inherit from the superior unit unless own settings.
  • Separate-invoice residents never get receipts and are not invoiced by the home's run unless named or the "additionally create separate invoices" option is used.
  • Invoices with total 0 and auto-print off → status Intern.
  • Bank accounts: exactly one default and one direct-debit account per contact; invalid BIC allowed with warning.
  • Collection account resolution: 1. "direct debit to company account" on the customer; 2. alternative pharmacy account of the invoicing model / Faktura settings; 3. company-master default account.
  • Debtor account (DATEV): 10000–69999, up to 9 digits, unless agreed otherwise with the tax adviser.
  • SEPA: no one-off mandates; creditor ID and valid IBAN + holder required; re-submitting a returned debit as "last direct debit" revokes the mandate at the next export.
  • Preferred payment method overrides workstation presets; conflicting preferences in one sale → no prefill. Pickups must be settled at the till, never via invoicing.
  • VAT-exempt modes require the professional invoicing licence; ship exemption also needs type company; intra-EU also needs a VAT ID.

Insurance (DE)

  • Insurance status default from age at creation; minors get "0 (K) – child prescription" (DOB required before first save).
  • With "update insurance status automatically" on: for active customers created or whose status was changed, at the 18th birthday statuses none, 0 and "0 (K)" are replaced by "1 – co-payment liable / extra-cost liable" unless a co-payment exemption is entered; a manual change after the 18th birthday stops auto-updates.
  • Exemption: entering a start date proposes the end as 31 December of the current year; on save, status none or "1" becomes "0 – co-payment free / extra-cost liable" when a valid exemption is entered; expired exemption → notice in sales.
  • Insured number is plausibility-checked (warning; walk-ins with invalid format cannot be saved).
  • Care-aid approval state: granted if approval periods for product groups 51 and 54 exist; requested if payer or period missing for one; none if neither.

Clinical

  • CAVE check needs age and sex (prompted).
  • ≥ 3 allergies → offer to add "allergic diathesis".
  • Temporary disease default end = today + 6 months; deactivating sets end = today; expired temporary diseases must be re-classified (keeping temporary requires a future end date).
  • Inactivated catalogue entries are not checked; adopting alternatives removes the old entry.
  • MM requires a family doctor; consent for care-relevant data is requested but not enforced.
  • BMP: unique customer match on surname + first name + DOB + insured number; stops shown only if plan and system agree or discontinuation ≤ 3 months old; auto-generated notes cover the next 28 days; > 3 ingredients → "combination product"; last printable line not a heading, no two consecutive headings, headings non-empty; as-needed with stock 0 not printed; course booking by stock (empty / 0 / > 0) as in 4.21.4; samples only if no plan article with the same active-ingredient key.
  • Sample articles: quantity ≥ 1 from sales data; 0 allowed from MM (dosing only); included in CAVE and interaction checks; not on co-payment lists.
  • Pharmaceutical service row complete only when all columns are filled.

Loyalty and discounts

  • Bonus redemptions consume oldest awards first (FIFO); expiry preview default 30 days; manual correction expiry defaults to the system's expiry period.
  • "Prefer model price" uses the model price regardless of whether it is cheaper; loss-making discounts trigger price correction.

Sales data

  • Default period 1 Jan of current year → today; unbilled advance deliveries excluded from totals.
  • Prescription debt = value (at entry time) of packs with missing prescriptions or stored as advance deliveries.
  • Flat-rate yield = flat-rate billing price − dispensing price of aids; remaining amount = billing price − sum of dispensings.
  • Care-aid yield = sum of dispensings − gross purchase prices; purchase price gross = average purchase price + VAT.

Duplicates, families, exchange

  • Merge: up to 8 contacts; same type; AND-combined match attributes; at least two hits; exclusive lock on contact editing; first contact wins addresses and legacy bank fields; all sources contribute cards, CAVE data, family and guardian relations; refusals as in 4.27; irreversible; new record, sources deleted group-wide.
  • Removing a family member leaving one member deletes the family; doctor customers excluded from joint family invoicing.
  • Exchange only with consent; activating for a care home includes all current and future residents; deactivation only for person customers without other roles (and for homes/clinics per consent page); MM data never exchanged.
  • Walk-ins: lock after the lock period once the process is closed; delete after the deletion period from lock date; signing consent converts to customer.

7. Configuration and settings​

ParameterScopeEffectDefault
Automatik (phonetic search)System settings Contacts, page phonetic searchMakes phonetic search the default searchStandard search
Kunde inkl. Laufkunden anzeigen (show customers incl. walk-ins)Contacts settingsYes = walk-ins listed in customer tab with icon, no separate tabSeparate tabs (implied)
Sperrfristen für Laufkunden (walk-in lock periods)Contacts settingsTime after process completion until a walk-in is locked automaticallyNot stated
Löschfristen für gesperrte Laufkunden (deletion periods)Contacts settingsTime from lock until final deletionNot stated
Automatische Laufkundenanlage im RezeptscanPrescription scan settingsCreate walk-ins automatically from scanned prescription dataNot stated
Hinweismeldung auf fehlende EinwilligungserklärungSystem settings Beratung > Kontakte > DatenschutzConsent dialog opens automatically on creation / personal-data change without consentOn
Other data-protection parametersSystem settings Beratung > Kontakte > DatenschutzWarning "check data-protection settings" when any is at its maximumNot stated
Kontaktaustausch automatisch zulassenSystem settings Beratung > Kontakte > AutomatisierungDefault of the exchange checkbox for person customers / converted walk-insOff
PLZ und Ort bei Neuanlage von Kunden vorbelegenContacts system parameters, page AutomatisierungPrefill postcode/city with the pharmacy's ownNot stated
Kassenstatus automatisch aktualisierenContacts system parameters, page AutomatisierungAuto-change insurance status to "1" at 18th birthdayNot stated
Zeitraum VerkaufsdatenContacts system parameters, page AbverkäufeDefault period of the sales data pageCurrent year to date
Doppelmedikations-Check aktivGlobalEnables per-customer duplicate-medication check flagNot stated
Doppelmedikations-Check bei KundenneuanlageGlobalDefault of the flag for new customersNot stated
Anzahl Tage für die PrüfungSystem settings Kasse, page InteraktionenLook-back window for risk checks from sales dataNot stated
Hide medication details for same medicationNot stated (MM-related parameter)Skip course-details dialog for identical follow-up prescriptionsNot stated
Group / sub-group exchange and visibilityCentral group settings; Contacts > Filiale & Partner > SichtbarkeitWhich pharmacies exchange contacts; which exchanged contacts are visibleNot stated
DATEV automatic debtor accounts, digit countFinance / DATEV settingsAutomatic debtor-account numbersNot stated
Default payment-terms modelPayment-terms administrationApplied to all customers without manual assignmentOne model flagged
Default invoicing model for customersInvoicing conditions moduleAssigned on walk-in → customer conversionOne model flagged
Default customer discount modelDiscount modelsAssigned to new / converted customers; shared group-wideOne model flagged
Bonus system expiry periodBonus modelDefault expiry of credited unitsPer system
Per-customer flagsCustomer fileAll flags in 4.6, 4.10, 4.11, 4.14As described there

8. Roles and permissions​

  • Sensitive-data permission concept (optional, with workstation protection): when on, many functions are bound to rights and approved workstations.
  • Contacts general: edit locked contact data (in role Leiter): see locked contacts (red), unlock, finally delete.
  • Contacts general: show change history or role Leiter (+ workstation protection): view change history.
  • Duplicate processing: workstation/user permission when the concept is on; merging employee contacts additionally needs "edit user accounts and assign rights" or role Leiter.
  • Customer bonus accounts right or role Leiter (+ workstation protection): manual bonus corrections.
  • Anonymise sales data right: see / set the per-customer sales-data hiding.
  • Visibility of exchanged contacts: changing the pharmacy's visibility setting requires a permission (not named).
  • Licences gate features: professional invoicing licence (VAT-exempt modes, price schemes) or clinic licences; delivery-management (preferred tour); MM licence (MM, book medication); customer add-on (family suggestions); connect product (customer app); blistering licence (blister participation history; own blister system warnings); customer-app ("Meine Apotheke"); EDI partner licence; DMS.

9. Integrations, hardware and external services​

  • Hand scanner: customer card barcodes; old cards in advanced search; prescription scanner for BMP 2D codes (one model unsupported).
  • Chip-card reader: health-insurance card → open / reconcile customer [DE].
  • Signature pad / digital signature: consent declarations, SEPA mandates, pharmaceutical-service contracts.
  • DMS / document directory: signed consents, mandates, service contracts and results, invoice PDFs.
  • VAT ID check services (German and EU online services) [DE/EU].
  • Geocoding and map for courier addresses.
  • General address database for postcode / city suggestions.
  • Customer app / web portal ("Meine Apotheke"): access data, app inbox messaging, app orders.
  • Drug-data provider catalogue (allergy / disease codes, inactivations; drug info) [DE data].
  • Telematics infrastructure / e-prescription / eMP / eML [DE].
  • E-mail with encrypted PDF attachments or encrypted download links.
  • EDI: an eye-clinic partner system; EDIFACT for orders / delivery notes / invoices.
  • Automated dispensing robot: output chute per contact.
  • Blister systems (in-house and third-party, contract blistering).
  • DATEV bookkeeping export (debtor accounts) [DE]; SEPA file export (payment-transactions module) [EU].
  • Electronic invoices (buyer reference from cost centre).

10. Printouts, reports and exports​

  • Consent declaration (template, customer-specific scopes; print date recorded as hand-out date when printed from hit lists or Reports).
  • Blank and filled SEPA mandate forms.
  • Customer-app login data / one-time password (printable once).
  • Federal medication plan (print preview, auto-offered after changes).
  • Change history (print / PDF).
  • Invoices, delivery notes, back-order delivery notes, reminders, collective slips, labels, receipts — forms, counts and automation per customer (4.11); automatic invoice PDFs with year/month folders and "-Kopie" suffix for copies.
  • Care-fund cost-coverage application for consumable care aids.
  • Data-subject access report includes personalised coupons.
  • Reports module queries used from this area: customers without consent (bulk lock), contact exchange (bulk set/unset), MM bulk activation, invoicing-model bulk assignment.
  • Digital courier list shows the delivery note text.

11. Dependencies on other modules​

  • Till / POS: customer assignment, quick creation, suggestion list, preferred payment method, open items, hand-over from sales history, phone reservations, pickups.
  • Invoicing (Faktura) and invoicing conditions / payment terms / dunning: invoicing models, runs, forms.
  • Payment transactions module: SEPA export, returned debits, revocation.
  • Medication management module / blister management: courses, stops, course details, objective impression, release history.
  • Clinical checks (CAVE, interactions, duplicate medication, cross-selling recommendations).
  • Prescription scan / e-prescription: walk-in creation, take-over dialog.
  • Care homes / nursing services / clinics (homes chapter): structure, separate invoicing, residents.
  • Discount, coupon and bonus model administration; contact classifications module.
  • Reports (bulk processing), Cockpit / analyses (analysis-neutral, cooperation partner, separate statistics), purchase-order optimisation.
  • Delivery management (tours, courier).
  • Company master (bank accounts, creditor ID, VAT ID, data-protection officer).
  • System settings / user and rights management (permission concept, workstation protection).
  • DMS; article management (articles, own article numbers, aids contracts database); sales administration.
  • Supplier, doctor, staff and other contact roles (chapter 16).

12. Portability notes​

Generic and directly reusable

  • One contact register with multiple roles per contact, person/company type, status active/inactive/deceased plus locked state.
  • Fast name search with wildcard grammar, phonetic fallback, role-scoped search with "search all roles" fallback, advanced search including former names/numbers, configurable hit-list columns with status icons.
  • Card-scan opening of customer records.
  • Walk-in (temporary) customers with automatic lock and deletion periods and conversion to full customers — a strong data-minimisation pattern.
  • Address-book entries promotable to any role.
  • Multiple typed addresses, address references between contacts with synchronisation, postcode/city assistance from own data first.
  • Per-channel communication with usage types and encrypted e-mail for health documents.
  • Customer numbering with per-branch ranges in a multi-branch setup.
  • Consent record with scopes (storage, marketing channels, clinical data sharing, cross-branch sharing), signature, hand-out tracking, withdrawal → lock.
  • Household (family) grouping with joint invoicing modes, and legal guardians as invoice recipients.
  • Credit limit, payment terms, invoicing model inheritance through an organisational hierarchy (homes → units → residents).
  • Loyalty points ledger with FIFO redemption and expiry; personalised coupons; discount models.
  • Patient risk profile (allergies, conditions with static/temporary/deactivated status and expiry review, weight, kidney function) driving automatic contraindication checks; documented risk overrides with expiry.
  • Medication-management enrolment with treating doctors, service log, audit trail of medication changes.
  • Recording externally obtained medicines (sample articles) so checks are complete.
  • Purchase history with re-sell / reserve / reorder shortcuts and retrospective risk checks.
  • Duplicate detection (attribute AND-matching) and a merge wizard with field-by-field resolution and relationship guards.
  • Multi-branch shared customer master with consent-gated exchange and per-branch exceptions (clinical enrolment not shared).
  • Field-level change history with permission control; sales-history anonymisation.
  • Patient app account linked to the customer record.

Germany-specific and the idea underneath

  • Federal medication plan (BMP/eMP) → standardised machine-readable medication plan exchanged with doctors and reconciled line by line.
  • Health insurance status, co-payment exemption, auto-status change at 18 → payer link with member number, co-payment category and exemption period, age-driven defaults.
  • Long-term-care insurance and consumable care aids (product groups 51/54, approval) → second payer with capped periodic supplies and approval tracking.
  • Flat-rate aids → periodic flat reimbursements with margin per period.
  • Drug-data provider's characteristic catalogue with inactivations → maintained clinical code catalogue with retired codes and successor mapping.
  • SEPA mandates and creditor ID → signed recurring-debit authorisation; DATEV debtor ranges → bookkeeping account per customer.
  • VAT exemptions and EU VAT ID verification → per-customer tax treatment and online tax-ID validation.
  • Batch documentation for inter-pharmacy supplies → batch traceability on B2B transfers.
  • Pharmaceutical services with e-prescription billing vouchers → billable clinical services with contract, result and billing evidence.
  • Insurance chip card read-in → identity document scan with reconciliation.
  • GDPR consent → local data-protection consent with scopes.

13. Open questions​

  • Phonetic search algorithm is not described.
  • Exact lock and deletion periods for walk-ins (defaults, units) are not stated; nor whether locked walk-ins remain reachable for open-items or legal retention.
  • Family-suggestion matching criteria are not documented.
  • Classification "delete": unclear whether it removes only this customer's assignment or deletes the classification for all contacts (wording suggests the latter).
  • Allergic diathesis threshold: one page says three or more allergies, another "more than three".
  • The automatic insurance-status rule lists status 0 with the label of status 1 (apparent typo in the source); the exact set of statuses replaced at 18 is therefore slightly uncertain.
  • How many guardians a ward may have is not stated (merge rules imply one).
  • Which permission governs the exchanged-contact visibility setting is not named.
  • Whether referenced-address synchronisation is immediate or batch is not stated (implied immediate).
  • Defaults of many parameters (prefill postcode, auto insurance status, duplicate-medication defaults, check look-back days) are not given.
  • The SEPA page says a mandate is needed "for direct debit or transfer" — presumably only direct debit.
  • Exact behaviour of the "further discounts" option (which discounts are restricted, how) is not detailed.
  • Whether deactivating contact exchange is possible for care homes/clinics: master data says yes, the exchange overview page names only person customers.
  • Inner workings of the contact-exchange synchronisation (conflict resolution when two branches edit the same contact) are not described, beyond the merge precondition that no other workstation edits contacts.

14. Source pages​