ONC puts it plainly: electronic medical records are a digital version of the paper charts in the clinician's office. An EMR contains the medical and treatment history of the patients in one practice, and it mainly supports that practice's diagnosis and treatment work. The weakness ONC points to is that the information in EMRs does not travel easily out of the practice.
EMR vs EHR
ONC notes that the two terms are often used interchangeably, but EHRs are broader. EMRs are usually limited to a single provider or practice. EHRs focus on the total health of the patient, contain information from all the clinicians involved in a patient's care, and are designed to reach beyond the organization that first collected the data.
Because the terms are used loosely, the label on a product is a poor guide to what it does. Ask concrete questions instead: Can it send and receive records from other systems? Is it certified under the ONC program? Does it expose a standard API that outside apps can use?
Why the distinction still matters
A system built as a single-practice record can work well inside the practice and still have the weakness ONC describes: its information does not travel easily when the patient is referred elsewhere. When a buyer says EMR, it is worth asking whether they need a record for one practice or a record that has to move with the patient. The second is a larger project, and the integration work belongs in the plan from the start.
Example
A small behavioral health practice runs a charting tool that holds its own notes and medication lists. When a patient is referred to a hospital, the practice exports a summary by hand. If the tool supported standards-based exchange, the summary could be sent electronically and filed directly into the hospital's record.