Hospital Information Systems: Implementation and Data

UPI Study › Courses › Healthcare Organization and Management › Free lessons › Lesson 10.1 Free with a free account

Hospital Information Systems: Implementation and Data

Healthcare Organization and Management · Chapter 10: Health Informatics and Technology ManagementSection 10.1 · lesson 59 of 10511 min · free with a free account

← Integrating Analytical Frameworks into Strategic PlanningNext lesson: Health Informatics Challenges and Care Delivery →

Earn 3 college credits for Healthcare Organization and ManagementRecommended for credit by NCCRS · Health 302 · self-paced · one payment, lifetime access
Enroll in Healthcare Organization and Management · $250 →Download the syllabus (PDF)

In this lesson

How hospitals implement information systems and keep shared data meaningful.

  • Distinguish integration from interoperability, and messaging standards from terminologies
  • Describe the stages of an information system implementation
  • Explain why system configuration is a form of policy
  • Plan for go-live support, the productivity dip, and benefits realization

Free study notes

Get this lesson's notes by email

The key points and 4 practice questions with answers, in your inbox. One email, free.

One email. Unsubscribe in one click.

Transcript

Everything said in the video, section by section (1,456 words). Read along, or search it.

Opening Case

A Go-Live Date That Can't Move

Larkfield is replacing its electronic health record. The go-live date is fixed, because the old vendor's contract expires that day. Jamal Carter, the emergency department's nurse manager, reads the latest plan. Testing has been cut by two weeks. Training has moved to just nine days before go-live. And three months of funded fixing after go-live are gone; problems will join the normal change-request queue. Jamal has no say over the timeline. What can he protect, and what must he escalate?

Defining Informatics

Information Use, Not Machines

Kenji Watanabe starts with what informatics is. It's about how information is captured, stored, moved, and used in care, not about the machines that carry it. Picture a lab result that arrives accurately and is stored securely, but the clinician who ordered it never sees it. The system worked perfectly. The informatics failed. That sets a manager's role. Few managers configure software. Almost all decide what information staff need, who enters it, when it must be complete, and what happens when it's wrong.

System Landscape

A Federation of Hospital Systems

A hospital runs not one system but a federation. Clinical systems hold the record of care, and the EHR is the largest. Administrative systems hold registration, scheduling, admission, transfer, and discharge. That's where a patient gets the identifier every other system uses, so an error there spreads everywhere. Financial systems hold charges and claims, built almost entirely on data from elsewhere. Departmental systems serve one function: lab, imaging, pharmacy, surgery. Decision-support systems hold data for analysis: registries, dashboards, and the reporting warehouse. No single system holds the full picture. At Larkfield, the warehouse loads once a night, so every dashboard shows yesterday.

Integration vs. Interoperability

Connecting Systems With Meaning Intact

Two words get mixed up. Integration is connecting systems inside one organization, so data entered in one appears in another. Interoperability is broader: systems exchanging information and using it with its meaning intact. A message can arrive perfectly and still be useless, if the receiver can't tell what a field meant. Most hospitals route connections through an interface engine, a translator between systems. Ten systems then need ten connections to the engine, instead of forty-five to each other. So when data doesn't appear, the fault may be in the sender, the receiver, or the translation. A useful report says what was expected, and what appeared.

Data Standards

Messaging Standards and Clinical Terminologies

Two kinds of agreement make exchange possible. Messaging standards, like HL7 and its newer FHIR standard, govern structure: which fields appear, in what order, meaning what. Clinical terminologies govern content, with an agreed code for each concept: LOINC for lab tests, SNOMED CT for clinical terms. The point is comparability. If two departments record the same test under different local names, a report counting them together undercounts both. Coded data can be counted, compared, and used to trigger support. Free text can't, at least not reliably. To a clinician, coding feels like overhead. To the organization, it's what makes measurement possible.

Implementation Lifecycle

Stages From Needs to Optimization

Tom Brennan says implementation is a change program, not an installation. The same stages recur. Needs assessment: what problem the system should solve. Selection: which product, on what contract, with what support. Configuration: how the software is set up. Testing: whether it behaves correctly in realistic cases. Training: who learns what, how close to go-live. Then go-live, and optimization: fixing what real use reveals. Each skipped stage shows up after go-live as its own failure. Selection takes the most executive attention and the least work. Configuration, testing, and training take most of the work, and they're cut first when time slips, because cutting them looks free that day.

Configuration

Policy Written in Software

Configuration deserves a closer look, because it's policy written in software. Making a field mandatory decides that nobody can finish the task without that information. Putting three items in a standard order set decides they'll be ordered together far more often. Adding a warning decides where clinicians spend their attention. Each is a clinical or operational policy, made faster, by fewer people, with less scrutiny than a paper policy would get. So managers should insist the people who live with it decide it. That takes frontline staff in design. Releasing them is costly, so they're often left out, and the system matches the manual, not the real work. Staff then close the gap with workarounds.

Quick Check

Nurses Still Retyping Vital Signs

Quick check. Six months after a go-live, nurses on 4 South still write vital signs on paper, then retype them. They learned the system three months before go-live, on a test version with different screens. Which failure is this? Pause, and decide. Compressed training. Training held too far from go-live, on a different version, lets skill fade before use, and the paper habit from week one became permanent. Ignoring workflow is tempting, because the paper step sounds like a poor fit. But nothing suggests the screens clash with how the nurses work. They were never taught the real ones.

Go-Live Models

Big Bang, Phased, or Parallel

