BUSI 505 Week 4 Discussion Board Forum 2 Example

Discussion Board Forum 2: Interoperability and Health Information Exchange

BUSI 505 Healthcare Informatics, Discussion Board Forum 2

Thread by [Student Name]

The hospital, its exchange data and the classmates are composites; the textbooks, Scripture and the peer-reviewed sources cited are real.

Two years ago our hospital connected its electronic health record to the statewide health information exchange. The project met every technical milestone: the interface passed testing, our records flowed to the exchange and clinicians could query records from other hospitals and clinics. Yet when our informatics team reviewed usage last spring, emergency physicians had queried the exchange in only a small fraction of visits, even for patients known to receive care elsewhere. Staff still called other emergency departments for records, waited for faxes and repeated computed tomography scans that had been done elsewhere days earlier. We had achieved interoperability on paper but not at the bedside. The cost was real: repeated scans exposed patients to extra radiation, added hours to emergency department stays and generated charges insurers often questioned. Leaders who had celebrated the go-live were surprised to learn how little the connection was used.

Nelson and Staggers (2014) describe interoperability at several levels, from the technical ability to send data to the semantic ability of the receiving system to understand it, and they stress that standards make exchange possible but do not guarantee it is useful. Braunstein (2014) describes health information exchange as a way to assemble a complete picture of a patient across settings, but that picture has value only if a clinician can see it at the moment of decision. Our exchange met the technical level; it failed the practical one, because the data were hard to reach and harder to scan in a busy shift. Clinicians had to leave the record, log in to a separate portal with a different password and search for the patient again, then scroll through dozens of documents to find the one result they needed, all while other patients waited.

Research describes the same pattern in other regions. Turbow et al. (2025) surveyed 276 internal medicine and emergency clinicians across eight Atlanta health systems. Although most reported using the exchange daily for laboratory results, notes and imaging reports, they named important barriers: 66.4% said needed information was often unavailable, 45.5% said using the exchange added time to patient care and 31.6% said it was simply easier to reorder a test. Dixon et al. (2025) interviewed 21 emergency clinicians across health systems in a mature statewide network and found that all valued exchange data for decisions and preferred it to phone calls and faxes. The most important facilitator of routine use was ease of access, especially single sign-on from within the electronic record, so that clinicians did not need a separate login.

For our hospital, these findings suggest three changes. First, embed the exchange in the record through single sign-on and a button in the emergency department workflow. Second, work with the exchange to present a concise summary, recent encounters, results, imaging and medications, rather than a long list of documents, so that the most useful information appears first. Third, measure what matters: exchange queries per emergency visit, repeat imaging within 30 days of an outside study and clinician satisfaction with the tool. Sharing these measures with emergency department leaders each month would keep attention on use rather than on connection, and a short training session showing clinicians where the new button sits would help the change take hold. Interoperability is not achieved when data can move; it is achieved when a busy clinician actually sees them in time to change a decision.

Paul describes the church as a body joined and held together by every joint, growing as each part does its work (English Standard Version Bible, 2001/2016, Ephesians 4:16). A health system is connected in the same way only when information flows to the person who needs it, at the moment it is needed.

Reply to Kayla

Kayla, you asked whether hospitals still need regional health information exchange organizations now that electronic record vendors and national networks can exchange data directly. Your question reflects a real shift in the market, as large vendors have built their own networks that connect thousands of organizations using the same software. It is a fair question, since many hospitals pay membership fees to regional organizations while also relying on vendor networks, and recent evidence suggests the answer is that these organizations remain useful but are no longer the only path. Richwine et al. (2025) linked national hospital survey data for about 2,200 hospitals with detailed information about exchange organizations and found that hospitals participating in an exchange organization were significantly more engaged in clinical information exchange, public health reporting and the exchange of information about patients' social needs. However, among participating hospitals, the specific services an organization offered were not strongly related to how much hospitals exchanged, which suggests that participation itself, or the commitment it reflects, matters more than any single feature. Turbow et al. (2025) remind us that access alone does not guarantee use, since clinicians cited missing information and added time as barriers even where exchange was available. A hospital evaluating its membership should therefore ask not only how many partners it can reach but how often its clinicians find what they need, and that requires usage data most organizations do not routinely review. Nelson and Staggers (2014) note that exchange infrastructure must serve multiple purposes, from care coordination to public health, and Braunstein (2014) describes community exchange as particularly valuable for connecting organizations that do not share a vendor, such as small independent practices, behavioral health agencies and long-term care facilities. For a hospital, then, the practical choice may not be either regional exchange or vendor network but both, with each serving different partners: vendor networks for large systems on the same platform and regional organizations for community clinics, public health and social service agencies. Leaders should review the costs and the use of each path every year rather than renewing memberships out of habit. The Preacher notes that a cord woven from three strands does not easily snap (English Standard Version Bible, 2001/2016, Ecclesiastes 4:12), and multiple exchange paths can make a community's information network more resilient when any single connection fails or a partner changes vendors. Would your organization keep its regional exchange membership if its vendor network already covered most of its hospital partners? The answer may depend on how much the hospital values connections to public health and community partners that vendor networks often miss. As programs addressing housing, food and transportation needs grow, those community connections may become more valuable than they are today, which argues for keeping them in place while their use develops.

