Skip to main content

Back-office prescription management, prescription requests to doctors and sales administration (Rezeptmanagement, Rezeptanforderung, Verkaufsverwaltung)

1. Purpose and scope​

This chapter covers three back-office modules of IXOS that sit behind the point of sale (POS, Kasse):

  1. Prescription management (Rezeptmanagement). A pre-billing quality gate for prescriptions. Before the pharmacy's prescriptions are collected and billed by its clearing centre (Apothekenrechenzentrum), every statutory-insurance (GKV) prescription is checked inside the pharmacy. Paper prescriptions are scanned in the back office, recognised, and compared with what was actually sold. E-prescriptions are checked from their data. The module also takes in pre-check feedback from the clearing centre over an online interface (ApoTI). The aim is to find and correct errors before billing and so avoid payer clawbacks (Retaxation, "retax"). Each prescription moves through four processing tabs: Not ready → Rx check → Rx box → Archive (billed). The module also covers: parenteral-preparation, unit-dose (Auseinzelung) and weekly-blister prescriptions; deferred prescriptions with deferral sleeves (Rückstellhüllen); signing e-prescription corrections with a pharmacist's health-professional card; research tools for retax disputes (24-month historic price and contract data, proof of non-availability, filing of clawback letters); and, for customers of one clearing centre (DRZ), a billing dashboard that pulls the centre's invoices, statistics and deviations into IXOS ("RX Control 4.0"), plus requests for advance payouts ("DRZ Cash").
  2. Prescription requests (Rezeptanforderung). A paid add-on that produces requests to treating doctors for follow-up prescriptions of long-term medication. It is mainly for patients in care homes and blister supply, where the pharmacy manages the medication on the patient's behalf. Requests are computed from the patient's medication courses, stock and dosage, then printed, faxed or e-mailed to the doctor and tracked until the prescriptions arrive.
  3. Sales administration (Verkaufsverwaltung). The store of every completed POS transaction and invoicing order. Staff use it to find past sales, see full details (prices, prescriptions, pack data, pickups, images), reprint any document, and make post-sale corrections: reactivate a sale for editing, cancel it fully or partly, change the payment type, change the customer assignment, correct invoice settlements and card payments, and move a POS sale into invoicing. It also explains the totals on daily summary receipts ("closing receipt analysis").

The three modules share data. Every prescription in prescription management is the prescription subtotal of a sale in sales administration. Editing a prescription always means reactivating that sale. Prescription requests feed the medication-management records that later receive the prescriptions.

Out of scope here (other chapters): the POS sale itself, the e-prescription dialog, medication management, blister management, the invoicing module, clearing-centre master data, print-form design, the notes/tasks module and card-terminal administration.

2. Key concepts and terms​

German termEnglishMeaning
Rezeptmanagementprescription managementBack-office module that checks prescriptions before billing and tracks them until billed.
Rezeptkontrolleprescription check (Rx check)Second tab of the module, and the overall checking activity: prescriptions that are not billable, faulty, improvable, unsigned, or flagged for manual review.
Nicht bereitnot readyFirst tab. Prescriptions that cannot be checked yet: print missing, original missing, deferred, or still waiting for clearing-centre feedback.
Rezeptboxprescription boxThird tab. Checked prescriptions waiting for collection by the clearing centre; a digital twin of the physical box.
Abgerechnete Rezepte (Archiv)billed prescriptions (archive)Fourth tab. Prescriptions collected, reported billed, or marked billed by hand.
Apothekenrechenzentrum (ARZ)pharmacy clearing centreService company that collects the pharmacy's prescriptions and bills the payers on its behalf.
DRZ (Digitales Rezept Zentrum), ApoOnlinea specific clearing centre and its portalClearing centre whose billing data IXOS can pull in (RX Control 4.0).
ApoTIclearing-centre online interfaceOnline interface that sends prescription data to the clearing centre for pre-check and returns feedback messages and statuses.
Retaxation / Retaxpayer clawbackPayer refuses or cuts payment for a prescription after billing because of an error.
Prüfstatuscheck statusTraffic-light status of a prescription: not billable (black), faulty (red), improvable (yellow), error-free (green), plus variants for ignored hints.
HinweishintOne finding of the automatic check or the clearing centre, on a prescription line or the whole prescription. The status is the most severe active hint.
Prüfregeländerungfeedback status remappingPharmacy-specific override of the severity of one clearing-centre message type.
Rückstellung, Rückstellungsnummer, Rückstellhülledeferral, deferral number, deferral sleevePrescription whose printing was postponed at sale. It is kept in a numbered sleeve and printed later after checking.
Rezeptnummerprescription number (Rx number)Number the system assigns to each printed prescription; printed on the form.
E-Rezept-IDe-prescription IDIdentifier of an e-prescription.
Rezeptklammerprescription bracketSeveral e-prescriptions grouped as one IXOS prescription (one sale subtotal).
Quittungreceipt (e-prescription)Dispensing receipt from the national e-prescription service; needed for billing an e-prescription.
QES, HBA / eHBAqualified electronic signature; (electronic) health-professional cardPharmacist's personal signature, required on e-prescriptions that were corrected or where the dispensing ranking was not followed.
Abgaberangfolgedispensing rankingStatutory order of which article must be dispensed (discount contract, cheapest, import, etc.).
Rabattvertragdiscount contractContract between payer and manufacturer that dictates which article must be dispensed.
aut idemsubstitution allowed / excluded flagPrescription flag saying whether the pharmacist may substitute another product.
Importquoteimport quotaDuty to dispense cheaper parallel imports to a certain share.
Sonderkennzeichen (SOK, PZN-like code)special codeCode printed on a prescription line for special cases (e.g. non-availability, pharmaceutical concerns, fees).
StückelungsplittingA prescribed quantity dispensed as several smaller packs; "priced" vs "dispensed" article can differ.
Muster 16standard paper prescription formGerman statutory prescription form.
Grünes Rezeptgreen prescriptionDoctor's recommendation form; patient pays.
BtM-Rezeptnarcotics prescriptionPrescription for controlled substances (BtM = Betäubungsmittel).
T-Rezeptthalidomide prescriptionSpecial form for thalidomide-type drugs.
Parenteraliaparenteral preparationsCompounded infusions made in the pharmacy.
Auseinzelung / Wochenblisterunit-dose / weekly blisterRe-packing of tablets per patient, billed with special data records.
Z-Datenelectronic additional dataExtra data records sent with certain prescriptions (parenterals, unit-dose, blisters).
Hashcodehash code40-digit number printed on a parenteral prescription that ties the paper form to its electronic data record.
Rx.securehistoric price/contract dataFeature that checks prescriptions against price and contract data valid on the dispensing date, for up to 24 months back.
Preispflegeservice (PAD)price update servicePrice and article data updates, applied on the 1st and 15th of each month.
Nichtverfügbarkeitsnachweisproof of non-availabilityPrintout showing that the articles that should have been dispensed could not be supplied at dispensing time.
Retax-Verwaltungretax letter filingScanned store of payers' clawback letters with notes.
Arztrückfragedoctor queryE-mail to the prescriber about a prescription, with the image attached.
Rezeptanforderungprescription requestRequest to a treating doctor to issue follow-up prescriptions.
Therapiearzt / Hausarzttreating doctor / family doctorDoctor assigned to a medication; fallback doctor in the contact data.
Verlauf (Medikationsverlauf)medication courseA medication line in medication or blister management with dosage, stock and history.
Reichweiterange / reachHow long the patient's current stock lasts at the current dosage.
Bedarfsdosierung vs. Bedarfsmedikationas-needed dosing vs. as-needed medicationTwo different concepts. The request filter applies to the dosing type.
Vorablieferungadvance deliveryMedication supplied before the prescription is received.
Rezept-Aboprescription subscriptionService in a customer app where the pharmacy orders repeat prescriptions; has its own request print form.
Verkaufsverwaltungsales administrationStore and correction tool for completed sales and orders.
Vorgang / Kassenvorgangtransaction / POS transactionOne completed sale ("total"), made up of one or more subtotals.
SubtotalsubtotalPart of a transaction with one sale type (cash sale, GKV prescription, private prescription, etc.). Each prescription is one subtotal.
Verkaufsartsale typeRx status of a subtotal: normal sale, GKV Rx, private Rx, green Rx, BtM Rx, care aids, and their cancelled variants.
Abschlussart / Zahlartclosing type / payment typeHow the sale was settled: cash, credit, card, direct debit, cheque, online, invoice.
Vorgangskettetransaction chainLinked transactions: original, cancellation/reactivation, follow-up document, pickup resolution, credit resolution.
Folgebelegfollow-up documentNew transaction created when a sale is reactivated and completed again.
Rezept-Verlaufsketteprescription history chainChain recording a dispensing-date change on reprint that did not change any print data.
AktivierenreactivateBring a completed sale back to the POS for editing.
Storno / Stornoboncancellation / cancellation receiptFull or partial reversal of a sale and its receipt.
Systemstornierungsystem cancellationCounter-posting generated by the system (e.g. when a quantity is reduced).
Kredit / Kreditschein / Kreditauflösungcredit sale / credit slip / credit resolutionSale left unpaid (customer owes); its slip; and the later settlement.
Abholung / Abholschein / Nachlieferungpickup / pickup slip / back-orderItems owed to the customer and collected later.
Botenboncourier slipSlip for courier delivery.
Forderungsauflösungreceivable settlementPayment of an open receivable at the POS.
Rechnungsbegleichunginvoice settlementPayment of an invoice at the POS.
Umbuchungs-Bonrebooking receiptInternal receipt that documents a payment-type change.
Z-Bon, X-Bon, T-Bon, S-, J-, M-Bonsummary receiptsSummary receipts that total sales over a period. Z is the closing receipt; an X receipt is recommended as a check before drawing the Z receipt; a T receipt can cover any period. The exact meaning of each letter is defined in the POS closing chapter, not here.
Z-Bon-GrenzeZ-receipt boundaryOption when creating a summary receipt; receipts made with it carry no breakdown.
Abschlussbonanalyseclosing receipt analysisBreakdown of each summary-receipt figure into the sales behind it.
ec-Abschlusscard terminal settlementEnd-of-day closing of the card terminal.
LadedrawerCash-drawer opening transaction.
Testrezepttest prescriptionPrescription printed for testing; stored as its own transaction type.
Faktura / Auftraginvoicing / invoicing orderOrder-based selling module with invoices and delivery notes.
Gegenscannencounter-scanSecond scan to confirm the right pack; bypasses are logged.
securPharmanti-counterfeiting verificationNational pack verification system; packs are deactivated on dispensing.
Ausfuhr- und Abnehmerbescheinigungexport and purchaser certificateDocument allowing VAT refund for goods exported outside the EU.
Abrechnungsbeleg Privatversichertebilling receipt for privately insuredReceipt a private patient submits to the insurer.

3. Data model​

3.1 Prescription (Rx) record in prescription management​

Each prescription is bound to one prescription subtotal of a sale in sales administration. Important attributes:

  • Identifiers: Rx number (system-assigned, printed); e-prescription ID(s) (several for a prescription bracket); deferral number (if printing was deferred); transaction and subtotal reference.
  • Form/type: Muster-16 paper or e-prescription; regulation type (GKV, private, green, BtM GKV, BtM private, thalidomide, accident insurer, care-aid billing, private with additional data, electronic additional data / unit-dose / weekly blister, parenteral; cancelled variants; "prescription missing"; "not scanned").
  • Dates: issue date (recognised or entered; editable); dispensing date (printed on the form; may differ from sale completion date); sale date/time.
  • Payer (Kostenträger, with institution code IK); customer; doctor (practice-site number BSNR, lifelong doctor number); operator; workstation.
  • Processing tab: Not ready, Rx check, Rx box, Archive.
  • Check status: none (not yet scanned/checked), not billable (black), faulty (red), improvable (yellow), error-free (green), improvable with active improvement hint plus ignored hints, green with only ignored hints.
  • Flags: print status (not printed / printed / printed with attachments); "prescription missing"; deferral; open pickup; "check later"; "requested again" (green arrow, moved back by "check again"); QES required / QES applied; receipt missing / attached; all three e-prescription data records sent (green tick); held back / returned from check.
  • ApoTI status: sent without feedback, feedback received, can be billed, to be cancelled, cancelled; plus send errors.
  • Hints: list of findings with severity (info, hint, improvable/warning, error), source (system check or clearing-centre message), state (active / ignored), and the line they belong to. Overall clearing-centre status line with expected billing month and correction deadline.
  • Image: one stored image (front and back if the back was printed). A back-office scan overwrites a front-office (POS) scan. It can be "outdated" after the sale is reactivated.
  • Info note: free text (blue icon when present). For e-prescriptions it travels with the prescription through the order list, e-prescription dialog, POS and prescription management.
  • Article lines: prescription line number (VO, which prescribed line the article belongs to), article, PZN, discount-contract and aut-idem indicators, uneconomic-dispensing indicator, split/blister indicators, dosage form, pack unit, standard pack size (N1–N3), quantity, supplier, sale price, special code, recorded batches.
  • History: one entry per status change (Created, Check accepted, Billed, manual hint changes) with time, workstation and operator.
  • Audit on the subtotal: date, time, operator and workstation for accept, check and change actions; dispensing-date change on reprint.

3.2 Batch records for billing​

Per article line: list of batch numbers. Each is marked as either captured during the sale (shown italic, read-only) or recorded afterwards (editable, pencil mark). A batch pre-recorded for a back-order is replaced when the real pack is scanned later. The sale quantity tells how many batches are needed.

