NR 640B Week 3 Site Orientation Write-Up Example

Site Orientation Write-Up: The Health System in Facts, Its Clinical Systems by Purpose, Where Informatics Sits and the Path a Nursing Request Takes

Student Name

College of Nursing, Chamberlain University

NR 640B: Informatics Nurse Specialist Practicum I

Instructor Name

Month Day, Year

Site Orientation Write-Up: The Health System in Facts, Its Clinical Systems by Purpose, Where Informatics Sits and the Path a Nursing Request Takes

The Organization

Three hospitals make up the system's inpatient side: the main campus, with 420 beds and a level II trauma center, and two smaller community hospitals of 90 and 60 beds. The system is not-for-profit. It also runs 22 primary and specialty care clinics and a home health agency. About 7,800 employees, of whom around 2,600 are registered nurses. Source: system fact sheet on the intranet of July.

Service lines at the main campus include cardiac, orthopedics, oncology, women's and children's, behavioral health and a 28-bed adult intensive care unit. The community hospitals provide medical-surgical, emergency and obstetric care, with critical patients transferred to the main campus. Source: same fact sheet.

Systems, Grouped by Purpose

Core record: one electronic health record across all three hospitals and the clinics, upgraded by the vendor four times a year. Nursing documentation, orders, medication administration and the patient portal all sit inside it. Source: preceptor, 9 September.

Medication systems beside the record: barcode medication administration through the record's own module; automated dispensing cabinets on every unit; smart infusion pumps that receive orders from the record at the main campus only. Extending pump integration to the two community hospitals is a live project. Source: project list, informatics shared drive.

Communication: a nurse call system and a secure messaging phone carried by each nurse, linked so that call lights and selected alerts reach the phone. Source: preceptor.

Specialty systems: a fetal monitoring surveillance system in labor and delivery, an anesthesia record in the operating rooms and a separate behavioral health scheduling tool. Each passes some data to the main record through interfaces. Source: interface list, informatics shared drive.

Data and reporting: an enterprise data warehouse refreshed nightly and a reporting tool used by the analytics team. Source: reporting manager, by email, 11 September.

Downtime: a read-only backup system on a dedicated computer on each unit, refreshed every two hours. Source: downtime drill, 2 September.

Where Informatics Sits

On the chart, the clinical informatics team sits under nursing: its leader, the CNIO, answers to the CNO, and a secondary reporting line runs across to the CIO. Of the nine people, five are specialists, each assigned a cluster of service lines; two are analysts with build rights; one runs training. A three-person physician informatics group answers instead to the CMO, and both groups sit together at the optimization meeting. Source: organizational chart as of July.

Technical build for larger changes is done by the information technology department's application analysts, who report to the chief information officer. That means nursing informatics can design and test but depends on another department for some builds.

The Path a Request Takes

1. A nurse or manager submits a request through the information technology service portal, choosing "clinical documentation change" as the category.

2. A clinical analyst triages it within two business days, sizing it as small, under eight build hours, or large.

3. Small requests join the nursing optimization queue. The specialist for that service line reviews each one with the requester, often sending it back with questions, as happened with the fall-risk request in week one.

4. Once a month, the optimization meeting ranks the queue. The CNIO chairs it, and nursing, pharmacy, physician informatics and quality each send someone. It approves the next items for build.

5. Large requests go to project intake and then to the information technology steering committee, which meets quarterly.

6. Every change, small or large, passes through the change advisory board, which meets each Tuesday and decides whether a tested change may move to production and on what date.

7. Around each vendor upgrade, a build freeze applies: the next runs from 18 January to 14 February 2027. Source: Clinical Systems Change Management Policy in its April revision; preceptor, 9 September; observation of the optimization meeting, 3 September.

What the Path Means in Practice

The preceptor estimated that a small request takes two to four months from submission to production, mostly in the queue. At the time of writing the nursing queue held 64 open requests, the oldest 14 months old. Requests that touch medication or alerts take longer, because pharmacy must review them. The long wait has a side effect the preceptor described: units sometimes build their own paper workarounds while they wait, which is a pattern seen elsewhere when systems do not match the work (Unertl et al., 2010).

Why the Path Matters for This Practicum

Any idea the practicum develops will either join the queue or sit outside it. Knowing the path in advance shows that a small analytical piece of work, which needs no build hours, can move faster than any build request, and that the optimization meeting is the place where its results would be heard. It also shows that changes are tested and approved separately, which protects against the unintended effects of small changes reported in the literature (Ash et al., 2004).

People the Student Will Work With

The preceptor; the chief nursing informatics officer as chair of the optimization meeting; one clinical analyst for testing; the reporting analyst; and the trainer. Each is named by role only in course work.

Sources Used

Every fact above names where it came from, so that a reader at the site could check it and a reader outside could judge how much weight it bears. The intranet fact sheet; the organizational chart; the Clinical Systems Change Management Policy; the informatics shared drive's project list and interface list; conversations with the preceptor on 2 and 9 September; an email from the reporting manager on 11 September; and direct observation of one optimization meeting and one downtime drill. Internal documents are cited by title and date because they cannot be linked.

How This Fits the Literature

Health information systems are usually evaluated across human, organizational and technology dimensions together (Yusof et al., 2008). This write-up follows that shape: people and roles, the governance path and the systems themselves.

What the Write-Up Does Not Cover

Contract details with vendors, budgets and security architecture, none of which the student has access to or needs for the practicum. Each would matter to a new employee, and each is available from other departments if a later objective ever requires it.

References

Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: The nature of patient care information system-related errors. Journal of the American Medical Informatics Association, 11(2), 104-112. https://doi.org/10.1197/jamia.M1471

Unertl, K. M., Novak, L. L., Johnson, K. B., & Lorenzi, N. M. (2010). Traversing the many paths of workflow research: Developing a conceptual framework of workflow terminology through a systematic literature review. Journal of the American Medical Informatics Association, 17(3), 265-273. https://doi.org/10.1136/jamia.2010.004333

Yusof, M. M., Kuljis, J., Papazafeiropoulou, A., & Stergioulas, L. K. (2008). An evaluation framework for health information systems: Human, organization and technology-fit factors (HOT-fit). International Journal of Medical Informatics, 77(6), 386-398. https://doi.org/10.1016/j.ijmedinf.2007.08.011