HIM 615 Topic 2 vendor demonstration script example

Health Care Information Systems and Technology Grand Canyon University Free custom sample in 24 to 48h

This HIM 615 Topic 2 sample paper is a vendor demonstration script, with rules and a scoring sheet, that a three-hospital system sends to its two EHR finalists. It belongs to GCU HIM 615, Health Care Information Systems and Technology, the course listed as HIM-615 in the Grand Canyon University MS in Health Informatics. Vendors must use test patients built to the system's specification, declare the release status of every function and stay on the script. Six scenarios follow care in order, from registration to discharge, each with an exception written in, plus downtime recovery. Observers score each scenario immediately, clinicians take the keyboard in an unscripted session and reference sites are chosen by the buyer.

CourseHIM 615 Health Care Information Systems and Technology
TopicTopic 2
Paper typeVendor demonstration script
LengthAbout 980 words, 3 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramMS in Health Informatics
UpdatedSeptember 2026

Free sample paper for HIM 615 Topic 2

1

Our Patients, Our Exceptions, Our Keyboard: A Vendor Demonstration Script and Scoring Rules for Paloma Basin's EHR Finalists

[Author Name]

College of Nursing and Health Care Professions, Grand Canyon University

HIM-615: Health Care Information Systems and Technology

Topic 2 Assignment

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

What this page is doingThe title lists the three things the script takes back from the vendor: the patients, the hard paths and the controls. Paloma Basin, the finalists and the scenarios are composites; the sources are real.
2

Our Patients, Our Exceptions, Our Keyboard: A Vendor Demonstration Script and Scoring Rules for Paloma Basin's EHR Finalists

Purpose of the Script

Paloma Basin Health has two finalists for an enterprise electronic health record that would serve its three hospitals and its twelve-clinic medical group. Each finalist will present for two days. A demonstration left to the vendor shows the vendor's best work: complete patient records, ideal paths and functions rehearsed many times. The purpose of this script is to see each product doing Paloma Basin's work instead, including the paths that go wrong in real care, so that the selection committee can compare the two products doing identical work on identical patients.

The script is sent to both finalists four weeks before their dates, with the test patient specifications and the scoring sheet. Nothing in it is secret. A vendor that can prepare for our hardest cases is a vendor worth seeing prepare.

Rules

Test patients. Each vendor builds eight test patients to Paloma Basin's specification, including a patient with a hyphenated surname and no Social Security number, a patient with an allergy documented only in a free-text scanned letter, and a patient transferred between two of our hospitals. Curated demonstration records may not be used.

Release status. Before showing any function, the presenter states whether it is generally available in the current release, in testing, or on the roadmap. Observers record the status beside each score. A roadmap function scores zero for this purpose, whatever it looks like.

Staying on the script. Presenters may not leave the script without saying so. If a scenario cannot be performed as written, the presenter says why, and the observers record it.

The unscripted session. The last three hours of each vendor's second day belong to Paloma Basin clinicians, who will use the product themselves with a vendor trainer beside them but not at the keyboard.

Scenarios

Table 1

Demonstration Scenarios in the Order Care Happens

ScenarioOrdinary pathException written into it
1. RegistrationRegister a new patient and schedule a clinic visitPatient has no Social Security number and a name the system may split; search must find the existing record from another clinic
2. Clinic visitDocument a visit, order a laboratory test and send a prescriptionThe only allergy is in a scanned outside letter; show how the prescriber would learn of it
3. ReferralRefer to cardiology and track the referralSpecialist report never arrives; show who is told and when
4. Admission and transferAdmit through the emergency department, then transfer to a second hospitalActive orders and the medication administration record must follow the patient; show what the receiving nurse sees
5. DischargeReconcile medications and send a summary to the clinicA home medication was stopped for a side effect; show where the reason is recorded and whether it reaches the summary
6. Downtime recoveryClinic works on paper during a four-hour outageShow the read-only record available during downtime and how paper orders and notes are entered afterward, including a duplicate order

Why the Exceptions Matter

Every scenario includes an exception because exceptions are where usability problems cause harm. Howe et al. (2018), analyzing four years of patient safety reports from one region, identified reports that explicitly linked possible patient harm to a usability issue in the record, including problems with data entry, alerts and the way information was displayed. A demonstration built on complete records and ideal paths tests the presenter's rehearsal, not the software's behavior when something is missing or wrong.

Scenario 6 is placed on its own because vendors rarely rehearse it. Downtime is certain in any large system, and recovery, when paper orders written during an outage must be entered and reconciled, is where duplicate and missed orders appear. A product whose vendor cannot demonstrate recovery has told the committee something important. The committee also asks each vendor to show how long its read-only downtime copy lags behind the live record, since a copy several hours old may omit the most recent orders and allergies.

What this page is doingEach exception is tied to a known source of harm, which shows the script was designed around risk rather than features.
3

Scoring

Eleven observers, including physicians, nurses, a pharmacist, a registration supervisor, an HIM coding lead and an informatics analyst, score each scenario immediately after it ends and before the next begins. Scores left for the end of the day are shaped by memory and favor whichever presenter was most confident or went last. Each scenario is scored from 1 to 5 on three criteria written before the demonstration: whether the task was completed as written, how many steps and screens it required, and whether the exception was handled safely. Observers also note any point at which the presenter left the script.

Ratwani et al. (2015) found that vendors varied widely in how they applied user-centered design, and several could not describe a process that involved end users. The scoring sheet asks observers from each role to score the scenarios that role would perform, so that a nurse judges the medication administration record and a registrar judges registration.

The Unscripted Session and Reference Calls