3.3 Parenteral preparation data record​

  • Header: hash code (40-digit decimal, computed from manufacturer IK, transaction number, timestamp and the PZN lines used); creation time; own pharmacy IK; transaction number (unique per pharmacy per year).
  • Batches (manufactured units): batch number, number of ready-to-administer units, manufacturer identifier (own/foreign manufacturer number or IK) and its type, manufacture date/time, number of components.
  • Components per batch: PZN, name, factor identifier, factor (per mille of a pack used: whole pack = 1000, 7 of 28 tablets = 250), discard factor, price identifier, price, discard flag (Verwurf: leftover that cannot be used elsewhere and may be billed).

3.4 Unassigned scan image​

Back-office image that could not be matched to a sale. It waits in a queue for manual assignment. Unusable images are kept 1 week; usable images are kept for assignment for 60 days.

3.5 Clearing-centre feedback remapping​

Per message type: message text, original status, adapted status (Info, Hint, Improvable, Error). Applies to all later feedback of that type.

3.6 DRZ billing data (RX Control 4.0)​

  • Per month (running month plus the two last closed billings): gross prescription turnover (total / e-prescriptions / paper); number of prescriptions (excluding the night/emergency-service fund self-declaration); deviation count and gross sum; peer-group comparison values; invoice PDF; statistics PDF.
  • Per payer (from the last billing): test-strip reduction total; import account balance.
  • Per prescription on the DRZ side: data and image as billed by DRZ.
  • Deviation record: match status (only IXOS, only DRZ, matched by different Rx number, matched by gross amount + payer IK + dispensing date, matched with content deviations, accepted); co-payment; total gross; optional info note with the acceptance reason.
  • Pickup dates: two per month (mid-month and start of next month), imported from DRZ.
  • Payout requests (DRZ Cash): amount, sent date; listed in the notes module.

3.7 Retax document​

Scanned A4 letter: capture date, operator, info text (e.g. affected Rx numbers, clarification state), image.

3.8 Availability query history​

Results of online availability queries made at the POS and in the e-prescription dialog for GKV sales, kept 36 months: article, supplier, query time, result (fully deliverable directly or via the chain/network; partly or not deliverable; no result).

3.9 Prescription request (Rezeptanforderung)​

  • Header: created at (date/time); recipient doctor (name, phone); period covered; created for (customer, care home or doctor scope); created by (employee); number of positions; processing channel and state (to print / printed / to e-mail / e-mailed / to fax / faxed); medication booking state (all / some / none of the requested prescriptions received and booked); archived flag; free-text "additional positions" (items not in medication management, e.g. dressings); supplementary note to the doctor.
  • Position: customer, birth date, care-home flag, article and dosage form (or for substance prescriptions: substance, strength, form), PZN (not for substance prescriptions), total patient stock of the course at creation, range (reach) at creation, dosage, computed need for the period, receipt state (booked into medication management or not), deferral state ("suspend until next request" or "do not request until <date>").
  • Doctor contact settings used: absence days, additional lead days, delivery mode (print, fax, e-mail).
  • Course-level override (in medication / blister course details): "do not request until <date>" or "request once against the automation"; the course also shows which automatic rule applies and whether it is on a request right now.

3.10 Sales transaction (sales administration)​

  • Transaction (total): date/time, workstation (main or secondary POS), operator ("System" for automatic ones such as webshop sales), customer(s), transaction type, total amount, closing/payment type(s), pickup slip number, credit slip number, sales channel, chain link, stored print data for every document (except test prescriptions), receipt/order number, external document number (e.g. webshop order).
  • Transaction types: till receipt (Kassenbon), sales (= receipts + orders), invoicing order (Auftrag), cash deposit, cash withdrawal, summary receipts (Z, S, X, J, M, T), card terminal settlement, drawer, test prescription.
  • Subtotal: running number, sale type and status text (e.g. "Kreditaufl. <credit slip no.>"), customer, Rx number / e-prescription ID, Rx history or Rx history-chain markers, Rx missing / printed, deferral number, Rx total, image flag, cancellation reason and note, care-aid data, webshop data.
  • Position: PZN, special code (with documented pharmaceutical concerns where relevant), name, split/blister flags, discount-contract/aut-idem/uneconomic flags, quantity dispensed, quantity not available (to be or already delivered later), position type (article, generic article, fee, cash-sale position, additional cost), VAT rate (full, reduced, none), price details, pack info (batch, expiry, securPharm serial).
  • Cancelled items: operator cancellations and system counter-postings (the latter shown only when configured).
  • Chains: cancellation/reactivation, pickup resolution, credit resolution, Rx history chain.
  • Pickup-terminal log per transaction: date/time, pickup number, shaft, status, description; robot retrieval and verification events.
  • Detail flags on the total: scanned discount coupons, bypassed counter-scans, bypassed securPharm verification, removed automatic courier fee, receipt printed / sent to app.

4. Features​

4.A Prescription management (Rezeptmanagement)​

4.A.1 Module overview and processing tabs [DE-SPECIFIC]​

General idea underneath: a staged, pre-submission audit queue for reimbursable prescriptions, so that errors are found before the payer sees them.

  • Purpose: check every statutory-insurance prescription before the clearing centre bills it; find and fix errors early; protect against clawbacks. Also covers parenteral-preparation, unit-dose and weekly-blister prescriptions (including private ones, for manufacturer-rebate handling) and deferral sleeves. Optionally sends prescriptions to the clearing centre for pre-check (ApoTI) and folds its feedback into the status.
  • Who/when: back-office staff, ideally at least once a day for all prescriptions received.
  • Access: permission "start prescription management" or role Leiter (manager). With the sensitive-data protection concept active, it can be a workstation permission or a user permission.
  • Tabs (processing state): Not ready → Rx check → Rx box → Archive. Each tab header shows a count (not the Archive). Not ready, Rx check and Rx box show the clearing centre's next pickup date in red.
  • What is checked: formal points (co-payment obligation, discount contracts correctly fulfilled, import quota); whether what was dispensed matches what was prescribed; whether substitution was correct. Checks run on the scanned image and the sale data. The result is a check status that also says whether a manual check is needed. The scan does not take away the pharmacist's responsibility.
  • Images: linked to the sale. They can be opened from sales administration and from the customer's sales list for research until the prescription is fully billed. The scan function has had a legal data-protection review.
  • List columns (all tabs, roughly): check-status icon; Rx number; regulation-type icon; date; customer; print status; deferral number; pickup icons (pickup exists; deferral and possibly pickup exists); info icons (info stored; held back/returned from check; both); scan icons (back-office scan with a matching sale; back-office scan but image outdated after reactivation or unassigned; POS scan with a viewable POS image); ApoTI status icons; total gross. Sortable by Rx number, date, customer, print status and deferral number.
  • Detail area: an Articles part (the article line attributes in 3.1) and a Hints part (hint texts per line; tooltips with e-prescription ID, recorded batches and clearing-centre feedback; an overall status line with billability, expected billing month and the deadline for changes). Feedback is sorted by severity, then alphabetically. Precedence of icons: the aut-idem icon wins over the discount-contract icon. Discount icon variants: aut-idem article with a discount contract for this payer; discount contract but not aut idem; article dispensed instead of the discount article that should have been given.
  • Search and filter: search needs at least the last 3–4 digits of a deferral or Rx number. A reset icon restores default filters, except the "only e-prescriptions" restriction.
  • e-medication list: the customer's electronic medication list can be opened from any tab for the selected prescription.

4.A.2 Not ready tab (Nicht bereit) [DE-SPECIFIC]​

General idea: hold items that cannot yet be checked, with a reason for each.

  • Shows prescriptions not yet ready for checking. Filters: All; Print missing (not deferred, but printing was aborted with "print later"); Prescription missing (sold on prescription but the original has not been handed in); Deferral. Sorted by date and Rx number, newest first.
  • With ApoTI active, it also shows everything without clearing-centre feedback that has not been scanned in the back office. This is informational. When feedback arrives, the prescription moves to Rx check automatically but gets no overall status until it is scanned. Scanning moves it to Rx check whether or not feedback exists.
  • E-prescriptions without a red overall status wait here for three days, then move to Rx check. E-prescriptions with a red error go straight to Rx check for correction.
  • Three days before month end, everything still here is moved into Rx check, so missing originals can still be obtained in time.
  • "Accept check" moves the selected items into Rx check (with the warning dialog in 4.A.14).

4.A.3 Rx check tab (Rezeptkontrolle) [DE-SPECIFIC]​

General idea: a work queue of items needing human attention, ranked by severity.

  • Holds every prescription that should be checked: not billable, faulty, improvable, lacking a required qualified electronic signature (QES), or flagged for manual check.
  • Search by Rx number or e-prescription ID.
  • Filters: All (everything sent via ApoTI and ready); Faulty; Improvable; Manual check-status change (two variants: improvable with an active improvement hint plus ignored hints; only ignored hints); Manual check; To check later; Checkable (not held back, no pickup, no deferral); Not scanned; For signature with HBA.
  • "Manual check" includes error-free prescriptions when: settings ask for it (see 7); the prescription was moved back from box or archive via "check again" (green arrow); a clearing-centre hint carries a message that may affect billing; there is a clearing-centre hint (even without a message) and no back-office scan yet; or the post-scan system check left a hint that needs manual review (e.g. check co-payment status, special narcotics checks).
  • Sort order: not billable first, then red, yellow, green; prescriptions without status after them, newest first.
  • Unmatched images (edition "Profi"): rows highlighted red when the scanned image could not be matched to a sale; assign by hand (4.A.8).
  • The hints area gives the deadline for corrections (except for non-billable prescriptions).
  • Context functions: copy Rx info (Rx number, e-prescription ID, PZN, batch); article information (for narcotics, also narcotics info); batch correction.
  • Accept check moves the prescription to the box. A manually accepted faulty prescription stays in the box unless a later ApoTI status query returns a worse status (green→yellow, yellow→red, green→red, yellow→black, etc.). It then returns to Rx check automatically.
  • Prescriptions already reported billed can be re-sent manually, and status queries are still possible.
  • Month-end signature reminder: from three working days before month end until the last working day, the system checks whether any prescription in Rx check still lacks an HBA signature. If so, it creates a task in the notes module with the number of open prescriptions.

4.A.4 Rx box tab (Rezeptbox) [DE-SPECIFIC]​

General idea: a "ready to submit" queue with a revenue forecast.

  • Digital twin of the physical box waiting for collection. Used for a month-end overview and a final check.
  • Contains professionally error-free prescriptions and faulty/improvable ones that were accepted by hand. Technically, all are signed: the normal connector signature is applied automatically at sale completion; prescriptions needing a QES move here only after a pharmacist has signed with the HBA. The e-prescription receipt is either attached or still missing (fetched automatically within a day). When all three data records of an e-prescription have been sent to the clearing centre, the globe icon gets a green tick.
  • Forecast (roles Leiter and Umsatzverantwortlicher only): values of potentially billable prescriptions for the next unbilled month. A details window ("potentially billable in MM/YYYY") gives a full breakdown of paper and e-prescriptions sent. E-prescriptions still lacking a QES are counted, on the assumption that they will be signed by month end. Filters change the header figures but not the details window.
  • Filters: All; E-prescriptions; Faulty (not billable); Improvable; Manual check-status change (2 variants); Error-free; Receipt missing; Automatically accepted (error-free and not marked for manual check); Manually accepted. Automatically + manually accepted = All.
  • The final e-prescription data records go to the clearing centre only when every prescription of an e-prescription containing verification-required (securPharm) medicines has been fully supplied.
  • Sort: red, yellow, green, then no status; newest first.
  • Functions: edit prescription (reactivate the sale); "Billed" moves the selected prescriptions to Archive regardless of check status, after a notice.
  • Move to archive: everything from the previous month (including manually accepted faulty/improvable ones) moves automatically from box to archive after the clearing centre's last pickup of the previous month's paper prescriptions. The pickup day is configurable (7). For DRZ customers it is the second DRZ pickup at the start of the following month.

4.A.5 Archive tab (Abgerechnete Rezepte) [DE-SPECIFIC]​

General idea: the billed ledger, kept for clawback research.

  • Shows prescriptions collected by the clearing centre, reported billed by it, or marked billed by hand.
  • Paper prescriptions: all with a dispensing date in the previous month or earlier move automatically from box to archive. E-prescriptions: move once their status becomes "billed". A prescription bracket moves only when all of its e-prescriptions are billed; until then it stays in its previous tab.
  • Header statistics for the filters "e-prescriptions billed in" and "dispensed in". An info button opens "details of prescriptions billed in MM/YYYY" with a full breakdown of paper and e-prescriptions billed by the centre. Filters change the header but not the details window.
  • Filters: All; e-prescriptions billed in current / last (default) / month before last; dispensed in current / last / month before last / three months back (paper and e-prescriptions); Not billable; Faulty; Improvable; Manual check-status change (2 variants); Error-free (billable, including billable ones sent to manual check and accepted); Cancelled.
  • Sort: date and Rx number, newest first.
  • After a change of clearing centre, the system stops a changed prescription in the archive from being sent to the new centre by mistake (message).
  • No image-to-sale assignment here; detail view only.
  • Retax research: 24 months of history. The detail view of a billed prescription shows data as of the real dispensing date. The comparison article search shows which dispensing date's data it uses. Proof of non-availability can be produced from a retaxed prescription here (4.A.18).

4.A.6 Back-office scanning and automatic checks [DE-SPECIFIC] (scanning and matching idea [GENERIC])​