Reply to Victor

Victor, you raised an interesting extension of interoperability beyond records exchange: connecting the electronic health record to medical devices such as smart infusion pumps. It is a good reminder that interoperability is not only about sharing records between organizations but also about connecting systems within a single hospital room. That kind of integration aims to remove manual steps where errors occur, since without it nurses must program pumps by hand and document infusions separately. Manual programming invites keystroke errors, such as a misplaced decimal, and separate documentation creates gaps between what the pump delivered and what the chart shows. Kuitunen et al. (2026) systematically reviewed seven U.S. studies of two-way integration between records and smart pumps and found mainly positive effects on medication errors, compliance with drug library safety software and workflow efficiency, along with some evidence of more accurate charging for infusions. They cautioned, however, that the evidence was of low quality because most studies were observational and concentrated in a few U.S. settings, which limits how confidently a hospital can expect the same results. The authors called for controlled studies and better economic data before organizations commit large sums. Dixon et al. (2025) found that ease of use, especially avoiding extra logins and steps, was the key to clinicians' adoption of exchange tools, and the same principle likely applies to pump integration: if the integrated workflow is slower or less reliable than manual programming, nurses will find workarounds. Nelson and Staggers (2014) describe device integration as part of the broader push for interoperable systems that reduce redundant documentation, and Braunstein (2014) notes that standards for device data have lagged behind those for clinical documents. For managers, the decision to invest in pump integration should include a clear plan to measure errors, compliance and nurse time before and after, since the published evidence cannot yet guarantee results. The investment is substantial, often involving new pumps, wireless upgrades and interface fees, so a business case should include safety benefits as well as any gains in charge capture. Proverbs says the Lord detests mismatched weights and dishonest scales (English Standard Version Bible, 2001/2016, Proverbs 20:23), and accurate measurement, whether of medication doses or of a project's results, is part of faithful stewardship. Integration that sends the correct dose straight from the order to the pump is, in a small way, an expression of that same care for accuracy. Would your hospital pilot integration on one unit with careful measurement before a system-wide rollout? Starting small would also reveal workflow problems, such as barcode failures or wireless gaps, that are much cheaper to fix early, and it would give the nurses who use the pumps a voice in the design before it spreads.

References

Braunstein, M. L. (2014). Contemporary health informatics. AHIMA Press.

Dixon, B. E., Ghimire, U., Richter, B., Bowditch, C., Rahurkar, S., Finnell, J. T., & Vest, J. R. (2025). Influences on emergency clinician use of health information exchange: Interview study. JMIR Medical Informatics, 13, e75865. https://doi.org/10.2196/75865

English Standard Version Bible. (2016). Crossway. (Original work published 2001)

Kuitunen, S., Alves, B. L., Peitsoma, H., Saleem, M. Z., Schepel, L., & Holmström, A. R. (2026). Effects of a bidirectional interoperability between electronic health records and smart infusion pumps in hospital settings: A systematic review. BMJ Health & Care Informatics, 33(1), e101723. https://doi.org/10.1136/bmjhci-2025-101723

Nelson, R., & Staggers, N. (2014). Health informatics: An interprofessional approach. Elsevier Mosby.

Richwine, C., Strawley, C., Chang, W., & Everson, J. (2025). Assessing the value of health information exchange organizations to hospital interoperability. Health Affairs Scholar, 3(7), qxaf133. https://doi.org/10.1093/haschl/qxaf133

Turbow, S. D., Kim, P. H., Vaughan, C. P., Ali, M. K., Clevenger, C. K., & Perkins, M. M. (2025). Perceptions of and barriers to health information exchange use among emergency medicine and inpatient internal medicine clinicians in the Atlanta, Georgia metropolitan region. JAMIA Open, 8(5), ooaf131. https://doi.org/10.1093/jamiaopen/ooaf131