HIM 615 Topic 1 baseline needs assessment example

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

This HIM 615 Topic 1 sample paper is a baseline needs assessment written before any vendor demonstration, asking whether a twelve-clinic physician group should replace its ambulatory EHR or optimize the one it has. It was written for GCU HIM 615, Health Care Information Systems and Technology, catalog code HIM-615, in the Grand Canyon University MS in Health Informatics. Five failing outcomes are measured from audit logs, queue reports and chart review, from referral loops closed only 54 percent of the time to 1.3 hours of evening documentation. Two problems turn out to be configuration choices, three are product limits, and non-functional needs for downtime, access, response time and hosting are stated before selection begins.

CourseHIM 615 Health Care Information Systems and Technology
TopicTopic 1
Paper typeBaseline needs assessment
LengthAbout 1,060 words, 3 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramMS in Health Informatics
UpdatedSeptember 2026

Free sample paper for HIM 615 Topic 1

1

Before the First Demonstration: A Baseline Needs Assessment for Replacing Paloma Basin Medical Group's Ambulatory EHR

[Author Name]

College of Nursing and Health Care Professions, Grand Canyon University

HIM-615: Health Care Information Systems and Technology

Topic 1 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 fixes the timing, before any vendor is seen, because a needs assessment written after demonstrations adopts the vendors' vocabulary. Paloma Basin and its figures are composites; the sources are real.
2

Before the First Demonstration: A Baseline Needs Assessment for Replacing Paloma Basin Medical Group's Ambulatory EHR

The Decision Under Consideration

Paloma Basin Medical Group is the twelve-clinic physician group of Paloma Basin Health, a system that also runs three hospitals. Its physicians have said for two years that they need a new ambulatory electronic health record. This assessment was written before any vendor demonstration, and it says so here because the order matters: once a group has watched a product, the product's features become the vocabulary in which needs are described. The decision under consideration is whether to replace the current system. Optimizing it, by reconfiguring and adding modules the group already licenses, is a real alternative and is treated as one from the start.

The assessment asks first what problems a new system would solve, measures each problem now so that later claims of improvement can be tested, and then sorts the problems into those the current system could fix and those it cannot.

Who Was Consulted

Over five weeks, the HIM and informatics team interviewed 14 physicians and advanced practice clinicians, 9 medical assistants and triage nurses, 6 front desk and scheduling staff, 4 referral coordinators and the billing manager, and observed full clinic sessions at four of the twelve clinics. Front desk staff and triage nurses were included deliberately, because their work is often disturbed first by a new system and they are rarely asked about the old one.

The list has gaps. Patients were not interviewed directly; their experience enters only through portal message data and complaint logs. Specialists outside the group, who receive its referrals, were not consulted. Both gaps are noted as limits on the findings about referrals and the portal.

Five Failing Outcomes and Their Baselines

Each problem below is stated as an outcome that is failing, not as a feature that is missing. "We need a referral module" names a solution. "Referral loops do not close" names a problem a solution can be tested against. Baselines come from the current system's audit logs, queue reports and a chart review, over the six months before the assessment.

Table 1

Failing Outcomes and Their Baselines

Failing outcomeMeasureSourceBaseline
Referral loops do not closeShare of specialist referrals with a consult report in the record within 60 daysChart review of 200 referrals54%
Refill requests waitMedian time from refill request to decisionRefill queue report2.6 business days
Documentation spills into eveningsPhysician time in the record outside scheduled clinic hours, per clinic dayAudit log1.3 hours
Outside results arrive as imagesShare of outside laboratory results stored as discrete valuesResults interface report22%
Patients cannot be scheduled across clinicsShare of transfers between clinics requiring a phone call to bookScheduling log sample100%

Reading the Baselines

The evening documentation figure is in line with what event log studies have found elsewhere. Arndt et al. (2017), combining log data with direct observation, found that primary care physicians spent nearly six hours of an eleven-hour workday in the record, including time after clinic hours. The referral figure matters for safety as well as convenience. Mehrotra et al. (2011) described how the referral process in the United States often fails to transfer information in either direction, leaving primary care physicians unaware of what specialists found. At Paloma Basin, nearly half of referred patients have no specialist report in the record two months later, and no one is responsible for noticing.

Configuration or Product?

The central question of the assessment is which problems a new product would solve that the current one cannot. Two of the five turned out to be configuration choices. The refill delay comes largely from routing: refill requests go to a single pool per clinic that no one owns during clinic hours, and the current system can route them to each physician's care team by protocol. The referral problem can be addressed by a referral tracking work queue the group already licenses but never switched on.

The other three trace to limits of the product. The current system stores outside results as documents unless each laboratory builds a vendor-specific interface, and the vendor has no plan to support newer exchange standards for results. Scheduling is configured as twelve separate databases, one per clinic, an architecture the vendor confirmed cannot be merged. The evening documentation burden reflects many causes, but physicians' descriptions pointed repeatedly at slow screens and an inbox that cannot be filtered, both product limits the vendor has not addressed in three releases. One further limit applies across all five: the group's three hospitals use a different system, so every admission and discharge crosses an interface.

What this page is doingThe paper finds that two problems do not need a new product, which is the honest result a board needs before approving a replacement.
3

Non-Functional Needs

Vendors rarely volunteer non-functional requirements, and they surface later as contract disputes if the buyer does not state them first. The group needs the following. Downtime tolerance: no more than four hours of unplanned downtime a year, and read-only access to schedules, medication lists and allergies within 15 minutes of any outage. Access control: role-based access, emergency access with mandatory reason and review, and audit logs the group can query directly. Response time: common screens loading in under two seconds for 95% of requests at peak clinic hours. Hosting: the group has no data center staff, so a vendor-hosted model with a stated disaster recovery time is preferred. Sittig and Singh (2010) included hardware, software and infrastructure as one of eight dimensions of health information technology in use, and these needs belong to that dimension.

