Update visualize-ontology-fabric-iq module for publication readiness

- Remove Cardiology references; use ICU, Surgical Services, Emergency Department throughout
- Remove builder framing in units 2, 3, 4
- Rewrite knowledge check: replace 3 builder-concept questions with content-grounded questions
- Fix knowledge check Q3: Cardiology -> Intensive Care Unit
- Set ai_generated_module_assessment: false (human-authored questions in YAML)
- Delete orphaned images: graph-nodes-edges, department-overview, department-instance
- Delete orphaned 8-summary.md duplicate
- Add 10 new screenshots: room-overview, room-instance, room-instance-graph, expand-graph, default-query, query-builder-ribbon, components, query-filter, query-results-views, launch-exercise
- Fix summary: filter example updated to RoomType = Critical Care
- Fix index.yml summary: remove builder framing
- Update level: intermediate -> beginner
- Update ms.date to 04/13/2026 across all unit YAMLs and index.yml

Author: theresa-i

learn-pr/wwl-data-ai/visualize-ontology-fabric-iq/1-introduction.yml

@@ -4,7 +4,7 @@ title: Introduction
 metadata:
   title: Introduction
   description: Introduction to visualizing ontology data with Microsoft Fabric IQ using the relationship graph and Query builder to explore connected business concepts.
-  ms.date: 03/30/2026
+  ms.date: 04/13/2026
   author: theresa-i
   ms.author: theresai
   ms.topic: unit

learn-pr/wwl-data-ai/visualize-ontology-fabric-iq/2-explore-ontology.yml

@@ -4,7 +4,7 @@ title: Explore the ontology
 metadata:
   title: Explore the Ontology
   description: Learn how to open the entity type overview, view entity instances, and inspect individual entity instance details and relationships in Microsoft Fabric IQ.
-  ms.date: 03/30/2026
+  ms.date: 04/13/2026
   author: theresa-i
   ms.author: theresai
   ms.topic: unit

learn-pr/wwl-data-ai/visualize-ontology-fabric-iq/3-visualize-relationships.yml

@@ -4,7 +4,7 @@ title: Visualize relationships in the relationship graph
 metadata:
   title: Visualize Relationships in the Relationship Graph
   description: Learn how to expand the relationship graph, run the default query to see entity instances as nodes and relationships as edges, and navigate connected business concepts in Microsoft Fabric IQ.
-  ms.date: 03/30/2026
+  ms.date: 04/13/2026
   author: theresa-i
   ms.author: theresai
   ms.topic: unit

learn-pr/wwl-data-ai/visualize-ontology-fabric-iq/4-query-ontology-query-builder.yml

@@ -4,7 +4,7 @@ title: Filter and explore with the Query builder
 metadata:
   title: Filter and Explore with the Query Builder
   description: Learn how to use the Query builder in Microsoft Fabric IQ to add filters, control components, explore cross-source data, and interpret results in Diagram, Card, and Table view.
-  ms.date: 03/30/2026
+  ms.date: 04/13/2026
   author: theresa-i
   ms.author: theresai
   ms.topic: unit

learn-pr/wwl-data-ai/visualize-ontology-fabric-iq/5-exercise-query-ontology.yml

@@ -3,8 +3,8 @@ uid: learn.wwl.visualize-ontology-fabric-iq.exercise-visualize-ontology
 title: Exercise - Visualize ontology data with Microsoft Fabric IQ
 metadata:
   title: Exercise - Visualize Ontology Data with Microsoft Fabric IQ
-  description: Practice visualizing entity instances, exploring relationship graphs, and filtering data to answer business questions using the Fabric IQ ontology preview experience.
-  ms.date: 03/30/2026
+  description: Practice visualizing entity instances, exploring relationship graphs, and seeing data through property charts and visualizations in Microsoft Fabric IQ.
+  ms.date: 04/13/2026
   author: theresa-i
   ms.author: theresai
   ms.topic: unit

learn-pr/wwl-data-ai/visualize-ontology-fabric-iq/6-exercise-query-ontology.yml

@@ -4,9 +4,9 @@ title: Module assessment
 metadata:
   title: Module Assessment
   module_assessment: true
-  ai_generated_module_assessment: true
+  ai_generated_module_assessment: false
   description: Check your knowledge of visualizing and querying ontology data with Microsoft Fabric IQ.
-  ms.date: 03/30/2026
+  ms.date: 04/13/2026
   author: theresa-i
   ms.author: theresai
   ms.topic: unit
@@ -17,47 +17,47 @@ durationInMinutes: 5
 quiz:
   title: "Check your knowledge"
   questions:
