A Simulator Result Is a Test-Method Result
A service record says an NIBP check passed, but the patient simulator has since received a firmware update and its preset was edited. Can the old result still support a release decision? Preserve it as evidence of the test performed at that time. A later simulator change does not, by itself, invalidate that historical observation. It also does not establish that a new test would be comparable, or that the monitor is ready for service today.
Record the simulator model and individual asset, the firmware actually installed, the applicable communications specification, automation software, preset or autosequence revision, test order, physical setup, raw readings, and acceptance criteria. If the old configuration cannot be reconstructed, state the gap. Obtain OEM information or repeat the relevant verification under the applicable device procedure before relying on an uncertain comparison.
This article proposes a practical documentation and comparison framework for biomedical equipment technicians, independent service organizations, and hospital equipment leaders. It is not a regulator-mandated field list. The concrete examples concern the Fluke ProSim 8; other simulators may expose versions and configurations differently.
Fluke describes NIBP static-pressure linearity and dynamic-pressure repeatability testing on its ProSim 8/8P product page. Those are different test purposes. Preserving the method lets a reviewer distinguish a changed monitor response from a changed bench configuration.
The Minimum Result-Provenance Record
Attach a method snapshot to each result rather than relying only on the current test-equipment inventory entry. An inventory field can change after an update; the earlier work order still needs its earlier configuration. The following fields are a recommended starting point. Entries are record descriptions, not test settings or acceptance limits.
| Record field | What to retain | Question it helps answer |
|---|---|---|
| Simulator identity | Manufacturer, model, serial or asset ID, and link to applicable calibration status or certificate. | Which individual instrument produced the stimulus or measurement? |
| Installed firmware | Full version/build returned by the instrument, capture date, and retrieval method. | Which software was running during this test? |
| Communications reference | Interface specification title/revision and connection or driver details when remote control was used; otherwise record not used. | Which command definitions applied? This is separate from firmware. |
| Automation and procedure | Application and plug-in versions when used, plus the controlled test procedure revision. | Which software and instructions executed and evaluated the run? |
| Preset, autosequence, and curve | Exact name, local revision, preserved export or settings record; include an R-curve if relevant. | Can the active configuration be recovered rather than guessed from a name? |
| Profile and sequence | Selected function, setpoints, test order, relevant timing, and any manual changes or interruptions. | What actually ran, and did it match the intended procedure? |
| Physical setup | Applicable cuff, tubing, adapters, mandrel or chamber, and setup record or reference. | Were the coupling conditions comparable? |
| Results and criteria | Raw readings, units, errors, acceptance limits and their governing document/revision. | What was observed, and why was it accepted or rejected? |
| Execution identity | Date/time with time basis, operator, monitor ID/configuration, and work-order reference. | Which device and service event does this result describe? |
| Disposition and gaps | Comparison scope, missing evidence, reviewer, follow-up action, and linked new test if performed. | What decision is supported, and what remains unresolved? |
Keep the original result and snapshot together. A single archive can support several linked work orders if each points to the exact preserved revision. Do not reconstruct an unknown historical version by copying today's asset record into an older entry. Record an additive clarification with its evidence and date instead. These fields extend the broader service work-order record for this particular test-method problem.
Record Firmware, Interface, and Automation Versions Separately
The ProSim 8 Communications Interface, revision 3.17, documents IDENT as a query returning the model and firmware version, including the build. Capture the actual returned string through a supported service workflow. A revision printed on the interface PDF identifies that document; it is not a firmware version read from the simulator.
At the November 6, 2026 source check, the product page listed firmware v2.11 and communications interface v3.17 separately. Neither download listing proves what is installed on a particular unit. Preserve the observed firmware alongside the reference used to interpret remote commands, and mark a field unknown when it was not captured. Use the version-retrieval method documented for the instrument rather than assuming a menu path or inferring the build from a download filename.
Automation has its own version dependencies. The Ansur page lists ProSim plug-in versions with different Ansur Executive requirements. Record the actual application and plug-in combination when automation is used. A successful connection alone is not evidence that every parameter or acceptance rule was correct. These examples do not establish compatibility for an unlisted combination.
Why Firmware 2.00's Pressure-Zeroing Step Matters
The older ProSim 8 Users Manual, revision 3, March 2016, contains a Zero Pressure subsection on printed page 58 specifically identifying firmware 2.00. This is an older manual revision used as a historical example; it should not be treated as the current operating procedure for every ProSim unit. Check the product page and OEM support for instructions applicable to the unit and firmware in use.
The narrow conclusion is useful: an OEM operating instruction can identify a firmware version, so a service procedure reference should be matched to the instrument being used. The example does not show that firmware 2.11 changed zeroing, menus, sensor accuracy, or pulse generation. Those release-specific changes need applicable OEM documentation.
Presets, Autosequences, and the Version You Actually Ran
Fluke's ProSim8 support FAQ says users can create and save customized autosequences, while default autosequences cannot be replaced. It separately says preset values can be replaced and restored. Therefore, do not describe all factory presets as immutable: the distinction between presets and default autosequences matters.
A familiar sequence name does not identify its complete contents. Preserve the settings or export that was actually used, with a local revision. When a name is reused, retain both versions and their effective dates. If available, a file hash can help distinguish exports, but it cannot prove that the archived file was the one loaded during a historical run.
Ansur documentation describes transfer of autosequences and presets and creation or modification of R-curves. Treat each relevant configuration item as part of the method. Record whether the run used a default or custom sequence, whether manual changes occurred, and whether tests ran sequentially or concurrently. Avoid changing a preset merely to make a monitor match a target value.
Fluke also describes version-controlled electronic test records as an Ansur capability. Check the actual exported record before assuming it contains firmware, configuration exports, and setup details. Software capability is not proof that a particular hospital's record is complete. Link any missing attachments explicitly rather than assuming the application saved them.
NIBP: Repeatability, Not Clinical Accuracy
The public abstract for ISO/TS 81060-5:2020 addresses repeatability and reproducibility of NIBP simulators for automated oscillometric devices. It excludes testing the simulator-monitor interaction, including agreement between set and displayed values and cuff/tubing properties. It also does not check absolute blood-pressure accuracy. The publicly available scope supplies this boundary; it does not supply acceptance limits for a monitor service test.
For this record framework, distinguish static-pressure checks, leak checks, and dynamic simulation. Record the test performed and the criteria applicable to the monitor and setup. A dynamic pass cannot be recast as clinical blood-pressure accuracy. Matching a displayed number to a simulator target is also insufficient evidence of method equivalence.
Fluke's FAQ identifies tubing, cuff size, pulse volume, and monitor algorithms as reasons dynamic readings can differ. Retain those setup details when relevant. For the underlying bench-test distinctions, see NIBP Simulator Testing: Limits of a Bench Result. The decision here is narrower: whether a historical result has enough method identity for the comparison now proposed.
SunTech Medical's NIBP simulator discussion likewise separates repeatability and agreement from clinical accuracy. This is manufacturer commentary supporting that limited distinction; its older regulatory references are not used here as current requirements.
Carry-Forward Decision: Same Method, Documented Change, or Re-Test
First define the purpose of the comparison. Reviewing a trend, investigating an earlier work order, and releasing a monitor after new corrective work are different decisions. The matrix below is a recommended review framework, not a universal OEM rule or authorization to skip required testing.
| Evidence situation | What can be concluded | Recommended disposition |
|---|---|---|
| The historical method is recorded and relevant configuration/setup match. | The record supports assessing comparability within the recorded scope; matching versions alone do not establish current device condition. | Retain the earlier observation. Complete any verification required for the current service event before release. |
| A version changed and applicable OEM notes identify its effects. | The notes may support a scoped comparison after considering settings, procedure, and automation dependencies. | Attach the exact notes and reviewer rationale. Re-run affected checks when called for by the applicable procedure or justified assessment. |
| Firmware effects are unknown, a preset changed, or the old configuration is missing. | Comparability is unresolved. The old observation remains historical evidence. | Seek OEM clarification; repeat relevant verification under a known, documented method or design a limited bridge assessment. Keep the gap explicit. |
| A different simulator model or physical setup is used. | Matching preset values do not establish interchangeable results. | Assess method suitability and applicable criteria for the new setup. Establish a new baseline when needed and document limits on comparison. |
For the opening scenario, retain the six-month-old pass and identify exactly what it records. If the old preset was not preserved, today's edited file cannot fill that gap. Document the missing revision and the update date, obtain any available OEM assessment, and record the current verification required for the monitor's service event. Avoid relabeling the earlier result as a failure solely because the bench changed later.
Equally, a well-documented old result does not replace tests required after subsequent repair, a new fault, or a change to the monitor. The department's responsible reviewer should record how historical evidence contributes to that specific decision. The site's major-repair return-to-service guide covers that broader service-event question.
After an Update or Rollback: What to Record and Re-Run
Use a controlled before-and-after record for an authorized update. These are documentation actions; installation and test execution should follow the applicable manufacturer instructions. The ProSim FAQ identifies USB as the firmware update path for that product, which should not be generalized to other simulators.
Before the change, preserve the observed firmware, relevant configuration exports, automation versions, existing records, and the reason for the update. Identify which service procedures use that simulator.
Record the authorized update source, action date, operator, and resulting observed version. Confirm configuration and automation compatibility using applicable OEM information; do not assume an update preserves every custom setting.
Assess which functions or procedures could be affected. Document the checks selected, their criteria and results, and why that scope answers the identified uncertainty. Use the acceptance criteria applicable to the selected test and method.
Link the new method revision to subsequent work orders while retaining previous snapshots. If an anomaly appears, identify potentially affected tests and route their review to the responsible equipment and quality owners.
A bridge assessment compares defined old and new conditions to answer a limited question. Before running it, specify the function, configurations, suitable stable reference or control, setup, repeats, applicable criteria, and decision owner. Keep other conditions controlled and retain individual observations. If the old method cannot be recreated, describe the exercise as a new baseline or limited comparison, not a demonstrated historical bridge.
Agreement on one control monitor or one profile does not establish equivalence for every monitor, waveform, or operating range, and it does not calibrate the simulator. State what remains untested. When evidence is insufficient for the intended use, obtain manufacturer guidance or use another qualified method rather than stretching the conclusion.
Do not assume rollback is available or authorized. If an OEM-supported rollback is performed, record it as another change and reassess the relevant configuration and testing scope. Preserve work orders created during the intervening version period for review if a credible impact is identified. An update alone does not prove those earlier tests were wrong.
What the Record Does Not Prove
A complete method record helps explain what happened; it does not guarantee reproducibility, clinical accuracy, compliance, or safety. A firmware update is not evidence of calibration. Link the simulator's applicable calibration evidence separately, and keep the device manufacturer's service criteria and any required broader release checks in view.
Close the work order with a bounded statement: which device was tested, which simulator configuration was used, which observations met which documented criteria, what comparison was justified, and which gaps remain. Retain records under the organization's applicable retention policy; these sources do not establish a universal retention period. Escalate unresolved suitability or release questions to the responsible technical reviewer and OEM rather than converting an incomplete pass into a wider assurance.
