Skip to main content
Article 02 · The Patient

How You Become a Data Record

You think you walk into a hospital as a person. The building disagrees. Here is what actually happens to you, in the systems, from the front desk to the parking lot.

The hospital does not see a person. It sees a record, then a record of that record, then a few dozen smaller records hanging off both. None of that is sinister. It is just what it takes to keep you straight from the next person who shares your name and your birth month. But almost nobody explains it to the person it is happening to. So here it is, in plain language, with the industry term sitting right next to it.

01
Register
The system finds you or creates you.
02
Admit
A visit record opens.
03
Care happens
Orders, results, notes pile up.
04
Transfer
Every move fires a message.
05
Discharge
The visit closes. You do not.
06
Code & bill
The visit becomes money.
07
Share & store
Copies leave the building.
Seven steps. The same you the whole way through. The rest of this article walks each one and shows what it does to your record.

Registration: the record gets born

You give your name, your birth date, your address. The plain version is the stuff you hand over at the front deskdemographics. Simple enough.

Here is the part nobody tells you. The system's first job is NOT to make you a record. It is to find the one you already have. It searches the master list of every patient the organization has ever touched, looking for a you-shaped match. That master list is the index of everyoneMPI, the Master Patient Index. The search itself, you against your existing record, is linking you to the right filepatient matching.

If it finds you, it attaches today's visit to your existing ID. If it does not, it mints a new one. That ID is your patient numberMRN, the Medical Record Number. It is the closest thing you have to a permanent identity in there. You keep it for life, across every clinic, every floor, every year. Everything else in this article hangs off it.

Patient lookup · how a clerk finds you
Patient Lookup Generic EMR
Search by who they are
Last name
Rivera
First name
Maria
Date of birth
05 / 14 / 1979
Legal sex
F
SSN · last 4
••••• 6841
Phone
(•••) ••• ••••
Search by identifier
MRN
not entered
Account number
not entered
Two ways in: who you are, or what number you carry. Search
A generic version of the lookup behind every front desk. Type a few of these and the system goes hunting for a match. Get one keystroke wrong here, a transposed birth date, a maiden name, a plain typo, and this is the exact moment a duplicate record is born.

HIPAA starts at the front desk

People think HIPAA is about their diagnoses. It starts earlier than that. The second a clerk types your name into that lookup and it lands next to the fact that you are a patient here, you have created Protected Health Information. The registration data is not the boring part of your record. Under the law, it is the regulated part.

Here is what actually attaches to those front-desk fields.

PHI
It is Protected Health Information
Your name and birth date are not sensitive on their own. Tied to the fact that you are a patient, they become PHI. The demographics carry the same legal protection as the chart.
18 IDs
Most of those fields are named in the rule
HIPAA enumerates eighteen kinds of identifier that make health data traceable to a person. Registration collects a stack of them in one screen: name, birth date, address, phone, SSN, MRN, account number. The lookup panel above is close to that list with a Search button on it.
MIN NEC
Minimum necessary
A registration clerk needs your demographics to find you and check you in. They do not need your diagnosis history. HIPAA's minimum necessary standard says access stops where the job stops.
TPO
Treatment, payment, operations
You do not sign a release every time your registration data moves to the lab or to billing. The Privacy Rule already permits it for treatment, payment, and healthcare operations. Registration is all three at once.
NPP
The one form you actually touched
The Notice of Privacy Practices, the page you acknowledged at the desk, is a HIPAA requirement. It is the only part of any of this that most patients ever see, and most people sign it without reading it.

None of that is bureaucracy for its own sake. It is the law recognizing that knowing WHO you are, in a medical building, is already sensitive. That happens before anyone writes down WHAT is wrong with you.

One you. Many visits.

Your MRN is permanent. Your visit is not. Every separate interaction with the system gets its own record. The plain word is a visit. The system word is this specific visitencounter. The ER trip last spring, the follow-up two weeks later, the lab draw this morning: one MRN, three encounters.

Running right alongside the clinical side is the money side. Each visit also opens a billing record, the tab for your careaccount. One person. One MRN. A string of encounters. A stack of accounts. You are already not one thing in there, and you have not even seen a doctor yet.

The shape of you in the database
YOU one human being MRN your permanent patient number ENCOUNTER ER visit last spring ENCOUNTER follow-up two weeks later ENCOUNTER lab draw this morning orders results notes · vitals + account orders results notes · vitals + account orders results notes · vitals + account
One human, one MRN, three encounters, and a cluster of timestamped data points under each. Every box below the MRN is a thing the system can query, report, and bill on its own. You are the top box. The system mostly works in the bottom ones.

