HIM 425 Module 2 Infrastructure Short Paper Example

What the Record Stands On: Infrastructure and Hosting Options at Cedar Fork Community Health

[Student Name]

Southern New Hampshire University

HIM 425: Healthcare IT Infrastructure and Network Management

Module Two Short Paper

[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 the Record Stands On: Infrastructure and Hosting Options at Cedar Fork Community Health

After a power supply failure took Cedar Fork Community Health's record system down for six hours, leadership asked a simple question: what else could fail? Answering it requires knowing what the record stands on. This paper inventories the health center's infrastructure in layers, identifies the components that pose the most risk and compares three hosting models the health center could adopt when its server is replaced next year.

Layers of Infrastructure

Health IT infrastructure is easiest to understand in layers. At the edge are end-user devices: 96 desktop workstations, 22 laptops used by care managers, label and wristband printers, document scanners, signature pads and the tablets patients use to complete intake forms. Beneath them is the network, which Module Four will examine in detail. Next come servers, the computers that run applications and databases; Cedar Fork has one physical server hosting the record application, its database and the interface engine that exchanges lab results and prescriptions. Storage holds the data, here a single array of disks attached to that server. Software spans the operating systems, the database platform, the record application and the interfaces. The foundation is power and environment: electrical supply, a battery backup unit, cooling and the physical security of the room itself.

Rating the Risks

Each component was rated on how likely it is to fail and how much a failure would disrupt care and documentation. Table 1 summarizes the ratings. The server and storage are single points of failure: one server with one power supply writes to one storage array, so the loss of any part stops every clinic. The battery backup has never been tested under load, and the closet has no dedicated cooling, so a hot summer afternoon is a risk in itself. By contrast, a failed workstation or printer affects one room and can be swapped from spare stock.

Table 1. Infrastructure Components and Risk Ratings

Note. Ratings by the author with Cedar Fork's contracted IT support provider.

Software Layers and Their Dependencies

Software risk is less visible than hardware risk but just as real. Cedar Fork's server runs an operating system version that reaches the end of vendor support next year, after which security patches stop. The database platform is licensed per processor, so any new hardware changes the licensing cost. The interface engine translates lab results and prescriptions between systems, and because it shares the record server, a failure of one takes down the other. Each layer depends on the one beneath it, which means an upgrade at the bottom, such as a new operating system, can force changes all the way up. An inventory that stops at hardware misses these dependencies.

Why Availability Matters

The ratings put availability first because downtime reaches patients. Wang et al. (2016) studied a hospital's pathology laboratory during periods of computer downtime and found that test turnaround slowed during outages and that effects continued after systems returned, as staff worked through backlogs. Cedar Fork saw the same pattern in miniature when a potassium result arrived four hours late. A health center with limited staff has little slack to absorb such delays.

Three Hosting Models

When the server is replaced, Cedar Fork can choose among three models. On-premises hosting means buying new servers and storage and keeping them at the main clinic, as now. Vendor-hosted delivery means the record vendor runs the system in its own data center and the clinics connect over the internet, with the health center paying a monthly fee. Cloud hosting on infrastructure rented from a large provider places the servers in commercial data centers, with Cedar Fork or a contractor managing the software. Table 2 compares them.

Table 2. Hosting Models Compared

Note. Cost figures are estimates from vendor quotes obtained for this analysis.

Security and Legal Considerations

Moving data off-site does not move responsibility. Any vendor or cloud provider that stores protected health information must sign a business associate agreement, and the health center must still perform its own risk analysis. Griebel et al. (2015), in a scoping review of cloud computing in health care, found growing adoption alongside persistent concerns about data security, privacy, legal requirements and reliable availability. Ransomware sharpens those concerns. Neprash et al. (2022) found that ransomware attacks on hospitals, clinics and other care delivery organizations more than doubled from 2016 to 2021, with many attacks disrupting care. A small health center with one closet server and no dedicated security staff is a hard target to defend, which weighs in favor of hosting with a provider that monitors threats continuously, provided the contract spells out backup, recovery times and breach duties.

Early Judgment

The on-premises model offers the most control but repeats the single-closet design that just failed, unless Cedar Fork buys redundant equipment and staff it cannot easily hire. The vendor-hosted model removes most hardware risk and security burden but makes every clinic dependent on its internet links, which are already fragile at two sites. That trade-off points to the central problem Milestone One will define: the choice of hosting cannot be separated from the network that connects the clinics.

Conclusion

Cedar Fork's record stands on layers of devices, network, servers, storage, software and power, and the most serious risks sit where one component supports everything. The three hosting models shift those risks in different ways: on-premises keeps control and burden together, vendor hosting trades hardware risk for network dependence and cloud infrastructure falls between. The next milestone will define the problem precisely so the solution can be chosen on evidence.

References

Griebel, L., Prokosch, H.-U., Köpcke, F., Toddenroth, D., Christoph, J., Leb, I., Engel, I., & Sedlmayr, M. (2015). A scoping review of cloud computing in healthcare. BMC Medical Informatics and Decision Making, 15, Article 17. https://doi.org/10.1186/s12911-015-0145-7

Neprash, H. T., McGlave, C. C., Cross, D. A., Virnig, B. A., Puskarich, M. A., Huling, J. D., Rozenshtein, A. Z., & Nikpay, S. S. (2022). Trends in ransomware attacks on US hospitals, clinics, and other health care delivery organizations, 2016-2021. JAMA Health Forum, 3(12), Article e224873. https://doi.org/10.1001/jamahealthforum.2022.4873

Wang, Y., Coiera, E., Gallego, B., Concha, O. P., Ong, M.-S., Tsafnat, G., Roffe, D., Jones, G., & Magrabi, F. (2016). Measuring the effects of computer downtime on hospital pathology processes. Journal of Biomedical Informatics, 59, 308-315. https://doi.org/10.1016/j.jbi.2015.12.016