EHR Integration: Read, Write and Sync Explained
Pharmacy Practice

EHR Integration: Read, Write and Sync Explained

Understand EHR integration, compare read and write capabilities, and test how a pharmacy connection handles corrected records and failed transfers.

November 16, 2026
6 min read

EHR integration connects an electronic health record with another system so they can exchange information or support a shared task. A connection might retrieve a patient's lab results, send a consultation note or update demographic fields. The useful question is which information moves, in which direction, and what the receiving system does with it.

For a pharmacy providing clinical services alongside its dispensing system, those details determine whether staff can use the information during a visit. Here, the pharmacy record means its clinical EHR; a dispensing-system patient profile is a separate possible destination. An integration that opens an outside report can be useful even if it doesn't populate the pharmacy's lab fields. A connection that reads records from a physician's EHR may need a separate capability and permission to send the pharmacist's note back.

Read, write and synchronize mean different things

Read access retrieves information. Write access creates or changes information in the receiving system. Synchronization keeps selected information aligned as it changes, according to the connection's rules and timing. A one-time transfer of historical records is migration; an ongoing interface needs to handle later changes too. Our EHR implementation guide covers the broader launch and migration project.

One-way integration moves information from a source to a destination. Two-way integration supports movement in both directions, but the supported information can differ in each direction. A pharmacy might receive lab results and return visit notes without being able to edit the outside practice's lab record.

Ask the vendors to describe the actual exchange in a sentence: “This connection retrieves these lab results from this practice and places them in this section of the pharmacy record.” Add the update timing and whether staff must accept the information. That description is more useful for evaluating the purchase than a list of connected product names.

APIs, FHIR, HL7 messages and documents

An application programming interface, or API, lets one application request information or an action from another. FHIR, short for Fast Healthcare Interoperability Resources, is an HL7 standard for exchanging healthcare information. It defines reusable data structures, called resources, for items such as patients and observations. FHIR can support APIs as well as other exchange methods.

“Supports FHIR” needs a more specific answer before purchase. The FHIR R4 API specification separates reading, searching, creating and updating records. Servers select the resources and interactions they support. Ask your technical contact to compare the proposed use with the deployed system's CapabilityStatement, which describes its supported behavior, and confirm the permissions available to your connection. Reading a resource doesn't imply permission or support for updating it.

HL7 version 2 uses messages to communicate events and information, such as lab results. It isn't simply another name for FHIR. HL7's comparison explains that implementations can place and represent information differently, so the vendors still need to agree on field mappings.

Document exchange moves a clinical document, such as a visit summary. Some documents contain structured information that compatible software can import; a scanned attachment may only be viewable. The CCD guide explains clinical summaries and reconciliation. If the pharmacy needs a lab value in a trend chart, ask to see that result in the chart, rather than only seeing the report arrive.

A direct connection links the participating systems. An interface engine or integration service can sit between them to route or transform information. A health information exchange can provide another route to outside records; the HIE guide covers participation and access. In each arrangement, confirm which organizations and data are included in the proposed configuration.

A corrected lab result tests the connection

Consider a fictional pharmacy preparing for a medication-review visit. Its clinical system retrieves a laboratory result from an outside practice. Later, the laboratory corrects that result in the source record. The pharmacy needs to know whether its displayed copy changes, whether the original remains in the history and whether anyone is alerted to review the correction.

A connection can handle the first import correctly and still leave the pharmacy with the earlier value. It might retrieve only newly created results, refresh on demand or require a scheduled update. These are different designs, so ask the vendor to demonstrate the configured behavior with synthetic data.

In that demonstration, first retrieve the original result, then correct it in the source and trigger the supported refresh. Compare the destination's value, units, clinical date and status with the corrected source. Keep the collection or observation date distinguishable from the pharmacy’s own last-received or last-refreshed time. The FHIR Observation definition distinguishes clinical timing, issued time and result status; the interface must preserve the meaning of the fields it uses.

Have the vendors show which result remains current, how a superseded result is identified or retained, and what the pharmacist sees. If a correction appears as an unrelated result with no clear current value, resolve that behavior before relying on it for care. Also ask them to demonstrate how the source patient is linked to the destination chart. If the records may belong to different patients, stop automatic filing and use the pharmacy's approved identity-review process. The pharmacist resolves any clinical discrepancy using the verified source and the responsible clinician when needed; software support resolves the transfer or mapping problem.

What happens when the connection stops?

Ask where staff see the last successful exchange and any records awaiting attention. An integration service’s “successful” label may describe a completed request, while an individual item has been rejected or saved somewhere unexpected. Its meaning depends on that service and the kind of request. Read the documented status and accompanying detail, then check the intended record. HL7's safety guidance calls attention to error handling, patient links, record lifecycle and dates.

Before replaying a failed transfer, have support confirm whether the destination already accepted it and how retries avoid duplicate records. For a specific unresolved incident, retain the transfer reference and the affected time range in the approved support process. Agree who monitors failures and how the pharmacy obtains needed information during an outage.

Access also needs maintenance. Confirm who can authorize the connection, what it can read or change, and how access is removed. FHIR's security guidance treats authentication, authorization, secure transport and audit as implementation responsibilities. A FHIR interface alone doesn't establish that the pharmacy's privacy and security requirements have been met.

What should an integration quote include?

Compare quotes for the same scope: source and destination systems, locations, data types, direction, refresh timing and supported corrections. Ask which party configures the mapping and patient matching, which party tests it, and who handles changes when either system upgrades.

Include setup, interface or API access, ongoing service, support and any usage charges the vendors require. Ask for a timeline tied to access approval, configuration and testing of your specific exchange. Have both vendors agree where the corrected information should appear and who will fix a mismatch before accepting that part of the connection.

Automation

Connect incoming data to the work that follows

Use dispensing, health plan, and CSV data to trigger the work that happens beyond the prescription.