Everything you do becomes a row

Step inside a single encounter and watch it fill up. The doctor decides something, and that decision becomes an instruction the system can trackorder: a medication, a lab, an image, a diet. The lab runs and sends back your numbersresults. The nurse charts your vitals. Notes get written. Medications get given and recorded.

None of it lands as a story. Each piece lands as a discrete, timestamped, structured row with your MRN and that encounter's ID stamped on it. That is the trade. Structure is what lets the system alert, trend, and bill. It is also why the human narrative, the WHY behind the visit, is the one thing the record holds worst.

ADT: the building's heartbeat

Every time you are admitted, moved between units, or sent home, the system fires off a small announcement. The plain version is "the hospital always knows where you are." The industry version is the admit, discharge, and transfer feedADT.

ADT is the heartbeat of the place. It is how the lab knows you exist before your blood arrives, how the pharmacy knows which floor to send the medication to, how billing knows the clock started. You change beds; a message moves. You go home; a message moves. Most of the systems that touch your care never see YOU at all. They just see your ADT.

What you'd call it
What the system calls it
What it actually is
Your patient number
MRN
Your one permanent ID, kept for life across every visit.
A visit
Encounter
One specific interaction. You have many; the MRN ties them together.
The tab for your care
Account
The billing record that runs parallel to each encounter.
Front-desk info
Demographics
Name, birth date, address. The data used to match you.
The index of everyone
MPI
The Master Patient Index, the master list every match runs against.
The doctor's instructions
Orders
Each decision turned into a trackable row: a med, a lab, an image.
Where you are right now
ADT
The admit, discharge, transfer feed every other system listens to.
Your record, traveling
FHIR / C-CDA
The modern standards that carry a copy of you to other systems.

Your record leaves the building

Here is the assumption most people carry: my record is a file, and it sits at my hospital. Neither half is true.

Your record is constantly handed between systems through the plumbing that connects theminterfaces. A packaged summary of you travels to your other doctors and other hospitals as a portable summary documentC-CDA. The modern pipe for moving the pieces on demand is a shared data standardFHIR. A regional shared record networkHIE may hold its own copy. Your insurer gets a version. And you have a legal right to your own copy, the HIPAA right of access.

So "your record" is not one file in one place. It is many partial copies, in many systems, each synced a little differently, each a little out of date. There is no master original sitting in a drawer. There is just the network.

Where it breaks: two records, one you

All of this rests on one fragile assumption. That the system can always tell it is YOU. It cannot.

Mistype a birth date at the desk. Use a nickname one visit and a legal name the next. Get married, change your name, move states. Any of it can make the match miss, and the system quietly does the worst possible thing: it creates a SECOND record. Now you are two records for one persona duplicate, and half your history lives on an MRN nobody is looking at.

The reverse is rarer and worse. Two different people get fused into one record, your chart tangled with a stranger'san overlay. Patient matching is not a solved problem. It is an ongoing one, tracked for years by the Office of the National Coordinator as a core patient-safety and interoperability gap.

The part that should bother you

The system is confident. It will show a clinician your record without ever flagging that it might be the wrong one, or only half of one. The fragile step, matching a human to a file, happens silently, and it happens before anyone in a white coat sees a thing.

Discharge is a status, not an ending

You walk out. The encounter closes. The record does not.

It gets coded into billing language, sent to your payer, counted in quality and public-health reporting, copied into the exchanges, and stored. Years from now it is still there, still tied to your MRN, still being matched against the next time you show up. Discharge changes a status field. It does not end anything.

So what are you, in there?

Not a patient. A patient number, a string of encounters, a stack of accounts, and a few hundred timestamped rows, copied into systems you will never log into.

Knowing that does not make you cynical. It makes you literate. It means you check the birth date on the wristband. It means you ask whether your other hospital's records actually made it over. It means the next time someone tells you THE COMPUTER HAS YOUR RECORD, you know enough to ask the only question that matters: which one.

Sources

This article uses only vendor-neutral, publicly documented terminology. Industry terms are drawn from open standards and federal guidance, not proprietary EHR documentation.

ONC
Patient matching, patient identity, and health information exchangehealthit.gov →
HL7
FHIR R4: the Patient and Encounter resource definitionshl7.org/fhir/R4/ →
HL7
HL7 International: the messaging standards behind ADThl7.org →
HHS
HIPAA Privacy Rule: protected health information, minimum necessary, and your right of accesshhs.gov/hipaa →