Nursing service management (APMS)

A complete application for outpatient nursing services on Toza. Same security, workspace, and metadata as every future app. TI / KIM when a gateway is connected.

Client management, service plans, and medication plans
Tour planning and duty roster
Electronic Leistungsnachweis and DTA billing for SGB XI and HKP: no surcharge
Compliance workflows and TI/KIM submission when connected

Try the live demo

Build the day's tours: morning through evening

Move the tour plan to the next working day

Open a client service plan in a few clicks

What's inside APMS

Every module below reuses the same security, records, and workflow engine as the rest of Toza.

Client records & care data: Every client's care data, Pflegegrad periods, diagnoses, doctors, payers, house key, and emergency details live in one record. Clients can sign in to their own portal to see their data and update contact details when you allow it.
Service plans & prescriptions: Plan which services a client receives, on which weekdays, and for how long. Prescriptions (Verordnungen) move through their approval status, and approved services flow straight into the service plan.
Tour planning & duty roster: Drag and reorder visits on the daily tour board, recalculate travel time, and publish the day. Caregivers see their own tour, office staff see everyone, and the duty roster plans shifts and absences alongside it.
Medication management: A medication catalog, per-client plans including as-needed lines, and stock that is consumed automatically each night. Import a scanned medication plan instead of typing it in by hand.
Billing & electronic submission: Cost estimates, month-end billing, and invoices, plus electronic Leistungsnachweis and DTA packages for SGB XI and HKP sent through KIM: no surcharge. Payer replies are filed automatically, and DATEV-Export for payroll closes out the month.

DATEV-Export for payroll
Care documentation: Anamnesis, SIS, care plan, and vital signs on a guided path toward MD-audit readiness. Staff validate chapters with a signature, and signed documents freeze so nobody can quietly change them afterward.
Wound care & clinical records: Numbered wound records with structured assessments, treatment plans, and photos, alongside fluid balance, insulin schema, medical findings, and shift or client reports.
Correspondence, TI & KIM: Letters, email, fax, KIM, and phone notes on the client record, with PDF preview and send. Connect the German telematics infrastructure (TI) and KIM gateway once, then reuse it for billing submission and secure messaging.

Read the full documentation

The host you can buy on its own

Toza is the workspace itself: sign-in, roles, lists, documents, mail, calendar, files, workflows, and audit. You can run that without APMS. Care adds ambulatory-care operations. ITSM adds Mira Desk: an internal service queue.

A working workspace before you install an app

Organization: Your company: the customer Toza serves.
Workspace: Your dedicated Toza environment, with its own isolated database.
Apps: Business applications installed inside the workspace: APMS for care, Mira Desk for the internal service desk, more as you grow.
Toza Platform: The infrastructure and core services that power every workspace and every app: including mail, calendar, and file connections.
Isolated instance: Your organization gets its own database and subdomain: your-org.toza-platform.com. Data does not mix with other customers.
Sign-in and access: MFA, roles, and ACL decide who can open the workspace and which records they can see or change.
Records, lists, and forms: Tables, list layouts, and forms are platform services. Apps add their tables; the way you browse and edit records is the same.
Documents: Attach and store documents on the workspace. File connections sit on the same host as mail and calendar.
Workflows and notifications: Business rules, automation, and notifications run on the platform. Installed apps reuse them instead of bringing a second engine.
Audit and sessions: System-wide audit logs and session policies apply across the workspace, not only inside one app.

Read the full documentation

Mail, calendar, and files in the same workspace

Connect the tools your organization already uses. Teams work in one environment instead of jumping between Outlook, a separate calendar, and disconnected drives.

Mail: Inbox and compose in the workspace via Microsoft 365 / Outlook (Microsoft Graph), or via SMTP and IMAP.

Integrates with Microsoft 365

Integrates with Outlook
Calendar: Workspace calendars with optional Outlook sync over Microsoft Graph: the same connection used for mail, or separate credentials if you need them.

Supports Outlook sync
Files: Browse, preview, upload, and attach documents from OneDrive or SharePoint, Google Drive, or an Amazon S3 bucket: without leaving the workspace.

Supports OneDrive

Supports SharePoint

Supports Google Drive

Supports Amazon S3

Shared core. Isolated workspaces. Installable apps.

One platform core provides security, workflows, and metadata. Those capabilities apply in every installed app. Each organization works in its own isolated environment.

Installable apps

APMS

Ambulatory care

Insight

Operational analytics

Mira Desk

Internal service desk

Future apps

Fleet, HR, and more

Toza Platform core

Tenant isolation: dedicated database per organization

Customer environment: your workspace

Select a core service to see how it applies across apps.

Install what your organization needs

The workspace is already the platform. Install the apps your organization needs: without replacing Toza.

Your workspace

Core vertical

Installed / Active

APMS

Ambulatory care operations: clients, tours, roster, electronic Leistungsnachweis and DTA billing with no surcharge.