Meeting all 10 ACOEM OEHR requirements

The American College of Occupational and Environmental Medicine (ACOEM) has long argued a point that sounds obvious and is constantly ignored: occupational and environmental health records have requirements a general clinical EHR was never designed to meet. ACOEM's guidance on the Occupational and Environmental Health Record (OEHR) is the clearest articulation of what "built for occupational medicine" actually means. Its guidance and position statements are published by ACOEM directly.

You can treat that guidance as a buyer's checklist. Below is a practical reading of the capabilities a system needs to satisfy it — grouped so you can score any platform against them.

The capabilities that separate occ-med from general EHR

An occupational-health record has to do things a primary-care chart never does. Hold the line on all of these:

• Manage employer relationships and employee populations, not just individual patients.
• Drive recurring surveillance protocols by exposure group and schedule.
• Capture work-relatedness, restrictions and work-status determinations as first-class data.
• Separate occupational from personal health information with appropriate access controls.
• Support regulatory reporting — OSHA recordkeeping, agency-specific exams — natively.
• Preserve long-retention records and exposure histories as required by 29 CFR 1910.1020.
• Interoperate with HR, labs, devices and external providers without re-keying.
• Maintain a complete, defensible audit trail of who saw and changed what.

Why a general EHR struggles

Most EHRs are organized around a patient and an episode of care. Occupational health is organized around an employer, an exposure and an obligation that recurs for years. Bolt the second onto the first and you get workarounds: free-text fields standing in for structured restrictions, side spreadsheets tracking who is due, and access boundaries that depend on people behaving rather than the system enforcing.

The access-and-separation requirement is where this gets serious. Under 29 CFR 1910.1020 employees and their designated representatives have rights to medical and exposure records — and the employer's access to personal health information is limited. A system that can't enforce that boundary cleanly isn't merely inconvenient; it's a liability.

How to use the checklist

Score honestly, native versus workaround. For each capability ask: does the platform do this as designed, or does your team do it with a spreadsheet beside the platform? Every "workaround" is a future audit finding and a recurring tax on your staff. A system that satisfies the OEHR framework natively is the difference between running occupational health and merely surviving it.

What is the ACOEM OEHR framework?

It is ACOEM's guidance defining what an Occupational and Environmental Health Record should do — the capabilities that distinguish a purpose-built occupational-health system from a general clinical EHR. ACOEM publishes its guidance and position statements directly.

Why can't a standard EHR meet occupational-health requirements?

General EHRs are built around a patient and an episode of care. Occupational health revolves around employers, exposure groups, recurring surveillance and long-retention records with strict access separation under 29 CFR 1910.1020 — needs a standard EHR meets only with workarounds.