In the unscripted session, clinicians attempt tasks from their own work without rehearsal: a hospitalist admitting a patient, a medical assistant rooming a patient, a nurse documenting a medication given late. The session shows what the product asks of an ordinary user, which a practiced presenter cannot.

Reference calls are arranged with organizations Paloma Basin chooses, not those the vendor supplies. The committee will identify customers of similar size with both hospitals and clinics on a single record, including at least one that went live in the past two years and one that has used the product for more than five. A vendor's own references are selected because they are satisfied, which makes them testimonials rather than evidence. Koppel and Lehmann (2015) noted that the market for enterprise records has concentrated among a few vendors, which makes independent evidence from other customers more valuable to a buyer, not less.

References

Howe, J. L., Adams, K. T., Hettinger, A. Z., & Ratwani, R. M. (2018). Electronic health record usability issues and potential contribution to patient harm. JAMA, 319(12), 1276-1278. https://doi.org/10.1001/jama.2018.1171

Koppel, R., & Lehmann, C. U. (2015). Implications of an emerging EHR monoculture for hospitals and healthcare systems. Journal of the American Medical Informatics Association, 22(2), 465-471. https://doi.org/10.1136/amiajnl-2014-003023

Ratwani, R. M., Fairbanks, R. J., Hettinger, A. Z., & Benda, N. C. (2015). Electronic health record usability: Analysis of the user-centered design processes of eleven electronic health record vendors. Journal of the American Medical Informatics Association, 22(6), 1179-1182. https://doi.org/10.1093/jamia/ocv050

What the HIM 615 Topic 2 instructions ask for

The Topic 2 instructions in HIM-615 ask students to plan how vendor demonstrations will be run and evaluated. Weak submissions accept the vendor's standard agenda. The assignment rewards scripts built from the organization's own work, with scenarios that include exceptions such as incomplete records, transfers and downtime, and with rules that prevent curated demonstrations. Students should require vendors to declare whether functions are available now or on a roadmap, design scoring that happens during the demonstration against criteria set beforehand, include a session where users operate the system themselves and plan independent reference checks.

How the HIM-615 Topic 2 example is put together

The finished document is the demonstration script a composite hospital sends to two finalist vendors, with a scoring sheet and a set of rules attached. Its scenarios come from the hospital's own work and lean on the paths demonstrations usually avoid: a patient registered with an incomplete record, an order that must follow a patient transferring between departments, an allergy recorded only in free text and a clinic re-entering data after a downtime. Each vendor must run the scenarios on test patients built to the hospital's specification rather than on curated demonstration records. Presenters declare the release status of every function they show, generally available, in testing or on a roadmap. A final session hands the keyboard to the hospital's own clinicians. Observers score each scenario before the next one begins.

Reading the HIM 615 Topic 2 rubric

Faculty grading the demonstration script reward control of the evidence. Excellent scripts specify test patients, write an exception into every scenario and explain why exceptions are where usability causes harm. Credit goes to release status rules that keep roadmap features from scoring. The rubric values immediate scoring by observers from the roles that will use each function, and a downtime recovery scenario that vendors rarely rehearse. The highest level hands the keyboard to clinicians and chooses reference sites independently. Scripts that follow the ideal path with complete records, or that let observers score from memory at the end of the day, usually lose marks.

Common HIM 615 Topic 2 mistakes, and how to avoid them

A script built from the vendor's standard agenda loses marks before it is sent, since that agenda was designed around the product's strengths. Scenarios that follow the ideal path, with complete records and no transfers, test the presenter's rehearsal rather than the software. Papers that forget release status let roadmap features score as if they could go live next year. Drafts that let observers score at the end of the day, from memory, reward whichever vendor presented last or most confidently. Leaving out the unscripted session means nobody sees what the product asks of an ordinary user. Reference calls taken only from the vendor's list collect testimonials rather than evidence, and a graduate paper is expected to say why those differ.

Get an HIM-615 Topic 2 example written to your instructions

Send the HIM-615 Topic 2 instructions, the rubric posted in your classroom and the system type or finalists your assignment names. We write a custom example to those criteria, with rules set in advance, exception paths in every scenario, release status declared, a clinician-driven session and scoring fixed before the visit, in 24 to 48 hours. The first one costs nothing.

More HIM 615 papers and MS in Health Informatics samples

HIM 615 Topic 2 questions, answered

Which parts of the work do demonstrations tend to skip?

The awkward parts. A vendor's team rehearses on tidy test records and chooses the paths where its product is strongest, so exceptions, transfers between departments and recovery after downtime rarely appear unless the buyer insists. The script puts those paths in writing before the visit. It also asks presenters to say which functions are released and which are planned, since roadmap items are easy to show and impossible to install.

Why should clinicians drive part of the demonstration?

Because a presenter who has run the product hundreds of times makes every task look effortless. When a nurse or physician from the organization attempts the same task unaided, the screens visited, the hesitations and the questions they ask reveal what the product will demand at go-live. The script sets aside time for this and records what happened, rather than relying on impressions.

Can the script be used for more than two vendors?

Yes, and it works the same way for three or four finalists, though time becomes the constraint. Your instructions may name the number. What matters is that every vendor receives the same scenarios, rules and test patients, and that scoring criteria are fixed before the first demonstration. Changing the script between vendors makes the scores incomparable.

Where can I find a free HIM 615 Topic 2 sample paper?

The complete script is above: its purpose, the rules, six scenarios with exceptions, why exceptions matter, scoring and the unscripted session with reference calls. Share your selection project for a free worked script.

Why declare release status in HIM 615 Topic 2?

A function on the roadmap may never arrive or may arrive years late. Recording release status keeps roadmap features from scoring as if they could go live with the system.