---
title: "Medical Equipment Service Software — PM, Dispatch & Audit-Ready History | FieldCamp"
url: "https://fieldcamp.ai/medical-equipment-service/"
date: "2026-07-10T00:00:00.000Z"
modified: "2026-07-19T00:00:00.000Z"
type: "WebPage"
resource: "https://fieldcamp.ai/medical-equipment-service/"
timestamp: "2026-07-27T11:26:00.128Z"
author:
  name: "FieldCamp Team"
word_count: 3249
reading_time: "16 min read"
summary: "Home https://fieldcamp.ai/ \\ Medical Equipment Service MEDICAL EQUIPMENT SERVICE SOFTWARE Software for the contractors hospitals call when in-house Bi…"
description: "Medical equipment service software for ISO and HTM contractors. Per-device service history, cert-gated BMET dispatch, recurring PM with offline mobile forms, service contract retainer auto-billing, OEM warranty tracking, and recall fan-out workflows — built for the contractor a hospital calls, not the hospital's in-house CMMS."
language: "en"
---
[Home](https://fieldcamp.ai/)\>Medical Equipment Service

MEDICAL EQUIPMENT SERVICE SOFTWARE

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

Per-device service history for every infusion pump, anesthesia machine, ventilator, and sterilizer you cover. Cert-gated dispatch that only routes BMETs with the right vendor cert and modality skill. Recurring PMs with Pass/Fail measurement forms that work offline in shielded imaging suites. Built for the ISO contractor who signs one master service agreement and covers hundreds of devices across an IDN — not the hospital’s in-house CMMS.

[Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)Built on the same data model that runs HVAC, elevator, and EV contractors — adapted for HTM.

4.8Capterra

Built around the contractor workflow.   
Compatible with whichever hospital CMMS the customer already runs.

TheWorxHub BioMedNuvolo HTMAccruent TMSPhoenix AIMSEQ2 HEMSServiceNow HTM

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](https://docs.fieldcamp.ai/data-model/property-management). Every [Baxter Sigma Spectrum, Datex-Ohmeda Aestiva, and Philips IntelliVue](https://docs.fieldcamp.ai/data-model/equipment) is an Equipment record with a [service history that accretes from every visit](https://docs.fieldcamp.ai/data-model/commercial-hvac).

OEM warranty, service agreement, calibration certificate, and MDS2 disclosure are [custom records configured day-one](https://docs.fieldcamp.ai/data-model/custom-objects-and-fields) — built on the documented Warranty and Service Agreement patterns and the [appliance-repair Customer → Appliance → Warranty Claim](https://docs.fieldcamp.ai/data-model/appliance-repair) shape — with [role-based layouts](https://docs.fieldcamp.ai/data-model/record-layouts) so the dispatcher, BMET, and office each see the right fields.

Hospital System → Facility → Device

Mercy Regional Health is the customer. Mercy Regional Hospital, Mercy West Surgery Center, and Mercy Outpatient Pavilion are three sites. ICU Room 412 is a department. Every device under it is its own Equipment record.

Equipment record holds the spec

Model, serial, OEM, modality, install date, warranty expiry, leakage history, MDS2, SBOM — every device field your BMET will look up before they touch it.

OEM warranty is a custom record

Provider, coverage type, dates, claim status. Configured day-one on the documented Warranty custom-object pattern — not a shipped HTM warranty module.

Role-based record layouts

BMET view (mobile, fields they need on a service call), Dispatcher view (table, fleet-wide), Office view (financial). One record, three layouts.

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](https://docs.fieldcamp.ai/data-model/service-agreements) with a stage pipeline (Negotiating → Active → Renewal Due → Expired), a [reusable contract template with T&Cs](https://docs.fieldcamp.ai/estimates-invoices/contracts-terms-and-attachments), and [auto-deduct on the monthly retainer](https://docs.fieldcamp.ai/payments/auto-deducting-payments-for-invoices-and-recurring-jobs). Recurring PM jobs chain off the contract, and the BioMed coordinator approves estimates from a [passwordless customer portal](https://docs.fieldcamp.ai/online-booking/how-to-set-up-your-customer-portal-for-self-service-scheduling-and-documents).

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](https://docs.fieldcamp.ai/job-management/job-types-and-templates). [Job Forms capture Pass/Fail measurements, signatures, photos](https://docs.fieldcamp.ai/job-management/job-forms-complete-digital-checklist-system), [Job Logs roll up time on device and parts](https://docs.fieldcamp.ai/job-management/tracking-job-logs), and [stage guardrails](https://docs.fieldcamp.ai/data-model/stages-and-workflows) 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](https://docs.fieldcamp.ai/job-management/job-forms-complete-digital-checklist-system) — auto-attached when the templated job type is created.

[Stage guardrails](https://docs.fieldcamp.ai/data-model/stages-and-workflows) 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](https://docs.fieldcamp.ai/job-management/using-forms-in-the-field-mobile-guide). Parts auto-decrement [multi-warehouse inventory](https://docs.fieldcamp.ai/products-services/inventory-management), and [Job Logs roll up time on device and labor cost](https://docs.fieldcamp.ai/job-management/tracking-job-logs) per visit.

Honest note · FieldCamp captures typed, drawn, or uploaded signatures on the PM report. [Per the docs, consult your legal advisor](https://docs.fieldcamp.ai/estimates-invoices/signatures-on-estimates-and-invoices) 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](https://docs.fieldcamp.ai/ai-dispatcher/skills-and-hierarchical-skills).

An anesthesia Annual PM needs BMET + CBET + a Datex-Ohmeda vendor cert + radiation-safety awareness — held on the [Team Member record](https://docs.fieldcamp.ai/data-model/team-members). [Service areas](https://docs.fieldcamp.ai/ai-dispatcher/service-areas-and-zones) trim the pool by drive radius, [capacity rules](https://docs.fieldcamp.ai/ai-dispatcher/capacity-and-workload-limits) honor billable hours, and [multi-day chaining with travel time](https://docs.fieldcamp.ai/ai-dispatcher/multi-day-and-travel-setup) lets a circuit-rider hit three hospitals on one [optimized route](https://docs.fieldcamp.ai/calendar/route-optimization-in-fieldcamp). [The live dispatch map and timeline](https://docs.fieldcamp.ai/ai-dispatcher/live-dispatch-map-timeline) show every tech on one board, and [AI Dispatcher returns a top suggestion with confidence and reasoning](https://docs.fieldcamp.ai/ai-dispatcher/what-is-ai-dispatcher).

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](https://docs.fieldcamp.ai/data-model/appliance-repair). On a covered device, FieldCamp splits the [estimate into Bill-to-Hospital vs Recoverable-from-OEM](https://docs.fieldcamp.ai/estimates-invoices/creating-estimates) line items; Repair / Refurbish / Replace becomes a [Good/Better/Best estimate](https://docs.fieldcamp.ai/estimates-invoices/estimate-options-and-templates); flat-rate repair bundles sit in the [price book as kits](https://docs.fieldcamp.ai/products-services/price-book-and-bundles) — 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](https://docs.fieldcamp.ai/workflow-automation/workflows-overview).

The advisory drops into the [unified inbox](https://docs.fieldcamp.ai/inbox/inbox-overview), the [AI document chat parses the PDF](https://docs.fieldcamp.ai/clients/client-files-documents-and-drive-fieldcamp) for lot ranges, and a Recall record is created — the same Custom Objects & Fields machinery the docs ship for [Permits](https://docs.fieldcamp.ai/data-model/permits). The [rules engine](https://docs.fieldcamp.ai/data-model/automations) handles the cascade — wired once, alongside the documented [workflow examples](https://docs.fieldcamp.ai/workflow-automation/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](https://docs.fieldcamp.ai/products-services/inventory-management) — auto-decrement on the job, transfers between locations.

When stock dips below min, a [Purchase Order opens against the right OEM distributor](https://docs.fieldcamp.ai/products-services/vendors-and-purchase-orders) — 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](https://docs.fieldcamp.ai/products-services/price-book-and-bundles), maintained in the standard [products & services workflow](https://docs.fieldcamp.ai/products-services/managing-products-and-services). 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](https://docs.fieldcamp.ai/estimates-invoices/creating-invoices).

[The retainer auto-deducts on the stored Stripe card](https://docs.fieldcamp.ai/payments/auto-deducting-payments-for-invoices-and-recurring-jobs) via the [documented Stripe connection](https://docs.fieldcamp.ai/payments/connect-stripe-for-online-payments-fieldcamp), and [invoices, payments, customers, and tax sync to QuickBooks, Xero, or Wave](https://docs.fieldcamp.ai/integrations/connect-quickbooks-xero-and-wave-to-fieldcamp). [Job Logs](https://docs.fieldcamp.ai/job-management/tracking-job-logs) roll labor, parts, and miles into per-contract profitability; [invoice views and analytics](https://docs.fieldcamp.ai/estimates-invoices/invoice-views-and-analytics) show AR aging. Payment scope is [Stripe cards plus manually recorded cash, check, and bank transfer](https://docs.fieldcamp.ai/payments/payments-overview) — 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](https://docs.fieldcamp.ai/getting-started/command-center-ai-chat-for-field-service-management-fieldcamp) — 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](https://docs.fieldcamp.ai/getting-started/ai-skills-what-you-can-do-with-chat), [AI summaries roll up activity](https://docs.fieldcamp.ai/clients/ai-summaries-for-clients-jobs-and-visits-fieldcamp) per customer, job, and visit, and [analytics dashboards](https://docs.fieldcamp.ai/analytics/analytics-overview) 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](https://docs.fieldcamp.ai/integrations/apps-and-integrations-all-fieldcamp-connections) and the [add-ons reference](https://docs.fieldcamp.ai/getting-started/fieldcamp-add-ons-all-features-explained) spell out what ships day-one vs what you turn on.

[Data modelHospital System → Facility → DeviceCustomer, Site, and Equipment ship day-one. The hospital is the customer; the hospital and surgery center are sites; ICU 412 is a department.docs · read more →](https://docs.fieldcamp.ai/data-model/commercial-hvac)[DispatchCert-gated BMET assignmentHierarchical skills filter the eligible pool — BMET parent, CBET child, vendor cert, radiation safety. Only the techs who hold all four get considered.docs · read more →](https://docs.fieldcamp.ai/ai-dispatcher/skills-and-hierarchical-skills)[RoutingMulti-day circuit-rider routesTravel chained across facilities — three hospitals in one regional route, route optimization on by default.docs · read more →](https://docs.fieldcamp.ai/ai-dispatcher/multi-day-and-travel-setup)[PM jobsRecurring monthly / quarterly / annualEach cadence is a separate recurring job. Single default form set per recurrence — no rotating PM-1 / PM-2 on one job.docs · read more →](https://docs.fieldcamp.ai/job-management/recurring-jobs)[PM formsPass/Fail + signature + photo + offlineMobile sync when online · works in shielded imaging suites and OR. Customer signature auto-prompted at job completion.docs · read more →](https://docs.fieldcamp.ai/job-management/job-forms-complete-digital-checklist-system)[BillingService contract retainer auto-deductStored Stripe card · monthly auto-charge for recurring PM contracts. Multiple cards per customer profile supported.docs · read more →](https://docs.fieldcamp.ai/payments/auto-deducting-payments-for-invoices-and-recurring-jobs)[PortalFacility BioMed coordinator portalPasswordless magic-link · 24h link expiry · approve estimates, download PM reports, view open work orders.docs · read more →](https://docs.fieldcamp.ai/online-booking/how-to-set-up-your-customer-portal-for-self-service-scheduling-and-documents)[EstimatesRepair / Refurbish / Replace tiersGood/Better/Best multi-option estimates · one-click customer approval · ESIGN/UETA disclaimer preserved.docs · read more →](https://docs.fieldcamp.ai/estimates-invoices/estimate-options-and-templates)[WarrantyOEM warranty as a custom recordConfigured pattern · provider, coverage, dates, claim status. No native OEM portal API integration.docs · read more →](https://docs.fieldcamp.ai/data-model/warranties)[RecallsFan-out workflow across affected serialsCustom Recall record (same shape as Permits) + workflow trigger generates corrective jobs per serial. Configured, not a native FDA MAUDE feed.docs · read more →](https://docs.fieldcamp.ai/workflow-automation/workflows-overview)[InventoryTruck + depot stock + OEM POsMulti-warehouse · min/max levels · auto-decrement on job · PO chain to OEM distributors. No lot-level traceability (honest).docs · read more →](https://docs.fieldcamp.ai/products-services/inventory-management)[AccountingQuickBooks / Xero / Wave syncInvoices, payments, customers, taxes sync to your accounting platform. Stripe cards + recorded cash/check/bank only.docs · read more →](https://docs.fieldcamp.ai/integrations/connect-quickbooks-xero-and-wave-to-fieldcamp)

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](https://docs.fieldcamp.ai/data-model/built-for-any-operation) carries the contractor side end-to-end — [lead to payment in seven stages](https://docs.fieldcamp.ai/getting-started/fieldcamp-workflow-from-lead-to-payment) — 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](https://docs.fieldcamp.ai/data-model/built-for-any-operation) with the vocabulary flipped. Cousins below.

[Appliance Repair →Warranty-claim cousin · Customer → Appliance → Claim. The pattern under §05B OEM warranty recovery.](https://fieldcamp.ai/appliance-repair/)[HVAC →Recurring-PM cousin · Property → Unit → Equipment. The §01 multi-facility data model template.](https://fieldcamp.ai/hvac-software/)[Elevator Maintenance →Compliance-inspection cousin · Building → Bank → Car. Cat-1 / Cat-5 cadence is structurally similar to recurring PM.](https://fieldcamp.ai/elevator-maintenance/)[Electrician →Electrical-safety cousin · Site → Panel → Circuit. Service + project + EV make-ready.](https://fieldcamp.ai/electrician-software/)[Pest Control →Recurring-route cousin · Site → Route → Treatment. Same recurring-job machinery in a different vocabulary.](https://fieldcamp.ai/pest-control-software/)[Installation →Equipment-install cousin · Equipment + Warranty + Service. The unit you install becomes a trackable asset.](https://fieldcamp.ai/installation-software/)

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.

What is medical equipment service software?

Medical equipment service software is the platform an ISO (Independent Service Organization) or HTM/BioMed service contractor uses to run service contracts on regulated medical devices — patient monitors, infusion pumps, ventilators, anesthesia machines, sterilizers, imaging systems, lab analyzers. The atomic unit is the service contract (one master agreement covering hundreds of devices across multiple facilities), and the platform runs the loop from device intake to recurring PM to OEM warranty recovery to invoice. It is distinct from a hospital-side CMMS (TheWorxHub BioMed, Nuvolo HTM, Accruent TMS, EQ2 HEMS, Phoenix AIMS), which is built for the in-house Clinical Engineering department and treats individual work orders as the atomic unit. FieldCamp sits on the contractor's side and plays alongside whichever CMMS the hospital already runs. Built on the documented Equipment record and the Customer→Site→Asset data model — see docs.fieldcamp.ai/data-model/equipment.

How is this different from a hospital CMMS like TheWorxHub or Nuvolo?

TheWorxHub BioMed, Nuvolo HTM, Accruent TMS, Phoenix AIMS, and EQ2 HEMS are built for the hospital's in-house Clinical Engineering department — they manage the hospital's view of its own equipment, and they don't bill an outside contractor. FieldCamp is built for the contractor a hospital calls when in-house BioMed is overflowed or absent. Service-contract billing, multi-facility IDN customers (one customer that owns many sites), cert-gated dispatch for an ISO's roving BMETs, OEM warranty recovery as recoverable revenue against the OEM, and recall fan-out across every affected serial in your contracted fleet — these are contractor problems the hospital-side CMMS doesn't solve. The two systems coexist: see docs.fieldcamp.ai/data-model/built-for-any-operation.

Does FieldCamp support PM compliance reporting for Joint Commission audits?

FieldCamp produces per-device service-history PDFs your hospital customer can hand to a surveyor — every visit threaded chronologically with date, tech, form completed, signature captured, parts used, and measurements. The documented building blocks are Job Forms (Pass/Fail measurements + signature + attachment), Job Logs (time on device, parts, miles), Stages with guardrails (PM can't advance to Complete without sig + photo + form), and per-record PDF export. We do not market FieldCamp as a Joint Commission compliance reporting module, and our docs do not claim accreditation-survey certification. Your customer's compliance team owns the framing of the export — we ship the export. See docs.fieldcamp.ai/job-management/tracking-job-logs.

Can I model an AEM (Alternate Equipment Maintenance) program?

Yes, as a configured pattern. Add a custom-field group to the Equipment record — AEM Eligible (Y/N), Risk Score (1-12), and Interval — using FieldCamp's Custom Objects & Fields machinery. Then create a recurring job per interval (typically separate recurring jobs for monthly Electrical Safety + quarterly Performance Verification + annual Full PM rather than rotating forms on one job). FieldCamp does not ship a built-in AEM module and the docs do not reference AAMI EQ103:2024\. The eligibility decision (which devices CMS S&C 14-07 allows to use risk-based intervals vs OEM intervals) is yours to make — FieldCamp models it as configuration. See docs.fieldcamp.ai/data-model/custom-objects-and-fields.

Does FieldCamp integrate with OEM warranty portals (GE, Philips, Siemens, Medtronic)?

FieldCamp tracks OEM warranty status and the claim lifecycle as a custom record per device — Provider, Coverage type, Effective and Expiry dates, Claim status pipeline (Draft → Filed with OEM → Approved → Reimbursed). The pattern is modeled on the documented Warranty custom-object example and the Customer→Appliance→Warranty Claim shape in the appliance-repair docs. The audit trail lives in FieldCamp. Your team still submits the claim through the OEM's own portal — Philips Customer Services, GE Service, Siemens Healthineers, Medtronic — because FieldCamp does not ship a native OEM portal API integration. See docs.fieldcamp.ai/data-model/warranties.

Can field techs work offline in shielded imaging suites or operating rooms?

Yes. The mobile Job Forms guide documents offline mode end-to-end: forms complete offline, photos capture offline, signatures draw offline, and everything syncs in the background when the phone returns to network. Customer signature is auto-prompted at job completion. This is the same machinery used for any offline environment — it doesn't require an HTM-specific module. See docs.fieldcamp.ai/job-management/using-forms-in-the-field-mobile-guide.

Is the captured signature on a PM report legally binding?

FieldCamp captures typed, drawn, or uploaded signatures on PM reports, estimates, and invoices. Per the docs, you should consult your legal advisor about whether captured signatures meet ESIGN/UETA legal-binding requirements in your jurisdiction. We do not market the captured signature as 21 CFR Part 11 compliant. The signature is captured, time-stamped, and attached to the record — your compliance counsel owns whether that meets the legal bar for your customer contract. See docs.fieldcamp.ai/estimates-invoices/signatures-on-estimates-and-invoices.

Does FieldCamp claim HIPAA compliance or ship a BAA?

No. FieldCamp's docs make no HIPAA claims — there is no HIPAA Security Rule, BAA template, PHI safeguard module, or field-level PHI redaction in the platform. Roles & Permissions ship at module-level only (Admin, Dispatcher, Field Tech Pro, Field Tech Lite plus custom roles on Pro) — not field-level access control. Any PHI/PII storage policy, BAA execution, and protected-health-information handling are your responsibility. You can attach your own BAA in Contracts, Terms & Attachments on a customer record. See docs.fieldcamp.ai/getting-started/roles-and-permissions-who-can-see-what-fieldcamp.

Can I run different PM cadences on one device (PM-1 monthly plus PM-2 quarterly)?

The recurring-jobs docs are explicit that each visit inherits a single default form set — there is no auto-rotating PM-1 / PM-2 / PM-3 checklist on one recurring job. The recommended pattern is to create separate recurring jobs per cadence on the same device — for example, a Monthly Electrical Safety recurring job, a Quarterly Performance Verification recurring job, and an Annual Full PM recurring job, each with its own templated job type and form. They all roll up under the device's service history. See docs.fieldcamp.ai/job-management/recurring-jobs.

How does FieldCamp price for an ISO with 15 BMETs and 200+ hospitals under contract?

FieldCamp scales from a two-truck residential installer through a multi-state regional ISO. Pricing is simple flat per-user, and add-ons (AI Dispatcher, Online Booking, Customer Portal, Job Forms, Workflow Automation, Multi-Day Jobs) unlock as you need them — book a fifteen-minute call and we'll spec your hospital portfolio, your dispatch rules, and your service-contract spine on the call.

Get started

## Bring your hospital portfolio. _We’ll spin up the data model on the call._

Fifteen minutes. We’ll set up your first hospital system, three facilities, and the service-contract spine live on the call — then drop in three devices threaded all the way to a PM checklist. See [the quick-start guide](https://docs.fieldcamp.ai/getting-started/quick-start-set-up-your-business-in-fieldcamp) for what we’ll cover.

[Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)