In the context of conceptual database modeling, consider a scenario where you are designing a database for a complex healthcare system that needs to store patient records, medical diagnoses, treatments, and billing information. You decide to use the Entity$-$Relationship Diagram $($ERD$)$ approach.

You have identified entities such as "Patient," "Diagnosis," "Treatment," and "Invoice." Each entity has various attributes. However, you face a significant challenge in modeling the relationships among these entities due to their intricate dependencies. Specifically, patients can have multiple diagnoses, treatments, and invoices, and treatments can be related to multiple diagnoses. Additionally, billing information depends on both diagnoses and treatments.

Which advanced modeling technique or concept would you employ to handle these complex relationships effectively, and how would you apply it to this database design?

Group of answer choices

Nested ERDs: You would create multiple ERDs, each focusing on a subset of relationships, and then nest them within the main ERD to represent the complex dependencies.

Bridge Tables: You would use bridge tables $($also known as junction or associative tables$)$ to handle many$-$to$-$many relationships, allowing you to link patients to diagnoses and treatments efficiently.

Hierarchical Modeling: You would design the database with a hierarchical structure, where each entity is organized in a tree$-$like fashion, representing the dependencies and relationships.

Recursive Relationships: You would implement recursive relationships within the ERD to handle the complex dependencies between entities such as patients and treatments.

Denormalization: You would denormalize the database to reduce complexity, combining entities and attributes into a single table to simplify the modeling of relationships.