| Course | BHA FPX 2106 Health Information Management in Healthcare Organizations |
|---|---|
| Assessment | Assessment 1 |
| Paper type | Information system evaluation |
| Length | About 1,110 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Health Care Administration |
| Updated | September 2026 |
Free sample paper for BHA FPX 2106 Assessment 1
Evaluating One System in One Department: The Registration and Scheduling System in a Hospital's Patient Access Department
Student Name
Capella University
BHA FPX 2106: Health Information Management in Healthcare Organizations
Instructor Name
Month Day, Year
One System and One Department
This evaluation examines one information system, the registration and scheduling module of the electronic health record, as it is used by one department, patient access, at a composite 200-bed hospital, here called Riverside Hospital. Patient access employs 38 staff who schedule outpatient tests and procedures, preregister patients before scheduled visits, register patients on arrival, and verify insurance. The module is the first place most patient information enters the hospital's systems, which makes its data quality important to every department that uses the record afterward, from nursing to billing. Limiting the evaluation to one system and one department keeps it specific enough to lead to action.
Workflow Mapped Before It Is Judged
The workflow was mapped by observing six patient access representatives across day and evening shifts and reviewing 60 registration records. Scheduling: a patient or physician's office calls to schedule an outpatient test. The scheduler searches for the patient in the master patient index, creates or selects the patient record, enters the order details, and books a time. Preregistration: two to five days before the visit, a preregistration representative calls the patient to confirm demographics and insurance, checks eligibility using the module's electronic eligibility inquiry, and records any copayment due. Arrival registration: on the day of service, a representative confirms identity with photo identification, scans the insurance card, has the patient sign consent forms on a signature pad, and prints the wristband or visit label. Insurance verification: for services requiring prior authorization, a separate team checks that authorization is on file, using payer websites outside the module. Mapping first showed that representatives use the module for most steps but leave it for insurance authorization and for looking up some payer rules, which they keep in a shared spreadsheet. Mapping the workflow before judging the system shows where the system is used, where people work around it, and why.
Criteria Stated Up Front
The module is judged against four criteria stated before the evaluation. Data accuracy: patient identity, demographics, and insurance information are correct. Completeness: required fields are filled before the visit. Timeliness: preregistration is completed before the day of service. Usability: representatives can complete tasks without workarounds or excessive steps.
Findings Against the Criteria
Accuracy. A review of 60 records found errors in 11: 4 with incorrect insurance subscriber information, 3 with outdated addresses, 2 with misspelled names, and 2 with incorrect dates of birth. The hospital's duplicate medical record rate is 1.4% of new registrations, above the department's target of 1%. Completeness. Required fields are enforced by the module, but "unknown" and placeholder values can be entered and are used in about 6% of records for fields such as employer or emergency contact. Timeliness. Preregistration is completed before the visit for 78% of scheduled outpatients; the rest are registered on arrival, which lengthens waiting times. Usability. Representatives take an average of nine minutes for a new outpatient registration. The eligibility inquiry returns results in seconds but displays them in a format that is hard to read, and representatives often call payers instead.
Data Quality Traced to Capture Points
Each data quality problem was traced to the point where the data were captured. Duplicate records trace to scheduling, where schedulers search by name and date of birth under time pressure and create a new record when the search returns no exact match, even if the patient exists with a slightly different spelling. Insurance subscriber errors trace to preregistration calls in which patients read information from their cards, and representatives key it in manually. Outdated addresses trace to arrival registration, where representatives confirm addresses verbally but are measured on speed and do not always update the record. Placeholder values trace to the module's design, which enforces the field but accepts any value. Tracing errors to capture points in this way shows that most are introduced by predictable steps under predictable pressures, which means they can be prevented at the source rather than corrected later by billing staff. Tracing each error to its capture point turns a list of data problems into a list of places to intervene.
Effects Downstream
The errors have effects beyond patient access. Insurance errors are the most common cause of claim denials at Riverside, accounting for about a third of initial denials. Duplicate records split clinical information, so a clinician may not see a patient's allergy recorded under the other record. Outdated addresses cause bills and test results to be returned by mail. Late preregistration crowds the registration desk on busy mornings.
Why Evaluate Use, Not Just Features
A feature list would suggest that Riverside's module is capable: it offers eligibility inquiry, required fields, electronic signatures, and a probabilistic search option. The evaluation shows that capability is not the same as performance in use. Ash et al. (2004) found that many problems with patient care information systems arise not from software defects but from a poor fit between the system and the way work is actually done, including systems that demand data entry at moments when staff are busiest. Riverside's registration errors fit that pattern: representatives under time pressure at scheduling and arrival take shortcuts the system allows. Evaluating use rather than features is what reveals these problems, and it points to solutions that combine configuration with changes in workflow and expectations.
What the System Does Badly
The module does several things well: it enforces required fields, supports electronic eligibility inquiry, and captures signatures electronically. It does some things badly. Its patient search uses exact matching, returning no results for minor spelling differences, which contributes to duplicates. It accepts placeholder values in required fields. It displays eligibility responses in a dense format that representatives find hard to read. And it does not scan insurance cards into structured data; cards are stored as images, so information must be typed. These weaknesses are not all failures of the system alone; some can be addressed through configuration, such as enabling the module's probabilistic search option, which is available but not turned on.
Conclusion
Evaluating the registration and scheduling module in one department, with workflow mapped first and criteria stated up front, shows that most data quality problems enter at predictable capture points. The module does some things well, but its exact-match search, acceptance of placeholder values, and hard-to-read eligibility display contribute to errors that affect billing and clinical care downstream. Several of the weaknesses can be addressed through configuration and workflow changes.
References
Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: The nature of patient care information system-related errors. Journal of the American Medical Informatics Association, 11(2), 104-112.
Reading the BHA-FPX2106 Assessment 1 instructions
The first assessment in BHA FPX 2106 asks you to evaluate a health information system in a specific department. You identify the system and department, map the workflow it supports, set evaluation criteria, assess the system against them, examine data quality at the points of capture and consider effects on other departments. Evaluation should be based on how the system is used, not only its features. Observation, staff input and system reports are useful evidence. Scholarly sources on health information management and data quality support the paper. The system you choose usually carries into the privacy analysis and improvement recommendation that follow.
How this BHA FPX 2106 Assessment 1 example is built
The example builds the yardstick before using it. It opens by naming the system, the department and the purpose of the evaluation. The second section maps the workflow the system supports, step by step, including handoffs and the points where data enters. The third section states the evaluation criteria and where they came from, which is what turns opinion into assessment. The fourth section works through each criterion in turn, presenting evidence for the finding rather than an impression. The fifth section concentrates on data quality, tracing accuracy, completeness and timeliness through the capture points identified earlier. The conclusion states an overall judgment about fit between system and workflow, and flags the single weakness with the largest operational consequence. Every finding points back to a step in the workflow map rather than to a feature list.
Reading the BHA FPX 2106 Assessment 1 scoring guide
Capella's scoring guide rates the system description, the workflow, the criteria, the findings, the data quality analysis and the writing. The workflow reaches Distinguished when mapped step by step with data entry points before any judgment. Criteria score higher when stated up front and tied to the department's needs. Findings earn credit when each criterion is addressed with evidence. Data quality analysis rewards tracing errors to where they start, such as duplicate patient records created at registration. Downstream effects, such as claim denials, show systems thinking. Writing and APA citations are graded.
Common BHA FPX 2106 Assessment 1 mistakes, and how to avoid them
Students often list a system's features rather than evaluating how it is used on a busy morning. Another common mistake is judging without criteria, so the evaluation reads as opinion. Workflow is skipped, so findings float free of the work the system supports. Data quality problems, such as duplicate records or wrong insurance, are noted without tracing their cause to a specific screen or step. Downstream effects are missed, though a registration error often becomes a claim denial weeks later. Only strengths are reported, or only weaknesses. Evidence is opinion rather than observation or system reports. Mapping one patient's registration from phone call to arrival is a simple way to see where the system helps and where it causes errors, and it gives the evaluation a concrete spine.
Get a BHA FPX 2106 Assessment 1 example written to your instructions
Send the Assessment 1 instructions and the scoring guide from your BHA FPX 2106 courseroom, plus the system and department you are evaluating if they are already set. We write a custom example to those criteria, with the workflow mapped and the evaluation criteria stated, and return it in 24 to 48 hours. The first custom sample is free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More BHA FPX 2106 papers and BS in Health Care Administration samples
- BHA FPX 2106 Assessment 2: Privacy and Security Analysis
- BHA FPX 2106 Assessment 3: Improvement Recommendation
- BHA FPX 2110 Assessment 1: Process Analysis
- BHA FPX 2102 Assessment 1: Leadership Analysis
- BHA FPX 3001 Assessment 1: System Analysis
- BHA FPX 2006 Assessment 1: Regulatory Analysis
BHA FPX 2106 Assessment 1 questions, answered
Which system should I evaluate for BHA FPX 2106 Assessment 1?
One you can describe at workflow level. Electronic health record documentation, registration and admission systems, computer assisted coding, patient portals, laboratory interfaces and scheduling systems all work well. Avoid evaluating an entire enterprise platform, since the detail disappears. If your instructions name a system or a case scenario, use that and hold the scope where they set it.
Where do evaluation criteria come from?
From the health informatics literature and from professional bodies rather than from your own preferences. Interoperability, usability, data quality, security, reporting capability and support for the clinical workflow are standard axes, and citing where you drew them from strengthens the assessment. Once stated, apply every criterion to the system, including the ones where the finding is unflattering.
Can I use a system from my own workplace?
In most sections yes, if you check the instructions and keep organization-identifying detail out. Firsthand knowledge of the workflow makes the evaluation far more specific, which is what the criteria reward. Describe the department, the process and the system behavior without naming the employer, and support your general claims about the system type with published sources.
Where can I find a free BHA FPX 2106 Assessment 1 sample paper?
The patient access system evaluation can be read here in full, with workflow, criteria, findings, data quality and downstream effects. A custom evaluation is available free.
What criteria should I use in BHA FPX 2106 Assessment 1?
Criteria drawn from the department's work, such as speed of registration, accuracy of demographics and insurance, duplicate records, ease of use and support for downstream billing. State them before judging.