- DIN 6868-150:2022-01 DR full acceptance — all 19 test points of the current standard (including the 6 missing from pre-2022 reference templates), wizard-guided workflow with veto logic against accidental close
- DIN 6868-4:2020-10 constancy testing — 7-8 default test points per AppUnit, three evaluation logics (SingleValue range, Difference |Δ|/target × 100, BinaryVisual yes/no), automatic escalation to partial acceptance on more than one fail (QS-RL §2.2)
- Multi-AppUnit + multi-detector — one X-ray system can have several detectors / generators / geometries; FieldService manages M:N assignments in the domain model and a dedicated baseline-values table per AppUnit
- Baseline-values appendix per DIN 6868-4 — setup page + per-AppUnit characteristic curve with min/target/max and 11 constancy-date columns (1 current + 10 follow-ups) — layout matches the DIN form templates
- PAdES-BES signed PDF protocols — qualified-tester signature via shared
EVIQUS.DocumentProcessinglibrary (DevExpress PDF Signer), visual signature stamp embedded in the document, optional visible signature widget with bitmap - Offline-first — encrypted SQLite (SQLCipher in release builds), master data via
?since=delta sync, signature tokens are pre-pooled from the portal for QR sign flows without internet - Portal sync via REST —
POST /api/xraymanagement/acceptance-tests(Embedded Option B with optionalreferenceSheetpart) andPOST /api/xraymanagement/constancy-tests(idempotency hit over a 48h window), audit coupling viaX-Idempotency-Key - Stale-detection for customer data —
CustomerStaleDetectorcomputes days-since-last-sync per customer and warns about outdated local data before a new acceptance protocol is started - Local-only customer promote — new customers can be created offline on-site and promoted to the portal on the next sync (
POST /api/fieldservice/customers) - Auto-update against the portal Downloads module — Windows MSI via the shared
EVIQUS.UpdateClientv2.3 (withCancellationToken-basedCanShutdownAsynchook for wizard veto during a running test); Android updates via Play Store (roadmap) - Cross-tier correlation for audit —
AcceptanceTestRunId(Guid.ToString("N")) in the PDF footer +Logger.BeginScope, so a test run can be traced end-to-end from tablet through portal audit log - Integrated feedback + 7-day log retention — bug-report button in settings spools to
%LOCALAPPDATA%\EVIQUS\FieldService\feedback-spool\with subject / description / severity dropdown; logs are retained locally for 7 days - English identifiers, German docs and PDF — measurement values and DIN references in the PDF appear standard-conformant in German, code base is consistently English
EVIQUS FieldService
EVIQUS FieldService is the mobile service app for X-ray service technicians and qualified testers — built for use directly at the equipment site, on tablet, notebook or handheld. The app guides the te…
- Type
- Software
- Deployment
- Mobile + Desktop (MAUI Hybrid)
- Platforms
- Windows 10/11, Android 10+
- Operation
- Offline-capable
Specifications
Deployment & license
- Deployment
- Mobile + Desktop (MAUI Hybrid)
- License model
- Perpetual per Service Technician + Annual Maintenance
System requirements
- Platforms
- Windows 10/11, Android 10+
- Operating system (min.)
- Windows 10 1809 (Build 17763) / Android 10
- Memory (RAM)
- 4 GB
- Disk space
- 2 GB
- Internet required
- No
Compliance
- Standards & certifications
- DIN 6868-150:2022-01-konforme Abnahmeprotokolle, DIN 6868-4:2020-10-konforme Konstanzprüfprotokolle, PAdES-BES-Signatur (DocumentProcessing-Lib)
- Medical device classification
- Standalone-Service-/Qualitätssicherungssoftware — kein MDR-Auslöser (nicht-diagnostisch, kein Patientenbezug am Endgerät)
Key features
System Requirements — EVIQUS FieldService
Device — Windows
- Windows 10 1809 (build 17763) or newer / Windows 11
- 4 GB RAM (8 GB recommended)
- 2 GB free disk space (app + encrypted SQLite + signed PDF archive)
- WebView2 runtime (Edge Chromium) — pre-installed on Windows 11, installed by the installer on demand on Windows 10
- Touch input optionally recommended (the wizard is also fully usable with mouse and keyboard)
Device — Android
- Android 10 or newer (csproj baseline is API 24 = Android 7.0; pilot recommendation is Android 10+ because of WebView stability)
- 4 GB RAM, 2 GB free internal storage
- Display 8" or larger recommended for the wizard steps
- Build is compiled but currently in the internal test channel (not listed on Play Store — Tech-Preview)
Data and storage
- SQLite (SQLCipher-encrypted in release builds) locally on the device
- App data under
%LOCALAPPDATA%\EVIQUS\FieldService\(Windows) or app-internal storage (Android):fieldservice.db,logs\,reports\,signatures\,feedback-spool\ - No mandatory cloud — data stays on the device until the signed PDF is deliberately uploaded to the portal via sync
Network
- Internet is optional — tests run fully offline. A connection is used for: – master-data delta sync (customers + X-ray systems + baseline values) – upload of signed acceptance / constancy protocols to the portal – OAuth login + token-pool refresh – auto-update (Windows) or Play-Store update (Android, roadmap)
- Wi-Fi or LTE recommended for the post-visit sync step
EVIQUS portal (mandatory)
- Account on
portal.eviqus.comwith role service technician or qualified tester - Device-linking flow on first start (OAuth2 + PKCE against
auth.dev.eviqus.com, clientfieldservice-app)
Tech-Preview notice
EVIQUS FieldService has been running in production with MSI v0.3.0.3 at pilot practices since May 2026 (Windows). The Android variant is built and internally tested but not yet listed on Play Store. iOS code exists in the repository but is not active in the build configuration and is not advertised. Auto-update on Android will follow with the Play Store channel once the tablet pilot phase begins.
Mobile service app for DIN-compliant DR full acceptance and constancy testing of X-ray systems. Offline-capable, PAdES-signed test reports, portal sync. Tech-Preview available.
Let's talk about configuration, price, and delivery.
No sales pitch. We analyse your requirements and propose the right configuration — vendor-neutral.