The first sponsored study teaches a practice something fast: the EHR it relies on was built to bill visits. Proving where a vial came from? Not its job. The chart handles a blood pressure reading and a diagnosis code just fine. But a lot number? A storage excursion? The certificate of analysis that arrived in the shipping box? There’s usually no sensible place for any of that.

And that gap is a problem. Monitors and auditors rate a site mostly on its paperwork — when the documentation trail breaks, the data itself comes under question.

So what should clinical research sites and research-active practices actually expect from an EHR or EMR once investigational compounds and research-grade materials enter daily operations? Here’s the rundown.

Where a Standard EHR / EMR Falls Short in Research

Most EHR and EMR platforms revolve around the encounter — patient arrives, provider documents, claim goes out. Research revolves around something else entirely: the protocol and the product. An auditor’s questions look nothing like a biller’s:

• Which lot arrived, on which date, sent by whom?
• Where was it kept — and did the temperature hold the entire time?
• Who touched it along the way, and whose signature sits at each step?
• Where did every unit end up, and what’s still on the shelf?
• Can you pull up the original record plus every change ever made to it?

Free-text notes and scanned PDFs can answer some of that — right up until a monitor wants a reconciliation spanning three months and two storage locations.

Better: keep research materials as structured data in the EHR / EMR itself — or in a module wired tightly into it — instead of attachments dangling off a chart.

Investigational Product Accountability

Accountability sits at the center of all this. Each unit that comes in has to be traceable from the receiving dock to wherever it ends up — used under protocol, shipped back to the sponsor, or destroyed with documentation.

What the record should capture

At minimum, a workable accountability log in an EMR needs:

• Protocol number and site number
• Product name, strength and formulation as listed by the sponsor or supplier
• Lot or batch number, with expiration or retest date
• Quantity received, quantity dispensed or used, quantity returned, quantity destroyed
• Running balance, calculated by the system rather than typed in
• Date, time and user ID for every transaction

Manual systems usually fall apart at the running balance. Let the EHR build it from discrete transactions and a discrepancy surfaces the day it happens — not at the close-out visit.

Lot and batch numbers as real fields

Lot numbers need their own structured, searchable field. Bury them in note text and you’re stuck the day a recall or a quality notice lands on a specific lot — the site then has to pull every record tied to that lot, fast. A dedicated field answers in one query. Scanned documents never will.

The better systems go further: an expired lot simply can’t get logged as used.

Linking Certificates of Analysis to the Record

A certificate of analysis (COA) is the supplier stating, on paper, what’s in a specific lot and how it was tested. With sponsor-supplied investigational product, the sponsor normally holds this documentation. But for research-grade materials a lab or site buys on its own, the COA may be the only proof of identity and quality the site ever gets.

Staff should be able to attach the COA to the lot record itself — not drop it in a general document folder. Open lot 24-0917 and the matching COA should sit one click away, with the uploader and upload time visible.

An example from laboratory procurement

Take a lab running in vitro assays that also buys research-grade peptides alongside its sponsored work. Retatrutide (LY3437943) makes a good example. It’s an Eli Lilly compound, still in clinical trials, not FDA-approved. Apart from the trials, labs source the retatrutide peptide as research-use-only stock for in vitro work only — same paperwork discipline as everything else on the shelf.

When a shipment lands, log the supplier name, the order and receipt dates, the lot number printed on the vial, and that lot’s COA. From the COA, pull these into structured fields: HPLC purity, identity confirmation (mass spectrometry, typically), net peptide content, endotoxin results. And if the lot number on the vial doesn’t match the one on the COA, the item goes into quarantine in the system until someone sorts out the mismatch.

Some US suppliers make life easier here, publishing third-party COAs tied to individual lots. HEEZ Research, for example, posts lot-specific third-party COAs across its catalog, reports HPLC purity of 99% or higher, and marks everything in vitro research only — not for human or veterinary use. A lab can pull the COA for the exact lot that arrived and file it against the receiving record the same day.

Same rule for all the research peptides and reagents a lab buys: a generic, undated COA tells you almost nothing. What makes a record defensible is a lot-specific document that matches the label.

Chain of Custody and Storage Logs

Chain of custody comes down to one question: who had this, and when? Practically, the EMR has to log every handoff — receiving, storage, the preparation area, use or disposal — each with a timestamp and a user ID.