-  - content: "A data analyst opens the entity type overview for the Patient entity type and notices the entity instances table shows fewer rows than the source lakehouse table. What is the most likely cause?"
+  - content: "In the relationship graph, what does a labeled arrow between two nodes represent?"
     choices:
-    - content: "The entity type has too many properties configured."
-      isCorrect: false
-      explanation: "Incorrect. The number of properties doesn't affect how many instances are loaded. The entity type key and binding configuration determine instance count."
-    - content: "The entity type key doesn't correctly match a unique column in the source table."
+    - content: "A relationship connecting two entity instances, such as a patient admitted to a room."
       isCorrect: true
-      explanation: "Correct. The key configuration determines how the system identifies and loads entity instances from the source data. A mismatched or missing key prevents instances from loading correctly."
-    - content: "The relationship graph tile hasn't been expanded yet."
+      explanation: "Correct. Edges are the named, directed connections between nodes—for example, the admittedTo edge connects a Patient instance to a Room instance."
+    - content: "A property of one of the connected entity types."
+      isCorrect: false
+      explanation: "Incorrect. Properties are attributes stored on a single node, such as RoomNumber or RoomType. Edges are the arrows that connect two separate nodes."
+    - content: "An entity type that groups related instances together."
       isCorrect: false
-      explanation: "Incorrect. The relationship graph tile is separate from the entity instances table and doesn't affect how instances are loaded."
-  - content: "In the relationship graph, a Room node shows no edges connecting it to any Patient nodes, even though the source lakehouse table shows patients assigned to that room. What does this indicate?"
+      explanation: "Incorrect. Entity types group instances of the same kind, such as all rooms or all patients. Edges are the directed connections between individual instances."
+  - content: "What does the entity instances table on the entity type overview page show?"
     choices:
-    - content: "The Patient entity type has too many active filters applied."
+    - content: "The actual records loaded from the bound source data for that entity type."
+      isCorrect: true
+      explanation: "Correct. The entity instances table shows the real rows from the source lakehouse or eventhouse table, one row per instance, with columns matching the entity type's configured properties."
+    - content: "A summary of all relationships configured for that entity type."
       isCorrect: false
-      explanation: "Incorrect. Filters narrow query results but don't affect whether relationship edges exist in the graph structure."
-    - content: "The Room entity type needs to be refreshed separately from the Patient entity type."
+      explanation: "Incorrect. Relationships appear in the relationship graph tile on the same page. The entity instances table shows the actual data records."
+    - content: "The schema showing how the entity type connects to others in the ontology."
       isCorrect: false
-      explanation: "Incorrect. Refresh applies to the graph model as a whole, not to individual entity types separately."
-    - content: "The relationship binding isn't finding matching records based on the configured entity type keys."
-      isCorrect: true
-      explanation: "Correct. Edges only appear in the graph when the relationship binding matches keys between entity instances. If source data exists but edges don't appear, the relationship binding configuration may not be matching records correctly."
-  - content: "You want to query the ontology for patients assigned to rooms in the Cardiology department. Which combination of Query builder controls do you need?"
+      explanation: "Incorrect. The relationship graph tile shows how entity types connect to each other. The entity instances table shows the actual data rows for this entity type."
+  - content: "You want to query the ontology for patients assigned to rooms in the Intensive Care Unit department. Which combination of Query builder controls do you need?"
     choices:
-    - content: "Add a filter for DepartmentName = Cardiology and ensure Department, Room, and Patient nodes are enabled in the Components pane."
+    - content: "Add a filter for DepartmentName = Intensive Care Unit and ensure Department, Room, and Patient nodes are enabled in the Components pane."
       isCorrect: true
-      explanation: "Correct. A filter on the Department entity type narrows results to Cardiology, while enabling the appropriate node and edge types in the Components pane controls what appears in the graph results."
+      explanation: "Correct. A filter on the Department entity type narrows results to Intensive Care Unit, while enabling the appropriate node and edge types in the Components pane controls what appears in the graph results."
     - content: "Remove all components except Patient nodes and run the default query."
       isCorrect: false
       explanation: "Incorrect. Removing Department and Room components from the query would exclude the entity types needed to trace the connection path from Cardiology to patients. All three node types are required."
     - content: "Switch to Table view and add a filter for each entity type separately."
       isCorrect: false
       explanation: "Incorrect. The view type (Diagram, Card, Table) only changes how results are displayed, not which entities are returned. Switching views doesn't affect query filtering."