Next, the switch itself. A big-bang go-live moves everyone at once. It's short and forces the change, but a serious defect hits everyone together. A phased go-live moves one area at a time, but old and new systems must coexist. A parallel run runs both: safest to verify, and punishing, since staff do everything twice. Whichever model, support decides how it's remembered. Danny Reyes, a new nurse, knows: at-the-elbow support means trained people on the unit, answering within ten seconds. It's the first cut when budgets tighten. A command center logs issues, ranks them, and publishes fixes, turning scattered frustration into a list the informatics team can act on.

Failure Patterns

Four Nontechnical Ways Implementations Fail

Implementations fail in four patterns, and none is really technical. First, the unrealistic timeline, set by a contract date or a fiscal year. The failure is what gets removed to protect it. Second, ignoring workflow: a configuration that's technically correct and hostile to how the work flows. Third, compressed training: fewer hours, sessions too early, or the wrong version. Fourth, unfunded optimization. If the budget is spent by go-live, nothing found in live use gets fixed. Then the system stays in its roughest state, and staff reasonably conclude that's just what the software is like. Jamal's plan has three of the four.

Productivity Dip

Planning for the Slowdown

Even a good go-live brings a productivity dip: output falls while experienced staff become beginners on a new tool. That's the normal cost, so plan for it rather than trying to prevent it. Reduce scheduled activity for a while, add staff for the slower pace, protect the schedule from being refilled, and tell everyone in advance that it's coming and roughly how long it lasts. The danger is at the far end. A dip that isn't recovering on time is a signal, not a phase. Telling the two apart requires stating, in advance, what recovery should look like.

Benefits Realization

A Baseline Before the Investment

Last, benefits realization: stating before the investment what improvements it should produce, then measuring whether they happened. Its absence is close to universal. A business case names benefits, the system goes in, and nobody revisits the case. The next investment proceeds with no evidence about the last one. It takes four things: a named benefit stated as a measurable change, a baseline captured before go-live, an owner accountable for the change, not the system, and a scheduled review. The baseline is missed most, and it's the one thing that can't be recovered afterward.

Quick Check

Proving Fewer Duplicate Lab Tests

Quick check. Larkfield's business case says the new record will cut duplicate lab tests. What must happen before go-live, so that claim can be proven later? Pause, and decide. Record today's duplicate-test rate. Without that starting point, no later number can show the change, and the benefit will eventually be assumed not to exist. The alert is tempting, because it might really cut duplicates. But it's a way to deliver the benefit, not a way to prove it.

Case Resolved

Protecting What He Can, Escalating One Item

Back to Jamal. He can't move the date, so he narrows the question. He protects training by refusing sessions on short-staffed days, and books final-week sessions with backfill from his own budget. He protects testing at no cost, by sending the testers his department's three most complex real scenarios. And he records the ED's current wait times and duplicate tests before go-live. What he can't absorb is losing optimization. So he escalates that one item, in writing: not a new date, but informatics time set aside for the eight weeks after go-live. He accepts the trade. He's spent his credibility on one issue instead of three. A fixable problem left unfixed for a year is the bigger harm.

Key Takeaways

Protect Testing, Training, and Optimization

To recap. Informatics is getting the right fact to the right person when a decision is made. Five system types, linked by integration, and interoperability that keeps the meaning. Configuration is policy, so the people who live with it should shape it. Protect testing, training, and optimization: they're cut first and missed most. And capture a baseline before go-live, or no benefit can be proven.

About Healthcare Organization and Management at UPI Study

Healthcare Organization and Management (Health 302) is a self-paced online course of 105 video lessons in 18 chapters, from health systems and the law to ethics, leadership, teams, strategy, informatics, finance, quality, human resources, marketing and evidence-based practice. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Health courses Every course with PRO →

Why take it here

Why students take Healthcare Organization and Management with UPI Study

How hospitals and clinics are runHealthcare Organization and Management covers how care organizations are led and run: health law and ethics, leadership and teams, strategic planning, health informatics, budgets, quality improvement, staffing and marketing. It is a core course in healthcare administration and health management degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Healthcare Organization and Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Hospital Information Systems: Implementation and Data

What is the difference between integration and interoperability in health IT?
Integration connects systems inside one organization so data entered in one appears in another. Interoperability is broader: systems exchanging information and using it with its meaning intact. A message can arrive perfectly and still be useless if the receiver cannot tell what a field meant. Many hospitals route connections through an interface engine that translates between systems.
What are HL7, FHIR, LOINC, and SNOMED CT used for?
HL7 and its newer FHIR standard are messaging standards that govern structure: which fields appear, in what order, with what meaning. LOINC and SNOMED CT are clinical terminologies that govern content, with LOINC coding lab tests and SNOMED CT coding clinical terms. Coded data can be counted, compared, and used to trigger decision support far more reliably than free text.
Why do EHR implementations fail?
Most failures are not technical. Four patterns recur: an unrealistic timeline protected by cutting other work, configuration that ignores how work actually flows, compressed training that is too short, too early, or on the wrong version, and unfunded optimization, which leaves problems found in live use unfixed. Configuration, testing, and training are often cut first because cutting them looks free at the time.
What is benefits realization for a hospital IT system?
Benefits realization means stating before an investment what improvements it should produce, then measuring whether they happened. It needs a named benefit stated as a measurable change, a baseline captured before go-live, an owner accountable for the change, and a scheduled review. The baseline is the step most often missed, and it cannot be recovered after go-live.

About the Healthcare Organization and Management course

How many college credits is Healthcare Organization and Management?
Healthcare Organization and Management (Health 302) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Healthcare Organization and Management cost and what is included?
$250, paid once, with lifetime access: all 105 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Healthcare Organization and Management take?
It is self-paced with no deadlines. The 105 lessons total about 17 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Healthcare Organization and Management.

105 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Healthcare Organization and Management →Download the syllabusEvery course with PRO →
Healthcare Organization and Management
3 credits · NCCRSEnroll →