A CSN, or Contact Serial Number, is a unique identifier that an electronic health record system assigns to every individual patient encounter. Each time you check in for an office visit, arrive at an emergency department, start a telehealth call, or have any other distinct interaction with a healthcare facility, the system generates a fresh CSN for that contact. In the widely used Epic EHR platform, the CSN is the primary way the system distinguishes one visit from another, even when the same patient has dozens or hundreds of encounters on file. The concept sounds simple, but the way CSNs interact with other identifiers, billing codes, and clinical workflows makes them one of the most practically important data points in modern healthcare IT.
How a CSN Gets Created
In Epic, which is the dominant EHR system in U.S. hospitals and large health systems, a unique CSN is generated the moment a new appointment is scheduled for an order. That first CSN also becomes what is called the Appointment Serial Number, or ASN, which then serves as the reference number linking all subsequent changes to that appointment, whether it gets rescheduled, its status changes, or additional documentation gets attached.1PubMed Central. Electronic Health Record Algorithm Development for Research Subject Recruitment Using Colonoscopy Appointment Scheduling If a patient cancels and rebooks, the new booking gets its own CSN, but the ASN from the original order ties the chain together so nothing gets lost in the shuffle.
Other EHR platforms use similar concepts under different names. Cerner (now Oracle Health) uses an “encounter ID,” and many smaller systems have their own version of a per-visit unique key. The underlying idea is universal across platforms: every contact between a patient and the healthcare system needs its own immutable reference number so that the notes, lab results, prescriptions, imaging orders, and billing charges associated with that specific visit stay bundled together and don’t bleed into records from a different visit.
CSN vs. MRN and Other Identifiers
One of the most common points of confusion, especially for new clinical staff and patients who peek at their own records, is the difference between a CSN and a Medical Record Number (MRN). The MRN is assigned to you as a person. It stays the same across every visit you ever have at a given health system. Think of the MRN as your permanent file folder and each CSN as a tab within that folder representing a single visit.
A third identifier worth knowing is the patient account number, sometimes called the Hospital Account Number (HAR) in Epic. This is a billing-level identifier. A single hospital stay might have one MRN, one HAR for the billing episode, and multiple CSNs if the patient had separate contacts within that stay, such as an initial emergency department encounter followed by an inpatient admission. The HAR groups those CSNs for billing purposes so the insurance claim reflects the full episode of care rather than fragmenting it into disconnected charges.
In practical terms:
- MRN: One per patient per health system, stays the same for life at that system.
- CSN: One per encounter, generated fresh every time.
- HAR: One per billing account, which may span multiple encounters.
Getting these confused can create real headaches. If a coder attaches a charge to the wrong CSN, the documentation for that charge may not match, which can trigger a claim denial. If a nurse pulls up the wrong CSN when reviewing a patient’s history, they might be looking at lab results from last Tuesday’s visit rather than today’s.
Why Every Encounter Needs Its Own Number
Patients with chronic conditions can accumulate hundreds of encounters over a few years. A study of hospital encounter data found that physicians in emergency settings pulled up reports from previous encounters more than half the time, while inpatient doctors referenced prior encounter data about a fifth of the time.2PubMed Central. Determinants of frequency and longevity of hospital encounters’ data use Without a reliable way to distinguish which visit produced which report, that kind of cross-referencing would be chaotic. The CSN is what makes it possible for a doctor to say, “I want the CBC from the March 12 ED visit, not the one from the March 15 follow-up,” and have the system retrieve exactly the right result.
The same study found that the practical lifespan of information varies dramatically by care setting: data from emergency encounters had a median useful life of about a day and a half, inpatient data lasted closer to five days, and outpatient data stayed relevant for over a month.2PubMed Central. Determinants of frequency and longevity of hospital encounters’ data use That difference underscores why encounters need clean separation. In a fast-moving emergency department, clinicians constantly cycle through recent encounter records for context. If those records were not clearly bucketed by CSN, finding the right data point in a patient with frequent ED visits would be like searching an unsorted filing cabinet during a crisis.
CSNs in Telehealth and Virtual Care
The explosion of telehealth during and after the COVID-19 pandemic raised new questions about how CSNs work when a visit happens over a screen or phone rather than in a clinic room. The short answer is that virtual visits generate CSNs just like in-person ones. A phone call with your doctor, a video appointment with a specialist, and a chat-based consultation each produce their own CSN in the EHR.
Where things get tricky is in classifying what kind of encounter a CSN represents. Research comparing scheduling-based and billing-based methods for identifying whether a visit was virtual found that the two approaches agreed about 96.5% of the time overall, but agreement dropped to roughly 89% when looking specifically at virtual care visits.3PubMed Central. Identifying virtual care modality in electronic health record data Most of the disagreement came from encounters that were scheduled as audio-only phone calls but billed as video visits, or vice versa. The same research found that audio-only visits outnumbered video visits by roughly two to one when looking at cases where both classification methods agreed on the modality.3PubMed Central. Identifying virtual care modality in electronic health record data
This matters for CSN-level analysis because the metadata attached to a CSN, including encounter type, visit modality, and department, is only as reliable as the workflows that create it. If a clinic schedules a phone call but the provider switches to video mid-encounter and the billing code reflects the video component, the CSN’s scheduling metadata and its billing metadata tell different stories. For health systems trying to measure how much care is delivered virtually, that kind of mismatch at the CSN level can skew the numbers.
How Staff Actually Use CSNs Day to Day
For front-desk staff, the CSN typically appears the moment they check a patient in. It prints on wristbands in hospitals, shows up on the header of clinical notes, and gets embedded in barcode labels for lab specimens. Scanning a patient’s wristband pulls up that specific encounter’s information, reducing the risk of mixing up patients or visits.
For clinicians, the CSN is mostly invisible. Doctors and nurses navigate by patient name, date, and department rather than memorizing serial numbers. But when something goes wrong, like a lab result filed to the wrong encounter or a medication order that doesn’t show up where expected, the CSN is the first thing an IT support analyst asks for. It is the skeleton key that unlocks the exact encounter record, cutting through ambiguity in a way that a patient name and approximate date cannot.
For billing and coding teams, the CSN is the anchor for charge capture. Every procedure, supply, and professional fee gets posted against a CSN. When a charge appears on the wrong CSN, it can mean a claim goes out without the supporting documentation, since the clinical note lives on a different encounter. Revenue cycle teams spend a nontrivial amount of time reconciling charges to the correct CSN, especially in complex cases like surgeries that span multiple days or patients who transfer between units.
For researchers and data analysts, CSNs are the fundamental unit of analysis when studying visit-level patterns. If you want to know the average length of an emergency department visit, the readmission rate within 30 days, or how often a particular lab test gets ordered at a primary care appointment, you are counting and filtering CSNs. The MRN tells you about the patient; the CSN tells you about the visit.
Common Problems With CSN-Level Data
One of the most frequent issues in healthcare data work is the duplicate encounter. This happens when a patient gets checked in twice for the same visit, generating two CSNs when there should be one. It can occur when a patient arrives at the ED, gets registered, leaves the waiting room briefly, and gets re-registered by a different clerk who doesn’t realize the first encounter exists. The result is two parallel encounter records for a single clinical event, which fragments the documentation and can cause downstream billing errors.
The opposite problem also occurs: encounters that should be separate get merged into one CSN. A patient who comes in for a morning appointment and then returns in the afternoon for an unrelated issue might have both visits lumped under the same CSN if the check-in process doesn’t clearly distinguish them. This creates an artificially long encounter with a confusing mix of clinical notes, and it can lead to incorrect billing because two distinct services appear as one bundled visit.
Another headache arises when patients transfer between care settings within the same facility. An ED visit that converts to a hospital admission might generate a new CSN for the inpatient portion, or it might continue under the original ED CSN depending on how the facility’s EHR is configured. Hospitals set up these workflows differently, and the choice has real consequences for how encounter data is reported to payers, quality registries, and public health agencies. A facility that splits ED-to-inpatient transitions into two CSNs will report a different average ED length of stay than one that keeps the encounter continuous, even if the actual patient experience is identical.
What Patients See
If you use a patient portal like MyChart, you may never see the CSN itself. Patient-facing systems typically display visits by date, provider name, and department rather than by serial number. But behind every visit summary, every test result notification, and every billing statement in your portal, there is a CSN tying that information to a specific encounter.
Occasionally, patients do encounter CSN-related artifacts. You might receive two separate after-visit summaries for what felt like a single appointment, which usually means two CSNs were generated, perhaps because you saw both a nurse practitioner and a physician who bill separately, or because a procedural component of your visit was tracked as its own encounter. You might also notice that a lab result appears under a different visit date than when you remember having the blood drawn, which can happen when the specimen is processed under an encounter CSN that was created at a different time from the actual collection.
When contacting a provider’s office about a billing discrepancy, having the visit date and, if visible, any encounter or confirmation number from your records can help the billing team locate the right CSN quickly. The faster they find the correct encounter, the faster they can identify whether a charge was posted correctly or whether documentation supports the service that was billed.
CSNs in Research and Population Health
Large-scale clinical research depends heavily on encounter-level data, and CSNs are the hooks that make such research possible. When researchers want to study, for example, how often patients who are scheduled for a colonoscopy actually follow through, they track the CSN generated at the time the appointment is booked and then look for a corresponding procedure note, pathology result, or completed encounter status tied to that same CSN chain.1PubMed Central. Electronic Health Record Algorithm Development for Research Subject Recruitment Using Colonoscopy Appointment Scheduling Without encounter-level identifiers, this kind of appointment-to-outcome tracking would require manual chart review, which is impractical at scale.
Population health initiatives use CSN-level data to identify care gaps. If a health system wants to flag diabetic patients who have not had a retinal exam in the past year, the query looks for patients with qualifying diagnosis codes whose most recent ophthalmology CSN is more than 12 months old. Quality metrics reported to the Centers for Medicare and Medicaid Services often hinge on whether a specific service was documented in an encounter that meets the measure’s criteria, and meeting those criteria comes down to what is recorded against a given CSN.
The granularity of CSN data also introduces privacy considerations. Because each encounter is a discrete, identifiable record, de-identification for research purposes requires careful handling. Simply stripping the patient’s name and MRN is not enough if the CSN can be cross-referenced with appointment schedules, billing records, or other systems where the CSN appears alongside identifying information. Health systems that share data for research typically replace CSNs with study-specific pseudonymous identifiers so that researchers can still link encounters for the same patient without being able to trace the record back to an individual.
When CSN Practices Differ Across Systems
There is no national standard that dictates exactly how a CSN must be formatted, when it must be generated, or what constitutes a single encounter. The Health Level Seven (HL7) messaging standard and the FHIR specification define the concept of an encounter resource, but the implementation details, including what triggers a new encounter, how encounters nest within each other, and what metadata gets attached, are left to the EHR vendor and the individual health system’s configuration.
This means that a CSN from one Epic installation is not interchangeable with a CSN from another. If you visit two hospitals that both use Epic, each will assign you its own MRN and its own CSNs. Even within health systems that have merged or affiliated, legacy encounter numbering schemes can persist for years before being harmonized. Analysts working across multiple facilities within a single health system often find that encounter-level data doesn’t stitch together cleanly without additional mapping tables that translate between different CSN schemes.
For patients, the practical consequence is that your records at one hospital are not automatically linked to your records at another, regardless of whether both run Epic. Interoperability initiatives like CommonWell and Carequality aim to connect records across systems, but they work through patient-matching algorithms that rely on demographic data, not by sharing CSNs across organizational boundaries. The CSN remains a purely local identifier, powerful within its own system and invisible outside it.