Storage conditions belong in that same record. Plenty of investigational and research materials need refrigeration or freezing, and one temperature excursion can render a lot unusable. Look for:

• Integration with digital temperature monitors, so readings flow in automatically
• Alerts when a reading falls outside the defined range
• A required excursion note, with an assessment of impact and the name of the person who made it
• The ability to link an excursion to every lot stored in that unit at the time

Freezer dies overnight? The site should be able to list every affected lot in a single report.

Audit Trails, E-Signatures and 21 CFR Part 11

21 CFR Part 11 is the FDA’s rulebook covering electronic records and signatures in regulated research. Plenty of sites fall technically outside its scope. Sponsors still increasingly expect Part 11-style controls as the default.

Audit trail requirements

The audit trail has to be computer-generated and time-stamped, with no way for ordinary users to edit it or switch it off. For each change to a research record it keeps the original value, the new value, the person, the time, and the reason. Make ’reason for change’ a required field that can’t be skipped — a small feature, but auditors notice it.

How Electronic Signatures Should Work

An e-signature should map to a single unique user and show the printed name, date and time, plus the meaning of the signature: reviewed, approved, verified count. Signing should mean re-entering credentials — not just clicking a button in an open session. Shared logins defeat the whole point. Block them technically instead of just discouraging them by policy.

Templates Built Around Each Protocol

Every protocol documents differently — its own visit schedule, its own assessments, its own quirks. With protocol-specific templates, the site builds those requirements into the workflow instead of relying on coordinators to remember them.

A solid template fills in the required fields ahead of time, keeps visits inside their windows, and nudges the coordinator for the accountability entry at the right step. Version the templates as well — when a protocol gets amended, the old record-keeping shouldn’t get rewritten.

Role-Based Access Control

Sensitivity in research records runs higher than in routine charts, and blinded studies complicate it further. Role-based access controls who sees unblinded product information, who can change inventory counts, and who signs as principal investigator.

Typically the setup splits into at least four roles: coordinator, pharmacist or product manager, investigator, and monitor. Monitors need read-only access to source documents and the audit trail — a restricted remote view is ideal, letting them finish much of the review before they set foot on site.

Connecting Inventory and Practice Management Software

Research spans systems, almost always. Practice management software covers scheduling and billing; supplies might sit in a separate inventory tool; sponsors layer their own electronic data capture platforms over everything.

What matters most, practically:

• Scheduling: when a study visit is booked in the practice management software, its protocol ID should travel with it, so the EMR opens the correct template.
• Billing: services covered by the research budget stay separate from billable care — mixing them invites double billing, a compliance risk in its own right.
• Inventory: entries for receiving, use and destruction should update stock counts in one place — not three.
• Data export: sponsor reporting runs on structured exports, never screenshots.

When the systems talk to each other, the coordinator enters data once.

Reporting for Sponsors and Monitors

All this structure pays off in reporting. A research-ready EHR or EMR produces, on demand:

• Product accountability logs by protocol, lot and date range
• Temperature logs and excursion reports by storage unit
• Audit trail extracts for specific records or users
• Enrollment and visit-compliance summaries
• Lot-level reports showing every use of a given batch

If a monitor’s standard request takes more than a few minutes to produce, the system isn’t doing its job.

FAQ

Can a standard EHR or EMR handle investigational product tracking?

Some can, with configuration — provided they support custom structured fields, record-level document linking and a locked audit trail. Many will still need an add-on module or an inventory integration.

Why should lot numbers be structured fields instead of notes?

Because structured fields can be queried, validated and reported on. Quality issue on one lot? The site finds every related record in minutes instead of trawling free text and scanned files.

What should a lot-specific certificate of analysis include?

Lot number, test date, HPLC purity, identity confirmation method and result, net content — at a minimum. Endotoxin results are expected too for many research materials. And the lot number on the COA must match the label on what actually arrived.

Does 21 CFR Part 11 apply to every research site?

Scope depends on the record types and whether they’re submitted to FDA. Even where it doesn’t strictly apply, sponsors commonly expect Part 11-style audit trails and e-signatures — building to that standard is the safer default.

How does practice management software fit into research workflows?

Scheduling and billing. Link study visits to protocol IDs, keep research-covered services apart from billable care, and the EHR, billing record and sponsor data stay consistent.