Software for the contractors hospitals call when in-house BioMed is overflowed — and the service contract is the unit of work.

01  The medical equipment data model

One hospital system. Many facilities. Every device. One record that knows them all.

The hospital system is the billing customer. The hospital, the surgery center, and the outpatient pavilion are three different service locations. Every Baxter Sigma Spectrum, Datex-Ohmeda Aestiva, and Philips IntelliVue is an Equipment record with a service history that accretes from every visit.

OEM warranty, service agreement, calibration certificate, and MDS2 disclosure are custom records configured day-one — built on the documented Warranty and Service Agreement patterns and the appliance-repair Customer → Appliance → Warranty Claim shape — with role-based layouts so the dispatcher, BMET, and office each see the right fields.

02  Service contract is the unit of work

Sign one master agreement. Cover hundreds of devices. Auto-bill the retainer.

The hospital-side CMMS treats a work order as the atomic unit because in-house BioMed doesn’t bill. You do. Your atomic unit is the master service agreement — covered devices, cadence, tier, renewal date, BAA attached.

FieldCamp models it as a Service Agreement custom record with a stage pipeline (Negotiating → Active → Renewal Due → Expired), a reusable contract template with T&Cs, and auto-deduct on the monthly retainer. Recurring PM jobs chain off the contract, and the BioMed coordinator approves estimates from a passwordless customer portal.

03  The PM calendar your customer can survive a tracer on

Risk-based PM intervals per device. Audit-ready service history per serial.

A surveyor pulls three random serials and asks for the last three PMs. The answer lives on the device record — every visit threaded chronologically with date, tech, form, signature, parts, and leakage readings.

Recurring jobs chain monthly, quarterly, or annually, each templated job type auto-attaching the right form and price-book lines. Job Forms capture Pass/Fail measurements, signatures, photos, Job Logs roll up time on device and parts, and stage guardrails block PM Complete without them. An AEM custom-field group keeps risk-based intervals separate from OEM intervals. One-click PDF export per serial is the artefact your customer hands the surveyor — we do not market it as a Joint Commission compliance report.

04  The PM checklist that actually runs in the field

Pass/Fail measurements. Signature on the device. Offline in shielded rooms.

The Annual PM on a Datex-Ohmeda Aestiva runs as a single Job Form — Pass/Fail rows, numeric measurements, a parts-replaced table, a signature block — auto-attached when the templated job type is created.

Stage guardrails block PM Complete until the signature, leakage reading, and photo are present. In the shielded imaging suite or the OR, the form completes offline and syncs when the phone returns to network. Parts auto-decrement multi-warehouse inventory, and Job Logs roll up time on device and labor cost per visit.

Honest note · FieldCamp captures typed, drawn, or uploaded signatures on the PM report. Per the docs, consult your legal advisor about whether captured signatures meet ESIGN/UETA or 21 CFR Part 11 binding requirements in your jurisdiction.

05  Cert-gated dispatch across the circuit

BMET + Datex-Ohmeda + radiation safety. Only the techs who hold all three.

Your dispatcher runs a circuit across four facilities, eleven techs, seventeen jobs a day — and the wrong tech sent to an anesthesia PM is a wasted truck. Hierarchical skills mean only techs holding the right cert get considered.

An anesthesia Annual PM needs BMET + CBET + a Datex-Ohmeda vendor cert + radiation-safety awareness — held on the Team Member record. Service areas trim the pool by drive radius, capacity rules honor billable hours, and multi-day chaining with travel time lets a circuit-rider hit three hospitals on one optimized route. The live dispatch map and timeline show every tech on one board, and AI Dispatcher returns a top suggestion with confidence and reasoning.

05B  OEM warranty recovery and T&M billing

Was this device under OEM warranty? Don’t eat the labor.

The single biggest revenue leak in ISO contracting: a device under live OEM warranty gets billed to the hospital as T&M because the warranty status lived on a spreadsheet. FieldCamp models OEM warranty as a custom record per device — provider, coverage type, dates, claim status.

The claim is a pipeline (Draft → Filed with OEM → Approved → Reimbursed), patterned on the documented Customer → Appliance → Warranty Claim model. On a covered device, FieldCamp splits the estimate into Bill-to-Hospital vs Recoverable-from-OEM line items; Repair / Refurbish / Replace becomes a Good/Better/Best estimate; flat-rate repair bundles sit in the price book as kits — all on documented Custom Objects & Fields. Your team still submits through the OEM’s own portal — FieldCamp does not ship a native OEM portal API.