Recommendation

The assessment recommends proceeding to selection, with two conditions. First, the refill routing and referral work queue changes should be made now in the current system, since they are cheap and would improve two outcomes during the 18 months a replacement would take. Second, selection should give heavy weight to a single record shared with the three hospitals, since that is the limit no amount of optimization can fix.

The assessment would have recommended optimizing alone if the three product limits had been fixable. If the vendor had committed to discrete results import and a merged scheduling database in its next release, and if the hospitals were not moving to a single enterprise system, replacement would cost far more than the problems it solved. The baselines in Table 1 will be measured again 12 months after any go-live, and the group's board should ask for them.

References

Arndt, B. G., Beasley, J. W., Watkinson, M. D., Temte, J. L., Tuan, W.-J., Sinsky, C. A., & Gilchrist, V. J. (2017). Tethered to the EHR: Primary care physician workload assessment using EHR event log data and time-motion observations. Annals of Family Medicine, 15(5), 419-426. https://doi.org/10.1370/afm.2121

Mehrotra, A., Forrest, C. B., & Lin, C. Y. (2011). Dropping the baton: Specialty referrals in the United States. Milbank Quarterly, 89(1), 39-68. https://doi.org/10.1111/j.1468-0009.2011.00619.x

Sittig, D. F., & Singh, H. (2010). A new sociotechnical model for studying health information technology in complex adaptive healthcare systems. Quality and Safety in Health Care, 19(Suppl 3), i68-i74. https://doi.org/10.1136/qshc.2010.042085

HIM 615 Topic 1 instructions, in plain terms

HIM-615 opens with Topic 1, where students assess an organization's needs before a system is chosen. Many papers start from a list of products or desired features. The assignment rewards assessments that state the decision, including optimizing the current system as a real option, consult a wide range of staff and describe problems as failing outcomes with measured baselines. Students should sort problems into those configuration could fix and those that need a different product, add non-functional requirements such as downtime tolerance and security, and give a recommendation with the conditions that would have changed it.

How this HIM 615 Topic 1 example is built

The finished assessment is written before anyone has watched a vendor demonstration, and it says so on its first page. A composite physician group of twelve clinics believes it needs a new ambulatory EHR, and the assessment asks first what problem a new system would solve. Five problems are named from interviews and observation, among them referral loops that never close and prescription refill requests that wait days. Each is measured now, from audit logs and queue reports, so that later claims of improvement have a baseline. Two problems turn out to be configuration choices the current system could fix. The other three are traced to limits of the product itself. Non-functional needs follow: downtime tolerance, access controls, response time and the hosting model. The recommendation proceeds to selection and defends that against optimizing alone.

Reading the HIM 615 Topic 1 rubric

GCU's rubric for the needs assessment rewards evidence before products. Excellent assessments consult front desk staff, nurses and billing as well as physicians and admit the gaps in who was asked. Credit goes to problems stated as outcomes with baselines drawn from logs and reports, so a later review can test the purchase. The rubric values an honest finding that some problems need only configuration. The highest level states non-functional needs and names the conditions under which optimizing would have won. Assessments that begin from a shortlist of vendors usually land in a middle band.

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

Marks slip here when the assessment is shaped by products before needs are known. A list of features the group wants, rather than outcomes that are failing, gives the selection team nothing to test a product against. Papers without baselines cannot show at the post-implementation review whether anything changed. Drafts often treat replacement as settled and skip the question of whether configuration would solve the problem more cheaply, which is the first question a board will ask. Stakeholder lists limited to physicians and IT miss the staff whose work changes first. Downtime and security needs left unstated tend to reappear as contract disputes, at a point when the group has far less room to negotiate.

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

Send the HIM-615 Topic 1 instructions and the rubric from your classroom, with the organization or case the assignment describes. We write a custom example to those criteria, with the decision framed before any product, problems stated as outcomes, baselines measured, configuration fixes separated from product limits and non-functional needs included, in 24 to 48 hours. The first one is free.

More HIM 615 papers and MS in Health Informatics samples

HIM 615 Topic 1 questions, answered

How is a needs assessment different from a requirements matrix?

The needs assessment comes first and asks whether a new system is the answer at all. It defines the problems, measures them and tests whether the current system could solve them. The requirements matrix follows once replacement is justified, translating needs into scored criteria for vendors. Skipping the assessment means the matrix describes a purchase nobody has shown to be necessary.

Why measure baselines so early?

Because nothing can be measured backward once the old system is gone. Documentation time from audit logs, refill turnaround and referral closure rates are available now and hard to reconstruct later. Without them, claims at the post-implementation review rest on impressions, and impressions after go-live tend to reflect the stress of transition more than the design of the new system.

Should the assessment ever recommend not buying?

Yes, when the evidence supports it, and a paper that could not reach that conclusion is not really assessing. Many problems blamed on a product trace to configuration, training or workflow, all of which cost less to fix than a replacement. Where your case supports replacement, the assessment still states what would have justified optimization, so the reader sees the decision was tested.

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

Scroll up for the full assessment, covering the decision, who was consulted, five failing outcomes with baselines, configuration or product, non-functional needs and the recommendation. Describe your organization for a free worked assessment.

Should the group replace or optimize in HIM 615 Topic 1?

Replace, but fix refill routing and switch on referral tracking in the old system now. Discrete outside results, merged scheduling and a record shared with the hospitals need a new product.