Frequently asked questions
Clear answers about Medeq and its limits
See what Medeq supports, what can be configured, and what needs to be scoped for your medical-equipment service operation.
Product and solution fit
Which Medeq solution is right for us?
Start with the problem you need to address:
The solution areas connect to one platform rather than operating as separate products. Use a consultation to confirm where to begin.
- choose Field Service Management for the path from ticket to signed device record;
- choose Equipment and Asset Management for equipment context, related service work, documents, and history;
- choose Service Management and SLAs for service-desk, catalogue, contract, priority, and target structures; or
- choose ISO 13485 compliance support for controlled service records and traceability within quality processes.
What is Medeq?
Medeq is a medical-equipment field-service and service-management platform. Its Field Service application gives technicians a workflow for assigned tickets, device job cards, configured procedures, readings, test instruments, service items, evidence, sign-off and linked service history.
Who is Medeq designed for?
Medeq is designed for medical-equipment distributors and service providers, in-house biomedical teams, service managers, quality leaders, operations leaders, technicians, and the customer facilities involved in the service record.
Platform and field workflow
How does a field-service job move through Medeq?
A technician starts from the assigned ticket and creates the job card, completes the configured checklist, fulfils test-instrument requirements, and records service items and evidence.
Medeq then prepares a branded PDF, supports the configured two-party signing flow, and links the completed document back to iTop service history.
Does Medeq replace iTop?
No. Medeq provides the field-service experience. iTop remains the underlying system of record for tickets, contacts, organisations, devices, documents, identities and service history.
Can procedures be matched to equipment and service type?
Yes, where the team has configured the relevant content. Medeq supports versioned checklist templates and assignment by brand, model, service, and service subcategory. Matching quality depends on maintained equipment data, active versions, assignment coverage, and an active fallback where one is configured.
Can Medeq record measurements and service evidence?
Yes. Medeq supports structured checklist items, supported measurement quantities and units, optional reference bounds, service items, photos, and supporting files. Procedure suitability and acceptance criteria remain the organisation’s responsibility.
Can Medeq show which test instrument was used?
Yes. Medeq can record instrument serial and calibration context and retain assignment, return, and swap activity against the job. Within the Medeq checkout workflow, an instrument must be available and have a future calibration expiry before assignment.
Can the customer facility sign the service record?
Medeq supports technician and site-contact electronic sign-off and retrieval of the completed signed PDF. The production signing provider, email setup, contact data, document layout, storage, and delivery path depend on the deployment.
Quality and service records
Does Medeq make an organisation ISO 13485 compliant?
No. Medeq can support controlled service and post-market records, procedure use, structured evidence, test-instrument traceability, sign-off, and linked service history. The organisation remains responsible for its quality system, procedures, people, controls, evidence, conformity, and certification.
Are completed job cards immutable?
No blanket immutability guarantee applies. Medeq uses submission controls and a signed service document within the completion workflow. Record retention and edit controls depend on the deployed configuration and organisational procedure.
Implementation and configuration
How is Medeq implementation approached?
Implementation can be scoped around discovery, source-data preparation, configuration, validation, training, rollout, and support. The work, timing, and support period depend on the service process, equipment and customer data, procedures, roles, external services, and acceptance needs.
Can Medeq migrate our existing data?
Medeq can assess a scoped mapping, cleaning, reconciliation, and load engagement where source access, ownership, data quality, and the target environment support it. Each named integration and migration outcome requires separate scoping and testing.
Are reporting, notifications, and SLA workflows included?
Medeq can assess and configure these iTop-backed capabilities against the deployed version, enabled functions, records, measures, permissions, triggers, and delivery needs. Available reports, reminders, and customer-notification flows depend on that scope.
What determines whether Medeq fits our operation?
Fit starts with the equipment portfolio, source data, service types, procedures, test-instrument rules, and service items. It also depends on customer and site structures, roles, document needs, signing, quality responsibilities, integration dependencies, and the expected support model.
Explore implementation and support services →Contact Medeq about your service workflow →
Bring your fit and scope questions together
Bring your equipment, procedures, data, roles, service rules and quality responsibilities. We compare them against the Medeq workflow.