By Thiago Bajur · CEO, Arkmeds
Cover: conceptual AI-generated illustration following the Arkmeds identity. It does not depict an actual test or measurement.
A test report needs to let another person identify the equipment assessed, understand the results and follow the review and the version delivered. In this article, we use Mark II and CMMS, solutions from Arkmeds, as examples to discuss this document organization. Records and responsibilities should be defined according to the service and the applicable references.
Imagine receiving a signed report that identifies an “infusion pump” and says “passed”. If the hospital has several similar pumps, which one was assessed? Which procedure was followed? A document can look complete while leaving essential questions unanswered. A useful record lets another person reconstruct the service without relying on the technician’s memory.
How do you connect testing to the delivered report?
Confirm the record and assessed assembly.
Link conditions, instrument and units.
Check the conclusion and responsibilities.
Confirm planned signatures and availability.
The diagram is an editorial workflow model, not a software screenshot. Before taking measurements, check the asset identifier, serial number, model and work order. A QR code can speed up access to the record, but the label must match the actual device. Check that link again when a device moves, an accessory is borrowed or a component is replaced.
During the service, preserve results and units, relevant conditions, instrument identification and the procedure reference. At completion, distinguish what was performed, what was observed and what can be concluded. “The symptom was not reproduced under the recorded conditions” differs from “the equipment has no defects”. Precise wording helps the next person decide what to do.
What belongs in a traceable technical report?
Use these blocks to review a template with technicians, approvers and customers. They are an adaptable proposal: actual fields depend on the service and applicable references.
| Record block | Information to preserve | Review question |
|---|---|---|
| Asset and service | Asset ID, serial number, model, work order and assessed accessories | Which assembly does this result belong to? |
| Scope and method | Agreed service, procedure and revision, relevant conditions | What was assessed, and what was outside the scope? |
| Instrument | Analyzer or reference identification and its applicable calibration reference | Can the instrument evidence be retrieved? |
| Results | Values, units, observations and linked files | Can another reader interpret the data? |
| Criteria and conclusion | Specification used and decision rule where applicable | Does the conclusion match the scope and results? |
| Responsibility | Execution, review, approval and corresponding dates | Who authorized each stage? |
| Version and delivery | Document ID, changes, recipient and availability confirmation | Which version is valid, and who received it? |
Document traceability and metrological traceability are different concepts. The former lets you retrieve the record’s history. The latter concerns a result’s relationship to a reference through a documented, unbroken calibration chain, with uncertainty contributions. Keeping a calibration certificate provides part of the evidence; it does not, by itself, demonstrate metrological traceability for every result produced with that instrument. Scope, use conditions and the measurement process matter too. VIM 2.41.
Why does “passed” need a defined criterion?
For a conformity statement, ILAC-G8:09/2019 connects the result, specification and decision rule, including how uncertainty is considered. It explains ISO/IEC 17025:2017 requirements for laboratories; it is not a blanket obligation for every maintenance report. Read the ILAC guidance.
Avoid a “passed” field that leaves the reference unidentified. Calibration, electrical safety testing and functional verification answer different questions. A satisfactory result in one does not automatically complete the other assessments needed for return to use. For repairs, see IEC 62353 and the release decision.
What does research reveal about disconnected records?
At two Dutch hospital sites, four weeks of collection in 2009 covered 911/1,580 procedures (57.7%). Dedicated collection found 148 incidents; routine reporting had 10, with six overlapping. These are overlapping records, not independent groups. Incomplete response limits generalization; no CMMS was evaluated. Wubben et al., 2010.
For your operation, ask: when an occurrence triggers a work order, do the two histories remain connected? Preserve a reference identifier between the occurrence and the technical investigation where the institutional process permits it. Incident notification and maintenance work orders serve different purposes; a CMMS does not automatically replace the institutional patient safety reporting system.
“Would not power on” is a reported symptom. “Discharged battery” may be a finding. Establishing the cause requires an appropriate investigation. Do not turn the initial report into a confirmed cause merely by selecting a failure category. Preserve the action taken and subsequent verification as well: these help assess recurrence without treating every new work order as a new defect.
Where do Mark II and the CMMS fit?
Arkmeds presents Mark II as a bridge between compatible analyzers and digital records, with Bluetooth, document generation and electronic signatures. Its CMMS organizes assets, work orders and history, with QR access and mobile offline work followed by synchronization. Check applicable features for the team’s version, instrument and configuration. Manufacturer documentation about Mark II, in Portuguese.
This connects measurement and documentation rather than leaving the team to start the record again at handover. During implementation, request a demonstration using your own service template: identify the asset, capture available data, add context, review the conclusion, generate the document, obtain the planned signatures and confirm customer access. A signature does not expand the test scope or turn an unresolved technical issue into an approval.
Explore Arkmeds maintenance and documentation workflows
How can you work offline and still track delivery?
Separate service states to locate unfinished steps. This example is fictional, with no measurements or customer results. Times illustrate the workflow; they are not a product duration promise.
| Illustrative time | Service state | Evidence to check |
|---|---|---|
| 10:00 | Field execution completed without internet | Local record linked to asset and work order |
| 10:20 | Connection restored | Synchronization confirmed and attachments accessible |
| 10:30 | Review completed | Scope, results, conclusion and version checked |
| 10:40 | Report delivered | Approved version available to the recipient |
Here, execution-to-delivery takes 40 minutes, and the stage after synchronization takes 20 minutes. Measuring execution alone misses the document wait. These numbers are calculations from the example. In a real operation, record actual events using the same time convention for every service.
Include an exception in the pilot: interrupted connectivity, a missing field or a report returned for correction. Check whether the team distinguishes data saved on the device from data available on the platform. Define who follows up outstanding records at shift end, and how corrections preserve the previous version and their rationale.
Which indicators help evaluate implementation?
Choose measures connected to the problem you want to solve. Work order volume alone does not represent quality, productivity or failure risk. For comparisons, identify the service type, event definition and denominator.
| Proposed indicator | Calculation | What to investigate |
|---|---|---|
| Time to delivery | Customer availability time minus field completion time | Waiting for synchronization, review or signature; examine median and long cases |
| Document returns | Reports returned for inconsistencies / reports reviewed | Ambiguous fields, incorrect asset links and template issues |
| Synchronization backlog | Services without confirmed platform records at a defined time | Connectivity, queues and responsibility for closure |
| Record completeness | Audited assets with complete critical fields / audited assets | Duplicates, mismatched labels and missing serial data |
These are editorial suggestions for local evaluation, not Mark II effectiveness results. Define how to count reports reviewed more than once so the same return does not become several distinct services. Consider review effort too: reducing transcription may change where time is spent without eliminating the need to check the record.
How do you start without rolling out everything at once?
WHO’s 2025 guidance recommends aligning objectives, people, resources, data quality, validated migration and training when implementing a CMMS. It is general guidance and does not endorse a vendor. WHO publication, section 7.5.
As a practical application, choose one service type and a set of identifiable assets. Review records, document templates and responsibilities. Follow the same record from execution to customer access. When a discrepancy appears, correct the entry rule or asset record, then check whether the next person can complete the workflow.
Before expanding the pilot, ask someone who did not perform the service to retrieve the asset, procedure and delivered version. If those answers depend on a conversation with the technician, a document link still needs improvement. This exercise makes the template useful for shift handover, audit and service continuity.
Sources and further reading
- Wubben et al. (2010) — Equipment-related incidents in the operating room
- WHO (2025) — Inventory and maintenance management information system for medical devices
- ILAC-G8:09/2019 — Guidelines on Decision Rules and Statements of Conformity
- JCGM VIM3 — 2.41 Metrological traceability
- Arkmeds — Mark II manufacturer workflow presentation (Portuguese)
- Arkmeds — CMMS maintenance management platform
Research and review: 6 October 2026. Diagrams and record model: Arkmeds editorial work. Example times and calculations are fictional, not customer results.
Original archive date: 2026-10-04. Editorial date reorganized on 8 October 2026.



