A patient comes in for a routine visit and opens their phone before the clinician has finished reviewing the chart. There’s a PDF from an imaging center, a cholesterol panel from another physician, six months of heart-rate data from a watch, and a sleep report from an app they started using in January.
None of it is technically missing. The patient has the files. The problem is that having information and having usable clinical information are two different things.
This is becoming a normal part of outpatient care. Patients are collecting more health data outside the practice, sometimes through another provider and sometimes entirely on their own. The EHR remains the main clinical record, but it’s increasingly being asked to make sense of information that began somewhere else.
The chart is only one version of the patient
For years, most practices could assume that the important clinical information would arrive through familiar channels: a referral note, a lab result, a hospital discharge summary, a pharmacy message. Those channels haven’t disappeared. They’ve been joined by many more.
A patient can now spend a day undergoing imaging, cardiovascular testing, metabolic measurements and fitness assessments without those results originating in the office that manages their routine care. Some advanced preventive health assessments in New York City, for example, combine MRI and CT imaging with cardiovascular screening, DEXA scans, metabolic testing and VO2 max assessment. When that patient later sees their primary-care physician, the useful question isn’t simply whether the results can be added to the record. Someone has to decide what deserves attention.
That distinction matters because different pieces of outside data carry very different weight.
A radiologist’s report identifying a pulmonary nodule is not equivalent to a fitness tracker showing a lower-than-usual recovery score. A documented medication change from another physician is different from a patient bringing in a spreadsheet of home glucose readings. Both may matter, but they shouldn’t automatically enter the workflow in the same way.
Good records preserve context. Where did the information come from? When was it collected? Was the test ordered for a particular clinical reason? Has another clinician already interpreted it? Is there a follow-up recommendation attached?
Without those details, a chart can become fuller without becoming clearer.
Getting the information into the practice is only half the job
Patients have broad rights to access much of the health information maintained about them by covered healthcare providers and health plans. The Department of Health and Human Services notes that this can include laboratory reports, medical images, billing records and other information used to make healthcare decisions. Easier access means patients are more likely to arrive with records from multiple sources rather than waiting for one office to request them from another.
Practices need reliable ways for patients to view and exchange information. A patient portal can give them access to parts of their health record and a more controlled channel for communicating with the practice instead of relying on paper notes, personal email accounts or memory at the next appointment. The harder question begins once new information reaches the clinical team.
Consider a common situation. A practice receives a 14-page laboratory report through its patient-facing workflow on Tuesday evening. The first 12 pages contain routine results. Page 13 includes an abnormal value the patient assumes is urgent.
Who reviews it?
If the answer is “the physician when they happen to notice it,” the practice doesn’t really have an outside-data workflow. It has an inbox.
Someone needs to determine whether a submission belongs in the permanent record, requires clinical review, should be routed to a nurse first, or can wait until the next appointment. Practices also need to be clear with patients about what sending information does and does not mean. Providing a report electronically shouldn’t create the impression that every document is being monitored continuously for emergencies.
The same discipline applies to repetitive data. One blood-pressure reading may belong in a note. Three months of home measurements may be more useful as a trend. Hundreds of smartwatch data points probably shouldn’t be copied individually into the chart at all.
The goal is not maximum collection. It’s enough structure that the next clinician can understand what happened without reconstructing the patient’s history from attachments.
Interoperability helps, but it doesn’t make judgment automatic
Healthcare has spent years trying to reduce the friction involved in moving records between systems, and there has been real progress. HL7 FHIR, for example, was designed to make clinical and administrative health information easier to exchange electronically; the Office of the National Coordinator for Health IT describes FHIR as a resource-based standard for exchanging health data through modern APIs. That gives healthcare organizations a more consistent technical language for moving information.
For practices, healthcare interoperability can reduce some of the manual work involved in receiving information from laboratories, hospitals, pharmacies and other systems. Data that arrives in a structured field is generally easier to reconcile than a scanned document buried in an attachment folder.
Still, interoperability answers a technical question: can System A exchange information with System B?
It does not decide whether an imported diagnosis is current, whether two medication lists conflict, whether an outside test needs follow-up, or whether a result should change today’s treatment plan.
Those decisions stay clinical.
This becomes obvious when records disagree. Imagine a cardiology record lists a patient as taking 20 mg of a medication, while the primary-care chart says 10 mg and the patient says they stopped it entirely two weeks ago. Successfully importing all three pieces of information hasn’t solved anything. It has simply put the disagreement in one place.
The useful workflow is reconciliation: identify the conflict, determine the current state, document the source and update the record. Automating the transfer can make that work faster, but it can’t eliminate the need for it.
Decide what changes care
Patient-generated information deserves the same kind of discrimination.
The volume reaching clinical systems is no longer marginal. According to a recent ONC analysis of hospital API and data-sharing practices, roughly two-thirds of surveyed U.S. hospitals in 2024 enabled some form of patient-generated health data to be submitted to an EHR. That doesn’t mean every reading or file deserves equal clinical attention.
Practices don’t need a universal rule saying yes or no to all of it. They need a threshold.
Start with the decision the data could affect.
If a hypertensive patient brings two weeks of properly taken home blood-pressure readings, those numbers may influence medication management. If someone with diabetes supplies glucose readings after a medication adjustment, the pattern could matter much more than one office measurement. A smartwatch alert that prompted a patient to seek evaluation may be relevant history even if the device itself never becomes part of the formal diagnostic process.
The harder cases are large amounts of information with no obvious clinical question attached.
A patient may arrive with genomic results, nutrition dashboards, sleep scores, body-composition reports and years of wearable data because they assume the physician needs all of it. Rejecting everything risks overlooking useful context. Importing everything creates noise that somebody else has to sort through later.
A well-maintained electronic medical record should help preserve the pieces clinicians actually need for documentation, orders, medications and ongoing care. Extra information can remain available without every number becoming a first-class chart element.
One practical approach is to separate outside data into three buckets.
First, information that could change diagnosis, medication, follow-up or immediate management deserves clinical review. Second, information that improves context but doesn’t require action can be summarized in the record. Third, data that adds little to the current clinical question can remain available without being copied into every subsequent note.
That sounds simple until five clinicians are making those decisions differently. The real work is agreeing on the threshold as a practice.
A cardiology group may want structured home blood-pressure and heart-rate readings. A behavioral-health practice may care more about symptom scores completed between visits. An orthopedic clinic may need outside imaging and therapy notes but have little use for continuous consumer fitness data.
The record should reflect the work of the practice, not every piece of health information a patient has ever generated.
Wrap-up takeaway
Patients are going to keep arriving with more information than their EHR started with, and much of it will be genuinely useful. The challenge is keeping important outside data from becoming another pile of documents that nobody has clearly agreed to own. A good workflow makes the source visible, gives incoming information a reviewer, reconciles conflicts and keeps clinically meaningful details easy to find later. It also leaves room to say that some data can be available without becoming part of every clinical decision. Practices don’t need to solve the entire interoperability problem to improve this. Pick one common source of outside data your team receives today and decide exactly who reviews it, where it belongs and what should trigger follow-up.
