FieldRepOps

What it does · documents and secure sends

What leaves the building, and the record that it did.

A spine distributorship sends the same few documents over and over: the delivery order to procurement and to the manufacturer, the monthly statement to each manufacturer, the rep's statement, the return report. FieldRep Ops sends each one from the system, by a link that expires, with no patient data in any attachment, and writes down every send and every open.

Last reviewed November 8, 2026

Every send and every open on record, in a log that cannot be edited 7 days and a delivery order link expires; leadership can revoke one sooner 1 attachment the system ever sends: a rep's own statement, with no patient data

A link, not an attachment

A delivery order, a manufacturer statement or a return report goes out as a secure link. The link is a 256-bit token stored only as a hash, checked for expiry and revocation on every open, and limited against abuse. Delivery order links expire in seven days; leadership can revoke a link at any time. The one attachment the system ever sends is a rep's own commission statement, which carries no patient data, and a test in the build keeps it that way.

Every send and every open, on record

Each outgoing email is written down once: recipients, subject, body, time. Each open of a secure link is logged. Leadership reads one access log under Compliance: who viewed a patient identifier, who exported what, which links were opened and when. The log cannot be edited or deleted.

Sent as your distributorship, from the platform

Email goes out as your distributorship's name via FieldRepOps, with replies routed to the address you set and blind copies to whoever you choose. Until that is set up, the system refuses to send anything external.

Your files, in your own bucket

Signatures, device-label photos and tray photos live in a storage bucket that is yours alone, with public access prevented at the bucket level. Nothing is served by a public or long-lived link: every file is fetched on the server under the signed-in user's own permissions. Photos taken in the operating room or sterile processing are treated as protected by default, and every reveal of one is logged.

A security summary for the hospital's IT

Leadership can download a Data Handling and Security Summary from inside the system, generated on demand and stamped with the build it describes, to hand to a hospital's IT department when they ask what system their purchase orders and patient identifiers pass through.

What it does not do

It does not attach delivery orders, manufacturer statements or return reports to email. It does not send from your own email domain; mail goes out via FieldRepOps in your distributorship's name. It does not store the hospital's PO document.

Straight answers

How does FieldRep Ops send a delivery order?

As a secure link in an email from the system, never as an attachment. The link is a 256-bit token stored as a hash, expires in seven days, can be revoked, and every open is logged.

Is any patient data in the emails?

No. The email to procurement carries the case number, not the patient identifier. The one attachment the system sends is a rep's own commission statement, which has no patient data on it.

Who can see the access log?

Leadership, under Compliance. It shows views of patient identifiers, exports and link opens, and it cannot be edited or deleted.

Where are the files stored?

In a storage bucket that belongs to your distributorship alone, with public access prevented. Files are fetched on the server under the signed-in user's permissions; there are no public links.

What do I give a hospital's IT department?

The Data Handling and Security Summary, downloaded by leadership from inside the system, and the public security page.

What it does, page by page

Each page describes one thing the system does for a spine distributorship, checked against the product as it runs today.

One signed record, for the whole spine distributorship

All of it keys off the delivery order signed at the case. From that one record come the send to procurement, the follow-ups, each rep's statement, the match against the manufacturer's statement, the tray check-in and the closed month. Nothing is retyped, so nothing drifts, and every total is reconciled back to the signed orders before every release and every week in production. It runs in a private environment that is your spine distributorship's alone; the security page says exactly what that means, in a form you can check.

Founding distributors

We are taking on a small number of founding spine distributors now, who use FieldRep Ops free while it proves itself on their books and know the price before they start. One private environment per distributorship; nothing shared with anyone.

FieldRepOps
FieldRep Ops is the operating and financial system of record for independent spine distributorships
Customer sign-in access@fieldrepops.com Updates Answers Security Privacy policy