General idea: scan the paper form after the sale, OCR it, match it to the sale, and compare prescribed vs dispensed against payer rules.

  • Put unchecked paper prescriptions into the back-office scanner (landscape, face up). From then on, work on screen only; the paper can go into the box bundled by day.
  • First back-office scan: the prescription leaves Not ready (if it has no ApoTI feedback yet) and is sorted into Rx check or the box by status. Error-free prescriptions not requested for manual check go straight to the box. Scanning an edited and reprinted prescription triggers a new check and re-sorting, whatever tab it was in.
  • Second scan of the same prescription: opens its detail view for manual checking (search in the current tab first, then other tabs from left to right; the newest prescription in the first tab with a hit is shown).
  • Scanning a deferral sleeve barcode opens the prescription detail from any tab (simple view if not yet back-office scanned, extended view if scanned). The first batch scan of deferral sleeves opens the first prescription; the user browses through all, and after each one is handled the next is offered.
  • Status icons show the combined result of the system check and the ApoTI check only after the back-office scan. Before scanning there is no status, even if ApoTI already reported faulty or improvable.
  • The POS (front-office) scan image is not used for checking, so that the full prescription is always checked again with the extended criteria. However, a payer or issue date entered by hand after a POS scan is reused in the back-office check. The issue date can be changed, which triggers a re-check. For a self-recorded sale, the payer entered at the POS is not taken as a proposal.
  • A wrong payer (bad print quality, or a different payer entered at the POS) should be corrected, because comparison article searches run with this payer. If the POS payer differs from the one on the prescription (example: customer stored with a long-term-care fund, IK starting with 18), the prescription gets red status. Fix it via Edit or via the customer function (IK at the customer). The setting "show deviations between recognised payer and the payer stored at the customer as improvable" is on by default.
  • Unscanned prescriptions have only the simple detail view.
  • Double-sided scanning lets the system check automatically for the patient's receipt confirmation on medical-aid prescriptions (hints for detected, not detected, or manual check needed).
  • Recognition tips: corrections and handwritten notes only in blue ballpoint; do not write over the doctor's prescription; no internal notes (e.g. staff initials) on the front; print a shortened pharmacy name on the form (company master data field "pharmacy name on prescription"); before reprinting a corrected form, cover the pricing field with a correction label and initial across the label edge and the form.
  • Fixed print rules for the prescription form, whatever the print form says: Rx number always printed; co-payment and extra costs not printed; operator number, if printed, always on the last line (narcotics form: top); extra info for the clearing centre not printed; no article names for the check printed (keeps the recognition rate high).

4.A.7 Extended detail view and the check rules (Rezepte kontrollieren) [DE-SPECIFIC]​

