WGU C792 Task 2: Entity Relationship Diagram (ERD) Reflection 100 correct

Entity Relationship Diagram (ERD) Reflection This task gave me hands-on experience modeling healthcare data and helped me better understand how informatics supports safe, effective care. In this reflection, I will describe the evolution of my thinking, interoperability, clinical decision support, and the roles of a nurse informaticist regarding databases and ERDs. Evolution of Thought My understanding of data modeling was minimal before starting this course. I had never heard of ERDs. Even with reviewing the coursework, I still had to look for more information to understand it better. At first, it felt overwhelming. But it made more sense once I started building my diagram and seeing how the tables connected. My biggest lightbulb moment was learning the difference between one-to-many and many-to-many relationships between the tables. That helped me understand how to avoid duplication and why using foreign keys matters. For example, by using look-up tables for symptom severity and recovery times, I could simplify the design and make it easier to update or expand. This task gave me a new appreciation for how much work goes into building databases. Building databases requires you to be one step ahead in thinking about what data you might need to pull out in the future, not just what you need right now. After completing this task, I feel more confident with the basics of ERDs and how they can be applied in real healthcare settings. Survey Interoperability One of the things I’ve learned is just how vital Interoperability is when it comes to patient care. When different electronic health record (EHR) systems can “talk” to each3 Downloaded by patrick kaylian () other, it helps improve provider communication and makes care more seamless for the patient. Interoperability ensures continuity of care and improves communication between healthcare facilities and interdisciplinary teams. Data, like asthma survey results, can be structured into a format that can be understood and exchanged on both ends, even if different vendors created them through standards like Health Level 7 (HL7) and Fast Healthcare Interoperability Resources (FHIR). (Health Level 7 (HL7) Fast Healthcare Interoperability Resources (FHIR) | HealthIT.gov, n.d.)