06  Recall response across every affected serial

FDA safety advisory drops. Tasks appear on every Sigma Spectrum you service.

An OEM safety advisory lands — a Baxter Sigma Spectrum software patch, 90-day deadline. Today, you hunt affected serials across twelve facility spreadsheets. With FieldCamp, a workflow fans out a corrective job to every device with a matching model and serial in range.

The advisory drops into the unified inbox, the AI document chat parses the PDF for lot ranges, and a Recall record is created — the same Custom Objects & Fields machinery the docs ship for Permits. The rules engine handles the cascade — wired once, alongside the documented workflow examples — and the progress bar tracks 12 patched / 47 affected with a closeout signature per device. This is a configured pattern, not a built-in FDA MAUDE feed.

07  Parts inventory — truck, depot, OEM PO

Sigma battery pack on the van? Or do we burn a trip for a $48 part?

The Annual PM has a battery pack on the line. The question is whether Maria has one on the van. FieldCamp models truck stock and depot stock as separate warehouses with min/max levels — auto-decrement on the job, transfers between locations.

When stock dips below min, a Purchase Order opens against the right OEM distributor — Quest International for Philips, AIV for Baxter — Draft → Sent → Received with auto stock updates. Flat-rate bundles like Annual PM — Anesthesia Machine sit on the price book as kits, maintained in the standard products & services workflow. Lot-level traceability for installed parts is not documented — if you need it that deep, evaluate it on the call.

08  Get paid — retainer plus T&M plus OEM clawback

One contract. Three revenue streams. Synced to QuickBooks.

ISO revenue is multi-stream: the monthly service-contract retainer, the T&M repair invoice to hospital AP, and the warranty-clawback invoice to the OEM. FieldCamp ships three documented invoice methods — from jobs, from estimates, from scratch.

The retainer auto-deducts on the stored Stripe card via the documented Stripe connection, and invoices, payments, customers, and tax sync to QuickBooks, Xero, or Wave. Job Logs roll labor, parts, and miles into per-contract profitability; invoice views and analytics show AR aging. Payment scope is Stripe cards plus manually recorded cash, check, and bank transfer — no Tap-to-Pay, Apple Pay, or native ACH.

09  Ask the fleet anything

Show all Datex-Ohmeda Aestivas with overdue PMs.

The Joint-Commission-tracer scenario is, at its core, ‘tell me about this serial in the next sixty seconds.’ Command Center is the built-in AI chat — ask in plain English, FieldCamp answers from the live data.

‘Show all Datex-Ohmeda Aestiva 5 machines with overdue PMs.’ ‘Last three PMs on SN BSP-04218 — export PDF.’ The platform ships built-in slash skills you extend with your own, AI summaries roll up activity per customer, job, and visit, and analytics dashboards sit alongside. The output is a fast query — not a Joint Commission compliance report; your customer’s compliance team frames the export.

10  Capabilities

Built for the contractors hospitals call when in-house BioMed is overflowed.

Every tile traces to a docs URL; configured patterns are tagged. Nothing here is marketing language without a source. The full integrations & add-ons catalog and the add-ons reference spell out what ships day-one vs what you turn on.

11  Why this matters for medical equipment service

Every other platform is built for the hospital. FieldCamp is built for you.

The category splits into two lanes, and both leave the contractor in the gap. The hospital-side CMMS never had to bill an external contractor; the generic FSM lane never had to model a regulated medical device.

FieldCamp’s vertical-agnostic core carries the contractor side end-to-end — lead to payment in seven stages — with the medical-equipment vocabulary riding on top.

12  Related industries

Same data model. Different trade.

The Hospital System → Facility → Device pattern reuses across every asset-heavy service trade — the same FieldCamp vertical-agnostic core with the vocabulary flipped. Cousins below.

13  FAQ

Questions medical equipment service contractors actually ask.

Honest answers — the kind we’d give on the call. If we don’t ship something, we say so: HIPAA, 21 CFR Part 11 e-sig, native FDA MAUDE feed, direct OEM portal API, Tap-to-Pay.

Every answer is checked against the docs: data-model/equipment, signatures, service-agreements, warranties, custom objects & fields, recurring jobs, and mobile forms.