| Course | HCIS 140 Fundamentals of Electronic Health Records (HCIS/140) |
|---|---|
| Week | 2 |
| Paper type | EHR definition and contents paper |
| Length | about 1,044 words, 4 double-spaced pages plus title page and references |
| Format | APA 7 student paper |
| School | University of Phoenix |
| Program | BS in Health Administration |
| Updated | September 2026 |
Free sample paper for HCIS 140 Week 2
Eight Things a Record Must Do: Defining the Electronic Health Record Through One Patient's Chart and the Core Functions Set Out by the Institute of Medicine
[Student Name]
University of Phoenix
HCIS/140: Fundamentals of Electronic Health Records
Week 2 Assignment
[Instructor Name]
[Date]
The patient and the chart described are composites written for a model paper; definitions and findings come from the sources listed.
A man of 64 living with diabetes and a weak heart has been seen by his primary care physician, a cardiologist, a hospital emergency department and a diabetes educator in the past year. Each of them read and added to his electronic health record. What exactly is that record, what does it hold and what is it expected to do? This paper answers by opening his chart section by section and comparing what it holds with the functions an expert committee said an EHR system should perform.
Defining the EHR
An electronic health record is a digital version of a patient's health information, created and managed by authorized clinicians and staff, that is designed to be shared across the organizations involved in the patient's care (Office of the National Coordinator for Health Information Technology, 2019). It differs from an electronic medical record, which typically holds one practice's data and is used mainly within that practice, and from a personal health record, which the patient controls and fills from sources the patient chooses.
Demographics and Insurance
The chart opens with his name, date of birth, address, phone numbers, emergency contact, preferred language and insurance. Front desk staff maintain this section, and billing depends on it. Errors here ripple everywhere: a wrong insurance number causes a denied claim, and a wrong phone number means a missed call about a lab result.
Problem List
His problem list shows type 2 diabetes, chronic heart failure with reduced ejection fraction, chronic kidney disease stage 3 and a history of a heart attack. Because it is structured data rather than free text, the system can count every patient with diabetes, remind clinicians about eye exams and pass accurate diagnoses to coders.
Medications and Allergies
His medication list includes metformin, an SGLT2 inhibitor, a beta blocker and a diuretic, along with a sulfa allergy. The list is reconciled at each visit and hospital discharge. When a clinician tries to prescribe a drug that interacts with one on the list or conflicts with the allergy, the system warns them.
Vital Signs, Results and Imaging
Weights, blood pressures, A1C results, kidney function tests and an echocardiogram report sit in their own sections, displayed as trends. His cardiologist can see at a glance that his weight rose five pounds in a week before his emergency visit.
Notes, Orders and Documents
Each encounter produces a note describing the history, examination, assessment and plan. Orders for tests, medications and referrals are entered electronically and tracked until completed. Scanned documents, such as outside records and signed consent forms, are attached.
Immunizations and Preventive Care
His flu and pneumococcal vaccines are recorded and reported to the state registry. Preventive care reminders flag his overdue diabetic eye exam.
The Eight Core Functions
In 2003 an Institute of Medicine committee identified eight core capabilities an electronic health record system should provide (Institute of Medicine, 2003). His chart shows each of them. Health information and data: the demographic, problem, medication and allergy sections. Results management: lab and imaging results delivered and displayed as trends. Order entry and management: electronic orders and prescriptions. Decision support: the drug interaction warning and the eye exam reminder. Electronic communication and connectivity: messages among his clinicians and the referral to the diabetes educator. Patient support: the education materials in his portal. Administrative processes: scheduling and billing data. Reporting and population health: his inclusion in the clinic's diabetes registry and quality reports. The eight functions show that an EHR is not a filing cabinet on a screen but a set of tools that act on the information it holds.
How Recently This Became Normal
Electronic records with these functions were rare until recently. A national survey from 2008 found comprehensive records in fewer than one hospital in fifty and electronic medication ordering in about one in six (Jha et al., 2009). Federal incentives and requirements changed that within a decade.
What the Record Cannot Do on Its Own
The record depends on the people using it. If a clinician copies an old note forward without updating it, the record repeats outdated facts. If an outside hospital uses a system that does not exchange data, the record has gaps. If alerts fire too often, clinicians learn to ignore them. And the record cannot make sense of information no one entered, such as a medication the patient stopped without telling anyone.
Privacy and Access Controls
Because many people touch the record, access is controlled by role. The front desk can see demographics and schedules but not therapy notes; a coder can read the documentation needed to code but cannot change clinical entries; clinicians see what they need to treat. Every view and change is logged, and the organization audits access to catch people looking at records without a reason. Some information, such as substance use disorder treatment records from specialized programs, carries additional federal protections that limit how it may be shared. These controls allow a record designed for sharing to remain private at the same time.
The Patient's View
The man with heart failure also sees part of his own record through the portal: his medication list, recent results, visit summaries and messages from his care team. Since his emergency visit, he checks his weight trend and lab values between appointments, which lets him spot a gain early and call the clinic. The portal turns the record from something kept about the patient into something he can use.
Who Uses the Record
Physicians and nurse practitioners document and order, nurses record vital signs and give medications, pharmacists check prescriptions, coders assign codes from documentation, billers submit claims, quality staff pull reports and the patient reads portions through the portal. Each user sees the part of the record relevant to their role, controlled by access permissions.
Conclusion
An electronic health record is a shared, structured record of a patient's health information, distinct from a single practice's EMR and from a patient-controlled PHR. One patient's chart shows its sections at work and the eight functions they support, while also showing that the record is only as good as the people and connections behind it.
References
Institute of Medicine. (2003). Key capabilities of an electronic health record system: Letter report. The National Academies Press. https://doi.org/10.17226/10781
Jha, A. K., DesRoches, C. M., Campbell, E. G., Donelan, K., Rao, S. R., Ferris, T. G., Shields, A., Rosenbaum, S., & Blumenthal, D. (2009). Use of electronic health records in U.S. hospitals. New England Journal of Medicine, 360(16), 1628-1638. https://doi.org/10.1056/NEJMsa0900592
Office of the National Coordinator for Health Information Technology. (2019). What is an electronic health record (EHR)? HealthIT.gov. https://www.healthit.gov/faq/what-electronic-health-record-ehr
What the HCIS 140 Week 2 instructions ask
HCIS 140 Week 2 generally asks students to explain what an electronic health record is and what it contains. Prompts often ask for a definition, a comparison with paper records and with related terms such as electronic medical record and personal health record, a description of the main components or sections of an EHR, and an explanation of who uses each part. Some sections ask students to describe the core functions an EHR should perform or the benefits it offers patients, clinicians and organizations. A length of up to three pages is usual, supported by reliable references. A good answer uses a concrete example, names sections accurately, links each function to a user and a purpose, and notes limits such as poor interoperability or documentation burden.
How this HCIS 140 Week 2 example is built
The sample starts with a patient so that every section of the record has content. It defines the EHR and separates it from an EMR, which holds one organization's data, and a personal health record, which the patient controls. It then walks through the chart: demographics and insurance, problem list, medication and allergy lists, vital signs and results, clinical notes, orders, immunizations, documents and billing data. The core of the paper maps those sections to the eight capabilities an Institute of Medicine committee listed for an EHR system, from health information and results management to decision support and population reporting. Historical adoption data provide context, and a closing section lists what the record cannot do by itself.
HCIS 140 Week 2 grading rubric: where the points go
Faculty grading this week usually reward an accurate definition, a correct distinction among EHR, EMR and PHR, and a clear description of the record's contents and functions. Using an authoritative framework for the functions of an EHR earns credit, as does linking each function to a user and a benefit. Concrete examples help. Discussion of limits or challenges shows balance and often earns points. Organization, such as moving through the chart section by section, makes the paper easy to grade. Writing quality and APA references complete the score. Papers that define the EHR vaguely, list sections without explaining them or treat the three record types as the same tend to lose points.
HCIS 140 Week 2 help: mistakes to avoid
Students often write a definition of the EHR copied from a website and stop there. Show the record at work instead, with an example chart. A second frequent error is using EHR and EMR interchangeably; explain the difference in scope and sharing. Describe the problem list, medication list and results as structured data that can be searched and counted, which is what makes decision support and reporting possible. Name who uses each section, such as coders reading diagnoses or pharmacists checking allergies. Cite an authoritative source for the core functions. Note challenges honestly, such as copied notes or incomplete outside records. Finally, keep the patient example consistent throughout, since switching patients midway confuses the reader.
Related HCIS 140 sample papers
Other HCIS 140 week samples
- HCIS 140 Week 1: Technology Behind the EHR
- HCIS 140 Week 3: EHRs in Play
- HCIS 140 Week 4: Health Care Information Systems
- HCIS 140 Week 5: Health Care Billing and Transactions
More BS in Health Administration sample papers
- HCS 120 Week 2: Speaking the Language of the Body
- HCS 131 Week 2: Communication Types and Preferences
- HCS 235 Week 2: Health Care Services
- HCS 325 Week 2: Teamwork, Communication, and Organizational Structure
HCIS 140 Week 2 questions, answered
What does HCIS/140 Week 2 usually ask for?
Many sections ask students to define the electronic health record, compare it with paper records, EMRs and PHRs, and describe its main components and functions.
Where can I find a free HCIS 140 Week 2 sample paper?
The chart-based EHR paper on this page costs nothing to read, and notes in the margin explain it. The first custom paper built around your own example is also free.
What are the eight core functions of an EHR?
An Institute of Medicine committee listed health information and data, results management, order entry and management, decision support, electronic communication and connectivity, patient support, administrative processes, and reporting and population health.
What is a problem list?
A running list of a patient's current and past diagnoses and health problems, kept as structured data in the EHR so clinicians, coders and decision support tools can use it.
Is an EHR the same as an EMR?
No; an EMR usually holds one practice's data for internal use, while an EHR is designed to follow the patient across providers and settings and to share information.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official University of Phoenix document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
Request this one custom, free · All HCIS 140 week samples · All courses