4.2 Acquiring Patient Data from External Sources

A patient's history rarely lives in one system. Test plan task 1.E — "acquire patient data from external sources (e.g., diagnostic laboratories, ancillary facilities, other health care providers, other EHR systems)" — makes retrieving and correctly filing outside information a core duty. Knowledge statement 1.K4 lists the sources; the skill being tested is knowing how the data arrives and what must be checked before it becomes part of the chart.

Where External Data Comes From

The Four Inbound Channels

1. Standards-based interfaces. An HL7 v2 result message or a FHIR API response lands as discrete data that populates a structured field and can be trended, alerted on, and reported. This is the highest-value channel and the one covered in Section 10.1.
2. Document exchange. A C-CDA summary or a Direct secure message delivers a structured document. Portions can be reconciled discretely (problems, medications, allergies, immunizations); the rest is retained as a viewable document.
3. Fax and image capture. Inbound faxes routed into the document management queue arrive as images. They are legible to people, invisible to queries, and must be indexed manually. Optical character recognition improves searchability but does not create discrete data.
4. Manual entry and scanning. Paper records the patient brings, outside forms, and completed questionnaires are scanned and indexed using the workflow in Section 3.1.

Verification Before Filing

The most consequential step is the one that happens before the document reaches the chart. Every inbound item is checked for:

• Patient match. At least two identifiers must agree — legal name and date of birth at minimum, ideally with a third such as address or the outside MRN. A near match is not a match. When identity cannot be confirmed, the item is held in an unmatched queue and researched, never filed on a best guess.
• Correct date. The date of service on the document, not the date it arrived, drives clinical interpretation and any timely-filing calculation.
• Source and authenticity. The sending facility, ordering provider, and (for results) the performing laboratory's CLIA identity should be present.
• Completeness. Missing pages, truncated result sets, and documents that reference attachments not received are returned to the sender rather than filed as complete.
• Legibility. An unreadable scan is rescanned; a blurry image in a legal record is a defect, not a nuisance.

A misfiled external document is an overlay error — Patient B's data inside Patient A's chart — and it carries the same clinical and privacy consequences described in Section 2.2.

Reconciliation Into the Chart

Receiving data is not the same as adopting it. Discrete inbound content is reconciled, meaning a qualified user compares the incoming list against the local list and decides what to accept:

Clinical acceptance decisions belong to clinicians. The EHR specialist's role is to make the comparison visible, remove obvious duplicates according to policy, and route anything ambiguous. Immunization reconciliation is often the exception — many organizations allow trained staff to accept registry doses because the registry is the authoritative source.

Notification and Closing the Loop

External data that arrives but is never seen is functionally lost. After verification and filing:

• Route results and documents to the ordering or responsible provider's inbox, not just into the chart.
• Flag abnormal or critical values so they surface above routine traffic; the critical-value protocol in Section 7.2 applies to outside laboratories as well.
• Update the tracking queue so an order that was pending is now closed, which is how open-loop diagnostic failures are prevented.
• Document the receipt with source, date received, and who filed it, so the audit trail explains how the record entered the chart.