HSN/376 Week 1: Nursing Informatics and the DIKW Framework, sample paper

One Oxytocin Titration Read Four Ways: Data, Information, Knowledge and Wisdom at a Labor Nurse's Bedside

[Student Name]

University of Phoenix

HSN/376: Health Information Technology for Nursing

Week 1 Assignment

[Instructor Name]

[Date]

The birthing center, the patient and the tracing are a composite written for a model paper.

Labor and delivery nurses produce data constantly. During an oxytocin infusion, I document contraction frequency, duration and strength, the fetal heart rate baseline, variability and any decelerations, the maternal blood pressure and pulse and the infusion rate, every fifteen to thirty minutes. Most of it goes into the electronic record and is rarely looked at again. This paper uses one composite infusion to show how those entries move from data to wisdom and argues that the movement is the heart of nursing informatics.

What Nursing Informatics Is

In the professional scope and standards published by the American Nurses Association (2022), nursing informatics is a specialty that joins nursing science with information and analytic sciences so that the data, information, knowledge and wisdom of nursing practice can be identified, managed and shared. The definition is broader than technology. A nurse practices informatics whenever she decides what to record, how to organize it and what it means, whether or not she ever works in an informatics department.

The data, information, knowledge and wisdom framework, often shortened to DIKW, describes that process as a series of steps. Matney et al. (2011) traced the framework's philosophical roots and argued that wisdom, the top level, belongs in nursing informatics because nursing decisions are applied to particular patients in particular situations, which requires more than knowledge alone. The framework's point is that nothing on a monitor becomes safe care until a nurse has carried it through every level.

The Case

Ms. L., a 29-year-old in her first pregnancy at 40 weeks and 5 days, was admitted for induction of labor. After cervical ripening, an oxytocin infusion was started at 2 milliunits per minute and increased by 2 milliunits every 30 minutes under the unit's protocol, which ties each increase to the maternal and fetal response rather than to the clock.

Data: The Separate Entries

At 1330, the monitor and my assessment produced the following separate data points: infusion rate 10 milliunits per minute; six contractions in the last ten minutes; contraction duration 70 to 90 seconds; fetal heart rate baseline 145 beats per minute; moderate variability; two late decelerations in the last twenty minutes; maternal blood pressure 118/72 mm Hg. Each is a fact without context. Six contractions, taken alone, does not say whether labor is going well or badly.

Information: The Data Organized

Organized together and set against the previous hour, the data become information. Over the last 30 minutes, contraction frequency rose from four in ten minutes to six, averaged over the window, which meets the common definition of tachysystole, more than five contractions in ten minutes averaged over thirty minutes. The late decelerations are new; none appeared before 1300. The rise in contractions followed the last increase in oxytocin at 1300. This is the level at which an electronic record can help most, because trend displays and flowsheet views put the numbers side by side, but only if the nurse has entered them consistently and on time.

Knowledge: The Information Interpreted

Knowledge comes from connecting the information with what nurses know from evidence and experience. Oxytocin is classed as a high-alert medication because errors and excessive dosing can cause serious harm, most often through tachysystole that reduces blood flow to the placenta between contractions (Simpson & Knox, 2009). Late decelerations reflect that reduced placental exchange. Knowledge tells me that the pattern at 1330 is a known, predictable result of the drug, that it can progress to fetal compromise and that the first step in response is to reduce or stop the oxytocin. Knowledge also includes the protocol's own rule: no further increase in the presence of tachysystole or a concerning fetal heart rate pattern.

Wisdom: The Decision for This Patient

Wisdom is using that knowledge rightly for this patient at this moment. I stopped the oxytocin, turned Ms. L. to her left side, gave an intravenous fluid bolus as ordered in the protocol and notified the obstetrician. Wisdom also meant judging what not to do. Ms. L. was frightened by the alarm and asked whether something was wrong with her baby. Explaining calmly that her contractions were coming too close together and that stopping the medication usually lets the baby recover was as much a part of the decision as the clinical steps. Within twenty minutes, contractions spaced to four in ten minutes and the late decelerations resolved. Oxytocin was restarted an hour later at half the previous rate.

What the Framework Shows About the Electronic Record

Walking through the framework shows where technology helps and where it cannot. The electronic record and the central monitoring display are strongest at the data and information levels. They collect, store and display values and trends, and they can alert staff when a value crosses a threshold. They are weaker at the knowledge level, where a decision support rule can suggest that tachysystole is present but cannot weigh it against a particular labor. They cannot supply wisdom at all. Clark et al. (2007) showed the value of building knowledge into a structured tool: after a hospital introduced a checklist-based oxytocin protocol that tied dosing to maternal and fetal response, maximum infusion rates fell and fewer newborns had any adverse outcome index, without a longer time to birth.

The framework also shows why documentation matters. If I had charted contractions late or only as "regular," the information level would have been missing, and the pattern would have been harder for me, the next nurse or the obstetrician to see.

Implications for My Practice

Three changes follow for me. First, I will chart contraction frequency as a count averaged over the recommended window, not as a description, because only counts can become information. Second, I will use the record's trend view during every titration, not only when an alarm sounds. Third, when I precept new nurses, I will teach the protocol as a knowledge tool, explaining why each rule exists, rather than as a set of steps to follow.

Conclusion

One oxytocin titration, followed from raw numbers to a bedside decision, shows that nursing informatics is the everyday work of turning bedside numbers into safe decisions. The electronic record helps most at the lower levels, and the nurse is responsible for the upper ones. Week 2 will look more closely at the record itself: what it captures about nursing care and how those data are used.

References

American Nurses Association. (2022). Nursing informatics: Scope and standards of practice (3rd ed.).

Clark, S., Belfort, M., Saade, G., Hankins, G., Miller, D., Frye, D., & Meyers, J. (2007). Implementation of a conservative checklist-based protocol for oxytocin administration: Maternal and newborn outcomes. American Journal of Obstetrics and Gynecology, 197(5), 480.e1-480.e5. https://doi.org/10.1016/j.ajog.2007.08.026

Matney, S., Brewster, P. J., Sward, K. A., Cloyes, K. G., & Staggers, N. (2011). Philosophical approaches to the nursing informatics data-information-knowledge-wisdom framework. Advances in Nursing Science, 34(1), 6-18. https://doi.org/10.1097/ANS.0b013e3182071813

Simpson, K. R., & Knox, G. E. (2009). Oxytocin as a high-alert medication: Implications for perinatal patient safety. MCN: The American Journal of Maternal/Child Nursing, 34(1), 8-15. https://doi.org/10.1097/01.NMC.0000343859.62828.ee