A practice that takes on its first sponsored study usually finds out fast that its EHR was built for billing visits, not for proving where a vial came from. The chart can record a blood pressure and a diagnosis code. It often has nowhere sensible to put a lot number, a storage excursion, or the certificate of analysis that came in the shipping box.

That gap matters. Monitors and auditors judge a site largely on its paperwork, and a broken documentation trail puts the data in question.

This article covers what clinical research sites and research-active practices should expect from an EHR or EMR when investigational compounds and research-grade materials are part of daily operations.

Why a Standard EHR / EMR Falls Short for Research

Most EHR and EMR platforms are organized around the encounter: a patient arrives, a provider documents, a claim goes out. Research work is organized around the protocol and the product. The questions an auditor asks are different:

• Which lot was received, on what date, and from whom?
• Where was it stored, and was the temperature in range the whole time?
• Who handled it, and who signed off at each step?
• Where did each unit go, and how much is left?
• Can you show the original record and every change made to it?

Free-text notes and scanned PDFs can sometimes answer these, until a monitor asks for a reconciliation across three months and two storage locations.

The better approach is to treat research materials as structured data inside the EHR / EMR, or in a tightly connected module, rather than as attachments.

Investigational Product Accountability

Accountability is the core requirement. Every unit received should be traceable from the receiving dock to its final disposition, whether that is use under protocol, return to the sponsor, or documented destruction.

What the record should capture

A useful accountability log in an EMR includes, at minimum:

• 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

The running balance is where manual systems usually break. If the EHR calculates it from discrete transactions, a mismatch shows up the day it happens rather than at the close-out visit.

Lot and batch numbers as real fields

Lot numbers should be structured, searchable fields, not text buried in a note. When a supplier or sponsor issues a recall or a quality notice for a specific lot, the site needs to pull every record tied to that lot in minutes. A query against a dedicated field does that. A search through scanned documents does not.

Good systems also flag an expired lot before it can be logged as used.

Linking Certificates of Analysis to the Record

A certificate of analysis (COA) is the supplier’s statement of what a specific lot contains and how it was tested. For sponsor-supplied investigational product, the sponsor usually controls this documentation. For research-grade materials a lab or site buys directly, the COA is often the only proof of identity and quality the site will ever have.

The EHR or EMR should let staff attach the COA to the lot record itself, not just to a general document folder. When someone opens lot 24-0917, the matching COA should be one click away, and the system should show who uploaded it and when.

An example from laboratory procurement

Consider a lab that runs in vitro assays and procures research-grade peptides alongside its sponsored work. Retatrutide (LY3437943) is a useful example. It is an investigational compound from Eli Lilly that remains in clinical trials and is not FDA-approved. Separately from those trials, research labs source the retatrutide peptide as a research-use-only material for in vitro work, and that material needs the same documentation discipline as anything else on the shelf.

When the lab receives it, the record should capture the supplier name, the order and receipt dates, the lot number printed on the vial, and the lot-specific COA. The COA fields worth recording as structured data are HPLC purity, identity confirmation (typically mass spectrometry), net peptide content, and endotoxin results. If the lot number on the vial does not match the lot number on the COA, the item should be quarantined in the system until the discrepancy is resolved.

Some US suppliers make this easier by publishing third-party COAs tied to individual lots. HEEZ Research, for instance, posts lot-specific third-party COAs for its catalog, reports purity of 99% or higher by HPLC, and labels its products for in vitro research only, not for human or veterinary use. A lab can download the COA for the exact lot it received and attach it to the receiving record the same day.

The general rule holds for any of the research peptides or reagents a lab buys: a generic, undated COA tells you very little. A lot-specific document that matches the label is what makes the record defensible.

Chain of Custody and Storage Logs

Chain of custody answers a simple question: who had this, and when? In practice, that means the EMR should log every handoff, from receiving to storage to the preparation area to use or disposal, with a timestamp and user ID.

Storage conditions belong in the same record. Many investigational and research materials require refrigeration or freezing, and a temperature excursion can make 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

When a freezer fails overnight, the site should list every affected lot in one report.

Audit Trails and 21 CFR Part 11-Style E-Signatures

FDA’s 21 CFR Part 11 sets expectations for electronic records and signatures in regulated research. Even when a site’s specific work falls outside its scope, sponsors increasingly expect Part 11-style controls as a baseline.

Audit trail requirements

The audit trail should be computer-generated, time-stamped and impossible for ordinary users to edit or disable. For every change to a research record, it should keep the original value, the new value, who made the change, when, and why. A “reason for change” prompt that cannot be skipped is a small feature that auditors notice.

Electronic signatures

E-signatures should be linked to a unique user, show the printed name, date and time, and state the meaning of the signature, such as “reviewed,” “approved” or “verified count.” Signing should require re-entering credentials, not just clicking a button in an open session. Shared logins defeat the whole point and should be technically blocked, not just discouraged by policy.

Protocol-Specific Templates

Every protocol has its own visit schedule, required assessments and documentation quirks. An EHR / EMR that supports protocol-specific templates lets the site build those requirements into the workflow instead of relying on coordinators to remember them.

A good template pre-populates required fields, enforces visit windows and prompts for the accountability entry at the right step. Templates should be versioned so amended protocols don’t rewrite history.

Role-Based Access

Research records carry different sensitivity levels than routine charts, and blinded studies add another layer. Role-based access should control who can see unblinded product information, who can adjust inventory counts, and who can sign as principal investigator.

Practical setups often separate at least four roles: coordinator, pharmacist or product manager, investigator, and monitor. Monitors in particular need read-only access to source documents and the audit trail, ideally through a restricted remote view so they can do much of their review before arriving on site.

Integration with Inventory and Practice Management Software

Research rarely lives in one system. The site’s practice management software handles scheduling and billing, a separate inventory tool may track supplies, and sponsors often run their own electronic data capture platforms.

Integration priorities usually look like this:

• Scheduling: study visits booked in practice management software should carry the protocol ID so the right template opens in the EMR.
• Billing: research-covered services must be separated from billable care to avoid double billing, which is a compliance risk in its own right.
• Inventory: receiving, use and destruction entries should update stock counts in one place, not three.
• Data export: structured exports, not screenshots, for sponsor reporting.

Connected systems mean the coordinator enters data once.

Reporting for Sponsors and Monitors

The payoff for all of this structure is reporting. A research-ready EHR or EMR should produce, 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 producing a monitor’s standard request takes more than a few minutes, the system is not doing its job.

FAQ

Can a standard EHR or EMR handle investigational product tracking?

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

Why should lot numbers be structured fields instead of notes?

Structured fields can be queried, validated and reported on. If a quality issue affects a specific lot, a site can find every related record in minutes instead of searching through free text and scanned files.

What should a lot-specific certificate of analysis include?

At a minimum, the lot number, test date, HPLC purity, identity confirmation method and result, and net content. For many research materials, endotoxin results are also expected. The lot number on the COA should match the label on the product received.

Does 21 CFR Part 11 apply to every research site?

Its scope depends on the type of records and whether they are submitted to FDA. Even where it does not strictly apply, sponsors commonly expect Part 11-style audit trails and e-signatures, so building to that standard is the safer default.

How does practice management software fit into research workflows?

It handles scheduling and billing. Linking study visits to protocol IDs and separating research-covered services from billable care keeps the EHR, the billing record and the sponsor’s data consistent.