Patient Chart Example: A Pharmacy Clinical Record
Pharmacy Practice

Patient Chart Example: A Pharmacy Clinical Record

See a fictional patient chart that connects health history, medications, allergies and a pharmacy visit note, with sources and follow-up visible.

November 18, 2026
6 min read

A patient chart is the health record used to document a person's history and care over time. It can contain medications, allergies, conditions, test results, clinical notes and follow-up. The fictional pharmacy chart below shows how those parts connect: the patient summary carries information between visits, while a dated encounter note records what happened during one consultation.

A chart may be electronic, paper or a combination. In an electronic record, the information often sits in separate tabs or lists rather than one long document. ONC describes an EHR as a longitudinal record containing history, diagnoses, medications, results and other clinical information. The example here is shortened for teaching; it isn't a complete treatment record or a ready-to-use billing template.

A patient chart and a visit note serve different purposes

The chart is the collection. An encounter note is one entry in it. A pharmacist can document today's medication consultation without copying the patient's entire history into the note. The note should contain the relevant context and what the pharmacist learned, assessed and did during that visit. Our pharmacy SOAP-note guide explains one way to organize that entry.

A pharmacy dispensing profile often shows prescription and fill history. A filled prescription doesn't establish how the patient currently takes the medicine, and medicines obtained elsewhere or bought without a prescription may be missing. HL7 distinguishes reported medication use from orders, dispensing and administration. A personal medication record helps the patient keep a medicine list; the clinical chart also contains the encounters and other health information.

Patient chart example: the current summary

This fictional summary shows the chart just after the November 16 consultation described below. Alex Morgan is a teaching name, and TRAINING-01 is a training identifier. In a real chart, the organization would use its approved identifiers and record-matching process; the patient demographics guide covers those fields in detail.

Identity and contact. Alex Morgan; training record TRAINING-01. Contact preference: telephone for this consultation's follow-up. Actual contact details and birth date are omitted from this teaching example.

Health history. Seasonal allergies, reported by the patient at intake on November 16, 2026; reviewed by Jordan Lee, pharmacist, that day.

Medication list. Loratadine: patient reports taking it as needed for seasonal symptoms on November 16, 2026; nonprescription product brought to the visit and checked by Jordan Lee. The patient also reports a multivitamin, with the formulation still unconfirmed. A previous short-course prescription appears separately in historical dispensing records, with current use not established by that entry. An actual medication entry would include the product, strength, dose, route and frequency available from the history and review; those prescribing details are outside this abbreviated example.

Allergy and reaction history. Penicillin: patient reports a childhood rash at the November 16 intake; Jordan Lee records that the exact product and timing aren't known. The entry preserves the reported reaction and uncertainty. It doesn't silently convert the account into either a confirmed allergy or “no known allergies.” HL7's allergy record separates reaction information from verification status; a qualified clinician determines the appropriate classification.

Documents and prior care. An outside visit summary is filed with its originating practice and visit date. Its upload date is shown separately. The presence of that attachment doesn't mean every item has been reconciled into the pharmacy's current lists.

Open follow-up. Confirm the reported multivitamin formulation when the patient brings its package on November 18. Assigned to Jordan Lee; linked to the November 16 encounter.

The encounter entry adds what happened today

For the same fictional patient, a consultation entry could read:

November 16, 2026, 10:00 a.m. | Community pharmacy consultation | Jordan Lee, pharmacist. Reason for visit: patient wants the pharmacy's clinical medication list to include a nonprescription product used for seasonal symptoms.

Information reviewed. Patient brought the loratadine package and described current use. Pharmacist reviewed the existing medication list and available dispensing history. Patient also reported taking a multivitamin but didn't have the package or know the exact formulation. No vital signs or laboratory results were collected for this example.

Assessment and action. The clinical medication list was missing the reported nonprescription product. Pharmacist documented the loratadine product and reported use from the package review and patient discussion. A separate entry records the reported multivitamin with formulation unconfirmed.

Agreed follow-up. Patient will bring the multivitamin package to the planned follow-up on November 18. Jordan Lee will confirm its identity and update the entry. The follow-up is linked to this encounter so another pharmacist can see what remains unresolved.

The summary now shows the additional medication information, while the encounter preserves how it was obtained. A new reader can distinguish a package the pharmacist checked from a product whose identity is still unknown. “Medication list complete” would lose that distinction.

A later update preserves the earlier uncertainty

On November 18 in this fictional example, the patient brings the multivitamin package. Jordan records the product details, the source and the update date, then closes the related follow-up. The November 16 note still shows what was known at that visit; the later entry supplies the answer.

When a signed note itself contains an error, use the record system's correction or amendment process. Keep the original event and the later correction distinguishable, with the author and timing clear. Updating today's medication list and correcting a past note are different tasks; the software should make both understandable to the next reader.

Other sections depend on the care provided

A fuller chart can include medical and surgical history, family and social history, immunizations, measurements, laboratory reports, referrals, care plans and patient communications. Add the information relevant to the service and preserve its source and date. A result measured elsewhere last month should remain recognizable as that result, even if staff upload it today.

Administrative information such as coverage, consent records or billing documents may sit alongside the clinical record. Hospital charts may also contain admission assessments, nursing observations and discharge summaries. A pharmacy consultation example doesn't supply all of those records, and a blank field should not become an invented normal finding.

Can a patient see or correct their chart?

For organizations covered by the HIPAA Privacy Rule, patients generally have rights to inspect and obtain copies of their medical and billing records, subject to exceptions. HHS explains how to request records and amendments; a patient can ask the covered provider or plan holding the record to address inaccurate information, and can submit a statement of disagreement if an amendment request is denied.

For the fictional chart above, “I no longer take that product” is new information to assess and date. “That product belonged to someone else and was entered in my chart by mistake” raises a record-correction and identity concern. Preserving that difference helps the pharmacy update the current list and address the historical error through the appropriate process.

Patient Operations

Keep patient work connected from outreach to follow-up

Keep scheduling, messaging, notes, and care coordination connected to the same patient record.