-  - content: "A clinical analyst adds three new patients to the Lamna Healthcare lakehouse. She then opens the ontology and doesn't see the new patients in the entity instances table. What should she do?"
+  - content: "After running a query, you want to compare RoomType and DepartmentId values across all returned rooms at once. Which view is most useful?"
     choices:
-    - content: "Modify the Patient entity type's property definitions to pick up the new records."
+    - content: "Table view, because results appear in rows and columns with one row per instance."
+      isCorrect: true
+      explanation: "Correct. Table view organizes results in a grid—one row per instance, one column per property—making it easy to compare values like RoomType or DepartmentId across many rooms at once."
+    - content: "Diagram view, because you can select each node to inspect its properties."
       isCorrect: false
-      explanation: "Incorrect. Changing property definitions triggers a schema refresh but doesn't help here—new data rows aren't detected automatically, only structural changes to the ontology are."
-    - content: "Open the Query builder and clear the active filters."
+      explanation: "Incorrect. Diagram view shows the graph structure with nodes and edges, but you must select each node individually to see its properties—not ideal for comparing values across multiple instances."
+    - content: "Card view, because it displays each instance with property values listed inline."
       isCorrect: false
-      explanation: "Incorrect. Clearing Query builder filters doesn't affect the entity instances table, which reflects the last ingested data regardless of any filters applied in the graph view."
-    - content: "Manually refresh the graph model from the workspace to re-ingest the updated source data."
-      isCorrect: true
-      explanation: "Correct. When data changes in an upstream lakehouse or eventhouse, the graph model doesn't update automatically. Manually triggering a refresh (or waiting for a scheduled refresh) re-ingests the updated source data and makes the new patient records visible."
+      explanation: "Incorrect. Card view is useful for scanning individual records, but comparing specific property values across many instances is easier in Table view where properties align in columns."

learn-pr/wwl-data-ai/visualize-ontology-fabric-iq/6-knowledge-check.yml

@@ -4,7 +4,7 @@ title: Summary
 metadata:
   title: Summary
   description: Summary of visualizing and querying ontology data with Microsoft Fabric IQ.
-  ms.date: 03/30/2026
+  ms.date: 04/13/2026
   author: theresa-i
   ms.author: theresai
   ms.topic: unit

learn-pr/wwl-data-ai/visualize-ontology-fabric-iq/7-summary.yml

@@ -1,7 +1,7 @@
-Imagine you're a data analyst at Lamna Healthcare. You've spent the past few weeks building an ontology in Fabric IQ. Hospital, Department, Room, Patient, and VitalSignEquipment entity types are defined, bound to the lakehouse and eventhouse, and structurally sound. Now comes the reason you built it.
+Imagine you're a data analyst at Lamna Healthcare. You've built an ontology in Fabric IQ. Hospital, Department, Room, Patient, and VitalSignEquipment entity types are defined, bound to the lakehouse and eventhouse, and structurally sound. Now comes the reason you built it.
 
-The clinical operations manager stops by with a question: "Which rooms in the Cardiology department currently have patients, and which vital sign monitors are active there?" Before the ontology, answering that question meant writing a multi-table SQL join—linking patient assignment records to rooms, rooms to departments, and departments to equipment logs. With the ontology in place, you can explore the answer visually by following named relationships across your semantic layer, no joins required.
+The clinical operations manager stops by with a question: "Which rooms in the Intensive Care Unit currently have patients, and which vital sign monitors are active there?" Before the ontology, answering that question meant writing a multi-table SQL join—linking patient assignment records to rooms, rooms to departments, and departments to equipment logs. With the ontology in place, you can explore the answer visually by following named relationships across your semantic layer.
 
-In this module, you open the entity type overview to inspect the entity instances that your data bindings have populated. You see individual Department, Room, and Patient records drawn from your OneLake sources. You expand the relationship graph to visualize how those instances connect—patients assigned to rooms, rooms belonging to departments, equipment monitoring patients. You use the Query builder to add filters for specific property values, control which entity types and relationship types appear using the Components pane, and explore data that spans your lakehouse and eventhouse without writing any SQL.
+In this module, you open the entity type overview to inspect the entity instances that your data bindings have populated. You see individual Department, Room, and Patient records are drawn from your OneLake sources. You expand the relationship graph to visualize how those instances connect—patients assigned to rooms, rooms belonging to departments, equipment monitoring patients. You use the Query builder to add filters for specific property values, control which entity types and relationship types appear using the Components pane, and explore data that spans your lakehouse and eventhouse without writing any SQL.
 
 By the end of this module, you're equipped to turn the ontology into answers: exploring connected healthcare data the way business users think about it.