General idea: field-by-field comparison of recognised prescription data against the sale, with colour-coded confidence and immediate re-check after correction.

  • Used for deferred prescriptions, printed prescriptions and e-prescriptions. Driven by scan recognition and evaluation logic.
  • Colour bars: green = data probably captured and printed correctly (only the bars are green; error-free fields stay white); yellow = data may be wrong, check it; red = critical wrong data printed or faulty dispensing (e.g. the dispensed article is not among the five hits of the discount-contract search).
  • Automatic pre-check covers: issue and dispensing date; payer assignment; presence of practice-site number (BSNR) and doctor number; prescription type; narcotics number on a narcotics prescription (only if the config parameter "ask documentation-relevant data at narcotics sale" is set); customer data (insured number present, birth date vs insured/Rx status; the card's validity end must be checked by hand in some federal states); fee-exemption flag, aut-idem flag and others; correct recognition of prescription lines; correct dispensing; prescribed vs dispensed counts; doctor's signature (a manual correction of signature recognition at the POS scan is carried over).
  • Special rules:
    • If a line was captured at the POS without a scan, the entered source article is used as the prescribed article, as long as it is among the back-office candidates.
    • For discount contracts, the import rule and price economy under aut idem, the priced article is compared. Without splitting, priced = dispensed. Split dispensings are always yellow.
    • Choosing an import whose statutory price is higher than the original shows a retax-risk icon and yellow.
    • Handwritten prescriptions: the POS-entered article is always yellow (see 4.A.9).
  • Full rule list: issue and dispensing date; BSNR and lifelong doctor number present; payer; customer data (insured number, birth date vs insured status, fee exemption); correct recognition; correct article dispensing (discount contracts, import rule, price economy under aut idem, reimbursability, price anchor exceeded (Preisanker)); correct pricing; aut-idem flag; prescribed vs dispensed counts; doctor's signature; aid supply agreements (A+V); patient's receipt confirmation on medical-aid prescriptions; narcotics number (configurable); prescriptions related to artificial insemination; billing deadlines.
  • E-prescription rule differences: some checks drop (signature). Added checks: products not allowed on e-prescriptions; justification of prescription corrections; justification of deviation from the dispensing ranking; justification of Rx status changes; back-orders fully resolved (only then can batch positions be recorded); batch designation for blistered or split articles.
  • What the window shows (paper prescription): a header with a selector to browse the last hit list; status icon (billable, hint, professional error, or no status = requested for manual check by settings); Rx number; regulation icon (including "missing"); printed dispensing date; customer; print status; pickup/deferral icons; deferral number; info icon; send status (ApoTI feedback received); sums of co-payments and extra costs; total gross. Scan area: image snippets (patient data at top, prescription lines in the middle, stamp/signature at bottom) with zoom. Check area: recognised printed data, operator, workstation, dispensing date, hints; fee liability, night (noctu) and other fees, accident flag; customer data comparison (payer, name, address for stored customers, else recognised data) and issue date; sale data (operator, workstation, Rx type GKV/private/green/BtM GKV/BtM private, printed dispensing date and sale date); up to three prescription lines with aut-idem flag, "A" (article prescription), special code set, prescribed quantity. For each line, row 1 = recognised prescribed article, row 2 = dispensable article found via discount contract / aut idem / import search. A dropdown offers other exchange articles. This list is rebuilt at check time and can differ from sale time, so check promptly; not shown for billed prescriptions. A delete button clears the source article for manual entry (not for billed). An icon shows why an exchange was proposed (discount search, aut-idem search, import search, "vicinity search"). Stock articles are shown in bold. Article-line column layout is shared with the POS prescription scan.
  • Hints table entry types: info, hint, warning, accepted (ignored) hint, accepted warning. ApoTI messages carry a status-adjust icon. E-prescription ID shown on hover.
  • Correcting: first check for a recognition error. Often selecting the right prescribed article from the hit list (or deleting and re-entering it) is enough, and the dispensed article is re-checked at once. If the dispensed article was not prescribed or not allowed, edit the prescription (reactivate the sale). For other data: reactivate, change the prescription subtotal, apply a correction label, reprint. After a correction the prescription is cancelled at the clearing centre and re-sent for checking; the internal status updates immediately.
  • Issue date can be changed in the customer-data area through a simple date dropdown.

4.A.8 Assign an image to a sale (Rezeptbild einem Verkauf zuordnen) [GENERIC]​

Matching unmatched scanned documents to transactions.

  • The automatic check tries to match every back-office image to an earlier sale. Unmatched images show as red rows in Rx check.
  • Assignment window: image plus a search for the last 3–4 digits of the Rx or deferral number, or a stored customer's surname. With no search term: the last 200 prescription sales without an image. With "*": prescription sales without an image from the past 60 days. Hits show regulation icon, Rx number, deferral number, customer, date, total gross. The detail shows Rx status, payer, operator, doctor and all articles of the prescription subtotal, with icons: "not available" flag stored; aut idem excluded; no discount contract with the payer although discount articles were reported at capture (retax risk); substitution notes from the federal joint committee (G-BA) and discount contract correctly observed; discount contract correctly observed; priced per aid agreement (A+V); split; open pickup (not fully delivered); supplier.
  • Take over the assignment: the prescription appears in Rx check. No match: discard the image (file deleted), or leave the window and assign later.
  • Outdated Rx numbers (a newer state with a new number exists) and test prescriptions cannot be matched automatically. A red hint shows, and the system warns on assignment. Recommended: discard and compare the printed form with the sale, or reprint with correct data. The user may still force the assignment.
  • Retention: unusable image files that cannot be assigned are deleted after one week; good images stay available for assignment for 60 days.

4.A.9 Special prescription kinds [DE-SPECIFIC]​

  • Handwritten prescriptions: checked automatically too. The prescribed article is the one captured at the POS (by hand or by scan); it is always shown yellow, but this does not make the status improvable. If everything else is fine, the overall status is error-free. The setting "handwritten prescriptions" under manual-check selection forces a manual check; otherwise error-free handwritten prescriptions go to the box after scanning.
  • Compounded preparations, parenterals, generic articles without PZN, rental articles, unit-dose/weekly blister: no automatic check; simple detail view (with option to show the image). They must be checked even with green status, because green here only means "billable according to the clearing centre", not pharmaceutically checked. Whatever the settings, prescriptions with compounded or parenteral preparations and those with special codes are always offered for manual check with yellow messages.
  • Private and green prescriptions: can be checked but are not listed in the overviews. Open them by Rx or deferral number in the simple detail view; the same functions as for GKV are available (check, print, accept, check later, etc.). They are still sorted into tabs by status (visible in the detail navigation). ApoTI functions are unavailable for private prescriptions without a parenteral preparation and for green prescriptions.

4.A.10 Manual check-status change and feedback remapping [GENERIC]​

Override of rule results by a responsible person, with an audit trail.

  • Ignore hint: a hint can be marked ignored (icon) after a thorough review, e.g. to accept an error on purpose. The prescription's status is the highest-priority remaining active hint. If all hints are ignored, the status is green "with hint" (own icon). "Activate hint" re-enables it. Every change is logged in the prescription history (operator, time). If ignoring makes the status green, the prescription moves at once from Rx check to box; reactivating the hint moves it back.
  • Remap clearing-centre messages (Prüfregeländerung): per ApoTI message type, the pharmacy can change the status to Info (no icon, lowest priority), Hint, Improvable or Error. All later feedback of that type gets the new status, shown with a suffix like "(originally: Error)". The list of remappings is on the settings page "ApoTI control"; each can be deleted. Recommended: set messages that never lead to action to Info, so affected prescriptions go straight to the box. Messages marked "(manual check)" can likewise be set per type to Info (no status, automatically to box) or Improvable.

4.A.11 Take over payer (Kostenträger übernehmen) [GENERIC]​

  • If the customer master record has a different payer than the one captured at the sale (e.g. the customer changed insurer), the recognised payer is highlighted yellow with a yellow hint. Options: copy the recognised payer into the customer record (with confirmation), or ignore the hint (marked ignored; payer not copied).

4.A.12 QES signing with the pharmacist's card (eHBA) [DE-SPECIFIC]​

General idea: a personal, qualified digital signature by a licensed pharmacist on corrected electronic prescriptions.

  • A pharmacist must sign with a QES using the HBA where prescription corrections were made or the dispensing ranking was not followed; otherwise the e-prescription cannot be billed. Some pharmaceutical services also need a QES. Prescriptions with the special code for non-availability need no HBA signature.
  • Indicators: QES required; QES applied.
  • Flow: in Rx check, quick filter "for signature with HBA" → Sign → list; tick "only own" to see only e-prescriptions assigned to me for signing; tick rows; confirm; insert card; enter PIN.
  • If the card's certificate expires in under 3 months, a notice with a reorder link appears.
  • Month-end reminder task (see 4.A.3).

4.A.13 Batch correction for billing (Chargenkorrektur) [DE-SPECIFIC] (batch traceability [GENERIC])​

  • Window shows article name, PZN, sale quantity (a guide to how many batches are needed) and the batches recorded so far, in the sale or here.
  • Batches scanned during the sale are shown italic and cannot be changed or deleted. Batches recorded afterwards are marked with a pencil.
  • No batch recorded: yellow warning plus notice. Too many batches: red warning plus error; the window cannot be left until the extras are removed.
  • Record by hand or by scanning the pack's securPharm code. A batch pre-recorded for a back-order is replaced when the pack info is scanned later. "Copy batch" for several packs of the same article; "suggest batch" picks from a proposal list.

4.A.14 Moving between tabs and cross-tab functions [GENERIC] (warnings [DE-SPECIFIC])​

  • Accept / move to next tab (F12): Not ready → Rx check; Rx check → box; box → archive ("Billed"). The prescription subtotal stores date, time, operator and workstation for accept, check and change.
  • Warnings on manual moves:
    • From Not ready ("accept check"): if the selection includes prescriptions without ApoTI feedback, with open pickups, with advance deliveries, unprinted paper prescriptions, or prescriptions with electronic additional data (Z data), a modal lists each point with a checkbox to decide what to move. A prescription listed under several points stays if it is unticked under any one. Up to 3 e-prescriptions are listed by ID and patient name.
    • From Rx check: prescriptions not yet accepted for billing, with open pickups, or without the required QES trigger a modal. Preset and not editable: "checked prescriptions" ticked; "without required QES" unticked, so these cannot be moved.
    • From box ("Billed"): e-prescriptions, prescriptions with open pickups, and e-prescriptions without a receipt trigger a modal. Warning: archiving e-prescriptions by hand loses track of which were really reported billed and distorts the billing forecast.
  • "Check again": asks for an already checked prescription in box or archive to be checked again. It moves to Rx check with a green arrow and must be moved to the box again by hand. Not available for cancelled GKV, narcotics, parenteral and thalidomide prescriptions.
  • "Check later" (später kontrollieren): marks the prescription with an icon; it stays in Rx check; an info note can be added. It does not stop transmission to the clearing centre.
  • Other functions available across tabs: add attachments (print attachments for medical-aid billing; DRZ billing only); edit prescription (4.A.15); info; article info (drug database); Rx details (subtotal details); print overview (list of the current tab, exportable to Excel from the print preview); customer details / edit or make customer assignment; retax management; risk check (customer-related); show e-medication list; print prescription; parenteral details (jump to the parenteral module); ApoTI details (data record; ApoTI only); show image; open sales administration with the prescription selected; refresh view (automatic every 10 minutes); doctor query by e-mail (image attached automatically; encrypting the attachment is recommended); query ApoTI status; send via ApoTI / re-send (for a cancelled prescription or one whose sending was cancelled); delete image (multi-select, with confirmation); history; comparison article search for the prescribed or dispensed article (for checking only; another article cannot be taken over); settings; multi-select; fetch e-prescription receipt (several selected e-prescriptions, any status, in Not ready, Rx check or box).
  • Extra functions in the detail view: calculation (price calculation of a position, simple view); position details (price info); show discount agreements; accept (with the worse-status rule from 4.A.3); settings (manual-check criteria; pickup date).
  • Restrictions on Edit and Print: not for prescriptions in archive (use "check again" first); not for cancelled parenteral or unit-dose prescriptions; not when the order is already fully invoiced (the invoice must be discarded first). Print prescription is likewise unavailable in archive and for cancelled parenteral/unit-dose prescriptions.
  • Copy Rx info for research: for the pharmacists' association after a retax notice: Rx number, PZN of the dispensed article, dispensing date; e-prescription data records can also be copied. The prescription data record holds personal data, so send it only encrypted.

4.A.15 Edit a prescription (Rezept bearbeiten) [GENERIC] (re-submission rules [DE-SPECIFIC])​

Post-sale correction by reopening the sale, with a mandatory reason and automatic re-check.

  • Reactivates the sale at the POS or the invoicing POS, the same as editing from sales administration. Any deferral number is released at once. Not possible for billed prescriptions in archive.
  • Reason dialog: a predefined reason (e.g. "article exchange") plus free text. Whether it opens on every reactivation or cancellation depends on the config parameter "input dialog cancellation reason" (POS system settings, general sales).
  • If the subtotal belongs to a sale with several prescription subtotals and at least one has a back-order or a credit payment, editing is only allowed for the whole transaction (message).
  • Complete the change with Total, finish the sale, then verify in the prescription print window. The print can be deferred (assign a deferral number) or aborted. Put a correction label on the price field and reprint.
  • Effects: the prescription moves to Not ready, so the re-check is not missed; its ApoTI status is deleted; it is cancelled at the clearing centre and re-sent; the internal check runs again automatically; the image becomes outdated, so rescan.
  • Changed dispensing date: a red warning icon appears at the date in the detail view; a window "change dispensing date for prescription print" lists the change; confirming updates the data; a notice recommends rescanning; the prescription moves from box to Not ready. If a back-office image is assigned and the date is changed, date rules (e.g. "issued more than 3 months ago") are no longer shown, and a grey camera icon appears after a change of form type or date.
  • If the dispensing date or form type of a printed prescription is changed and the print is then aborted, it still counts as printed, keeps its Rx number and is not re-sent via ApoTI.
  • Deferring the print after editing: with ApoTI it waits in Not ready to be sent; without ApoTI it goes straight to Rx check; marked with the deferral icon. Aborting the print gives no deferral mark.
  • Editing a prescription in box or archive (from prescription management, sales administration or the invoicing order overview) shows a warning about its processing state. One already sent to the centre and billed should be edited only if the centre returned it for correction (data kept 24 months); rescan after printing the correction.

4.A.16 Deferrals (Rückstellungen bearbeiten) [DE-SPECIFIC] (deferred documentation [GENERIC])​

  • Prescriptions whose print was deferred at sale must be checked by hand and then printed.
  • The back-office scan reads both the deferral number on the sleeve and the prescription image. Matched prescriptions always open in detail; unmatched ones open the assignment window.
  • Deferrals are no longer possible for e-prescriptions. Exception: when a paper prescription that was owed (Rezeptschuld) is settled with an e-prescription, the deferral number is removed on settlement.
  • Steps: scan sleeves (back-office scanner, hand scanner or POS scanner) or type the deferral number; at most 10 sleeves per batch recommended; check; edit the sale if needed; accept; correction label; print; next. Accepted prescriptions go to the box.

4.A.17 Images, info notes and history [GENERIC]​

  • Show image: front and back, full and enlarged. Quick view by click (front only) or via the function (front and back if the back was printed; detected automatically at scan). Only one image is stored; a POS image is overwritten by a back-office image. Also viewable in sales administration and the customer's sales list. An image from before a re-edit is labelled "outdated image". The detail view prefers the back-office image, otherwise the POS image.
  • Delete image: removes the file. If the prescription had already been checked and accepted (manually or automatically) and was in the box, all internal check statuses are deleted and it returns to Rx check.
  • Info note: free text that can be stored, edited and deleted on a paper prescription, an e-prescription and a DRZ deviation. For e-prescriptions it is a "digital sticky note" available throughout the process (order list, e-prescription dialog, POS, prescription management). Blue icon = info present, grey = none. On accepting a deviation the info window opens automatically for an optional reason; info on an accepted deviation shows with a green overlay.
  • History: every status change in the module with time, workstation and operator. Logged statuses: Created (a prescription attached to a sale was made available for checking), Check accepted, Billed; plus manual status changes (ignored hints).

4.A.18 Retax research tools [DE-SPECIFIC] (historic-data audit [GENERIC])​

General idea: be able to prove, after the fact, that a dispensing decision was correct with the data that was valid at the time.

  • Rx.secure: checks run with the price and discount-contract data valid on the dispensing date, even after the price update service has changed the data (on the 1st and 15th of each month). 24 months of history on prices, discount contracts and billing info for medicines and aids; this also allows correct checks after a price-update change. If the dispensing date was set (in the print window) outside the current price-update period and the prescription was not edited despite the warning, the detail view shows the dispensing date in red with a red message that it was changed after sale completion and needs a manual check. Billed prescriptions returned by the centre can be reprinted with the data as of the real dispensing date. The comparison search list shows which date's data it used. The detail view shows: processing date/time ("Vorgang"), the stored, possibly changed and printed dispensing date ("Abgabedatum"), and a note "checked against update service of <date range>".
  • Proof of non-availability (Nichtverfügbarkeit nachweisen): for a retax on a GKV prescription, produce proof that all articles that could have been dispensed were unavailable. Uses the stored history of online availability queries (36 months). View: source article for the comparison search (the prescribed article, or if none, the dispensed one); hit list of availability results at dispensing time (green = fully deliverable at once or via the group/network; red = partly or not deliverable; no symbol = no result for that article on that date, e.g. not every search was run at dispensing). The hit list shows the best result: if at least one supplier could deliver, it says "deliverable". The detail shows availability per supplier. Steps: in archive, find the retaxed prescription by Rx number or e-prescription ID; select the retaxed line; "prove non-availability"; choose the reference time for the query history (at query time, or another time, e.g. if a different article was dispensed after completion or the dispensing date was changed by hand); print with option "proof of non-availability". The printout lists only the preferentially dispensable articles with result "not available". If the article is available via wholesalers, only the results of wholesalers that could not deliver at the query time are printed. If it is available only direct from the manufacturer, only that supplier's result is printed, if it could not deliver.
  • Retax letter filing (Retax-Verwaltung): scan A4 clawback letters with the prescription scanner; list shows capture date, operator, info icon, info text (e.g. affected Rx numbers, clarification state) and preview. Functions: save info, next document, delete, enlarged view, print with preview.

4.A.19 Cleanup of old prescriptions (Rezeptkontrolle aufräumen) [GENERIC]​

  • For pharmacies that never or only partly used the check: mark old prescriptions as billed and move them to archive.
  • Criteria: created/issued before a date; "include" checkboxes for printed prescriptions / e-prescriptions (signed and with receipt), unprinted prescriptions, missing prescriptions (original not present), and deferrals.

4.A.20 Search prescriptions (Verordnungen suchen) [GENERIC]​

  • "Only e-prescriptions" toggle: limits all tabs (and their counts) to e-prescriptions; saved per operator across restarts; not cleared by the reset icon.
  • Search by e-prescription ID (or some digits), deferral number, or Rx number (last 3–4 digits for paper). The Rx number is assigned by the system; the deferral number is assigned when a sleeve is scanned or typed in when deferring the print. Both are stored on the prescription subtotal. A sleeve can also be scanned (including with the back-office scanner). One hit opens the detail. For e-prescriptions a simulated prescription image can be shown. Search order: current tab first; otherwise the newest prescription with that number in another tab.
  • At most 200 results, newest capture date first.
  • Filter criteria window: dispensing date as printed (range inclusive at both ends); billing of pharmaceutical services (included by default); paper / e-prescription type toggles; customer; print status; and others. Filters apply to all tabs. One hit opens the detail. If there are hits in the current tab and others, focus stays; if none in the current tab, the leftmost tab with hits opens. Option "include old prescriptions from data migration" (default: only prescriptions captured in this system). A filter for e-prescriptions with an "RX real-time check" exists (described elsewhere).

4.B Clearing-centre online pre-check (ApoTI) [DE-SPECIFIC]​

General idea: send each claim to the billing intermediary immediately after the sale for a pre-check, and show its verdict in the pharmacy's work queue.

4.B.1 Setup​

  • ApoTI is an online interface to the clearing centre, which bills GKV prescriptions and private parenteral, unit-dose and weekly-blister prescriptions. It is switched on in company master data (clearing-centre page; another module).
  • System parameters (POS system settings, scope system parameter, group "prescription check"): transmission interval (setting an interval turns on automatic sending; the value "no transmission (internal installations only)" has no effect in pharmacies, so the default 10 minutes applies); "send only GKV parenteral prescriptions"; "send private parenteral prescriptions".
  • No automatic sending during the nightly system maintenance (manual sending still works). During a registered emergency service (Notdienst) sending continues as normal.

4.B.2 Sending and status​

  • All prescriptions are sent automatically for pre-check after the sale is completed, except unprinted prescriptions without a deferral (e.g. print aborted). Default interval 10 minutes; the view refreshes every 10 minutes.
  • Manual send: sends an unchecked prescription at once; its feedback must then be fetched by a manual status query. Re-send is needed after a send error or if the centre's check has an undefined status. Status queries are normally automatic with several attempts.
  • Reasons a prescription cannot be sent (it is marked with an error): the system's own pre-validation fails (Rx number must exist; Rx numbers must be unique; the pharmacy number stored on the prescription must match company master data); technical or network errors; centre unreachable; centre overloaded and returning an error.
  • Status icons: feedback received; can be billed; sent, no feedback; to be cancelled; cancelled.
  • Editing a prescription cancels it at the centre and re-sends it (4.A.15). After a change in sales administration, the prescription must be printed again when the print preview appears; only then does it go on the send list. If the print is aborted it is not sent (workaround: print on blank paper).

4.B.3 Connection scenarios​

  1. Connected (normal): prescriptions are sent; statuses "sending" and "with feedback". Prescriptions cancelled in sales administration are filed in the archive.
  2. First connection: after saving the settings, all ApoTI functions are activated and prescriptions are sent automatically. Prescriptions captured more than 2 weeks before the first connection go to the archive; newer ones are sent and join the normal process.
  3. Change of clearing centre: disconnecting and reconnecting need not happen together. While disconnected, ApoTI functions are greyed out; after reconnecting, automatic sending resumes. Statuses from the old centre's feedback and the status of not-yet-sent prescriptions are kept. A changed prescription in archive cannot be sent to the new centre by mistake.
  4. No connection configured: initial state.
  5. No connection due to errors: as in 4.B.2.
  6. Data migration from another system: prescriptions processed in the old system are not shown at first but can be found via search (option "include old prescriptions from data migration"). If one is edited, it joins the normal process.

4.B.4 Parenteral transmission info (ApoTI details)​

  • For a parenteral prescription, the window "information on data record" shows the data in 3.3. The hash code is printed on every paper and private parenteral prescription.
  • Price identifier rules: preparations whose calculation basis is neither "hospital supply" nor an individual contract — all components with price identifier 14, labour prices 74. Hospital supply (from 2015-10-01) — application aids (flag A) and finished medicines with price identifier 16; a surcharge above 0 is flagged with special code 06460518; labour price identifier 76; only one preparation surcharge per manufacturing segment. Individual contracts — finished medicines and application aids 15, labour price 75.

4.C Clearing-centre billing dashboard (RX Control 4.0, DRZ) [DE-SPECIFIC]​

General idea: reconcile what the pharmacy thinks it sold on prescription with what the billing intermediary actually billed, month by month, and act on the differences.

4.C.1 Overview​

  • Pulls billing data from the DRZ portal into prescription management: overview, details for the current and two previous months, download/print invoices and statistics as PDF for billed months, and tracing of deviations between IXOS and DRZ data. Access is permission-protected when the sensitive-data concept is on. Portal credentials are set in the clearing-centre settings (another module).
  • Overview tab, for the running month and the last two closed billings: gross prescription turnover at DRZ (total, e-prescriptions, paper); number of prescriptions billed or to be billed, minus the night/emergency-service fund self-declaration (total, e-prescriptions, paper); deviations = count and gross sum of prescriptions with yellow or red status in the Deviations tab (accepted ones not counted), computed as DRZ minus IXOS, only for billed months; best value = comparison with pharmacies in the same peer group on turnover and count (closed billings only). Buttons: request direct payout; download invoice PDF; download statistics PDF. Bar chart of gross prescription turnover for the last six months.
  • Per-payer figures from the last billing (only in the main pharmacy for chains; after the billing closes): option to show 0.00 values; test strips = total reduction per payer, ascending; import account = balance per payer, ascending.

4.C.2 Month tabs​

  • Current month: prescriptions received so far from IXOS with a dispensing date no older than 24 months, whose gross amount and co-payment per DRZ billing agree with IXOS, or whose deviations were accepted. Previous two months: billed prescriptions, plus invoice and statistics download. The months roll over when the DRZ billing documents are ready and uploaded to the portal.
  • Filters: All; only e-prescriptions; high-priced (at least one article with a pharmacy purchase price of 1238.53 EUR or more); narcotics; practice supplies (SSB).
  • Comparison count DRZ vs IXOS and gross sums DRZ / IXOS (tooltip splits e-prescription vs paper).
  • Table: Rx number; regulation icon (GKV, narcotics, electronic additional data / unit-dose / weekly blister, thalidomide, accident insurer, cancelled variants, private with additional data, not scanned, care-aid billing); dispensing date/time (sale completion); customer; print status (printed; printed with attachments); deferral number; pickup/deferral icons; info icon (info stored; returned from check; both); image icon (back-office scan with matching sale; scanned but outdated or unmatched; POS scan); total gross.

4.C.3 Deviations tab​

  • Deviations between DRZ billing and IXOS capture, typically caused by operating errors. Care-aid billings above the monthly cap of 42 EUR are not shown as deviations and are excluded.
  • Two-sided view: IXOS side (count and gross sum; data and image from IXOS) vs DRZ side (count and gross sum; data and image from DRZ). Month selector.
  • Filters: All; matched green (matched uniquely though with a different Rx number, no content deviations); matched yellow (content deviations); only IXOS / only DRZ red (not matched); accepted. Checkbox to show accepted deviations.
  • Match icons: only IXOS / only DRZ (could not be matched to an IXOS sale or to a physical prescription at DRZ); matched but not via a unique Rx number in the transmission, or prescription at the end of a sale chain (different matching number, Rx number history known); Rx numbers differ — matched via gross amount, payer IK and dispensing date; accepted.
  • Columns: Rx number, regulation icon, dispensing date, customer, co-payment (0.00 if fully cancelled in IXOS), total gross (0.00 if fully cancelled).
  • Detail views: last scanned image; dispensed articles (IXOS) vs billed articles (DRZ); print preview of the last state of the sale; prescription history if data changed; targeted hints about the detected deviation.
  • Functions: check the deviation (print preview, or open the sale in sales administration); accept deviation → status accepted, shown in the month tab, no longer counted, so the month sum matches the DRZ sum (an info window opens for an optional reason); check again returns an accepted deviation to its previous yellow/red status.

4.C.4 DRZ Cash​

  • Request an automatic advance payout from within the system. Needs permission "Rezeptmanagement-DRZ-Cash" if the permission concept is used. Enter an amount (capped at 80% of last month's prescription turnover), send, get a confirmation. Sent requests are listed in the notes module.

4.C.5 DRZ pickup dates​

  • For DRZ customers, the next pickup date is shown in Not ready, Rx check and box. Two dates per month (mid current month and start of next month) are imported from DRZ, so no pickup day needs to be set in the settings. Box → archive happens only at the second pickup at the start of the following month. Dates appear in the "today's tasks" window; tasks are created automatically in the notes module in good time before each pickup; calendar entries are flagged DRZ and can be moved.

4.D Prescription requests to doctors (Rezeptanforderung)​

4.D.1 Request list [GENERIC]​

Pharmacy-initiated repeat-prescription requests for patients whose medication it manages.

  • Paid add-on module. Opened from the desktop/Sales menu, from a selected doctor contact or contact details (Print → prescription request), or from a care-home contact or home structure (Print).
  • Legal basis (DE): the customer's consent to store care-relevant data includes a power of attorney to ask the treating doctor for follow-up prescriptions of long-term medication. General idea: patient consent that authorises the pharmacy to contact prescribers on their behalf.
  • List: free-text search (doctor or customer). Filter "Current (n)" = requests not yet printed, sent or archived, n = open count. "All (n)" = open plus archived from the last 12 months. Date range filter, default the last 14 days.
  • Columns: see 3.9 (created at, recipient doctor with phone, period, positions, created for, created by, medication-booking state icon, channel/state icon, info icon if extra positions exist).
  • Positions table: care-home icon, customer, birth date, article and dosage form (or substance, strength, form), PZN, stock and range at creation, receipt state. Range is not computed for substance prescriptions, as-needed or free-text dosing, or negative stock in blister courses.
  • Per-request text fields: "additional positions" (items not in medication management, e.g. dressings) and "supplementary note" (per-doctor text; if empty, a system default is printed). Both editable only until printed/sent.
  • Functions: New; Print/Send (channel from the doctor contact: print, fax or e-mail); Reprint (for sent requests); Delete one or several (confirmation states the count); Delete position, with two options: suspend until the next request (removed only from this request; it reappears next time) or do not request until a date; Archive; jump to the customer's medication plan.
  • Archiving: automatic when all requested positions have been booked into medication management after the prescriptions arrived. Manual archive for requests where some prescriptions will never come; position states are kept.
  • E-mail needs the system e-mail configuration. Fax needs a fax service provider in company master data (external services); two providers are supported.

4.D.2 Create requests [GENERIC]​

  • Scope (choose one):
    • For a customer: picker lists all customers in medication management (care-home unit filled in automatically). Doctor dropdown: "all doctors" (default; only medications assigned to a treating doctor), "without doctor assignment" (medications with no treating doctor; the request goes to the family doctor stored in the contact data), or one specific treating doctor. If "for customer" is chosen but left empty: all pharmaceutically cared-for customers who need a request in the period.
    • For a care-home unit: picker lists homes and living units assigned to cared-for customers; same doctor dropdown; empty = all.
    • For a treating doctor: only customers/medications assigned to that doctor; empty = all customers/medications with a treating doctor.
  • Period: "calculated automatically" = 14 days from today, extended by the doctor's extra lead days and absence/holiday days; or "absolute" = user-defined, ignoring the doctor's extra days and absence.
  • Scope filters (each With / Without / Only): blister articles (default With); as-needed dosing (default With); long-term medication (default With); advance deliveries (default Without).
  • Checkbox "long-term medication with customer stock 0": includes long-term medication at zero stock, however long it has been at zero; only affects non-blister courses.
  • Checkbox "print current customer stock": adds a stock column to the printout (off by default).
  • "Save as default" stores the filter choices.
  • Blister automation: include every blister medication that would reach negative stock within the period, except when: the resident is deceased or inactive; the period lies entirely inside a pause, or after a discontinuation with reason "inpatient stay"; no dosage is entered for the period. Blister courses manually forced to be requested are also included. These rules do not apply to non-blister courses.
  • Config "ignore courses discontinued in the past" (system settings, blistering): excludes blister medications with negative stock whose discontinuation started in the past.
  • Course-level override (course details, from blister management or medication management): "do not request until <date>" or "request once against the automation". The course details show which rule applies and whether the course is currently on a request.

4.D.3 Print or send requests [GENERIC]​

  • With filter "Current", all unarchived open requests are listed. Tick the ones not yet printed/faxed/e-mailed (select-all toggle) and Print/Send; each goes by its preset channel. Printer settings can be adjusted. Layout comes from the print-forms module; two templates: standard, and one for app customers using a prescription subscription service.
  • Printout content for the doctor: need period end (basis 14 days); customer (surname, first name, home name, living unit); birth date; article; dosage form; stock at request time; dosage; need = requirement for the period computed from dosage and current stock.
  • Warnings: not all open requests are selected; an already sent request is selected; leaving the module while requests are unprinted/unsent.

4.E Sales administration (Verkaufsverwaltung)​

4.E.1 Transaction list and search [GENERIC]​

A searchable journal of all completed sales and orders, used to trace, reprint and prove past transactions.

  • Search header: date/time from–to; customer (a name in at least one subtotal); article (a name in the transaction); sale type; closing/payment type (All, Cash, Credit, Card, Direct debit, Cheque, Online); transaction type (default "till receipt"; alternatives "sales" = receipts + orders, "All", invoicing order, cash deposit, cash withdrawal, Z/S/X/J/M/T summary receipts, card terminal settlement, drawer, test prescription). Opened from the POS with a customer assigned, the filter starts on "sales". The default is set by the config parameter "Vorbelegung Vorgang" (default transaction type).
  • Number field: an exclusive search over document numbers (e-prescription ID, Rx number, deferral number, receipt or order number, pickup slip number, external document number such as a webshop order), independent of the transaction filter.
  • Hit list: transactions handled, edited or cancelled in the period, in time order; default period today. Columns: date/time; workstation; operator surname ("System" for webshop sales); customer(s); transaction/document type; total; pickup slip number; credit slip number; chain icon (linked to other transactions by cancellation/reactivation, pickup resolution or credit resolution).
  • Subtotal list (sales only): running number; sale-type icon (normal sale, GKV, private, green, narcotics prescription, care aids; cancelled variants); sale type and status text; customer; Rx number (e-prescription ID in a tooltip); Rx history / Rx history-chain icons; Rx missing / Rx printed; deferral number; Rx total; image icon.
  • Article list: PZN; special-code icon (tooltip shows the code, and for "discount article not dispensed due to pharmaceutical concerns" also the documented concerns); name/details; split/blister icons; discount-contract / aut-idem / uneconomic icons; quantity dispensed; quantity not available (to be or already delivered later).
  • Cancelled items: cancelled by an operator = red italic. System counter-postings (e.g. when a quantity was reduced) = dark grey italic, shown only if the config parameter "show system cancellations" is on.
  • Receipt preview: the receipt of a POS transaction or the details of an order; extra previews for pickup slip, credit slip and courier slip. Print data is stored for every transaction except test prescriptions. Partial delivery is a special case.
  • Show history: narrows the list to all transactions linked to the selected one, by date; "end history" returns.
  • Rx history chains: if a prescription is printed later with a changed dispensing date and the change does not alter any print data (prices, discount contracts), a history chain records the date change (icon at the GKV subtotal). If print data do change, the prescription is edited and a new transaction appears in a normal chain.
  • Other functions: risk check for the assigned customer; prescription image (at total level or via the subtotal icon; a selector if several prescriptions were scanned; always the last scanned image, POS or back office); reprint of the billing receipt for privately insured (a filter for private e-prescriptions = sale type private Rx + form e-prescription); position details; drug-database article info; change delivery type (pickup ↔ courier ↔ post).
  • Find by pack scan: scanning a pack barcode lists all sales of that article, including packs with their serial numbers. Scanning a securPharm DataMatrix finds the exact sold pack by article and serial number. Scanned without an article selected, the article is filled in and only sales with that pack are shown.
  • Find by receipt barcode: scan the barcode on a till receipt (if barcode printing is set in the print forms). In sales administration this lists and selects the sale; at the POS it opens the sale for editing.
  • e-prescription ID: full ID in the Number field, or partial in the advanced search.

4.E.2 Advanced search [GENERIC]​

  • Criteria: date/time from–to; workstation (all or one); employee; "created automatically by the system" (for totals: webshop sales, pickup terminal; for orders: stock transfers); customer; article; sales channel (All, pharmacy, customer app ("Meine Apotheke"), clinic portal (Klinik.connect), care-home order, doctor portal (Arzt.connect), webshop, wholesaler-standard order interface (MSV3.connect), a further ordering portal (PHBEST.connect), the national e-prescription app (Gematik app)); sale type (Rx status, including care aids); Rx form (none / paper / e-prescription); closing type; position type (All, article, generic article, fee, cash sale, additional costs); VAT rate (All, full, reduced, none); transaction type; document number; e-prescription ID / Rx number (partial allowed).
  • A document number identifies one transaction uniquely, so other criteria (e.g. the period) are then ignored; the same applies to credit numbers, Rx numbers and the like.
  • Extra parameters by transaction type: external order number (webshop; full number with leading zeros, or with % wildcards such as %210%); securPharm serial number; "only settlement of" invoices / credits / dunning notices (dunning only when a dunning fee was charged, otherwise listed under invoices) — finds receipts that settle such documents (receipt transactions only).
  • Searching "All" can be slow.
  • Test prescriptions are hidden by default; choose transaction type "test prescription". Supported: search, advanced search, details, help; no receipt preview. Details show general data and the reason entered.

4.E.3 Transaction details (Detailangaben) [GENERIC]​

  • Total — General tab: general data; names of scanned discount coupons; articles for which counter-scanning was bypassed; verification-required articles whose securPharm verification was bypassed; an automatic courier fee that was removed by hand. Printer icon if the receipt was printed; a combined icon if printed and sent to the customer app. With a customer-display licence ("kassen-TV"), icons show how a 2D code was issued: printed only, sent to the app, or both.
  • Discounts / coupons / vouchers tab: manual discounts, redeemed discount coupons, value vouchers, sum of discounts after total.
  • Pickup terminal tab: log of terminal events (date/time, pickup number, shaft, status, description; with a picking robot, retrieval and verification). For terminal type "BD Rowa Pickup": cancel a pickup order (status Created or Stored), which cancels it in the pickup cloud; retrieve (status Stored) to the workstation output.
  • Test prescription details: general data and reason.
  • Other transaction types: deposit details; order details; cross-site stock withdrawal order (quantity requested vs withdrawn); clinic order.
  • Subtotal details: tabs General (sale info including prices); Prescription (prescription info and check info, including date/time/operator/workstation of accept, check and change, and dispensing-date changes on reprint); Care aids; Cancellation (reason and note; only if cancelled); Prescription image; Webshop.
  • Position (article) details: available from the POS (price info), prescription management (position details) and sales administration. Tabs depend on position and sale type:
    • General: article and sale features, reason for a special code. For medical aids: captured billing data, whether it is a consumable aid with a supply period; composite aids have a second billing line for the extra component; tooltips on contract-code fields (service-provider group key, billing number, billing flag) show whether a value came from the aid-contract database or was entered by hand.
    • Sale prices: price determination, discounts, effective price. For OTC items priced by the pricing module: calculation details including price usage model, validity period and dispensing time. If the sale was based on a cost estimate/offer, the offer number. An icon if discounting is restricted.
    • GKV prices: co-payment, extra costs, whether the co-payment was changed by hand and its reference (e.g. per line).
    • Price statistics: price bases as of the reference date.
    • Advance delivery info.
    • Pack info: batch documentation, expiry date, securPharm pack data.
    • Flat-rate billing (aid flat rates): name of the flat rate and all articles billed against it, with prices and net yield.
    • Unit-dose / weekly blister: the calculation rule used and the billing price.
    • Other position types: generic-article/special-code details, aid flat rate, fee details, cash-sale position details.

4.E.4 Reprint documents and labels [GENERIC] (some documents [DE-SPECIFIC])​

Available from sales administration (and the POS) for the selected transaction:

  • Till receipt; with direct-debit payment also a SEPA direct-debit reminder slip.
  • Partial receipt for a selected subtotal (plus its SEPA reminder).
  • Receivable-settlement receipt(s): receipt with article list and total; if part of the credit was paid earlier, also the partial-settlement receipt. If already printed, choose original or copy.
  • Additional receipt (Zusatzbon): customer and all articles with quantities, prices and total; configurable print form; useful as an extra slip for courier delivery; also for receivable settlement.
  • Receipt and voucher (sale of a value voucher).
  • Card merchant slip reprint; card terminal closing slip.
  • Labels for all articles: customer and care-home labels for every article of a transaction with a customer; adjustable count.
  • Address labels for pickups (standard label, chosen count).
  • Check-out coupons, reprinted on a separate slip.
  • Cancellation receipt (cancelled subtotals).
  • Pickup slip for back-ordered items; cross-branch/partner pickup slip reprint.
  • Packing list for assembling back-orders for a pickup; courier slip, courier label, courier packing list.
  • Credit slip, on the receipt roll or A4.
  • Prescription form.
  • Care-aid billing (declaration of receipt of a care aid), one per care-aid subtotal.
  • Reminder slip for missing prescriptions; SEPA reminder slip.
  • Usage instructions: patient notes from the drug database for the medicines of a prescription sale, for the total, a subtotal or one medicine; printed on the receipt printer.
  • Proof of GKV prescription (so the patient can claim back self-paid costs).
  • Billing receipt for privately insured (offered at completion of a private e-prescription sale; reprinted here; permission-bound).
  • Export and purchaser certificate for customers taking goods to a non-EU country (e.g. Switzerland): contains customs data; when the stamped document is presented, the VAT can be refunded. For a total or a subtotal.
  • Rules:
    • Reprinting a receipt that was already printed asks: new original or copy (marked "Kopie"). Only one original may be in circulation; the old one must be retrieved and destroyed.
    • For a sale flagged "missing prescription", printing the prescription asks whether the original is now present: Yes prints; No keeps the status "missing". A missing prescription whose print is deferred cannot be printed from sales administration; the deferral must be resolved in Rx check.
    • Print prescription later: only if not deferred. Select the subtotal → Prescription → print preview (shows whether it was handed in later or has a deferral number) → print. With ApoTI, after a change in sales administration the prescription must be printed when the preview appears, or it is not put on the send list (workaround: print on blank paper).
    • Pickup slip vs credit slip: sales with pickups may not be closed with payment type credit, so a transaction has either a pickup slip or a credit slip, never both.
    • Missing-prescription reminder slip: for the selected total or only a selected subtotal; only one copy, regardless of the config parameter "Erinnerungsbon Fehlendes Rez." (reminder slip missing prescription); content: pharmacy address, customer name, and per subtotal the articles lacking a prescription with quantity, name, dosage form, amount, unit, supplier and standard pack size.

4.E.5 Reactivate a POS transaction for editing (Kassenvorgang aktivieren) [GENERIC]​

Correct a completed sale by reopening it; the original is cancelled internally and a linked follow-up document is created.

  • Brings a completed sale back to the POS. An open credit sale is resolved automatically. Invoicing sales and POS transactions closed as "invoice" can also be edited. A single subtotal can be reactivated.
  • Blocked when: the prescription was already collected by the clearing centre (neither reactivation nor cancellation; use "check again" in the prescription archive first); the sale is a courier delivery already marked "handed to courier" in delivery management; the transaction was already edited (a newer follow-up document exists).
  • Fiscal logging: under the cash-register security regulation every POS transaction is logged, including aborts after reactivation.
  • With ApoTI: after the change, the prescription must be reprinted when the print preview appears, to be put on the send list.
  • Reason window: predefined reasons (e.g. article exchange) plus free text; the config parameter "input dialog cancellation reason" controls whether it opens automatically.
  • At the POS: a cancelled subtotal (original articles) and an active subtotal (same positions) appear; edit the active one. Plus a credit-slip resolution subtotal if there was an open credit. All subtotals of the transaction come to the POS. If the original dispensing date lies before the current price update, or the payer was changed in a way that bypasses a discount contract, messages and changed icons appear. At Total, the original payment type is preset and can be changed (e.g. transfer to invoicing). A new "discount after total" is possible for non-prescription items.
  • Result: a follow-up document is created automatically. Price differences from sale-price changes or a discount-model assignment are shown as separate positions on the new receipt. When editing a sale with an unresolved pickup, the pickup number is kept for the whole chain and the new pickup slip shows it.
  • Historic data: the original dispensing date is kept (not set to today), and existing positions are not re-checked automatically. A new article entered with a past dispensing date is checked against historic discount contracts and prices (Rx.secure); the data-state date is shown (red = the data state actually used, set automatically to the nearest date with data). If no historic data exist, an icon shows and discount contracts cannot be checked. Setting the dispensing date to another date (e.g. today) re-checks and updates. Articles removed from the price list have no historic data.
  • Transfer of a completed POS sale to invoicing: a sale on prescription with Rx status 0, or one closed on credit and not yet paid, can be reactivated and then transferred (invoice or immediate invoice). The POS transaction is cancelled and an order is created in invoicing with the existing prices (existing purchase contract); printed prescriptions are carried over. Preconditions: no test prescription; no voucher or bonus redeemed; no mix of sale and buy-back subtotals; no credit or invoice redemption in the chain coming from a foreign receivable settlement; no payment received (cash, card, cheque, bonus, voucher, credit slip, etc.); credit slips without payment; the whole transaction reactivated, not a single subtotal. The chain then shows: sale on reservation; activation; internal cancellation; orders from the subtotals.
  • Invoicing orders can also be found in sales administration (transaction type "order"), viewed (print preview, subtotals, articles), edited, cancelled and printed (order overview, order details, article labels, delivery notes, prescriptions). On reactivation a follow-up order is created automatically. Delivery notes are printed only for newly captured articles, unless batch documentation is active.

4.E.6 Take over pack info [DE-SPECIFIC] (serialised-pack traceability [GENERIC])​

  • When a verification-required article is moved to another subtotal during editing (Rx status change), the pack info in the original subtotal is deleted. At Total, the pack-info capture window opens: scan the securPharm code or type it if the pack is at hand. Otherwise "take over pack info" shows the data from the previous transaction (serial number, batch, expiry); this is offered only for new positions that were deleted in the previous transaction. Confirm to adopt.

4.E.7 Cancel a POS transaction (Storno) [GENERIC]​

  • Full or partial: Storno on the selected sale, or reduce a quantity while editing. Always documented by a stored receipt.
  • Blocked when: the transaction was already edited (newer follow-up exists); an invoice was already created (and not discarded); the prescription was collected by the clearing centre.
  • Side effects: config "automatic print of cancellation receipt" prints it automatically when cash is refunded. Open credit is resolved automatically. Cancelling a back-ordered article reduces or deletes the not-yet-ordered shopping-basket (order proposal) line. Cancelling the dispensing of a verification-required pack automatically asks the securPharm server to reactivate it (INACTIVE → ACTIVE) if still within the 10-day undo window.
  • Steps: select → Storno → reason (e.g. article return) + text → the POS opens with all subtotals for cancellation → Total shows the amount to return, original payment type preset → confirm (turnover and stock are booked, cancellation receipt created) → the Return field shows the payout → confirm the payout. Can still be aborted with Delete before confirming. The cancellation receipt can be printed by hand later.
  • Direct-debit payments: on cancelling or changing the customer of a subtotal paid by direct debit, the system asks whether to undo the debit.
    • Yes, without the payment-transactions module: a SEPA reminder slip is printed to arrange the refund. With the module: a debit not yet exported is removed; an exported one is flagged with a red warning, excluded from re-export, and a reminder slip is printed. For a cancellation the amount due becomes 0.00, and a refund is made by bank transfer if already collected. For a reactivation with customer change, the full amount is due again from the new customer, by any payment type.
    • No: the debit is kept. After a customer change the new customer pays nothing; after a cancellation a cash payout is offered regardless of export.

4.E.8 Cancel or reactivate an already changed or partly cancelled transaction [GENERIC]​

  • A message window ("activation total" / "cancellation total") appears when the transaction is not the last in its chain, or when a discount after total was given and part was already changed or cancelled. It lists subtotals with subtotal number, receipt number, status (current / already activated / already cancelled) and new receipt number. The user decides about the remaining subtotals. The discount after total is not taken into account for a partial action.

4.E.9 Change payment type (Zahlart ändern) [GENERIC]​

  • For a sale or an invoice settlement closed with the wrong payment type. The total can be split across several payment types.
  • Not possible if part of the total was already edited or cancelled, or for a credit sale closed by a payment.
  • Card: the change is recorded in the system but not at the terminal; do it at the terminal too.
  • No new price determination.
  • Window: total; previous payment types with partial amounts; new payment types; open remainder; "given" field preset with the total (if config "input of given amount" is on, the remainder is always preset to 0). Options: cash; direct debit (needs a customer; only without the payment-transactions licence); cheque; card (choose card type); online; invoice; credit (needs a customer).
  • Result: an internal rebooking receipt (Umbuchungs-Bon) documents the change and the payment types.

4.E.10 Card payment change or cancel [GENERIC]​

  • Cancel fully or partly via Storno; edit (e.g. change a quantity) via reactivation; change the payment type if the card payment failed. These changes are not passed to the card terminal automatically: a notice says the cancellation or change must also be done at the terminal. Unlock the terminal in the electronic-cash administration module and carry it out there. Cancelling in IXOS works even without a connected terminal.

4.E.11 Credit sale reactivate or cancel [GENERIC]​

  • Open credit sales (payment type credit) show their credit slip number. Reactivating or cancelling resolves the credit automatically.
  • Edit: the POS shows a cancelled subtotal (original articles), an active subtotal (same positions, editable) and a credit-slip resolution subtotal; all subtotals come to the POS; Total to complete. The resolved sale shows sale type/status "Kreditaufl. <credit slip no.>".
  • Cancel: the POS opens with the cancelled subtotal and the credit-resolution subtotal; Total; confirm.

4.E.12 Customer assignment (view, edit, assign) [GENERIC]​

  • Available in sales administration (for each subtotal of the selected total, or only the selected subtotal) and in prescription management (for the selected prescription subtotal). If a customer is assigned: edit the assignment or show customer details.
  • Use cases: no customer or the wrong customer at sale; buy-back/return without a customer; later assignment e.g. when resolving a pickup.
  • Not possible for credit sales.
  • When assigning, the system checks for each customer and article whether documentation would need to be created or removed and whether the payer (and so the discount-contract situation) changes, and shows this in the window.
  • Not re-run by reassignment: customer-related documentation (narcotics, blood products, medication management, batch documentation) and discount contracts. Deviations are flagged, and the user can choose "edit manually": the sale goes to the POS, where the customer must be assigned again so all checks run (and a special code may be needed). If an aid article's price came from the aid-contract database, always reactivate to get the correct billing prices. Price determination and the automatic article check are also not re-run.
  • Window: subtotals table (type, Rx number, customer with picker); a free-text customer line for the receipt (printed instead of all customer addresses; not stored on the customer); copy customer to all subtotals (including those already assigned); remove customer; print receipt with the new assignment.
  • Consequences: the till receipt changes, so make sure only receipts with the new assignment are in circulation and destroy older ones. All later actions (receipt print, prescription print, prescription management, open items, pickup, courier) show the new customer; the sales are listed under the new customer and included in their co-payment list.

4.E.13 Invoice settlement edit or cancel [GENERIC]​

  • Invoice settlements made at the POS (e.g. booked to the wrong customer) can be edited, cancelled or have their payment type changed, even when the transaction contains other subtotals. Also possible at the POS straight after completion (after confirming the amount given). Credit-note payouts work the same way.
  • Edit: select the settlement subtotal and reactivate it at the POS (e.g. to record a partial payment). Cancel: the whole total or only the settlement subtotal. Cancelled subtotals and the cancellation receipt preview are shown. The customer's invoice becomes open again (open items).
  • Summary receipts show cancelled sums under turnover cancellation and cash cancellation. In the accounting (DATEV) export, the cancellation of an invoice settlement appears as an invoicing transaction.

4.E.14 Closing receipt analysis (Abschlussbonanalyse) [GENERIC]​

Drill-down from every summary figure to the individual sales behind it.

  • For each figure on a summary receipt, shows which sales went into it and with what amount. Permission: Leiter or Umsatzverantwortlicher (needed to open details of closing receipts).
  • Window: filter by type (any figure of the summary receipt); list of item, closing date/time, receipt number and amount; filtered sum at the bottom, which matches the summary receipt to the cent.
  • Steps: sales administration → transaction type e.g. Z receipt → select → Details. Jump to sales administration for selected items (multi-select); search is not available in that view.
  • Only for summary receipts computed directly from sales; receipts made with the "Z-receipt boundary" option have no details.
  • Filter "articles from purchase price" (high-priced) only appears when the config parameter "count and turnover of articles from purchase price" has a value.
  • Print, filtered or unfiltered (the filter is stated on the printout).
  • Older receipts: the breakdown is recorded only since version 2012.4.120. Workaround: create a T receipt over the same period without the Z-receipt boundary.
  • Z-receipt view of a sale: shows with which values a selected sale enters the Z receipt. Requires the sale to be Z-relevant and already included in a Z receipt.
  • Recommended: draw an X receipt before the Z receipt to verify.

5. Workflows​

5.1 Daily prescription check (paper and e-prescriptions)​

  1. At sale completion, the prescription is printed (or its print deferred). A connector signature is applied to e-prescriptions automatically. With ApoTI, the prescription is queued and sent to the clearing centre within the transmission interval (default 10 minutes), unless it is an unprinted prescription without a deferral.
  2. The prescription appears in Not ready (waiting for feedback, print, original or deferral). E-prescriptions without a red status wait there 3 days; red ones go to Rx check at once.
  3. At least once a day, staff open prescription management and put the day's paper prescriptions face up, landscape, into the back-office scanner.
  4. Each image is matched to its sale. Unmatched images show as red rows in Rx check and are assigned by hand or discarded (5.4).
  5. The automatic check runs (4.A.7) and combines with the ApoTI feedback into a check status. Error-free prescriptions not selected for manual check go straight to the box. The rest go to Rx check, sorted by severity.
  6. For each prescription in Rx check: scan it again (or select it) to open the detail view; first rule out recognition errors (pick the right prescribed article); then either accept it (→ box), ignore hints with a reason (→ box if all ignored), mark it "check later", send a doctor query, or edit it (5.2).
  7. E-prescriptions needing a QES are filtered with "for signature with HBA" and signed in a batch by a pharmacist (card + PIN). From 3 working days before month end, a notes task reminds of open signatures.
  8. The paper goes into the physical box bundled by day.
  9. Later ApoTI status queries can push an accepted prescription back to Rx check if its status gets worse.
  10. Three days before month end, everything left in Not ready moves into Rx check.
  11. The clearing centre collects the box. After the last pickup of the previous month (configured day, default the 3rd; for DRZ the second DRZ pickup), the previous month's prescriptions move from box to archive. E-prescriptions move when reported billed (brackets when all parts are billed).

5.2 Correcting a prescription after the sale​

  1. From the prescription detail (or from sales administration), choose Edit. Enter a reason (if the reason dialog is configured).
  2. The sale is reactivated at the POS: original subtotal cancelled, copy active. Any deferral number is released. If another prescription subtotal in the sale has a back-order or credit payment, the whole transaction must be edited.
  3. Make the change (e.g. exchange the article, fix the payer or dispensing date). New articles with a past dispensing date are checked against historic data.
  4. Total and complete the sale. A follow-up document is created; price differences appear as separate positions.
  5. In the print preview, print the prescription (with ApoTI, it is only put on the send list once printed), or defer it, or abort. Put a correction label on the pricing field, initial across it, and reprint the form.
  6. The prescription returns to Not ready, its ApoTI status is cleared, and it is cancelled and re-sent to the centre. Its old image is marked outdated.
  7. Rescan it in the back office; it is re-checked and sorted into Rx check or box.
  8. If the prescription was already billed: first use "check again" in the archive (only if the centre returned it), then edit. Reprints use the data valid at the real dispensing date.

5.3 Deferred prescriptions​

  1. At the sale, the print is deferred and the prescription is put in a numbered sleeve; the deferral number is stored with the subtotal.
  2. In the back office, scan up to about 10 sleeves at a time (or type the deferral number). The first prescription opens in detail.
  3. Check it; edit the sale if needed; accept.
  4. Apply a correction label if needed; print the prescription; go to the next. Accepted prescriptions go to the box.
  5. A missing prescription with a deferred print can only be resolved here, not from sales administration.

5.4 Assigning an unmatched image​

  1. In Rx check, select a red row (unmatched image) and open the assignment window.
  2. Search by the last 3–4 digits of the Rx or deferral number, or the customer surname; or leave empty (last 200 prescription sales without an image) or use "*" (last 60 days).
  3. Compare the image with the sale's articles and icons; take over the assignment. The prescription appears in Rx check.
  4. If the hint says the Rx number is outdated or it is a test prescription, prefer to discard and reprint with correct data; forcing is possible.
  5. If no sale fits, discard the image, or leave it for later (unusable images are deleted after 1 week; usable ones stay 60 days).

5.5 Handling a payer clawback (retax)​

  1. Scan the payer's letter into retax management and note the affected Rx numbers and status.
  2. Find the prescription in the archive by Rx number or e-prescription ID. Review its detail as of the dispensing date (Rx.secure) and its history.
  3. If non-availability is the defence: select the retaxed line, choose "prove non-availability", pick the reference time, and print the proof.
  4. Copy the Rx info (Rx number, PZN, dispensing date, e-prescription data records) for the pharmacists' association; send it only encrypted.
  5. If the centre returned the prescription for correction, use "check again", edit, and reprint with historic data.

5.6 DRZ monthly reconciliation​

  1. Open the DRZ Overview: compare turnover, prescription counts and deviations for the current and last two months; download invoice and statistics PDFs.
  2. In the Deviations tab, pick a month and go through yellow and red rows: compare IXOS vs DRZ data, images and articles; open the sale if needed.
  3. Correct the IXOS sale where IXOS is wrong, or accept the deviation (optionally with a reason); accepted deviations stop counting and the month sums align.
  4. Optionally request an advance payout (DRZ Cash, up to 80% of last month's prescription turnover).

5.7 Prescription requests to doctors​

  1. Make sure medication courses have a treating doctor (or a family doctor in contact data), dosage and stock; set doctor absence, extra lead days and delivery mode in the doctor contacts.
  2. Open Prescription requests → New. Choose scope (customer, care-home unit or treating doctor), period (automatic 14 days + doctor extras, or absolute), and the With/Without/Only filters. Optionally include zero-stock long-term medication and the stock column. Save as default if wanted.
  3. The system builds one request per doctor with positions from the automation rules and course overrides.
  4. Review: add free-text extra positions and a note to the doctor; remove positions (until next request, or until a date).
  5. With filter "Current", tick open requests and Print/Send; each goes by the doctor's channel (print, fax, e-mail).
  6. When prescriptions arrive, they are booked into medication management; the booking state of each request updates. When all positions are booked, the request archives itself; otherwise archive it by hand.

5.8 Correcting a completed sale in sales administration​

  1. Find the sale (period, customer, article, number field, receipt barcode or pack scan).
  2. Check the chain icon and history; check details and receipt preview.
  3. Choose the action:
    • Wrong payment type → Change payment type (rebooking receipt; card change must also be made at the terminal).
    • Wrong or missing customer → Customer assignment (reprint the receipt; edit manually if documentation or discount contracts are affected).
    • Wrong items or quantities → Reactivate (reason; edit the active subtotal; Total; follow-up document).
    • Return or void → Storno (reason; payout; cancellation receipt; securPharm pack reactivation if within 10 days; direct-debit decision).
    • Should have been an invoice → Reactivate the whole transaction and transfer to invoicing (if the preconditions hold).
  4. Reprint any affected documents; reprinted receipts are marked as copies unless a new original is chosen, and only one original may circulate.

5.9 Explaining a summary receipt​

  1. In sales administration set the transaction type to the summary receipt (e.g. Z receipt) and select it.
  2. Open Details: filter by the figure to explain; the filtered sum equals the figure on the receipt.
  3. Jump to the underlying sales if needed; print the analysis.

6. Business rules and calculations​

6.1 Prescription status and movement​

  • Status of a prescription = highest-priority active hint. Priority: not billable (black) > error/faulty (red) > improvable (yellow) > hint > info (no status). All hints ignored → green "with hint".
  • Remapped clearing-centre messages take their adapted severity.
  • No overall status is shown before the back-office scan, even if ApoTI feedback exists.
  • Tab movement: Not ready → Rx check (on scan, on ApoTI feedback, after 3 days for non-red e-prescriptions, at once for red e-prescriptions, 3 days before month end for everything, or by "accept check") → box (error-free not selected for manual check, or accepted, or all hints ignored; QES prescriptions only after signing) → archive (previous month after the last pickup; e-prescriptions when billed; brackets when all billed; by hand with "Billed").
  • Backward movement: worse ApoTI status after acceptance → back to Rx check; reactivating an ignored hint → back to Rx check; deleting the image → back to Rx check with statuses cleared; editing → Not ready; "check again" → Rx check with green arrow (must be moved to box by hand again).
  • Final e-prescription data records go to the centre only when every prescription with verification-required medicines in that e-prescription has been fully supplied.
  • Box forecast counts e-prescriptions lacking a QES, assuming they will be signed by month end.
  • "Check later" never stops transmission to the centre.

6.2 Check logic details​

  • Discount contract, import rule and price economy under aut idem are judged on the priced article; split dispensings are always yellow.
  • A dispensed article not among the five hits of the discount search is red.
  • An import with a higher statutory price than the original → yellow with retax-risk icon.
  • Handwritten prescriptions: POS-entered article always yellow but does not make the status improvable.
  • Payer on the prescription differs from the POS/customer payer → red (e.g. long-term-care fund IK starting with 18); recognised vs stored payer deviation → improvable by default.
  • Cheaper import possible → improvable if the setting is on, else information only.
  • The exchange-article list is computed at check time and can differ from sale time.
  • Compounded, parenteral, PZN-less generic, rental and unit-dose/blister prescriptions get no automatic check; prescriptions with compounding, parenterals or special codes are always offered for manual check.
  • Dispensing date changed outside the current price-update period without editing → red date and manual check required.
  • Changing dispensing date or form of a printed prescription and aborting the reprint: still counts as printed, keeps its Rx number, not re-sent.

6.3 Thresholds, limits and retention​

ItemValue
ApoTI default transmission interval / view refresh10 minutes
E-prescription (non-red) wait in Not ready3 days
Not ready sweep before month end3 days before month end
HBA signature reminderfrom 3 working days before month end to the last working day
HBA certificate expiry noticeless than 3 months to expiry
Historic price/contract data (Rx.secure) and returned-Rx correction window24 months
Availability query history36 months
Unassigned unusable images kept1 week
Usable images available for assignment60 days
Image assignment default listlast 200 prescription sales without image; "*" = last 60 days
Prescription search result cap200
Search key minimumlast 3–4 digits of Rx or deferral number
Recommended sleeves per scan batchmax 10
First ApoTI connection: older prescriptions to archivecaptured more than 2 weeks before connection
Price update service dates1st and 15th of each month
Manual-check value threshold preset500 EUR
Default last pickup day (non-DRZ)3rd day of following month
DRZ high-priced filterat least one article with pharmacy purchase price 1238.53 EUR
DRZ care-aid monthly cap (excluded from deviations)42 EUR
DRZ Cash payout cap80% of last month's prescription turnover
Prescription request default period14 days from today (+ doctor lead days and absence)
Prescription request list default date filterlast 14 days
"All" requests listopen + archived of last 12 months
securPharm undo of a dispensed pack on cancellationwithin 10 days
Closing receipt breakdown availablesince version 2012.4.120

6.4 Parenteral data record rules​

  • Factor = per mille of a pack used (whole pack 1000; 7 of 28 = 250).
  • Hash code = 40-digit decimal from manufacturer IK, transaction number, timestamp and PZN lines; transaction number unique per pharmacy per year.
  • Price identifiers: standard 14 / labour 74; hospital supply (from 2015-10-01) 16 / labour 76, surcharge > 0 with special code 06460518, one surcharge per manufacturing segment; individual contracts 15 / labour 75.

6.5 Prescription request computation​

  • Need for the period = requirement computed from dosage over the period, against current stock.
  • Range is not computed for substance prescriptions, as-needed or free-text dosing, or negative stock in blister courses.
  • Blister courses are included when they would reach negative stock within the period, with the exclusions in 4.D.2; non-blister courses follow the With/Without/Only filters and the zero-stock checkbox.
  • "Without doctor assignment" → request addressed to the family doctor.
  • Automatic period = 14 days + doctor's extra lead days + doctor's absence days; absolute period ignores both.
  • Request auto-archives when every position has been booked into medication management.

6.6 Sales administration rules​

  • A sale cannot be reactivated or cancelled if: its prescription was collected by the clearing centre; a newer follow-up document exists; an invoice exists (cancel); a courier delivery is marked handed to courier (edit).
  • Reactivation keeps the original dispensing date and does not re-check existing positions; new positions are checked against historic data at that date.
  • A sale with pickups cannot be closed on credit (pickup slip and credit slip are mutually exclusive).
  • Only one original receipt may circulate; reprints are copies unless a new original is issued (old one destroyed).
  • Payment-type change: no new price determination; not for partly edited/cancelled totals or credit sales closed by payment; card changes must also be done at the terminal.
  • Customer reassignment does not re-run price determination, article checks, documentation or discount contracts.
  • Editing a sale with an open pickup keeps the pickup number for the whole chain.
  • Partial cancel/activate ignores a discount after total.
  • A document number (or Rx number, credit number) in the advanced search overrides all other criteria.
  • Closing receipt analysis sum equals the summary-receipt figure to the cent.

7. Configuration and settings​

ParameterScopeEffectDefault
Manual check selection: all prescriptions / all from X EUR incl. conspicuous / all without reimbursement entitlement from "RX real-time check" from X EUR incl. conspicuous / only conspicuous (faulty + improvable)Prescription management settingsWhich error-free prescriptions are still offered for manual check in Rx check. With the real-time-check option, e-prescriptions with a confirmed reimbursement claim go straight to the box.Source is inconsistent: one place says all prescriptions by default, another calls the 500 EUR option the default; X preset 500 EUR
"And additionally" checkboxes: narcotics prescriptions; special code 2567024; emergency-service prescriptions; medical-aid prescriptions; handwritten prescriptions; self-entered (handwritten) prices; e-prescriptions with free-text prescriptions (no PZN); e-prescriptions with special code 2, 3 or 4 that need no QES; e-prescriptions with an info note; e-prescriptions from discharge management (after hospital stay)Prescription management settingsAdds these groups to manual checkNarcotics initially ticked; others not stated
Always manual (informational, not switchable)—Compounded preparations; prescriptions billed via ApoTI; prescriptions with special codes without PZNAlways on
Last pickup on N-th day of following monthPrescription management settingsDay on which previous month's prescriptions move from box to archive; weekends/holidays handled automatically; not used by DRZ customers3rd day
Show possible dispensing of cheaper imports (import quota) as improvablePrescription management settingsIf off, shown as information only; with "only conspicuous", such prescriptions go straight to the boxNot stated
Show deviations between recognised payer and payer stored at customer as improvablePrescription management settingsPayer mismatch makes status improvableOn
ApoTI control (adapted feedback list)Prescription management settingsLists message types with original and adapted status; delete to revertEmpty
Only e-prescriptions togglePer operator, persistedLimits all tabs to e-prescriptions; not reset by the reset iconOff
Search including old prescriptions from data migrationSearch filterIncludes migrated prescriptionsOff
Clearing-centre connection (ApoTI on/off, DRZ credentials)Company master data, clearing-centre pageEnables ApoTI / DRZ functionsNot configured
Transmission intervalPOS system settings, system parameter, group prescription checkTurns on automatic ApoTI sending10 minutes (the "no transmission" value has no effect in pharmacies)
Send only GKV parenteral prescriptionsSameRestricts sendingNot stated
Send private parenteral prescriptionsSameIncludes private parenteralsNot stated
Pharmacy name on prescriptionCompany master dataShort name printed on prescriptions to improve recognition—
Ask documentation-relevant data at narcotics saleConfig parameterEnables the narcotics-number checkNot stated
Input dialog cancellation reason (Eingabedialog Stornogrund)POS system settings, general salesWhether the reason dialog opens on every reactivation/cancellationNot stated
Default transaction type (Vorbelegung Vorgang)Config parameterDefault transaction filter in sales administrationTill receipt
Show system cancellations (Systemstornierung anzeigen)Config parameterShows system counter-postings in grey italicNot stated
Automatic print of cancellation receipt (Automatischer Druck Stornobon)Config parameterPrints the cancellation receipt when cash is refundedNot stated
Reminder slip missing prescription (Erinnerungsbon Fehlendes Rez.)Config parameterNumber of reminder slips at the POS; ignored for reprints from sales administration (always one)Not stated
Input of given amount (Eingabe des Gegeben-Betrags)Config parameterIf on, the remainder in the payment-type window is preset to 0Not stated
Count and turnover of articles from purchase price (Anzahl und Umsatz Artikel ab EK)Config parameterEnables the high-priced filter in closing receipt analysisEmpty
Z-receipt boundary (Z-Bon-Grenze)Option when creating a summary receiptReceipt has no breakdown—
Receipt barcodePrint formsEnables finding sales by scanning the receiptNot stated
Prescription request filters ("save as default")Prescription request dialogStores scope filtersBlister With, as-needed dosing With, long-term With, advance deliveries Without
Ignore courses discontinued in the pastSystem settings, blisteringExcludes negative-stock blister courses whose discontinuation began in the pastNot stated
Doctor contact: absence days, additional lead days, delivery modeDoctor contactExtends request period; chooses print/fax/e-mail—
E-mail sendingSystem settings, e-mailNeeded for e-mailed requests—
Fax service providerCompany master data, external servicesNeeded for faxed requests (two providers supported)—
Course override: do not request until / request onceMedication or blister course detailsOverrides request automation—

8. Roles and permissions​

  • Start prescription management: permission "Rezeptmanagement starten" or role Leiter. Under the sensitive-data protection concept it can be bound to a workstation or a user.
  • Rx box forecast and closing receipt analysis details: roles Leiter (manager) and Umsatzverantwortlicher (turnover responsible).
  • DRZ rights (group prescription management): show month tabs (3 tabs); enable PDF download (invoice and statistics buttons in overview and month tabs); show Deviations tab; show Overview tab. By default only role Leiter has them. DRZ access is protected when the sensitive-data concept is on.
  • DRZ Cash: permission "Rezeptmanagement-DRZ-Cash" when the permission concept is in use.
  • QES signing: only a pharmacist with an HBA can sign; "only own" filter shows e-prescriptions assigned to the signed-in user for signing.
  • Billing receipt for privately insured: reprint is permission-bound (permission name not given).
  • Audit: accept/check/change actions on prescriptions store date, time, operator and workstation; history logs every status change and manual hint change; every POS transaction including aborted reactivations is logged under the cash-register security regulation; operator shown on each transaction.

9. Integrations, hardware and external services​

  • Clearing centre via ApoTI [DE-SPECIFIC]: online send of prescription data for pre-check, status queries, cancellation and re-send; returns feedback messages with severities, billability, expected billing month and correction deadline. Not during nightly maintenance; continues during emergency service.
  • DRZ portal (ApoOnline) [DE-SPECIFIC]: import of billing figures, per-prescription billed data and images, invoice and statistics PDFs, peer-group benchmarks, per-payer KPIs, pickup dates; outbound advance-payout requests (DRZ Cash).
  • National e-prescription service [DE-SPECIFIC]: dispensing receipts (fetched automatically within a day or on demand), e-prescription data records, connector signature at sale completion.
  • Health-professional card (eHBA) with card reader and PIN [DE-SPECIFIC]: QES on corrected e-prescriptions.
  • securPharm server [DE-SPECIFIC]: pack verification data; automatic reactivation (INACTIVE → ACTIVE) of a dispensed pack on cancellation within 10 days; serial-number search of sold packs.
  • Back-office prescription scanner: landscape scanning of paper prescriptions, front and back (back detected automatically), deferral-sleeve barcodes and A4 retax letters. Hand scanners or POS scanners can read sleeves too. OCR/recognition of patient data, prescription lines, stamp and signature.
  • Barcode scanning in sales administration: receipt barcodes, pack barcodes and securPharm DataMatrix codes.
  • Card terminal: payment changes and cancellations are not sent to the terminal; they must be repeated there via the electronic-cash administration module.
  • Pickup terminals (incl. "BD Rowa Pickup" with pickup cloud) and picking robots: event log; cancel or retrieve pickup orders.
  • Fax service providers (two supported) and system e-mail: delivery of prescription requests and doctor queries (doctor queries attach the prescription image; encryption recommended).
  • Customer app: receipts sent digitally; prescription subscription service with its own request print form.
  • Order channels visible as sales channels: customer app, clinic portal, care-home orders, doctor portal, webshop, wholesaler order interface, other ordering portal, national e-prescription app.
  • Accounting export (DATEV) [DE-SPECIFIC]: cancelled invoice settlements are exported as invoicing transactions. General idea: post-sale corrections must flow into the accounting export with the right document type.
  • Price update service (1st and 15th of each month) and drug database: historic data for Rx.secure; article info and patient usage notes.
  • Data migration: prescriptions from a previous system are searchable but not shown until edited.

10. Printouts, reports and exports​

  • Prescription management: prescription form (with fixed print rules, 4.A.6) and attachments for medical-aid billing (DRZ only); print overview of the current tab (export to Excel from print preview); proof of non-availability; retax letter print; DRZ invoice and statistics PDFs; DRZ overview chart; details windows "billed in MM/YYYY" and "potentially billable in MM/YYYY"; parenteral hash code printed on the form; copy of Rx info / e-prescription data records to the clipboard; doctor query e-mail with image.
  • Prescription requests: request printout/fax/e-mail per doctor (need period end, customer, home and living unit, birth date, article, dosage form, stock at request, dosage, computed need; optional current stock column; additional free-text positions and the note to the doctor or the system default text). Two templates: standard and prescription-subscription.
  • Sales administration: full reprint list in 4.E.4 (till receipt, partial receipt, receivable-settlement receipts, additional receipt, voucher receipt, card merchant and terminal closing slips, article and care-home labels, address labels, check-out coupons, cancellation receipt, pickup slips incl. cross-branch, packing lists, courier slip/label, credit slip, prescription, care-aid receipt declaration, missing-prescription reminder slip, SEPA reminder slip, usage instructions, proof of GKV prescription, billing receipt for privately insured, export and purchaser certificate); rebooking receipt on payment-type change; closing receipt analysis printout (states the filter).
  • Reprint rule: original vs copy ("Kopie"); only one original may circulate.

11. Dependencies on other modules​

  • POS (Kasse) and invoicing POS: all edits and cancellations run there; prescription print window, deferral, payment, discounts after total.
  • E-prescription dialog / order list: e-prescription info notes and availability queries.
  • Invoicing (Faktura): orders visible and editable in sales administration; transfer of POS sales to invoicing; a fully invoiced order blocks prescription editing until the invoice is discarded.
  • Medication management and blister management: medication courses, dosage, stock, treating doctor, pause/discontinuation, booking of received prescriptions; course-level request overrides.
  • Contacts: doctor contacts (absence, lead days, delivery mode), care-home structures, customer data (payer/IK, family doctor, consent declaration).
  • Company master data: clearing-centre connection, pharmacy name on prescription, fax providers.
  • System settings / config parameters: e-mail, POS parameters, blistering parameter.
  • Print forms: request templates, receipt barcode, additional receipt.
  • Notes / tasks and calendar: month-end signature reminder, DRZ pickup tasks, DRZ Cash request list.
  • Parenteral (compounding) module: parenteral details.
  • Delivery management: courier status blocks editing; delivery type change.
  • Electronic-cash administration: unlocking the terminal for card changes.
  • Payment transactions module (direct debits): handling of exported/unexported debits on cancellation.
  • Open items / receivables: invoices reopened when a settlement is cancelled; credit resolution.
  • Pricing module, aid-contract database (A+V): price details shown in position details; reactivation needed for correct aid prices after reassignment.
  • Drug database: article info, discount agreements, comparison article search, usage notes.
  • Risk check (customer-related medication check) and e-medication list.
  • POS closing / summary receipts (Z, X, T, etc.).

12. Portability notes​

  • Generic and worth copying for Shefa:
    • A staged prescription audit queue (not ready → check → ready to submit → billed) with severity-ranked hints, a single derived status, manual override with reason and audit trail, and automatic regression if new information makes a case worse.
    • Post-sale scanning of paper prescriptions, matched to the sale, with an unmatched-image queue and retention limits.
    • Prescribed-vs-dispensed comparison with colour-coded confidence and immediate re-check after a correction.
    • Correction by reactivating the sale: original cancelled internally, follow-up document created, chains kept, mandatory reason, original dispensing date kept, historic prices used.
    • Historic price/rule data kept for at least 24 months, so past decisions can be re-checked and defended.
    • Availability query history (36 months) to prove that a substitute was necessary.
    • Deferred documentation with numbered sleeves.
    • Pharmacy-initiated repeat-prescription requests computed from dosage, stock, reach and doctor lead times, with per-course overrides and automatic close-out on receipt. Very relevant where pharmacies manage chronic patients or care homes.
    • Sales journal with document-number search, pack/serial search, receipt-barcode lookup, transaction chains, full stored print data and reprints with original/copy control.
    • Payment-type change via a rebooking receipt; customer reassignment with explicit "what is not re-checked" warnings; partial cancellation of chains.
    • Closing receipt drill-down that ties every summary figure back to sales to the cent.
    • Reconciliation of the pharmacy's own claims against what the payer/intermediary actually paid, with matching strategies (unique number; amount + payer + date fallback) and "accept deviation" with reason.
  • Germany-specific, with the idea underneath:
    • Statutory insurance billing via a clearing centre and retax → pre-submission validation of reimbursement claims against payer rules.
    • ApoTI pre-check → online pre-validation by the billing intermediary, with configurable severity mapping of its messages.
    • DRZ dashboard and DRZ Cash → intermediary billing statements, benchmarks and cash-advance requests integrated into the pharmacy system.
    • Discount contracts, aut idem, import quota, price anchors, dispensing ranking → payer-specific substitution and pricing rules checked at dispensing and again before billing.
    • QES with eHBA → personal, qualified signature by a licensed pharmacist on corrected electronic prescriptions.
    • E-prescription receipts and data records → the national e-prescription service's proof of dispensing.
    • securPharm → serialised pack verification and reversible decommissioning.
    • Parenteral hash codes and price identifiers → tamper-evident link between a paper form and its electronic compounding record, with payer-specific price categories.
    • Cash-register security regulation logging → tamper-evident fiscal log of every POS action including aborted edits.
    • Export and purchaser certificate → VAT refund documents for exported goods.
    • DATEV export → accounting export that reflects post-sale corrections.
    • Consent-based power of attorney for prescription requests → patient consent authorising the pharmacy to contact prescribers.

13. Open questions​

  • The default manual-check selection is described inconsistently ("all prescriptions" vs "all from 500 EUR").
  • Defaults of several config parameters (cancellation-reason dialog, show system cancellations, automatic cancellation receipt, import-quota-as-improvable, send-only-GKV-parenteral) are not stated.
  • How the automatic check's recognition works (OCR engine, confidence thresholds) is not described beyond the colour bars.
  • The full list of clearing-centre message types and their default severities is not given.
  • How "need" on a prescription request is exactly computed (rounding to packs, pack size choice) is not stated.
  • The exact rule that matches a back-office image to a sale (beyond Rx/deferral number) is not described.
  • The DRZ peer-group definition and how "best value" is calculated are not explained.
  • What the "RX real-time check" is and how it confirms reimbursement is described elsewhere, not here.
  • The permission name for reprinting the billing receipt for privately insured is not given.
  • Exact meaning of S, J, M and T summary receipts is outside this slice.
  • Whether payment-type changes and cancellations update the card terminal settlement totals is not stated (only that the terminal must be handled separately).
  • How long sales-administration data and print data are kept is not stated.

14. Source pages​