Start with the device
The field record should make clear which device was serviced, why the work began and who was involved.
About Medeq
Built around the device, not the paperwork.
Medeq focuses on the path from assigned service request to structured field work, signed device record, and retrievable equipment history.
Built around a specific service problem
Medical-equipment service teams need to connect the request, device, procedure, readings, test instruments, parts, field evidence, site contact, sign-off and completed record.
When those elements sit across tickets, forms, emails, and folders, the history of the device becomes harder to recover. Medeq focuses on keeping that service context connected.
Medeq focuses on keeping that service context connected.
The principles behind the product direction
Structure the work reviewers need
Procedures, readings, test instruments, service items, attachments and sign-off should remain connected to the job, not scattered as separate evidence.
Be precise about quality support
Software can support controlled service records and traceability. It cannot replace quality ownership, competent people, controlled procedures or conformity decisions.
Match configuration to the model
Equipment structures, procedures, service rules, roles, documents, notifications, migration, reporting and support must reflect the deployed environment and agreed operating model.
A field workflow, not a generic screen
The Medeq Field Service application gives technicians a device-specific workflow for:
- assigned service tickets and customer context;
- structured job cards;
- configured, versioned digital checklists;
- readings and service results;
- test-instrument requirements and calibration context;
- parts, consumables, labour, photos, and supporting files;
- branded service PDFs; and
- technician and site-contact sign-off.
Built on iTop, with the roles kept clear
iTop remains the underlying system of record for tickets, contacts, organisations, devices, documents, identities and service history. Medeq adds the field experience and the orchestration that links the completed job back to that foundation.
Broader equipment, service-desk, catalogue, contract, service-level, document, workflow, migration, integration and reporting capabilities can be assessed against the deployed iTop environment.
Delivery follows the service process
Implementation can include discovery, source-data preparation, configuration, validation, training, rollout and support. The final scope depends on the organisation’s data, equipment portfolio, procedures, users, integrations and acceptance needs.
Continue the conversation with your service workflow
Bring your medical-equipment operation. We assess how Medeq’s product direction and delivery approach fit.