Medication history is not an active-medication list
Surescripts presents medication-history, e-prescribing, formulary, benefit, and prior-authorization services as distinct parts of its health-information network. A returned history should remain source evidence until a clinician reconciles patient match, prescriptions, fills, cancellations, reversals, timing, adherence uncertainty, and current intent into an active list.
Editorial figure by Health Interoperability Review. Source context: Surescripts Trusted Health Intelligence Sharing.
Preserve the returned history as source evidence
The direct answer is to store the response without relabeling every row active. Retain the query purpose, requester, patient demographics and matching result, consent and authority context, network or source, request and response identifiers, observation and retrieval times, covered history window, prescriber, pharmacy, medication identifiers, strength and form, directions when present, quantity, days supply, order, fill, refill, cancel, reversal, transfer, claim, and response status.
Label provenance and limits for each event. An order may never have been dispensed; a paid claim may later be reversed; a fill does not prove ingestion; a cancellation can concern a particular prescription rather than the therapy; and an old medication may remain clinically relevant. Missing sources, cash purchases, samples, inpatient administrations, compounds, over-the-counter products, and data latency should stay visible rather than being interpreted as no use.
Create a separate clinical reconciliation record
The active list should record the clinician-reviewed medication concept, intended dose and schedule, route, indication where appropriate, start and stop status, prescribing owner, patient or caregiver report, external-source evidence considered, discrepancies, adherence uncertainty, contraindication or duplication questions, decision, reviewer, time, and follow-up. Keep reported, prescribed, dispensed, claimed, administered, and reconciled states distinct.
When identifiers or directions conflict, preserve candidates and route them for clinical resolution. Do not let a latest-date heuristic silently select the regimen. A medication can be intentionally held, tapered, taken differently, obtained outside the visible network, or associated with the wrong person. High-risk discrepancies require an escalation path appropriate to the care setting and should not be adjudicated by transport or matching logic.
Keep adjacent network services from filling gaps
Formulary, benefit, prior-authorization, e-prescribing, and medication-history responses answer different questions. Coverage or price information does not prove clinical intent; an authorization does not prove a prescription was written or filled; an electronic prescription does not prove dispensing; and a history response does not determine coverage or appropriateness. Link related transactions while preserving their separate purposes, participants, effective times, and decision owners.
Corrections need end-to-end receipts. If patient identity, medication mapping, source event, or clinician status changes, record the original value, new evidence, authorized change, affected users and systems, notification, and acknowledgement. Do not overwrite the history response to make it agree with the active list; preserve both and their reconciliation.
Test an intentionally contradictory history
Use a test patient with similar demographics to another person, duplicate prescriptions, one unfilled order, a reversal, a cash fill outside a primary source, a discontinued medication, a changed dose, an inpatient administration, and a patient report that conflicts with the latest transaction. Reviewers should reproduce the source history, avoid identity leakage, surface gaps, document clinical reconciliation, and preserve corrections without inferring current use from one event.
Surescripts's official site supports the attributed medication-history, e-prescribing, formulary, benefit, prior-authorization, and network positioning. It does not establish patient identity, source completeness, current medication use, adherence, clinical intent, appropriateness, coverage, authorization, dispensing, payment, reconciliation quality, or outcome. Patients and qualified clinicians, pharmacists, health-information, privacy, security, payer, and legal owners retain their responsibilities.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Health Interoperability Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.