Collaboration (Notes: tasks, calendar, messaging, order inbox, chats, vendor support), optional devices and add-ons, FAQ and practical guidance (Kooperation / Notes; Sonstiges: CashGuard, Kundendisplay, Preisimporter, Faxschnittstelle, ELO-DMS, Rx.secure, ApoTune, ClickOnce/WinClient, FAQ, Tipps & Tricks, DRZ-Hinweise)
1. Purpose and scope
This chapter covers two groups of help pages.
A. The collaboration menu (Kooperation) and its main module Notes. Notes is the pharmacy's internal "Outlook": it combines
- a calendar of appointments (Termine) and tasks (Aufgaben) per employee and for the whole pharmacy, with recurrence rules, private flags, deputies and printing;
- task management (Aufgaben) and task control / controlling (Aufgabensteuerung) with per-occurrence completion logs, overdue highlighting and a daily "today's tasks" pop-up at operator login;
- tasks generated by other modules (report queries run interactively or automatically, replenishment lists, assortment-control ratings, vaccine self-declaration reminders) and incoming customer/provider orders (customer app, national e-prescription app, doctor practices, care homes, web shop, secure-mail e-prescriptions, deferred items, compounding);
- an order inbox (Bestell-Liste) with per-order conversation thread with the customer, auto-generated status messages, SMS, and internal notes;
- mailboxes: internal/system messages, ordinary e-mail (with attachment encryption and DMS filing), messages to customer-app users, and the German health-sector secure mail (KIM);
- chats between workstations, the staff mobile app and branch pharmacies;
- vendor support ticketing (IXOS.eCall) with drafts, automated answer suggestion, follow-ups and a public feature-request ("requirements") register;
- acoustic signals for selected events, and remote opening of a partner/branch pharmacy's system.
B. Optional products, devices and miscellaneous topics (Sonstiges).
- CashGuard closed cash-recycling device integrated with the till: payment, change, refunds, pay-in/out, connection handling, offline fallback, error codes, and the separate BackOffice software for reconciliation, emptying, refills, warning levels and inventory.
- Customer display (graphic second screen at the till).
- Price importer for external selling-price lists (CSV), including a consultancy-specific variant.
- Fax interface to online fax providers.
- ELO external document management link (print-to-archive).
- Rx.secure: 24-month effective-dated master data for prescriptions.
- ApoTune: third-party courier route optimisation.
- IXOS WinClient / ClickOnce deployment on pharmacy-owned hardware.
- FAQ pages (courier app U5, ORBIZ DMS, e-prescription, ePA, institution card on owner change, pharmaceutical services, in-store TV, customer app & online payment).
- Tips & tricks index and notes for customers of the vendor's billing centre (DRZ).
Out of scope here (owned by other chapters, referenced only as dependencies): the customer app/web shop itself, the connect products' order editing screens, Reports query design, the till's sale/total windows, delivery management, prescription scan and prescription management, the DMS ORBIZ module, contacts, prices & calculation, print forms.
2. Key concepts and terms
| German term | English | Meaning |
|---|---|---|
| Kooperation | Collaboration menu | Menu grouping information-exchange tools: Notes, order list, remote access to partner pharmacies. |
| Notes | Notes module | Calendar, tasks, task control, order list, chats, mailboxes, vendor support. |
| Termin | Appointment | Plain calendar entry (meeting, vacation) for time planning; may have location and private flag; not "worked off". |
| Aufgabe | Task | Calendar entry that must be explicitly completed; tracked in task control; reminded at daily first login. |
| Standardaufgabe | Standard task | Task created manually in Notes (or by evaluations, assortment control, overstock management) without automatic coupling to Reports. |
| Reports-Aufgabe / interaktive Aufgabe | Interactive report task | Task that opens a stored report query for manual execution and logs before/after PDFs. |
| Automatischer Druck / Export / Nachrichtenversand | Automatic report job | Task series that runs a report automatically and prints, exports or e-mails the result. |
| Download-Link / OData-Datenfeed | Cloud report feed | Task that uploads a report result as a download link / OData feed to the cloud. |
| Serie / Serientyp | Series / recurrence pattern | Recurrence rule (daily/weekly/monthly/yearly + duration). |
| Vertretung | Deputy | Second person who performs a task if the responsible person is absent; sees it in own calendar. |
| Zuständig | Responsible | Employee (or whole pharmacy) the entry is assigned to. |
| Priorität | Priority | High / normal / low. |
| Infotext | Info text | Internal free-text note on a task occurrence or order. |
| Protokoll | Log / occurrence record | Record of each occurrence of a task series with due date, executor, completion; for report tasks also PDFs. |
| Erledigt setzen / Unerledigt setzen | Mark done / undone | Toggle completion, logging time and operator. |
| Aufgabensteuerung | Task control | Management view over all one-off tasks and series with statistics. |
| Heutige Aufgaben/Bestellungen | Today's tasks/orders pop-up | Window shown at first activation of an operator's register each day and on new orders. |
| später erinnern | Snooze | Postpone the pop-up by 1, 2, 4, 8 hours or 1 day. |
| Bedienerregister | Operator register | Per-operator session tab at the till; activating it triggers task reminders. |
| Bestell-Liste | Order list / order inbox | Inbox of incoming orders from apps, doctors, homes, KIM, deferrals, compounding. |
| Mitteilung senden | Send message (to customer) | Text message to the customer's app/phone about an order. |
| Textbaustein | Text template / snippet | Reusable text block (max 500 characters) for messages and e-mail templates. |
| Systemnachrichten-Postfach | System message mailbox | Mailbox with folders System, vendor (Pharmatechnik), Branches, Personal, Sent, Deleted, Reminder, Duplicate processing, Automatic tasks. |
| Infocenter | Info centre | Notification area in the menu bar and process bar showing unread counts and previews. |
| Vorgangsleiste / Vorgangskarussell | Process bar / process carousel | Side bar listing open processes and info-centre items. |
| Kontaktklassifikation | Contact classification | Named grouping of contacts (here: of employees) used as distribution list / group chat. |
| Apothekenverbund | Pharmacy group | Owner's network of main and branch / partner pharmacies. |
| Kontaktaustausch | Contact exchange | Group-level setting allowing employees to see/address each other across pharmacies. |
| IXOS.eCall | In-app support ticketing | Support requests, drafts, follow-ups and requirement register. |
| Anforderung | Requirement / feature request | Accepted development request; open, fulfilled or rejected. |
| IXOS.Assistent | Support assistant | Automated solution proposal shown before a ticket goes to human support. |
| Fernwartung | Remote maintenance | Vendor remote login consent ("enable for today"). |
| KIM | Secure health-sector e-mail | German closed e-mail network of registered healthcare providers over the telematics infrastructure (TI). |
| TI (Telematikinfrastruktur) | Telematics infrastructure | German national health data network. |
| E-Rezept-Direktzuweisung | E-prescription direct assignment | Structured e-prescription sent by a provider straight to a pharmacy. |
| gematik-App | National e-prescription app | State app in which patients hold e-prescriptions and choose a pharmacy. |
| Arzt.connect / Rezept.connect | Doctor / care-home connect products | Vendor channels for orders from practices and care homes. |
| Rückstellung | Deferred item | Item set aside for later (appears as order type). |
| Mandant | Tenant / legal entity | Pharmacy company context for DMS filing. |
| CashGuard | Cash recycler | Closed cash-handling device replacing the drawer; accepts and dispenses notes and coins. |
| Banknotenwechsler / Münzwechsler | Note recycler / coin recycler | Device units for notes (4 cassettes) and coins (up to 8 denominations). |
| Banknotensammler / Leerungsbox | Note collector / emptying box | Removable box attached when notes are emptied. |
| BackOffice | Device back-office software | Admin software for reconciliation, emptying, refill, warning levels, inventory. |
| Wechselgeldbestand | Change float | Cash that stays in the device after reconciliation and emptying. |
| Warnlevel | Warning level | Per-denomination low/high count thresholds. |
| Kassenabrechnung (CashGuard) | Device reconciliation | Count/settlement report of a device's cash content. |
| Leerung | Emptying | Physical removal of cash down to the float or of a single denomination. |
| Gesteuerter Wechsel | Controlled exchange | Insert one note/coin and specify the denomination to receive as change. |
| Z-Bon / S-Bon | Z receipt / sum receipt | Till closing receipt for one till / summary over all tills. |
| Kassenbuch | Cash book | Module listing closing receipts over a period. |
| Kundendisplay | Customer display | Customer-facing screen at the till. |
| Eigen-VK | Own selling price | Pharmacy-defined retail price for an item. |
| Preisliste / Preisverwendungsmodell | Price list / price usage model | Named price list; ordered priority of price lists used to determine an item's price. |
| PZN | Central pharmaceutical number | German 7/8-digit article number. |
| PÄD (Preisänderungsdienst) | Price change service | Master-data update on the 1st and 15th of every month. |
| Retaxierung | Claw-back | Payer's refusal/reduction of a prescription claim. |
| Rx.secure | Effective-dated prescription data | 24-month history of prices, discount contracts, etc. |
| DRZ (Digitales Rezept Zentrum) | Vendor billing centre | Prescription billing service to statutory insurers. |
| ELO-DMS / ORBIZ DMS | External / vendor DMS | Document management systems linked to IXOS. |
| Verschlagwortung | Keywording / indexing | Assigning metadata (type, date, number, amount) to a document. |
| ApoTune | Courier route optimiser | Third-party tour optimisation and courier tablet app. |
| U5-Bote | Vendor courier web app | The vendor's own courier app (FAQ only). |
| WinClient | Client on own hardware | Client installation for pharmacy-owned devices. |
| SMC-B | Institution card | Pharmacy's TI identity card. |
| HBA | Health professional card | Pharmacist's personal signature card. |
| ePA / eML / eMP | Electronic patient record / medication list / medication plan | National patient record and its medication documents. |
| PDL | Pharmaceutical services | Billable clinical services by pharmacies. |
| apoTV / KassenTV | In-store TV / till TV | Digital signage in the pharmacy / at the till. |
3. Data model
The help describes behaviour, not tables; the following entities and fields are what a designer needs to reproduce the described behaviour.
3.1 Calendar entry (appointment or task)
| Field | Notes |
|---|---|
| id | |
| kind | appointment or task. |
| origin / task type | standard (Notes or other modules without Reports coupling), evaluation (manual run of a report), report_interactive, report_auto_print, report_auto_export, report_auto_mail, report_cloud_feed (download link / OData), replenishment_list, assortment_control_rating, vaccine_self_declaration_reminder, and order types (see 3.4). Drives icon, available actions and which fields are editable. |
| assignee | One employee or the whole pharmacy ("for"). Default = first employee under "my calendar". |
| deputy | Tasks only; optional employee. Task appears in deputy's calendar too, marked as deputy. |
| subject | Pre-filled for module-generated tasks (e.g. "standing special orders"). Not editable for orders. |
| location | Appointments only. |
| start date/time, end date/time | |
| all_day | Boolean. |
| description | Instructions. Not editable for orders. |
| priority | high / normal / low. |
| private | Appointments: displayed with a "(private)" suffix; can be excluded from prints. |
| series_id / recurrence | Optional link to a series (3.2). Not editable for orders. |
| info_text | Optional internal text per one-off task or per occurrence. |
| created_at / created_by | |
| changed_at / changed_by | Updated by edit or by drag-move in the calendar. |
| last_executed_at / last_executed_by | Report tasks: set each time "execute" is pressed, whether the query is completed or cancelled. |
| done_at / done_by | Cleared again (including operator) on "mark undone". |
| snoozed_until | Per user, from the today's-tasks pop-up. |
| query reference, query variables | Report tasks: name/description of the query and its variable values. |
| before_pdf / after_pdf | Interactive report tasks: snapshot of the result at opening and at completion (licensed add-on). |
| printout_pdf | Automatic print jobs: the printed PDF. |
| download link usage/validity | Cloud feed tasks. |
3.2 Series (recurrence rule)
| Field | Values |
|---|---|
| time of day | start time, end time, or all-day. |
| pattern | Daily: every N days, or every working day. Weekly: every N weeks on a chosen set of weekdays. Monthly: on day D of every N months, or on the {first, second, third, fourth, last} {day, working day, weekend day, specific weekday} every N months. Yearly: every N years; on day D of month M; or on the {nth} {weekday} of month M. |
| duration | start date; then one of: no end date / ends after N occurrences / ends on date. |
| early end | Task series can be ended early; logs remain. |
| conversion | One-off appointment or task → series: allowed. Appointment series → single appointment: allowed. Task series → single task: not allowed. |
| statistics | For task series: number of occurrences due so far, number done, number overdue (deleted occurrences excluded). |
3.3 Occurrence log (Protokoll)
One record per occurrence of a task series (and for one-off tasks): responsible/deputy, executing operator, completion date, due date, info text (editable), report PDFs. Deleting a task series deletes all its logs.
3.4 Order (entry in the order list)
| Field | Notes |
|---|---|
| order type / channel | customer app ("Meine Apotheke"), national e-prescription app (gematik), doctor practice (Arzt.connect), care home order / care-home prescription request (Rezept.connect), web shop, KIM e-prescription, deferred item (Rückstellung), compounding (Rezeptur), callback request, prescription-pickup appointment for billing-centre customers. |
| customer | Name, mobile number, linked contact (can be reassigned in sales management). |
| received_at | Date/time of receipt; for KIM additionally the send time if it differs from receipt by more than 2 hours. |
| sender | For KIM: sender address; for homes: home name. |
| items | Ordered article positions; prescription images (from app/home) in a separate tab. |
| processing status (app orders) | not processed → ordered → partially ready for pickup → completely ready / changes, completely ready → done (definitions in §6.3). |
| active/done flag | Done orders listed under "Done"; can be set undone. |
| assigned processor | Optional employee. |
| info_text | Internal; never sent to the customer. |
| conversation | Ordered thread of messages: from customer, system messages, auto-generated messages to customer, pharmacy messages to customer; each with read/unread state. |
| attached KIM message | Message text and list of non-prescription attachments. |
| online payment | If prepaid (e.g. PayPal) – refund via interface possible until the sale is closed at the till. |
3.5 Message (system mailbox)
| Field | Notes |
|---|---|
| folder/type | System, vendor (with subfolders News, Tips & Tricks, Software, Events, Requirements, eCall Support, General), Branches, Personal, Sent, Deleted, Reminder, Duplicate processing, Automatic tasks. |
| sender, recipients | Recipients: employee(s), contact classification (resolved to members, shown in tooltip), whole pharmacy, other pharmacy in the group. |
| subject, body | |
| priority | High-priority messages can trigger a sound. |
| read state | Per user for system/internal messages; shared for KIM messages. |
| short-message-visible-until | Date until which it appears in the info centre / process bar. |
| expires-at | Date at which it is deleted automatically. |
| deleted_from_folder | For the Deleted folder (restore puts it back with its original validity). |
3.6 E-mail / KIM / customer-app message
Sender address (one of several KIM addresses, or the configured e-mail sender), To/Cc/Bcc (semicolon-separated, e-mail and KIM addresses mixed), subject (mandatory for KIM), rich text body, template and placeholders used, attachments (with encryption mode: encrypted download link / encrypted in mail / unencrypted; password), folder (Inbox, Sent, Archive), DMS filing reference, retention (auto-delete after 3 calendar months).
3.7 Contact-level communication settings
Per contact e-mail address: password for automatic attachment encryption, and a "link" flag (always deliver attachments as password-protected download link). Per employee: permission to see eCall support and requirements message types; favourite flag for message recipients.
3.8 Chat
Chat id, subject (optional for one-to-one; defaults to the counterpart's name), participants (persons, a contact classification as group, whole pharmacy, branch/partner pharmacies), messages (text, emoji, image jpg/png, PDF), per-user read/unread.
3.9 Support ticket and requirement (eCall)
Ticket: title, category (e.g. professional question, hardware & technology, improvement suggestion, sales inquiry), urgency (answer by tomorrow / urgent-emergency), description, up to 8 attachments, remote-maintenance consent for today, state (draft → open → closed), conversation thread, last activity (date, time, operator, status), follow-up link to a closed ticket (reference number in description). Requirement: id, title, classification, demand level (number of requesting pharmacies, shown as bars), state (open / fulfilled / rejected), answers, link to the help topic describing the implementation.
3.10 Cash device (CashGuard) entities
- Device: id, group, store, connection port (COM1–COM4) at its till workstation, connection owner (till or BackOffice), status (connected/disconnected, warning, error, time-locked, BackOffice link lost).
- Denomination stock: per denomination (up to 8 coin values, notes in 4 cassettes: €5, €10, €20, €50+€100) current count, low warning level, high warning level, maximum capacity (manufacturer fixed; coin tubes 200–550 coins).
- Change float: target count per denomination left after emptying.
- Connection log: every logon/logoff with operator number and till number.
- Reconciliation (Kassenabrechnung): timestamp, device, counted content; may be run any number of times; the next emptying is based on the last reconciliation.
- Emptying report, refill report, coin-correction report: printable automatically or manually.
- BackOffice user: user name, password, level "Apotheker" (pharmacist) or "PTA" (technician); idle auto-logout minutes.
3.11 Price import configuration (per price list)
Import type (none / manual / on file change / scheduled with time table), selected file in the fixed server import directory, flag "remove articles no longer in file", flag "also remove articles from previous import that have a valid-until date", import history (files moved to a "read" folder with date stamp), result messages. Imported row: PZN, price, optional valid-from, optional valid-to.
3.12 Effective-dated article data (Rx.secure)
For each article and each master-data release in the last 24 months, the values of the historised fields (list in §6.9), queryable by dispensing date.
3.13 Customer display configuration
Welcome-page media (image, video or HTML page), full-screen flag, header/footer colours, show operator name flag.
4. Features
4.1 Notes module shell and entry points [GENERIC]
- Purpose: one place for internal planning and communication, comparable to a desktop groupware client.
- Entry points: desktop tile; menu Kooperation; an "information" (messages) button and a "tasks" button in the global menu bar (the tasks button carries a badge with the number of today's tasks); a support (eCall) button in the navigation bar of every module, which opens Notes directly on the support category.
- Views (left navigation): system-message mailbox (incl. eCall), chats, calendar, tasks, order list, task control. The active view is highlighted; the navigation pane can be collapsed.
- Capabilities stated by the help: see all employees' schedules; create appointments and tasks for one employee or the whole pharmacy; task management and task controlling; read and send messages (also across branches and to customers); conversations with the staff mobile app; process orders from the customer app, the national e-prescription app, doctor practices and care homes; contact vendor support; start report queries from tasks; see scheduled report print jobs in the calendar.
4.2 Calendar [GENERIC]
- Purpose: time planning (appointments) and visual planning of work items (tasks) per employee and for the pharmacy as a whole.
- What is shown: initially all entries assigned to the logged-in employee plus all pharmacy-wide entries. The pharmacy calendar is always shown; the own employee calendar is shown by default unless the workstation parameter "only pharmacy calendar" is on. Further employees' calendars can be ticked on, but only for employees with an active user account.
- Views: day; week (work week Monday–Saturday, or full 7-day week = default; with several employees ticked in full-week view only one employee's week is shown at a time, with a toggle); month (with or without details). A mini month calendar marks today, the selected day and days that have entries (bold). Navigation by day/week/month arrows and "today".
- Markers: series icon; high/low priority icons; icons for standard task, interactive report task, automatic report task; interactive report entries prefixed "Reports:"; greyed icons for done tasks; overdue tasks in red; past appointments and done tasks in grey; deputy-only assignment is visibly marked when viewing an employee's plan.
- Direct manipulation: for entries without a series, drag to move, drag edges to lengthen/shorten, drag onto another operator's column to reassign. Rules: moving, resizing and opening by double-click of appointments and of any series is only allowed for one's own objects; for other users' objects it needs the right "Notes: edit task". Single (non-series) tasks can be manipulated for own and other users. A deputy's series objects can be changed only via the edit dialog and only with that right. Toolbar buttons are enabled/disabled accordingly.
- Upcoming-appointment alert: 15 minutes before an appointment starts, a notice appears in the menu bar (tooltip with full title and content; double-click opens Notes on the entry). Tasks are not announced this way. Each alert is also stored in the "Reminder" folder of the system mailbox (auto-deleted after 2 days).
- Create: "New" asks for the type (appointment or task); pre-selecting a time slot or double-clicking it pre-fills start time.
4.3 Appointment and task creation/editing [GENERIC]
- Where: appointments only from the calendar; tasks from calendar, task list and task control.
- Inputs: assignee (employee or pharmacy), subject, location (appointment), deputy (task), start/end date and time, all-day, description, priority, private (appointment), recurrence.
- Rules:
- Data remain editable after creation; "edit" changes one entry, "edit series" changes the whole series.
- For order-type tasks, subject, description and series type are locked.
- Conversions: see §3.2.
- Notes itself creates only standard tasks; report-coupled tasks are created in Reports.
- Permission: creating, editing and deleting tasks and opening task control require the right "Notes: edit task" (contained in the roles "Manager" and "Notes: edit task") when the pharmacy uses the permission concept.
4.4 Recurrence patterns [GENERIC]
Full rule set in §3.2. Example given by the help: "last Friday of every month". The series of automatic report print jobs is viewed/edited with the same dialog.
4.5 Deleting entries in a series [GENERIC]
- Delete asks whether to delete only the selected occurrence or the whole series (calendar: appointments and tasks; task list: tasks).
- Deleting a task series also deletes all of its occurrence logs (warning given). Same permission as editing tasks.
4.6 Task list (Aufgaben) [GENERIC]
- Content: all active and done tasks assigned to me, to the pharmacy, and where I am deputy; further employees can be ticked on.
- Time filter: Current = overdue + due today and the next two days + done; Week = overdue + due this week + done; Month = overdue + due this month + done.
- Type filter: standard; evaluation (manual report run); report task.
- Grouping/sorting: active; active within the next two working days; done. Overdue in red, done in grey.
- Columns: type icon (standard, interactive report, automatic report print, replenishment list, assortment control, and connect orders: app order, care-home order, care-home prescription request, doctor-practice order, web-shop order), subject, series icon, priority, info-text icon, responsible/deputy, due date/time.
- Detail pane: description, series details, created (when/by), changed (when/by), last execution (report tasks), done (when/by), query description, before/after PDFs. For connect orders, the order details instead.
- Actions by origin:
- standard task → mark done;
- replenishment-list task (from storage locations module) → "mark done" opens the list for processing;
- vaccine self-declaration reminder, assortment-control rating reminder, report task → "execute" opens the target function;
- report task execution: opens Reports with the query; user may do bulk result editing; "query done" returns and marks the task done; before/after PDFs and operator/time stored. A done report task can be executed again; last execution is always logged.
- Mark done/undone: for standard tasks (one-off or a single occurrence) and for overdue report tasks even if not executed. Undo removes the completion log entry (who/when).
4.7 Info text on tasks [GENERIC]
Free internal text on a one-off task or on one occurrence of a series; indicated by an icon; viewable/editable from calendar, task list and task-control log tab.
4.8 Today's tasks and orders pop-up [GENERIC]
- Trigger: the first time an operator's register is activated on a day, if that operator has tasks due today or overdue from earlier days. Tasks added during the day are signalled at the next activation of the register. New incoming orders are signalled immediately on every workstation unless disabled per workstation (parameter "remind on order arrival").
- Content: type icon (standard, interactive report, assortment control, replenishment list; app order, care-home order, care-home prescription request, doctor-practice order, web-shop order, prescription-pickup appointments for billing-centre customers; KIM order with home name for care-home customers), task title, series and priority icons, responsible/deputy, due, snooze icon with "remind again at" tooltip. Overdue in red.
- Actions: open a task (goes to task view) or an order (goes to order list); OK continues to the till or desktop; "open tasks" jumps to Notes; snooze for 1, 2, 4 or 8 hours or 1 day — the pop-up then reappears after that time at the next trigger (e.g. operator switch) even without new tasks. The tasks button in the menu bar reopens the list at any time.
4.9 Task control (Aufgabensteuerung) [GENERIC]
- Purpose: planning, monitoring and controlling of all task series and one-off tasks (manager view).
- Filters: Current (overdue + current + next two days), All, Only series; task type (standard, evaluation, report task, automatic export, automatic print, automatic e-mail dispatch, download link/OData feed).
- Display: active vs done; expired tasks and series containing overdue occurrences in red. Left pane shows the employees to whom the selected task is assigned.
- Columns: type, subject, series (tooltip with pattern), priority, info, responsible/deputy, next due, series start, series end.
- Detail tabs:
- Series/one-off: description, recurrence, created, done (one-off), query name, statistics (due so far / done / overdue; deleted excluded), before/after PDFs (one-off manual report), printout PDF (automatic print).
- Logs: every occurrence with responsible/deputy, executing operator, completion date, due date, info text; for cloud feeds the usage and validity of the link. Execute, mark done/undone, edit, edit series and info are performed here per occurrence.
- Query variables: the variables of the report query/print job.
- Orders: connect orders can be executed and marked done from here as well.
- Permission: "Notes: edit task".
4.10 Order list (Bestell-Liste) [GENERIC] (channels partly [DE-SPECIFIC])
- Sources: customer app, KIM, national e-prescription app, doctor practices, care homes, deferred items, compounding orders.
- Filters: time (Current: active today/tomorrow/day after + overdue + done today; Week: active next 7 days + overdue + done today or in last 7 days; Month: active next 30 days + overdue + all future + done today or in last month); customer-name search; "my orders" (only orders of the active user); order-type filter.
- List: categories Active, Active – next two working days (only with Current), Done. Columns: channel icon, customer name, envelope if unread messages exist, info-text icon, assigned processor, received date/time.
- Detail: left – customer name, mobile, items, internal info texts, processor, read state; right – conversation thread: customer messages, system messages, IXOS auto-messages and pharmacy messages, visually separated.
- Functions:
- Info – internal free text (never sent).
- Message/SMS – for app orders, national-app orders and callback requests: one-line message (Ctrl+Enter for new line, Enter sends). SMS only enabled if a mobile number exists. A larger message window offers text templates and lets the user create new ones.
- Mark done / undone.
- Sales management – opens the customer's orders there: edit, reassign to another customer, cancel.
- Execute – Rx items open the prescription window, others the till window; if an item is not in stock a window to message the customer appears; afterwards the order is in Done and its messages are automatically marked read.
- National app specifics: if the patient is logged in to the app, communication runs via the app; if not, via e-mail when an address is stored; otherwise the pharmacy must contact the patient another way.
- Online-paid orders: marking done offers "refund" (automatic full refund through the payment interface) or "done" (see §4.38).
4.11 Customer messages for app orders (Mitteilung senden) [GENERIC]
- Purpose: keep the ordering customer informed on their phone.
- Manual: select the order task anywhere in Notes → send message → free text → send.
- Automatic proposals: after defined process steps the message window opens with generated
text which the user can extend, change or delete before sending:
- order closed at the till without back-orders, status becomes done → "your order is ready for pickup";
- order closed at the till with back-orders → "not in stock, you will be notified when it arrives";
- back-order booked in goods receipt;
- an ordered item had to be substituted (discount contract, successor article, or splitting into several smaller packs);
- order deleted in Notes;
- order manually marked done.
- Header shows customer contact data and the order's processing status (§6.3) and order date/time.
4.12 Prescription images from orders [GENERIC]
- App and care-home orders can carry photos of prescriptions, shown as thumbnails in a dedicated tab.
- Print all images of the order or only the selected ones (count shown). No print preview by default (can be enabled in print settings).
- Parameter "number of prescription images per A4": 4 (default), 2 or 1. With 1 or 2 per page the image size is the same; 1 per page leaves more space for handwritten notes.
4.13 E-prescription orders via secure mail (KIM) [DE-SPECIFIC]
General idea: provider-to-pharmacy electronic prescription routing over a closed network, auto-converted into an order work item.
- Providers (doctors, homes, clinics) send KIM messages that may contain e-prescriptions (structured direct assignment or a PDF with the prescription code). Typical case: a faulty e-prescription is deleted by the doctor and the new one is sent directly to the pharmacy.
- Automatic conversion: structured direct assignments go straight to the order list; KIM mails whose attachments contain e-prescription data are also converted into an order and the mail is filed in the KIM Archive folder. Several messages in quick succession from the same sender for the same patient are merged — up to three e-prescriptions per order. The order shows the mail text and notes any other non-prescription attachments.
- Signalling: the today's-tasks/orders pop-up on all workstations (if configured), with a KIM icon.
- Processing: open from the pop-up → order list shows sender and content (plus send time if
2 h before receipt) → execute → prescription-scan window with reservation mode preset (goods collected later; switchable off, or globally via parameter "automatically reserve") → release and transfer → items arrive in the till subtotal with reservation set to "customer not present", so all items become back-order/pickup items → at total, the pickup/delivery dialog asks for payment and delivery conditions (e.g. courier) → sale closed → order moves to Done → goods prepared for pickup or delivery.
4.14 System message mailbox [GENERIC]
- Folders and retention:
| Folder | Content | Retention |
|---|---|---|
| System | Generated by automatic processes: master-data update installed, wholesaler offers updated, order transmission error, appointment note handed to a purchasing cart, price-import results, … | per message expiry |
| Pharmatechnik (vendor) | Vendor news: new version installed, legal changes, tips, events, general; subfolders News, Tips & Tricks, Software, Events, Requirements, eCall Support, General | per message |
| Branches | Auto-generated by branch processes (e.g. stock transfer initiated) or sent by another branch | auto-deleted after 2 days |
| Personal | Sent to me personally by staff of the pharmacy/group, and messages to the whole pharmacy | never auto-deleted |
| Sent | Messages I sent; recipients listed, classification members in tooltip | |
| Deleted | Manually deleted | permanently deleted after 1 week; "restore" moves back with original validity |
| Reminder | All 15-minute appointment reminders | auto-deleted after 2 days |
| Duplicate processing | Unresolvable differences when merging duplicate articles | shown in info centre up to 7 days (unless superseded by higher priority), deleted after 3 months |
| Automatic tasks | Report appointments/tasks that could not be executed, with cause |
- Signalling: new messages appear in the menu bar (black text, or white for personally addressed messages) with title and first line next to the info-centre icon; the number shows total unread; the same count appears in the process carousel; optional sound.
- Reading: newest first; search in titles (prefix
*wildcard to match words not at the start). Read state is per user; marking unread affects only oneself; "mark all read" per folder. - Deleting personal messages: two-step (to Deleted, then permanently).
- Cross-pharmacy messages require central activation of cross-pharmacy Notes, plus contact exchange between the pharmacies and in the employee contacts.
4.15 Composing internal messages and choosing recipients [GENERIC]
- New message → To (browse) → recipient picker → subject → text → send.
- Recipient picker groups: last sent to; favourites (star toggle); contact classifications of type "employee" (distribution lists such as back office, front counter, managers); contacts. Single pharmacy: the pharmacy itself plus all active employees (contact role "active", regardless of whether they have a user account). Pharmacy group: all pharmacies enabled for messaging (incl. own) and all active employees of those pharmacies with contact exchange enabled. Extra column: job title and birth date (to disambiguate namesakes) or description of the classification.
- Search narrows the list; double-click adds several recipients; empty groups are hidden.
4.16 Chats [GENERIC]
- Workstation ↔ workstation, workstation ↔ staff mobile app, app ↔ app. With one person, several (group), the whole pharmacy or connected branch/partner pharmacies (licence).
- Prerequisite for mobile: staff app installed and paired from the employee contact.
- Group chat requires a subject; one-to-one may leave it empty (counterpart's name used).
- Send with Enter; list shows subject, profile picture, last message; unread in bold; mark read/unread; attachments jpg/png/PDF; emojis; last text message also shown in the menu bar.
- Group chats via contact classifications: put staff into a classification (e.g. an "e-prescription team") and address the classification; members visible in tooltip.
- Delete chat.
4.17 E-mail mailbox [GENERIC]
- Write, send, forward, manage e-mail; all e-mails auto-deleted after 3 calendar months.
- Message attributes: "short message visible until" (info-centre display end) and "expires from" (automatic deletion date); recipients (groups expanded in tooltip). Folders with unread mail show bold with a count.
- Where e-mails originate: Notes; DMS; contacts (encrypted or not); many processes (goods logistics, invoicing, evaluations, Reports, prescription requests to doctors, pharmaceutical services); any print preview ("send e-mail"); the copier/scan function.
- Sender is pre-filled from system settings: with an own mail provider "pharmacy name – pharmacy address – reply-to"; with the vendor's mail service "pharmacy name (do not reply) – vendor no-reply address – reply-to".
- Recipients: context-filled or chosen from contacts (search ≥3 letters, filter by address type e-mail / KIM / customer app, icon per type). Cc/Bcc lines accept several addresses separated by semicolons, e-mail and KIM mixed. If a KIM address is only in Cc/Bcc the message goes out from the main KIM address (no sender choice).
- Body: formatting, placeholders, text templates, context-specific default text, pre-attached documents.
- Attachments: single attachment >10 MB → warning that delivery may fail; several attachments totalling >10 MB → automatically split into several e-mails. Send errors show a hint with tooltip.
- Sent folder; optional automatic Bcc copy to the sender address (system setting). Sent items with encrypted attachments show the lock icon and the password is kept in the mail header for the pharmacy's reference.
- DMS filing (with DMS licence): every e-mail with attachments is filed: recipient contact has role supplier → document type "e-mail supplier" under the supplier structure; role customer → "e-mail customer" under the customer structure; no role → "e-mail" under the tenant structure; if the specific types are deactivated → "e-mail".
4.18 Attachment encryption [GENERIC]
- Modes: encrypted download link (via vendor cloud), encrypted attachment directly in the mail, unencrypted. Encryption is recommended because documents often contain personal data.
- Manual: click the lock, choose a mode, type a password or generate one. Generated
passwords use digits 1–9, lower- and upper-case letters and
! # $ % * + / : ; = ? @, and deliberately exclude the ambiguous characters 0,-, l (lower L), I (upper i), O and o. - Automatic per contact: store a password on the contact's e-mail address → attachments to this contact are always encrypted; additionally tick "link" → always delivered as protected download link. Tell the password once via a separate channel; the contact can then open all future attachments.
- All attachments are converted to PDF, then encrypted, then attached. Cc/Bcc recipients need the main recipient's password. KIM mails are always encrypted by the network.
- The e-mail action/icon is available on these contact types: customer, doctor, company master, branches/partners, employee, supplier, field sales rep, vendor/provider, care home, clinic, payer.
4.19 E-mail templates [GENERIC]
- Each print form has its own default e-mail template; one general template is used for mails started from contacts, Notes and DMS and for digital customer messages in the extended customer-task functions.
- Editing (right "manage print forms"): formatting, placeholders from company master/contact data, text templates (max 500 characters each; manage/new/delete; fax-order templates appear too). Templates in editing are marked; saved custom templates marked; "reset template" restores the original. When sending, the template can be changed for that one mail only.
4.20 Messages to customer-app users [GENERIC]
- Mailbox lists messages sent to app users (deletable).
- New message: recipient by ≥3 letters of the customer name or contact search; filter checkboxes for e-mail / KIM / app addresses (app addresses recognisable by their domain suffix); Cc/Bcc; templates; attachments.
- Delivery: web-app users receive an e-mail notification; mobile-app users an e-mail and, if enabled, a push notification without content preview; they read the message in the app's mailbox (privacy).
- Also startable from the customer's master data (icon next to the app field; absent if the customer has no app account).
4.21 Secure health-sector mail (KIM) [DE-SPECIFIC]
General idea: a closed, directory-based, end-to-end encrypted messaging network between registered healthcare institutions, excluding private persons.
- Setup: at least one activated KIM address (company master → add-on modules). Address form "pharmacyname.city@<provider>.kim.telematik"; name part may be changed during confirmation only, not afterwards. Main address plus up to two further addresses; each address has its own mailbox (Inbox, Sent, Archive).
- Compose: recipient typed or searched in the central directory (by name parts, address parts or medical specialty; Space opens the directory; recently used addresses kept as favourites); sender chosen from own addresses (auto if only one); subject mandatory; rich text with templates; attachments only PDF, PNG, JPG (file, screenshot, scan); signature from company master (overridable); closing line from a configurable template.
- Inbound: preview in menu bar and process bar, unread count at the info-centre icon (tooltip by type), optional sound; e-prescription orders are signalled via the tasks/orders pop-up instead. Attachments in other formats cannot be opened (security). Reply, forward, delete, print (with preview), archive.
- Read state is shared: once one user reads a KIM message it is read for everyone; marking unread affects all users. Mark folder all read.
- Retention: KIM messages (including archived) are deleted automatically after 3 calendar months; with the vendor DMS all KIM messages and attachments are filed in a "Mails" folder.
4.22 Vendor support ticketing (IXOS.eCall) [GENERIC]
- Purpose: contact vendor support in writing with attachments instead of waiting on the phone; also a transparent register of feature requests.
- Access: activated by the vendor; right "edit support requests"; workstation protection may apply; per-employee visibility of the support and requirements categories set in the employee contact (message types page).
- Ticket list: search; status filter open/closed; groups Drafts (saved, unsent), Open (not fully answered), Closed (fully answered). Columns: title, category, urgency, last activity (date, time, operator, status). Detail shows the conversation.
- Create: mandatory fields must be filled before "send" is enabled; attach files (jpeg, png, tiff, bmp, pdf, mp4, mov, 3gp), screenshots taken earlier with the built-in screenshot function, or a scanned PDF; max 8 attachments; option "enable remote maintenance for today" on by default (consent for vendor remote login). Before reaching a human, an automated assistant usually proposes a solution: accept it (ticket closed) or send to support.
- Follow-ups: questions added in the thread; follow-up on a closed ticket creates a new ticket titled "follow-up to: <original title>" with a reference number in the description that must not be removed.
- Closing: the pharmacy accepts the solution (with confirmation); support may also close a fully answered ticket if the pharmacy asks nothing further within 5 days.
- Requirements: search by full text or requirement number; lists Open, Fulfilled, Rejected (rejections follow product-management criteria that are periodically reviewed and may lead to re-evaluation); columns id, title, demand level, classification; inquiry on a requirement pre-fills the title; fulfilled requirements link to the help topic that describes the implementation.
- Closed tickets and fulfilled requirements remain visible 2 years after their last update.
- Creation, changes and state changes are signalled in the info centre; read/unread per item.
4.23 Acoustic signals [GENERIC]
- Events that may play a sound: incoming high-priority message, new stock-transfer order, imminent send time of a purchasing cart, incoming supplier call (listed), automatic back-order quantity determined, automatic order attempt.
- Two-level configuration: which tone per event is pharmacy-wide (each branch separately); whether a tone is played per event is set per workstation/till, plus "minutes before cart send time" for the cart alert. Recommendation: give every event a distinctive tone; switch off the back-order tone on workstations mainly used for invoicing order entry. Volume at server via monitor controls, at workstations via OS volume.
4.24 Remote opening of a branch/partner pharmacy [GENERIC]
- Menu Kooperation lists every partner/branch pharmacy reachable by remote desktop; selecting one opens the session.
- Right "Collaboration – remote: connect to partner pharmacy"; which pharmacy may access which is configured by vendor support; seats used for partner connections are counted separately from licensed remote-work seats.
4.25 Cash recycler integration at the till (CashGuard) [GENERIC]
- Concept: a closed cash system replaces the drawer. The till sends the amount due; the customer feeds coins (single slot or bulk "auto-coin" hopper) and staff feed notes; the device counts, the till's "given" amount updates live, and after confirmation the device dispenses exact change. It also acts as a safe. Benefits claimed: no change errors, no shortages, faster service, no hand counting at closing, fewer nickel-allergy issues for staff, manager need not be present at closing time.
- Hardware facts: note recycler with four cassettes (€5, €10, €20, €50+€100); €200/€500 notes are not loaded — staff exchange them from a separate float in the safe and feed only the needed smaller notes. Coin recycler with up to eight denominations of one currency, one tube each (200–550 coins), a display (inserted amount, stock info), coin tray in a drawer. Console with a green "change" key (emptying, change an inserted amount) and a red "cancel" key (return the inserted amount without booking); both together reset the device.
- Exclusive access: the device is driven either by its till or by the BackOffice software, never both; on IXOS start the till always connects (device shows a customer greeting).
- Supported till flows:
- Cash payment – payment type "CashGuard" preselected in the total window (can switch to another type and back). Coins can be inserted already during item entry. Enter confirms; overpayment → change dispensed, return shown; underpayment → "settle remainder" window (other payment type or credit); the inserted cash is kept, except when the additional card payment fails at the terminal. A further cash top-up is not possible there — the operator must escape, eject all, and restart payment (partial-payment flow). Enter again finishes the sale.
- Abort / eject – "eject all" in the CashGuard window returns everything inserted (customer short of cash, wrong customer inserted coins, customer confused).
- Pay-in / pay-out (e.g. postage) – the pay-in amount is the counted inserted amount (field locked); pay-out amount is typed and dispensed; a reason is entered; booking then complete for the till.
- Cancellation / sale edit – if the cancellation exceeds the sale, the total window shows a negative amount; it is passed as pay-out and dispensed; a positive remainder is shown on the device as amount to insert.
- Not supported: changing the payment type afterwards in sales management, or in the total window after the given amount has been confirmed.
- Courier settlement: a returning courier can pay in the tour's cash through the device.
- Operational prerequisites: check that the pharmacy's insurance covers cash stored in the device (usually accepted). Regular cleaning is mandatory to keep the maker's warranty/liability (clean the coin validator inside and out, the coin chute — ideally with PTFE spray — and the hopper sensors). Use cases not described in the help are either unsupported or set up by the service partner; settings should be changed only with the service partner.
- Connection handling: parameter "port" (COM1–COM4) per workstation; automatic connect at start; status "logged on"/"logged off"; each logon/logoff logged with operator and till number; manual log off/on in the CashGuard window (opened via a button in the sale window or the drawer key). The button icon shows OK / warning / error.
- Offline fallback: (a) at the same till: press red cancel to eject inserted money, log off CashGuard (stops reconnect attempts); the total window then shows coloured note icons meaning "cash without device"; finish the sale with a separate float; log on again after repair. (b) Move the sale to another working till; the faulty till keeps retrying and reconnects automatically when fixed.
4.26 Cash device status and error handling [GENERIC]
- The CashGuard window opens automatically when a problem blocks completion (e.g. no suitable change) at confirmation of the given amount.
- Three states: OK; warning (fill hint: a warning level crossed or a coin tube empty); error (connection fault or device error, e.g. no change possible).
- Messages list: red errors first, then yellow warnings, each newest first. After fixing, "reset". With the bulk coin unit, always start with a reset (also releases jammed coins).
- If not fixable, finish the sale with the offline fallback. BackOffice actions need the till disconnected.
- Error codes and actions are tabulated in §6.6.
4.27 Cash device BackOffice [GENERIC]
- Installed on the server, linked to devices through a serial-to-network converter; staff open it via remote desktop from a secondary workstation. Login with user name/password, idle auto-logout (minutes agreed with the vendor). Note: the POS vendor now only supports existing installations; new installations go to the device maker.
- Functions: recommended changes (suggested refill per device and total; notes as count, coins as rolls; a "compensation for lowest note" line so change can be paid in notes only; printable; prevents overfilling); empty according to a saved list (not supported); empty to change float; reconciliation (no emptying); empty last reconciled device; empty single denomination; refill; correct coin stock; unlock coin unit; warning levels; BackOffice and user settings (vendor technician only); help.
- Device tree status icons: red lamp (no till connection), green lamp (till connected), lamp with yellow frame + spinning coin (stock warning), question mark (BackOffice cannot reach device), red exclamation (device error, code also at till), blue exclamation (time-locked), crossed red circle (device–BackOffice link cut). A spinning coin at the bottom indicates any device outside its warning levels.
- Stock view: bar per denomination: red = outside warning levels (till warns too) → refill if below, controlled exchange if above; yellow = approaching; green = within levels including tolerance. Counts visible only when logged in.
- After any configuration change, "update till" pushes the settings to the selected device.
4.28 Device reconciliation, emptying, refill, inventory [GENERIC]
Detailed procedures in §5.6–5.9; rules in §6.5. Key points:
- Reconciliation (pharmacist level only) can be run any number of times and never empties.
- Emptying comes in three forms: last reconciled device down to the float (pharmacist or technician), any device down to the float (pharmacist), single denomination by quantity or "to zero" (pharmacist). Notes go into the attached collector, coins into the coin drawer; an emptying report prints.
- Refill raises the float without dispensing; confirmed in BackOffice; refill report printed; no other BackOffice work and no till logon until confirmed.
- Change composition ("change float") keeps the total: inserted money is paid back in the largest possible denominations (to stock small coins); fast coin refill feeds whole coin rolls through the device keypad; controlled exchange returns one inserted note/coin in a chosen denomination (e.g. €20 note then a €1 coin → 21 × €1).
- Correct coin stock sets the true count when known (no payout).
- Inventory of notes (empty to zero → count → compare with report → refill) and coins (count per denomination on device keypad → empty → compare → refill within 10 s).
4.29 Customer display [GENERIC]
- Graphic screen at the till via USB; legacy line displays remain supported. Configured in the company master.
- Idle: welcome page with screensaver content (image, video, or an HTML page such as the pharmacy website); header with pharmacy name and logo unless the screensaver is full-screen. When IXOS is not running the desktop background is shown (without support info).
- During a sale: operator name (optional), pharmacy name, date/time, the last scanned item's price, running total, grand total at completion, given and change amounts for cash sales only (not for card/direct debit) — change appears as soon as the received amount is typed; closing line thanking the customer; change labelled "back". Header/footer colours configurable. Rationale: helps elderly and foreign-language customers check prices.
- E-prescriptions: while prescriptions are fetched from the national server the display says so; a toggle key shows the retrieved prescriptions (article number, name, dosage form, dosage …) to the customer and hides them again; at transfer to the till the number of prescriptions with date/time is shown; if none are available it says so and asks to remove the health card. (FAQ: on card insertion the display shows how many e-prescriptions are open and how many items each contains.)
- Moving a sale to another till returns the old till's display to the welcome page; switching the operator register shows that register's sale.
4.30 Price importer for external selling-price lists [GENERIC]
- Purpose: let a cooperation or pricing consultancy supply own selling prices as CSV.
- Mechanics: file copied manually into a fixed server import folder (created on first use); import into any chosen price list; imports are independent of stock status (stocked and non-stocked items updated). After successful import the file is moved to a "read" subfolder with a date stamp.
- Import type per price list: none (default; also stops an existing import), manual, on file change (only when a new file is present), scheduled (time table; e.g. 19:00 after closing so new shelf labels can be printed; nothing happens if no new file). Changing the type asks for confirmation.
- Options: remove articles no longer contained in the file (they fall back to a lower-priority price list); additionally remove articles from a previous import that carry a valid-until date.
- Import now shows a result message in every case; results (complete, partial with reasons, failed) are also posted in the System mailbox.
- Use: place the imported list at the top of a price usage model (above even the "own selling price" list) so it is consulted first; manual overrides in the file or in article management remain possible; price history is visible in article management.
- Deactivate: set import type to none (link to the file removed) and confirm.
- CSV formats: §6.8.
4.31 Pricing consultancy variant (Baufeldt & Partner) [DE-SPECIFIC]
General idea: outsourced price consulting fed by sales statistics exported by the pharmacy.
- The consultancy files the installation order with the POS vendor; vendor staff import two report queries via remote maintenance: an article statistics query and a customer-card sales analysis.
- The pharmacy runs both queries, exports them to spreadsheet files and e-mails them itself to the consultancy (vendor staff are not allowed to, for data-protection reasons), typically once or twice a year. The consultancy returns a tailored price CSV which goes through the importer.
4.32 Online fax interface [GENERIC]
- Interface to two online fax providers (fax.de and faxverteiler.com); transmission, fax archive (incoming and outgoing) and data protection are the provider's responsibility. Benefits: no printing/media break, no fax machine, central online fax management.
- Prerequisite: own account with the provider; credentials entered in company master "external services".
- Available for: sending purchasing carts from goods logistics (as transmission type), prescription requests to doctors, any document from print preview, the copier function.
4.33 External DMS link (ELO) [GENERIC]
- Printable IXOS documents can be filed in the external DMS manually or automatically; documents can also be scanned module-wise or via the copier.
- Automatic per print-form type (print settings, best for all workstations): choose the virtual "ELO printer" (archive only, no paper) or "additionally file in DMS" (print and archive). Option to let a defined user group change this preset in the print preview.
- Manual: print preview → adjust printer → exclusively or additionally to DMS.
- Example SEPA mandates: a blank mandate (no customer data) lands in the DMS postbox in a folder named after computer and DMS user; a customer SEPA notice with address (with or without mandate reference and bank details) lands in the import directory under "consents"; the signed mandate should be scanned into the customer contact.
- Transfer to the DMS postbox/archive may take up to 5 minutes; the user then completes metadata (document type, voucher number) in the DMS client and files the document. Failed transfers are cached and retried cyclically.
4.34 Rx.secure — effective-dated prescription master data [DE-SPECIFIC]
General idea: keep versioned (effective-dated) price, contract and dispensing-rule data so any past transaction can be priced, checked and reprinted as of its dispensing date.
- Keeps the data of all master-data releases (twice monthly, 1st and 15th) for 24 months; for any dispensing date in that window the correct discount contracts, prices, import relationships and aid-supply contract data apply.
- Integrated in till, prescription scan, prescription management, invoicing, article management, comparison searches and the aids-contract database.
- Use cases: printing a prescription the day after a data switch (emergency the night before; adding an item to a late-submitted prescription) by setting the dispensing date; correcting prescriptions found faulty in prescription checking across release boundaries; correct reprint of prescriptions returned by the billing centre; investigating claw-backs and arguing them with the payer; researching prices up to 24 months back. Searches dated before a 2019 framework-contract change follow the old rules.
- Rule: changing the dispensing date within the current release period leaves contract and price data unchanged; outside it they may change.
- Only fields relevant for legally mandated searches and dispensing decisions are historised (§6.9).
4.35 Courier route optimisation (ApoTune) [GENERIC]
- Third-party service (by BLUEBIZZ); requires the delivery-management licence and a separate contract. When a tour is handed to the courier in delivery management, its stops are sent to the service, which optimises routes over all transferred addresses and may split them into one or several tours.
- Recommendations: create only one tour in IXOS regardless of distances (otherwise reconciling billing across re-split tours is hard); each tour needs at least two stops; transfer only complete tours.
- Courier gets the stop list on a tablet and packs bags in that order; the IXOS delivery list (different order) should be used only internally — set "print count delivery list" to 0 and optionally print the internal list with articles instead. The pharmacy can see the courier's live position and ETA per customer; the customer signs on the tablet.
- No back-channel: deleting a tour in IXOS is not propagated; tour billing is done manually in IXOS.
- With "data transfer active", address fields become mandatory (marked *) in the till's pickup/delivery dialog, invoicing delivery conditions and courier task editing; phone number is sent if "call customer" is ticked; time windows (from/until, e.g. practice hours) are sent and used in route planning; free tour notes are not supported.
- Transfer outcomes (on "close tour"; only the focused tour is processed even if several are selected): incomplete contact data → error, tour not handed over, nothing sent; data complete but service unreachable → error, tour is handed over and flagged, retry later or print paper list; success → handed over. Retry from the deliver/bill tab. Each tour carries a unique IXOS id → repeated transfers never create duplicates.
- Install on a secondary workstation or office PC, not on a till; may be placed in the server's pharmacy folder to be callable from tills.
4.36 Client deployment on own hardware (WinClient / ClickOnce) [GENERIC]
- Paid option to run IXOS on pharmacy-owned Windows devices (macOS/Linux/iOS/iPadOS only through virtualised Windows 11; not iPad mini; not inside a VM for the client itself). Default role is secondary workstation; till role costs extra licence/installation fees. Supports peripherals on Windows (document scanner, barcode scanner, prescription printer, fingerprint scanner).
- Operating models: DIY (own hardware; customer responsible for OS, programs, firewall, antivirus, updates; vendor cannot guarantee support) vs full service (vendor-managed devices).
- Pre-check tool compares the device (RAM, OS, disk, GPU, screen resolution, network speed, CPU, storage medium) with the vendor's reference platforms (comparable and next higher) and states in green/red whether installation is possible and until when the platform is supported. Minimum OS: Windows 11 64-bit.
- Display: minimum 900 px height, recommended 1280×1024, OS scaling ≤100%.
- Admin rights: installation/updates need admin elevation; UAC must prompt (set to the default level) rather than block.
- Prerequisite components checked at start/update: auto-installable ones with a grace period during which the user may postpone ("start IXOS") — after the grace period or once a component is installed, postponing is no longer possible; manual ones are downloaded via links from the help.
4.37 FAQ-derived operating knowledge [mixed]
Recorded in §6.10–6.16 (courier app, DMS, e-prescription, ePA, institution card, pharmaceutical services, in-store TV, customer app/online payment).
4.38 Online-paid app orders: refunds and closing (from the customer-app FAQ) [GENERIC]
- Online payment through a payment provider (card possible without provider account); vendor passes only the amount and cannot see payment data. Prepayment is normally not yet a contract; the pharmacy may refuse the order and must then refund.
- Online payment is not offered if the cart contains a statutory-insurance prescription (private prescriptions are fine), any item quantity exceeds 3, the order total exceeds €500, or a branch is chosen for pickup; the buyer is told why.
- Refusal with refund: in the order list mark done → choose "refund" → full refund through the interface. Possible only until the order has been closed at the till with total; after that, refund in cash or in the provider portal. Partial refunds only in the provider portal; amount differences during processing are settled at the till.
- Already refunded in the portal → mark done with "done" (not "refund"); a duplicate refund is rejected by the provider (error mail can be ignored). For an open pickup refunded in the portal: bring it to the till, cancel the items (or set to 0) and choose cancellation mode "online" so no cash is paid out (same for partial refunds).
- Online payments count as "online given", not cash, in till closing; when cancelling an online-paid pickup switch to "online given".
- Do not use "clean up pickups" for online-paid orders: it can only book a cash cancellation with a simultaneous cash deposit; cancel via the till instead.
- Provider disputes are handled in the provider portal only. Onboarding/disconnection of the merchant account in company master → external services; on owner change disconnect the old account first; one merchant account can technically serve several branches (tax caution). If the pharmacy revoked the usage permission in the provider portal, it must disconnect and onboard again. Support routing: provider-side payment errors (e.g. insufficient funds message the buyer disputes) → provider; repeated other payment errors → POS vendor.
- Other customer-app facts from the FAQ (app itself is covered in another chapter): a digital receipt also asks whether to forward the receipt to the app; scanning an e-prescription collective code shows the customer which article they will get under their discount contract and when it is available; prescription and OTC items can share a cart (an e-prescription creates a partial order); guest ordering without registration (mandatory fields, privacy consent, pickup or courier, terms, comment); prescription items without photo/e-prescription: on the web choose statutory/private and enter the insurer id, in the app only if the insurer id is already stored on the contact; re-order from "my medicines"/"my orders"; per-order message to the pharmacy; switching the linked pharmacy via account settings (search or pharmacy QR code); same login across app and web.
4.39 Billing-centre good practice (DRZ notes) [DE-SPECIFIC]
General idea: data-quality practices that reduce payer rejections when prescriptions are billed through a clearing house.
Summarised in §6.17.
4.40 Tips & tricks catalogue [GENERIC]
An index of stand-alone how-to articles (targets outside this slice). Its topic list signals recurring operational needs a designer should expect: drug database look-ups (international drugs, dossiers, SmPC search, non-drug info); pickup slips, labels and processing time; cross-branch sales; app interior image and courier radius; article-management views, aut-idem and import search configuration, own product images, expiry column, statistics transfer; annual industry survey; fixed-supplier cleanup; demand determination; narcotics documentation (corrections, electronic with digital signature, issue date); federal medication plan scan; CAVE and customer interactions; cross-selling images; accounting export (DATEV, pay-in/out accounts); raw-material testing monographs; ePA handling; e-prescription info, structured dosage, active-ingredient prescribing; invoicing cleanup; logo and bank details; legal guardians for care patients; aids billing (made-to-measure stockings, attachment printing, online contract portal); annual inventory guide and year-end checklist; till operations (item position, dosage labels, missing prescription, extra costs to payer, gross margin display, advance delivery, change payment type); receipt contents and printer consumables; fiscal till inspection and TSE reporting; till TV digital receipt; deposits; picking-robot interface and output chute per contact; privacy settings, duplicate customers, consent form, new wholesaler, co-pay exemptions; customer evaluations and co-payment lists; assisted reproduction billing; replenishment lists, locations, stock valuation; supplier offers, condition sheet, delivery days, turnover targets; energy saving; defects and back-orders; emergency-fund reporting; non-availability rules (several small packs, children's urgency list, proof, partial quantities); receivables; online availability inquiry; staff fingerprint, new operator, roles; care-aid billing and electronic approval; effective purchase price, human drugs for animals, discount campaigns; QR code on invoices, e-mail invoices to home residents; starting sales with reservation "not present"; claw-back connector data; e-prescription management; scanner cleaning; compounding price basis and Latin/German ingredient search; vaccination billing; securPharm operation; national pharmacy directory, emergency-duty data; telemedicine billing; paperless goods receipt by delivery advice, returns without shipment; gift vouchers.
5. Workflows
5.1 Plan a recurring team task and control it
- Manager (right "Notes: edit task") opens calendar, task list or task control → New → Task.
- Chooses assignee (employee or pharmacy), optional deputy, subject, start/end or all-day, description, priority.
- Opens the recurrence dialog: e.g. monthly on the last Friday, no end date → OK.
- Each day, at the first activation of the responsible operator's register, the today's-tasks pop-up lists due and overdue occurrences; the operator opens, snoozes (1/2/4/8 h, 1 day) or continues.
- After doing the work the operator marks the occurrence done (time and operator logged); an info text can be attached.
- The manager reviews task control: series with overdue occurrences in red; statistics show due vs done vs overdue; the log tab lists who completed which occurrence when.
- Mistaken completion → "mark undone" removes the completion entry.
- To stop the routine without losing history: end the series early (do not delete; deletion removes all logs).
5.2 Execute an interactive report task
- Task (created in Reports) becomes due → appears in pop-up/task list.
- Execute → Reports opens with the stored query (and variables).
- User reviews, optionally bulk-edits results → "query done".
- Back in Notes the task is done; a PDF of the original result (before) and of the edited result (after) is stored (licensed add-on); operator and time of last execution stored.
- If the automatic run of a report task fails, a message with the cause is posted in the "Automatic tasks" folder.
5.3 Process a customer-app order end to end
- Order arrives → pop-up on every workstation (unless disabled per workstation) → open order.
- Order list: read customer messages, add internal info, optionally assign processor; print prescription images if attached.
- Execute → Rx items to the prescription window, others to the till; not-in-stock items prompt a customer message.
- At total: if all items available, status becomes done and the "ready for pickup" message is proposed; if back-orders are needed, the "not in stock, we will notify you" message is proposed.
- When the back-order is booked in goods receipt, a new message is proposed; substitutions (discount contract, successor item, pack splitting) also trigger a proposal.
- Order moves to Done; messages are marked read. Deleting or manually completing the order also proposes a message. Online-paid and refused orders follow §4.38.
5.4 Receive an e-prescription via secure mail
As in §4.13: automatic conversion (≤3 prescriptions merged per sender/patient burst) → pop-up → order list → execute → prescription scan with reservation preset → till subtotal with "customer not present" → total with pickup/delivery dialog → done → prepare goods.
5.5 Raise and close a support ticket
- Support button (any module) → New request → title, category, urgency, description.
- Attach up to 8 files/screenshots/scans; leave "remote maintenance today" on if remote analysis is acceptable.
- Send → the assistant proposes a solution → accept (closed) or send to support.
- Conversation continues in the thread; the info centre signals updates.
- Accept the solution (or support closes it after 5 days of silence). Further issue → follow-up request referencing the closed ticket.
5.6 Cash sale with the cash recycler
- Items entered; customer may already insert coins.
- Total window: payment type preset to the device; notes fed by staff; "given" updates live.
- Enter → device dispenses change; or remainder window for underpayment (other means/credit).
- Enter → sale closed. To abort: CashGuard window → eject all.
- Device failure: red cancel key → log device off at the till → sell with manual cash float, or move the sale to another till.
5.7 Daily closing with the cash recycler (prompt joint variant)
- At the till: closing receipt — Z (this till) or S (all tills). One per day after closing or before opening is sufficient.
- CashGuard window → log off (frees the device for BackOffice).
- On the server (via remote desktop) start BackOffice, log in as pharmacist.
- Reconciliation → choose device → result shown; print it (File → Print → mark last reconciliation → print marked).
- Compare with the Z/S receipt; the "total cash" figure of the Z/S receipt goes into the cash book. All devices included in the IXOS closing must be reconciled too, and no sale may occur between the two closings.
- Optional emptying now or later (5.8).
- Back at the till: log on to the device to resume selling.
Separated variant: Z/S daily into the cash book; device reconciliation only every few days; traceability via kept Z/S receipts and the cash-book listing. The next emptying always follows the last reconciliation.
5.8 Empty a cash recycler
- Ensure the till is logged off (red lamp in BackOffice).
- Choose: empty last reconciled device / empty to float / empty single denomination (enter quantities or "to zero").
- Take the note collector to the device, remove the note tray, attach the collector. Device display shows CLOSED; when it shows "CLOSED, emptying running", press the green change key.
- Notes (and, for single denominations, coins into the coin drawer) are ejected; finished when CLOSED appears and a beep sounds; the emptying report prints if configured.
- Remove the collector; BackOffice "update till"; at the till log on again (this disconnects BackOffice).
5.9 Refill / maintain the float
- Refill: till logged off → BackOffice refill → choose device → physically insert → confirm refill → report printed. No other BackOffice action meanwhile; finish before any till logon.
- Fast coin refill with rolls: unlock coin unit (BackOffice or log off/on at device) → wait for blinking star → keypad down, up, OK → refill menu → "refill coins" → open coin drawer within 10 s → choose denomination → OK → set number of full rolls → OK → repeat → C to exit → unwrap rolls (no paper) and pour in → display shows amount → green key → equivalent paid out in the largest denominations (float unchanged). Errors → coin correction or inventory.
- Controlled exchange and change composition as in §4.28.
5.10 Cash recycler inventory
- Notes: empty single value "to zero" for each note denomination (also those the counter says are empty) → attach collector → green key → report → physical count vs report → discrepancy → internal procedure → refill the notes → confirm refill (no till logon in between).
- Coins: container ready → unlock coin unit → enter code → menu "count coins" → note the count per denomination on an inventory sheet → select denomination → OK → it empties; display shows count → OK when silent to save → compare → refill via coin drawer within 10 s → next denomination → C twice to exit.
5.11 Set up price import
- Obtain CSV from the service provider (or build one).
- Copy to the server import folder.
- Prices & calculation → create/open the target price list → import prices → choose type (manual / on file change / scheduled with times) → choose file → options for removing dropped/expired articles → import now.
- Check the result message (also in the System mailbox).
- Put the price list at the top of the relevant price usage model.
- Later: drop new files into the folder; processed files move to the "read" folder.
5.12 Hand a tour to the route optimiser
- Delivery management → plan/pack → one complete tour (≥2 stops) focused → close tour.
- Outcome per §4.35; on transfer failure retry from deliver/bill ("send to ApoTune") or print a paper list for the courier.
- Courier works from the tablet; pharmacy watches position/ETA; customers sign on the tablet.
- Bill the tour manually in IXOS; delete cancelled tours manually in the service.
6. Business rules and calculations
6.1 Task visibility and time windows
- Task list "Current" = overdue + today + next 2 days + done; "Week" = overdue + this week + done; "Month" = overdue + this month + done.
- Order list "Current" = active today, tomorrow, day after + overdue + done today; "Week" =
active next 7 days + overdue + done today/last 7 days; "Month" = active next 30 days + overdue
- all future + done today/last month.
- Task control "Current" = overdue + current + next 2 days (the overview text also mentions a window of the last two and next two months).
- A task is overdue when its due time has passed and it is not done (shown red). Series are red when any occurrence is overdue.
6.2 Reminders and notifications
- Appointment reminder exactly 15 minutes before start (appointments only, not tasks).
- Today's-tasks pop-up at first operator-register activation per day; again for newly added same-day tasks; snooze durations 1/2/4/8 h or 1 day.
- New orders signalled immediately on all workstations unless the workstation opts out.
6.3 App-order processing status (derived)
| Status | Condition |
|---|---|
| not processed | No subtotal has been transferred to the till. |
| ordered | ≥1 subtotal at the till and no position fully available. |
| partially ready for pickup | ≥1 subtotal at the till, ≥1 position with back-order and ≥1 position partially ready. |
| completely ready | All items of all subtotals fully ready. |
| changes, completely ready | All ready but at least one item's deliverable quantity differs from the ordered quantity. |
| done | Whole order done. |
6.4 Message retention and read semantics
| Item | Rule |
|---|---|
| System/internal messages | Read state per user. |
| KIM messages | Read state shared across all users; auto-deleted after 3 calendar months (incl. archive). |
| E-mails | Auto-deleted after 3 calendar months. |
| Branch messages | Deleted after 2 days. |
| Reminder messages | Deleted after 2 days. |
| Deleted folder | Purged after 1 week; restore returns original validity. |
| Personal messages | Never auto-deleted. |
| Duplicate-merge difference | Info centre up to 7 days (unless outranked), deleted after 3 months. |
| eCall closed tickets / fulfilled requirements | Visible 2 years after last update. |
| eCall ticket auto-close | Support may close a fully answered ticket after 5 days without response. |
| Message display window | "Visible until" date limits info-centre display; "expires from" date deletes the message. |
6.5 Cash recycler rules
- Exclusive control: till or BackOffice, never both; BackOffice actions (warning levels, refill, emptying, inventory, coin correction) require the till to be logged off.
- Underpayment keeps inserted cash; exception: if the remainder is paid by card and the terminal fails, the cash is returned.
- Payment-type change after confirming the given amount is not supported.
- Cancellation amounts larger than the sale are paid out by the device.
- Emptying "after reconciliation" empties to the float based on the last reconciliation.
- Float composition, fast coin refill and controlled exchange never change the float total; refill increases it; emptying decreases it.
- Change dispensed always in the largest possible denominations unless a controlled exchange specifies the denomination; controlled exchange accepts only one note or coin at a time.
- Warning levels per denomination (low and high) drive status icons and bar colours; maximum capacity fixed by the manufacturer.
- Coin drawer must be opened within 10 seconds after unlock.
- Note collector: more than five connection attempts, or swapping collectors during a running emptying, aborts the emptying (restart required).
6.6 Cash recycler error codes and operator actions
| Code | Meaning | Action |
|---|---|---|
| 1 | Faulty memory chip in CPU | Call service. |
| 2 | Note cassette motor blocked | Check drive belt; as pharmacist run inventory "empty to zero" for that note; restart; refill notes; else service. |
| 4 | Counter error in note/coin acceptance | Restart; else service. |
| 5 | Note sensor covered after rejection | Service. |
| 6 | Note sensor error | Remove stuck note; inventory "to zero" for the cassette; restart; refill; else service. |
| 8 | Length measurement error | Remove stuck note; restart; else service. |
| 9 | Note cassette inserted wrongly | Re-seat; service if persists. |
| 10 | Device closed while till requested pay-in/out | Log on and off at the till. |
| 11–17 | Note dispensing interrupted during emptying (11 = cassette with highest note, 12 = second highest …) | Check note recycler for obstructions; inventory of that value; service if repeated. |
| 21–29 | No communication with note recycler or active flap (per cassette) | Check cassettes seated; restart; service. |
| 30 | Note of wrong size at payout | Service. |
| 36 | Note cassette overfull | As pharmacist, empty the cassette. |
| 41–49 | Note payout error (per cassette) | Service. |
| 50 | Coin carousel (slot model) / step feeder (hopper model) blocked | Open unit, remove blocking coins, put them in the right tube. |
| 51 | Casing protection of note recycler not activated | Service. |
| 52 | Dye/staining unit activated (slot model; anti-theft) | Service. |
| 53, 54, 56, 57, 58 | Coin feed error / coin validator error / no communication with coin feeder or validator(s) | Reset with both console keys; service if persists. |
| 55 | Coin validator sensor covered (hopper model) | Remove stuck coins. |
| 59 | Coin validator reset error (hopper model) | Reset; check change actually paid and compensate any shortfall; coin inventory. |
| 60 | Change error — no change payout possible | Find the denomination to refill; if coins present check for blockage; remove and do coin inventory. |
| 61 | Communication lost between device and BackOffice (e.g. during emptying) | Restart. |
| 62 | Maximum change payout limit exceeded | Check the max-change setting in BackOffice. |
| 63 | Coin recycler content mismatch | Coin inventory; restart. |
| 64 | No communication with emptying box | Check collector correctly attached and undamaged. |
| 65, 66 | Cover error / electric lock failure of active flap | Service. |
| 67 | Note collector refuses notes (cover error) | Unplug collector power 5 s to release it, remove, restart emptying. |
| 68 | Collectors swapped during emptying | Emptying aborted; restart. |
| 69 | More than five attempts to attach collector | Emptying aborted; restart. |
| 81–95 | A denomination exceeded its maximum (81 = highest coin value …) | Inventory of the cassette/coin unit. |
6.7 Customer display rules
Given/change amounts shown only for cash payments; e-prescription list shown only while the operator toggles it on; display follows the sale when it is moved between tills or registers.
6.8 Price import CSV rules
- Any file name; one record per line ending CR+LF; semicolon separator; spaces around fields ignored; unsorted.
- PZN: valid 7- or 8-digit number; leading zeros may be omitted.
- Price: positive decimal with two decimals, or a lone minus sign
-(meaning not explained by the help). No thousands separators. Consultancy format: comma decimal separator; standard format: comma or dot. Tolerances: >2 decimals are rounded to 2; a dot is accepted as decimal separator if there is no comma. - Standard format validity (optional):
<PZN>;<price>;<valid-from>;<valid-to>, datesDD.MM.YYYYorYYYY-MM-DD; valid-to is inclusive (until end of that day); valid-from may be empty; without dates the price applies from import until further notice. One validity range per line; several non-overlapping ranges → several lines for the same PZN. - Examples (standard):
8012430;2,39;01.05.2015;31.05.2016,5899519;4,60;;15.05.2016,2916217;33,00. - Removed articles fall back to lower-priority price lists if the removal option is on.
6.9 Rx.secure historised fields
| Historised (effective-dated) | Computed from current + historical | Not historised |
|---|---|---|
| pharmacy purchase price; dosage form; pack unit/size; purchase price; reference price (Festbetrag); statutory-insurance note; statutory-insurance selling price; import flag; negative aut-idem reference-price flag; standard pack size class; selling price; co-payment + extra cost (value and icon); distribution status; dispensing conditions; pharmacy retail price; extra cost; co-payment | gross margin; favourable-margin icon | product group; supplier/provider; article names; info icons; preferred-article flag; blister flag; own purchase/selling price icons; GTIN/EAN; aid number; customer-article flag; short code; storage icon; partner stock info; storage location (and icon); crushability; online order-query icon; PZN; status; divisibility; distribution information icon |
Changing the dispensing date within the current release period leaves contract and price data unchanged.
6.10 Courier app (U5) rules (FAQ)
- Runs as a website in the default mobile browser (Android/iOS; installable as web app on Android); everything except tour start works offline and syncs later.
- AES-256 end-to-end encryption; one key per tour derived from a device-specific tour password; change the password if a device is lost; protect devices with fingerprint/PIN.
- Live feedback only while the app is open; tour retrievable on a device for 4 days unless finished; one device per tour at a time; device swap allowed (password by phone); data kept on device until browser cache cleared or a new tour arrives; cloud keeps only anonymised data.
- Paper-list mode keeps optimisation/visualisation but loses customer SMS/e-mail notifications, courier feedback and simplified billing; switching from digital to paper only before the tour is handed over.
- Geocoding needs recipient name, city, postcode, street and house number; otherwise place the point manually on the map.
- Care-home residents at one address count as one tour stop; usage (distinct stops per month) is shown under add-on modules (billing basis).
- Per new tour choose optimiser service, own courier app or paper; settle old optimiser tours before switching. Requires map/geodata services.
6.11 DMS rules (FAQ)
- Own letterhead: header/footer content is not archived, only body; document the procedure for scan-and-replace compliance.
- Password-protected PDFs cannot be imported.
- Search masks: new (last 48 h), active (not archived), stamped, tax office (last closed month, flagged relevant; late scans need a custom filter), awaiting qualified signature.
- Moving = changing document type (one-way structure); no drag-and-drop.
- Non-invoice documents generated by IXOS land in the inbox and must be keyworded manually.
- Deletion: only unkeyworded inbox documents can be deleted; filed documents can only be hidden; retention period per document type deletes automatically on expiry; deleted inbox documents cannot be restored (but may be re-scanned). Predefined document types can be deactivated, not deleted; own types deletable without affecting filed documents. Archived documents can be reactivated.
- Supplier goods invoices: scanned at the end of invoice valuation in goods logistics (one-way); missed scans only via the archive's rescan; never alter values. Cost invoices (non-goods suppliers) scanned/imported in the DMS with type "cost invoice" after creating the issuer in the address book (name mandatory); wholesaler collective invoices use their own type. Keyword top to bottom; take date, number and gross amount from the PDF by right-click. Extra pages can be added to a voucher only from paper.
- Office documents: save as PDF, import.
- Card-terminal day-end: manual daily closing with integrated terminal attaches EC slips automatically (terminal must not be in power-save); automatic daily closing does not — print each EC slip to the DMS from sales management and keyword as daily closing with the right date; non-integrated terminals → scan slips. Retention: integrated → day-end slip suffices; non-integrated with provider digital access → day-end suffices; without → keep each slip. New tills must be added to print settings. Without the card-payment licence, scan the terminal's closing slip.
- Supported scanners: only Canon DR-M140, Canon DR-M260 and Fujitsu fi-7160.
6.12 E-prescription rules (FAQ) [DE-SPECIFIC]
- Pharmacy may correct status, dosage, quantity, dispensing deadline; keep dosage structured.
- Sale blocked for prescription types not yet permitted electronically: narcotics, substitution dosing machines, thalidomide-type (T) prescriptions, practice supplies, medical aids, dressings, blood-glucose test strips, enteral nutrition.
- Free pharmacy choice by the patient (card, app or printed token).
- Prescriptions changed at the sale or carrying certain special codes need a later qualified signature with the pharmacist's professional card (batch signing with PIN in prescription management).
- Corrections possible until the billing centre's acceptance deadline.
- Validity typically 28 days at statutory cost (exceptions e.g. discharge prescriptions).
- From July 2026 up to four items on one printout; per item: redeem, defer in pharmacy, or return (released for other pharmacies).
- Dispensing receipt must be retrieved by end of the working day after dispensing; IXOS does it automatically.
- Doctors cannot edit; they delete and reissue; pharmacy can record a correction and whether the doctor agreed.
- Card insertion shows all redeemable prescriptions of the last 100 days (not redeemed ones).
6.13 ePA rules (FAQ) [DE-SPECIFIC]
- Medication list (eML): automatic retrospective list of e-prescriptions and dispensations, usually 12 months; manual additions by doctors/pharmacies; only non-e-prescription additions deletable; manual additions cannot be edited after first save (delete and recreate).
- Medication plan (eMP): curated current medication with structured dosage; editable; history of versions; items can be taken from eML or a scanned paper plan (with dosage).
- Suggestion: on non-e-prescription sales, a blinking ePA button proposes an eML addition with items from the current sale and history (regular customers: plus sales of the last 90 days); needs a customer assignment and ePA access (e.g. card inserted).
- Patient objection → no eML/eMP; patients can block individual providers.
- Access points in IXOS: e-prescription dialog, sale, prescription management, customer contact details and the customer at-a-glance view; tabs switch between eML and eMP; eMP printable.
6.14 Institution card on owner change (FAQ) [DE-SPECIFIC]
- Apply: premises in the chamber's district, applicant holds professional card and is the future owner; usually ≤8 weeks before takeover; ~8 working days to delivery.
- New card for: new founding, name change, takeover, replacement of the partner who originally applied; not for a mere legal-form change. Predecessor's card may be used transitionally; old card blocked (usually by the chamber) after the new one is commissioned. Same telematics id kept only on name change, partner constellations and replacement cards. Directory certificate available within ~48 h.
6.15 Pharmaceutical services (FAQ) [DE-SPECIFIC]
- Phone number optional; paper signature required (digital not legally sufficient); contract signed per service delivery; predefined candidate queries in Reports (customers category); walk-in customers can only be billed at the till — documentation needs a registered customer; repeat services prefill name, birth date, doctor, diseases, allergies and items of the last 6 months; manual confirmation "mark as delivered" (green tick) except medication review, which confirms automatically when completed; dosage taken from maintained plan or scanned plan QR; plans scannable with item or document scanner.
6.16 In-store TV (FAQ) [GENERIC]
- No picture: connectivity, router changes, IT changes, power, wrong input source.
- Emergency-duty info missing: wrong opening hours.
- Vendor advertising cannot be disabled; standard playlists cannot be replaced, own playlists only added into them; images must be PNG, videos MP4.
- Till-TV offers need: offer items in the list/price list, "auto-generated" ticked, offer slide in the standard till-TV editorial, offer list assigned.
6.17 Billing-centre data-quality rules (DRZ) [DE-SPECIFIC]
- Scan every statutory prescription (and handwritten, private and green ones): automatic discount-contract search and plausibility checks (doctor signature, issue date); fix misrecognised lines; scan images retrievable in sales management.
- Daily prescription management catches wrong payer or family member's card from the image and shows who processed each prescription (training needs).
- Use effective-dated data for older-period prescriptions.
- Care aids: store payer, insured number and approval once; monthly dispensing by selecting customer and items; contract prices show when the limit is reached; automatic billing with attachments.
- Printing: print within fields, avoid skewed feed; short pharmacy name (set a "name on prescription" field, else "name postcode city"; portrait private forms always full name) not overlapping the doctor's stamp; correction stickers, never correction fluid; a reprocessed sale gets a new prescription number which must be printed (always printed with billing-centre + prescription management); countersign bottom right; nothing printed or glued on the back.
- Attachments: not reduced (≥A6), printed with prescription number, payer id and running number (then no physical link needed), otherwise paper clips — never staples, tape or rubber bands; fold to prescription size.
- Shipment boxes: cover form at start or end; care-aid forms before/after; high-price list right behind the cover form; each box its own address label.
- Billing documents to pharmacy/tax adviser are encrypted; restrict staff access to statistics and invoices in the billing portal's user management.
- E-prescriptions are backed up in the cloud; restore free for billing-centre customers.
6.18 Customer-app offer rule (FAQ)
If the pharmacy defines no offers, the app picks items whose own selling price is at least 6 % below the pharmacy retail price, showing only one pack per product family. Self-created articles appear only if stocked, priced and flagged for the pharmacy distribution channel. Staff see prices with their own discount model; customers see their contact's prices.
7. Configuration and settings
| Parameter (German identifier) | Scope | Effect | Default |
|---|---|---|---|
| Only pharmacy calendar (Nur Apothekenkalender) | Workstation (Notes) | Opening Notes shows only the pharmacy calendar, not the own employee calendar. | Off |
| Pharmacy calendar hidden | Workstation | The pharmacy calendar can be hidden per workstation (help mentions it; name not given). | Shown |
| Remind on order arrival (Bestellung beim Eintreffen erinnern) | Workstation (Notes) | Pop up today's tasks/orders immediately when a new order arrives. | On (all workstations) |
| Prescription images per A4 (Anzahl Rezeptbilder auf DIN A4) | System (Notes) | 1, 2 or 4 order prescription images per printed page. | 4 |
| Automatically reserve (Automatisch Reservieren) | (prescription scan) | Preset reservation mode when processing e-prescription orders. | On |
| Closing line (Grußzeile Nachricht) | System | Default greeting text template for KIM/e-mail messages. | "Kind regards" template |
| Bcc copy to sender address | System (e-mail sending) | Automatically copy each sent e-mail to the sender. | Not stated |
| E-mail service provider / sender addresses | System (e-mail sending) | Own provider or vendor service; sender and reply-to. | — |
| Per-contact e-mail password + "link" flag | Contact | Automatic attachment encryption / download-link delivery. | None |
| Tone for event X (5 parameters: high-priority message, automatic order attempt, imminent send time, new transfer order, automatic back-order determination) | System (pharmacy; branches separate) | Which sound plays. | Not stated |
| Play tone for event X (6 parameters) + minutes before send time | Workstation / till | Whether the sound plays at this station; lead time for cart alert. | Not stated |
| KIM addresses | Company master → add-on modules | Activate main + up to 2 extra addresses. | — |
| eCall visibility | Employee contact → message types | Who sees support tickets / requirements. | — |
| Cross-pharmacy Notes + contact exchange | Central / group | Enables messages/chats across pharmacies. | Off |
| CashGuard port (Anschluss) | Workstation (system maintenance, CashGuard page) | COM1–COM4 serial port. | — |
| CashGuard warning levels | BackOffice (device) | Low/high count per denomination. | Set by service |
| CashGuard change float | BackOffice (device) | Target float per denomination. | Set by service with pharmacy |
| CashGuard max change payout | BackOffice | Upper limit for change (error 62). | Not stated |
| BackOffice automatic printouts | BackOffice settings | Auto-print emptying/refill/correction reports. | Not stated |
| BackOffice idle logout | BackOffice | Minutes until auto logout. | Agreed with vendor |
| Customer display | Company master → customer display | Media, full-screen, colours, operator name. | Neutral |
| Price import type and schedule | Price list | none/manual/on change/scheduled; removal options. | None |
| Fax provider credentials | Company master → external services | Online fax account. | — |
| ELO archiving per print form | Print forms → print settings | ELO printer only / additionally archive / allow user override. | Off |
| ApoTune connection; data transfer active | Company master → ApoTune page | Enables transfer, mandatory address fields. | Off |
| Delivery list print count / with articles | Delivery management | Set 0 to suppress the courier list when using the optimiser. | Not stated |
| Pharmacy name on prescription | Company master → master data | Short name printed on prescriptions. | Empty (→ name postcode city) |
| Online payment onboarding | Company master → external services | Link/unlink payment-provider merchant account. | Not linked |
| DMS settings | System settings → office → DMS | DMS configuration. | — |
8. Roles and permissions
| Right / role | Grants |
|---|---|
| Notes: edit task (Notes: Aufgabe bearbeiten) — contained in roles "Manager" (Leiter) and "Notes: edit task" | Create/edit/delete tasks, open task control, move/resize/open other users' appointments and series, edit deputies' series via the edit dialog. |
| Edit support requests (Supportanfragen bearbeiten) | Use IXOS.eCall. |
| Employee message-type permissions (eCall support / requirements) | See vendor support communication. |
| Collaboration – remote: connect to partner pharmacy | Open a partner/branch pharmacy by remote desktop. |
| Manage print forms (Druckformulare verwalten) | Edit e-mail templates. |
| Workstation protection (Arbeitsplatzschutz) | Workstation-level gating of sensitive modules (eCall, remote). |
| CashGuard BackOffice "Apotheker" | Warning levels, change float edit, reconciliation, empty after reconciliation, empty device, empty single value, refill/coin correction/inventory, printouts. |
| CashGuard BackOffice "PTA" | Empty last reconciled device, printouts. |
| BackOffice and user settings | Vendor service technician only. |
| ELO preset override | User group defined per print form. |
| Users of the billing portal | User management restricts access to statistics and invoices. |
Without the permission concept, all users can do everything listed for Notes.
9. Integrations, hardware and external services
| Integration | Direction / data | Notes |
|---|---|---|
| Reports module | Reports → Notes: interactive tasks, automatic print/export/e-mail/cloud-feed jobs; Notes → Reports: execute query; PDFs back. | Failures posted to "Automatic tasks" folder. |
| Storage locations, assortment control, overstock, evaluations | Create tasks in Notes. | Replenishment list opened from task. |
| Customer app, national e-prescription app, doctor/home connect products, web shop | Orders and messages into the order list; messages/SMS/push back. | Push without content preview. |
| KIM (secure health mail over TI) | Bidirectional mail; e-prescriptions auto-converted to orders. | PDF/PNG/JPG only; 3-month retention. |
| E-mail provider (own or vendor service) | Outbound mail, encrypted attachments via cloud links. | 10 MB splitting rule. |
| Vendor DMS (ORBIZ) | Automatic filing of e-mails and KIM mails with attachments. | Document type by contact role. |
| External DMS (ELO) | Print-to-archive, scan; postbox → archive within ≤5 min; cached retry. | |
| Online fax providers (two named) | Outbound faxes of carts, prescription requests, print outputs, copies; provider keeps fax archive. | |
| Vendor support (eCall) | Tickets, attachments, remote-maintenance consent; requirement register. | Automated assistant. |
| Staff mobile app | Chats, attachments. | Paired per employee. |
| Branch/partner pharmacies | Messages, chats, transfer notifications, remote desktop. | Activation & contact exchange. |
| CashGuard device | Serial link per till (COM1–4); BackOffice over network converter. Till sends amount due, receives inserted amount, commands payout/eject; logon/logoff logged. | Exclusive access. |
| Customer display | USB at till PC. | Line displays still supported. |
| Payment provider (PayPal) | Online prepayment of app orders; refund API from order list. | Limits in §4.38. |
| ApoTune | One-way tour export (stops, addresses, phone, time windows, unique tour id). | No back-channel. |
| Courier app U5 | End-to-end encrypted tour data, offline operation, map services. | FAQ only. |
| Price list providers | CSV files dropped in a server folder. | Results to System mailbox. |
| Billing centre (DRZ) | Prescriptions, care-aid claims, cloud backup of e-prescriptions. | Physical box shipments. |
| National directory (VZD) | Institution certificate after card activation (≤48 h). | |
| WinClient pre-check service | Device benchmark against vendor reference platforms. |
10. Printouts, reports and exports
| Output | Content / options |
|---|---|
| Calendar print | Day or date range; include pharmacy calendar, my calendar, private appointments (at least one calendar required, matching the calendars shown); sorted by weekday, empty days omitted, within a day by start time; criteria in header; priorities low/high shown; private entries labelled; space for handwritten notes. |
| Message print / PDF | Any message in any mailbox; KIM with print preview. |
| Order prescription images | All or selected images; 1/2/4 per A4. |
| Report task PDFs | Before/after snapshots (interactive), printout PDF (automatic print) — licensed. |
| Recommended float changes | Per device and total; notes as counts, coins as rolls; printable. |
| CashGuard reconciliation report | Per device; printed via "marked printouts". |
| Emptying report, refill report, coin-correction report | Automatic (if configured) or manual (last / marked / preview). |
| Z / S closing receipts | From the till; "total cash" goes to the cash book; compared with device reconciliation. |
| Price import result | Message in System mailbox (complete / partial with reasons / failed). |
| Consultancy exports | Two spreadsheets (article statistics, customer-card analysis). |
| Delivery list | Suppressible (print count 0); internal list with articles. |
| Customer-facing SEPA documents | Filed to ELO per rules in §4.33. |
| Medication plan (eMP) | Printable for the patient (FAQ). |
11. Dependencies on other modules
- Reports — query definitions, scheduled jobs, PDF licences (Reports Profi / MMR Reports / MMR Reports Profi).
- Till (Kasse) — operator registers (trigger reminders), total window, payment types, reservation "customer not present", pay-in/out, cancellation, closing receipts, sales management (Verkaufsverwaltung).
- Prescription scan / prescription management — e-prescription order processing, signatures, Rx.secure consumers.
- Connect products / customer app / web shop — order sources and order-editing screens (other chapter).
- Goods receipt (Warenlogistik) — back-order booking triggers customer messages; cart transmission (fax); supplier invoice scanning to DMS.
- Storage locations, assortment control (RX 4.0), overstock management, evaluations — task creators.
- Contacts — employees (user accounts, contact role active, message types, app pairing), contact classifications, customer e-mail encryption settings, address book for cost-invoice issuers.
- Company master (Firmenstamm) — KIM addresses, external services (fax, payment, ApoTune), customer display, signature data, pharmacy name on prescription.
- Prices & calculation — price lists, price usage models (price importer target).
- Article management — price history, Rx.secure columns.
- Delivery management (Liefermanagement) — tours, delivery lists, courier settlement via CashGuard.
- Print forms — e-mail templates, ELO archiving settings, print preview send functions.
- DMS ORBIZ — mail filing, document types, daily-closing receipts.
- System maintenance — acoustic signal parameters, CashGuard port.
- Cash book (Kassenbuch) — receives closing totals.
- Info centre / menu bar / process bar — notification surfaces.
- Permissions / workstation protection — rights listed in §8.
- Remote support / IXOS Remote — remote maintenance and remote work seats.
12. Portability notes
| Feature | Classification | Idea to carry over |
|---|---|---|
| Calendar, tasks, deputies, recurrence, task control with occurrence logs, daily reminder at login, snooze | Generic | Build as a tenant-wide work-item engine: every module can create typed tasks with an "execute" deep link; keep immutable per-occurrence completion records for audit; never delete history when stopping a series. |
| Module-generated tasks (report runs, replenishment, assortment review) | Generic | A task type registry with handler per type (open screen, run report, auto-export). |
| Order inbox with conversation thread and auto-generated status messages | Generic | Unified omnichannel order queue; status derived from fulfilment progress (§6.3); message proposals at lifecycle events (ready, back-ordered, substituted, cancelled). Very relevant to Shefa's patient app. |
| Internal messages with per-user read state, folders with retention, distribution lists | Generic | Notification centre with typed folders and TTL per type. |
| Shared vs per-user read state (KIM vs internal) | Generic | Decide per channel whether a mailbox is a shared team inbox (shared read flag) or personal. |
| E-mail with automatic attachment encryption, password alphabet without ambiguous characters, size-based splitting, DMS auto-filing by contact role | Generic | Directly reusable. |
| KIM secure mail and e-prescription assignment | DE-specific | Closed provider network with directory lookup; structured e-prescription routed to a chosen pharmacy and turned into an order; bursts from same sender/patient merged. |
| Vendor support ticketing inside the product, with assistant-first deflection, remote-access consent and public feature-request register with demand counts | Generic | Valuable for a SaaS/self-hosted vendor supporting many pharmacies. |
| Acoustic alerts per event and per station | Generic | Configurable sound map; station-level opt-out. |
| Cash recycler integration | Generic | Device abstraction: amount due → inserted amount stream → confirm → payout; eject; pay-in/out; refunds as negative payout; exclusive device ownership; offline fallback with manual float; error code catalogue with operator actions; reconciliation vs till closing (joint or separated). |
| Customer display | Generic | Second screen showing line prices, totals, change, idle signage; good for price transparency. |
| Price importer (CSV, schedules, fallback priority, tolerant parsing, processed-file archive, result notifications) | Generic | Supplier/price-list import with effective dates (valid-from/to) and lenient parsing; Syrian market can use it for distributor price lists. |
| Fax to online providers | Generic (declining) | Outbound document channel abstraction (fax/e-mail/portal) from any print preview. |
| ELO / print-to-archive | Generic | "Virtual printer" that archives documents with metadata; retry queue. |
| Rx.secure | DE-specific | Effective-dated master data (prices, payer contracts) with 24-month history; reprice/re-check any past dispensing as of its date. Highly relevant where official prices change by decree. |
| ApoTune / U5 courier | Generic | Route optimisation, idempotent tour export with unique ids, mandatory geocodable addresses, offline courier app with E2E encryption, stops-based billing, proof-of-delivery signature. |
| WinClient pre-check, UAC rules | Generic | Hardware compatibility checker and component prerequisite installer with grace period. |
| DMS FAQ rules (one-way filing, deletion only before indexing, retention per document type, tax-office search) | Generic (tax-law flavoured) | Immutable archive semantics: once indexed, hide not delete. |
| E-prescription, ePA, SMC-B, PDL, DRZ printing rules | DE-specific | National e-prescription token flows; shared medication list/plan; institution identity certificates; billable clinical services with consent; claims-processing hygiene. |
| Online payment rules for app orders | Generic | Thresholds for prepayment (qty, amount, Rx type, pickup branch), refund-before-dispense via API, cancellation mode "online" so tills don't pay out cash. |
| apoTV / KassenTV | Generic | In-store signage with offer slides fed from price lists. |
13. Open questions
- The help describes no general linking of a task, appointment or internal message to a customer, article or sale. Only order-type tasks carry a customer and items, and module-generated tasks deep-link to their source (report query, replenishment list). A designer wanting "note about customer X" must decide this independently.
- Recipients/assignees can be a person, a contact classification (group), the whole pharmacy or another pharmacy in the group; the help mentions no addressing by role or by workstation for messages or tasks (chats run "workstation to workstation" but are addressed to people or pharmacies).
- No reminder/alarm settings per task (only the daily login pop-up and snooze) and no configurable lead time for appointment alerts (fixed 15 minutes) are described.
- Exact meaning of a lone
-as price in the CSV (delete own price? reset?) is not explained. - The standard CSV example contains overlapping validity ranges for the same article although the rules require non-overlapping ranges; behaviour on overlap is not documented.
- Task control "Current" filter: the help gives two different definitions (overdue + next two days vs last two and next two months).
- No information on how reminders behave for tasks assigned to the whole pharmacy (which operator sees the pop-up — apparently everyone).
- No description of notification of the deputy beyond appearing in their calendar; no escalation rules for overdue tasks.
- Whether the "reason" field for CashGuard pay-in/out is mandatory, and how pay-in/out appears on the Z receipt, is not specified here.
- Default values for acoustic-signal parameters, e-mail Bcc setting and CashGuard max change are not given.
- The help does not explain how CashGuard counts are reported back to IXOS (whether IXOS ever knows the device's stock) beyond the reconciliation in BackOffice.
- Chat message retention and whether chats are stored on the server or synced to the app are not described.
- No data on how app orders are merged or split when a customer sends follow-up messages.
- The "Automatic tasks" folder retention period is not stated.
- Whether price-import removals affect items that were manually edited is not stated.
- Rx.secure: storage approach and behaviour beyond 24 months are not described.
- ELO: which metadata are pre-filled automatically is not listed (separate page).
14. Source pages
- Notes (Kalender/Nachrichten, IXOS.eCall) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/01_notes_start.htm
- Termin oder Aufgabe anlegen und bearbeiten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Aufgaben/aufgabe_termin_neu.htm
- Aufgaben — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Aufgaben/aufgaben.htm
- Signalisierung von Aufgaben des aktuellen Tages — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Aufgaben/aufgaben_heutige.htm
- Mitteilung senden — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Aufgaben/aufgaben_mitteilung_senden.htm
- Rezeptbilder ausdrucken (Connect) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Aufgaben/aufgaben_rezeptbilder_ausdrucken.htm
- Informationstext für eine Aufgabe hinterlegen und einsehen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Aufgaben/info.htm
- Aufgabensteuerung — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Aufgabensteuerung/aufgabensteuerung.htm
- E-Rezept-Bestellungen via KIM — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Bestell-Liste/KIM_bestellung_erezept.htm
- Bestell-Liste — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Bestell-Liste/bestell_liste.htm
- Chats — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Chats/chats.htm
- Kalender — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Kalender/01_kalender.htm
- Drucken im Notes-Kalender — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Kalender/kalender_drucken.htm
- Typ für Neuanlage auswählen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Kalender/kalender_neu.htm
- Serientyp anlegen und bearbeiten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Kalender/kommunik_serientyp.htm
- Serientermin oder Serienaufgabe löschen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Kalender/kommunik_termin_aufgabe_loeschen.htm
- IXOS.eCall – Supportanfragen und Anforderungen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/IXOS.eCall/01_notes_supportanfragen_start.htm
- Anforderungen einsehen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/IXOS.eCall/notes_anforderungen.htm
- Anfrage erstellen und bearbeiten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/IXOS.eCall/notes_anforderungen_erstellen.htm
- Anforderungen suchen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/IXOS.eCall/notes_anforderungen_suchen.htm
- IXOS.eCall Support-Anfragen einsehen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/IXOS.eCall/notes_online-support.htm
- KIM-Postfach — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/KIM/KIM_Postfach.htm
- „Meine Apotheke“-Postfach — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/Meine_Apotheke/Meine_Apotheke_Postfach.htm
- E-Mail-Postfach — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/email/email_postfach.htm
- Angehängte Dokumente oder Dateien verschlüsseln — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/email/email_verschluesseln.htm
- E-Mail-Vorlagen und Druckformulare — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/email/email_vorlagen.htm
- Differenzmeldungen der Artikel-Dublettenbearbeitung einsehen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/kommunik_dublettendiff.htm
- Nachricht erstellen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/system/kommunik_nachrichten_neu.htm
- Nachrichtenempfänger auswählen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/system/kommunik_nachrichten_neu_empfaenger.htm
- Systemnachrichten-Postfach — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/Nachrichten/system/systemnachrichten_postfach_start.htm
- Signaltöne für Meldungen und Ereignisse — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/infocenter_akustische-signale.htm
- Nachrichten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/Notes/nachrichten_start.htm
- IXOS einer Filial- und Partnerapotheke per Remote öffnen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/fup_remote.htm
- IXOS.KIM - sichere Kommunikation im Medizinwesen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/ixos_kim.htm
- Kooperation — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT2_Kooperation/kooperation.htm
- Ergänzende Produkte und Geräte für IXOS — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/01_optionale_produkte_geraete.htm
- ApoTune – Das mobile Liefermanagement — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/ApoTune/apotune_start.htm
- Einführung in das CashGuard-Gerät — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/00_cg_einleitung.htm
- Barzahlung mit CashGuard-Gerät — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/IXOS-Kasse/cg_barzahlung_allg.htm
- Ein- und Auszahlung mit CashGuard-Gerät — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/IXOS-Kasse/cg_ein-auszahlung.htm
- Bargeld-Rückgabe mit CashGuard-Gerät — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/IXOS-Kasse/cg_geld_auswerfen.htm
- IXOS-Kassenarbeitsplatz mit CashGuard-Gerät — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/IXOS-Kasse/cg_ixos_start.htm
- Anbindung des CashGuard-Gerätes an IXOS — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/IXOS-Kasse/cg_konfiguration_kasse.htm
- Status- und Systemmeldungen einsehen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/IXOS-Kasse/cg_statusmeldungen_kasse.htm
- Stornierung mit CashGuard-Gerät — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/IXOS-Kasse/cg_stornierung.htm
- Verbindung zum CashGuard-Gerät herstellen und trennen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/IXOS-Kasse/cg_verbindung_kasse-cg.htm
- An- und Abmelden — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/backoffice/cg_backoffice_an-abmelden.htm
- Ausdrucke erstellen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/backoffice/cg_backoffice_druckoptionen.htm
- Kassenabschluss und CashGuard-Abrechnung durchführen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/backoffice/cg_backoffice_kassenabschluss.htm
- Leerung der CashGuard-Geräte — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/backoffice/cg_backoffice_leerung.htm
- CashGuard-BackOffice Software — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/backoffice/cg_backoffice_start.htm
- Warnlevels für Bargeldbestand einstellen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/backoffice/cg_backoffice_warnlevels.htm
- Wechselgeldbestand bearbeiten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/backoffice/cg_backoffice_wechselgeldbestand.htm
- Inventur vornehmen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/backoffice/cg_inventur.htm
- Vorbemerkung — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/CashGuard/cg_vorbemerkung.htm
- Administratorrechte für Windows 11 konfigurieren — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/ClickOnce/administratorrechte_konfig.htm
- Voraussetzungen für IXOS WinClient — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/ClickOnce/co_voraussetzungen.htm
- Systemvoraussetzung für IXOS auf kundeneigener Hardware — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/ClickOnce/systemvoraussetzungen.htm
- Ablegen von IXOS-Dokumenten im ELO-DMS — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/ELO-DMS/ELO_dokumente_ixos_ablegen.htm
- FAQ – Häufig gestellte Fragen — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/FAQ/01_faq_start.htm
- Botendienst IXOS U5 – FAQ — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/FAQ/botendienst_faq_haeufige_fragen.htm
- ORBIZ DMS – FAQ — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/FAQ/dms_faq_haeufige_fragen.htm
- E-Rezept – FAQ — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/FAQ/e_rezept_faq.htm
- Inhaberwechsel und SMC-B-Karte – FAQ — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/FAQ/ehealth_SMCB_inhaberwechsel.htm
- ePA – FAQ — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/FAQ/epa_faq.htm
- App & Web „Meine Apotheke“ – FAQ — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/FAQ/kunde_apo_faq.htm
- Pharmazeutische Dienstleistungen – FAQ — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/FAQ/pdl_faq.htm
- apoTV und KassenTV – FAQ — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/FAQ/wissensartikel_apoTV.htm
- Fax-Schnittstelle zu Online-Fax-Dienstleistern — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Faxschnittstelle/fax_start.htm
- Das Kundendisplay — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Kundendisplay/kundendisplay.htm
- Verwendung von externen VK-Preislisten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Preisimporter002/00_importer_einleitung_help.htm
- VK-Preisimport von Baufeldt & Partner — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Preisimporter002/01_funktion_baufeldt.htm
- Standard VK-Preisimport — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Preisimporter002/01_funktion_preisimport.htm
- Beschreibung der CSV-Schnittstelle (Baufeldt Partner) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Preisimporter002/02_csv-schnittstelle.htm
- Beschreibung der CSV-Schnittstelle (Standard) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Preisimporter002/02_csv-schnittstelle_preisimport.htm
- Rx.secure - Übersicht über die historisiert abgelegten Daten — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Rxsecure/rx.secure_uebersicht_daten.htm
- Rx.secure - Historische Daten in IXOS — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Rxsecure/rxsecure_historische_daten.htm
- Tipps & Tricks — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/Tipps_Tricks/01_tipps_tricks_start.htm
- Hinweise für Kunden des Digitalen Rezept Zentrums (DRZ) — https://ixos-onlinehilfe.pharmatechnik.de/Default/Content/PT99_Sonstiges/drz_hinweise.htm