{
  "sim_id": "remote-monitoring-data-flow-graph-model",
  "diagram_name": "Remote Monitoring Data Flow Graph Model",
  "chapter_number": 11,
  "chapter_title": "Specialty Care, Surgery, and Remote Monitoring",
  "chapter_dir": "11-specialty-care-surgery-remote-monitoring",
  "chapter_rel_dir": "chapters/11-specialty-care-surgery-remote-monitoring",
  "library": "vis-network",
  "bloom_level": "Understand<br/>",
  "bloom_verb": "explain, classify<br/>",
  "learning_objective": "Explain how patient-generated data (portal, PRO, wearable) flows through a remote patient monitoring process into a telehealth visit, and classify each node by whether it is patient-originated or system-generated.",
  "completion_status": "validated",
  "quality_score": 100,
  "validated_date": "2026-09-07",
  "implementation_path": "sims/remote-monitoring-data-flow-graph-model/main.html",
  "extracted_date": "2026-09-07",
  "specification": "Type: graph-model\n**sim-id:** remote-monitoring-data-flow-graph-model<br/>\n**Library:** vis-network<br/>\n**Status:** Validated\n\nBloom Taxonomy: Understand<br/>\nBloom Taxonomy Verb: explain, classify<br/>\nLearning objective: Explain how patient-generated data (portal, PRO, wearable) flows through a remote patient monitoring process into a telehealth visit, and classify each node by whether it is patient-originated or system-generated.\n\nPurpose: Show learners the complete graph-model path from a patient's own devices and self-reports through an RPM algorithm to a scheduled telehealth visit, and the separate but related path through the patient portal.\n\nNode types to show (color-coded):\n1. Patient (pink circle) -- the central node\n2. Wearable Device (light blue square) -- properties: device_type, manufacturer\n3. Vital Sign / Biomarker Reading (small light blue circles, shown as a cluster of 3-4) -- properties: value, unit, timestamp\n4. RPM Algorithm (gray gear-shaped node) -- properties: threshold_rule, evaluation_frequency\n5. Alert (orange triangle) -- properties: severity, triggered_at\n6. Telehealth Visit (green circle) -- properties: scheduled_time, modality (video/audio)\n7. Patient-Reported Outcome (purple square) -- properties: instrument_name, score\n8. Patient Portal (dark blue hexagon) -- aggregates PRO and secure messaging\n\nEdge types to show:\n1. Patient --WEARS--> Wearable Device\n2. Wearable Device --GENERATES--> Vital Sign / Biomarker Reading (one edge per reading in the cluster)\n3. Vital Sign / Biomarker Reading --FEEDS--> RPM Algorithm\n4. RPM Algorithm --TRIGGERS--> Alert\n5. Alert --SCHEDULES--> Telehealth Visit\n6. Patient --SUBMITS--> Patient-Reported Outcome\n7. Patient --ACCESSES--> Patient Portal\n8. Patient-Reported Outcome --VISIBLE_IN--> Patient Portal (dashed, showing portal aggregates PRO data)\n\nData Visibility Requirements:\nStage 1: Show only the Patient node and the two paths branching from it unlabeled (toward Wearable Device and toward Patient Portal), so the learner first sees there are two distinct data origins.\nStage 2: On clicking the Wearable Device node, reveal the GENERATES edges to 3-4 concrete Vital Sign / Biomarker Reading nodes with real example values (e.g., heart rate 72, 74, 118, 76 bpm across four timestamps).\nStage 3: On clicking the RPM Algorithm node, show the actual threshold rule being evaluated (e.g., \"alert if heart rate > 100 bpm for 3 consecutive readings\") applied against the visible readings, with the triggering reading highlighted.\nStage 4: On clicking the Alert node, reveal the resulting Telehealth Visit node with its scheduled time, closing the loop back to a human encounter.\nStage 5: On clicking the Patient Portal node, reveal its aggregation of the Patient-Reported Outcome node and a placeholder \"secure messaging\" property, showing the second, parallel path.\n\nInteractive controls:\n- Click any node: opens a side-panel infobox with the node's label, definition, and properties\n- Hover any edge: shows a tooltip naming the relationship type and a one-sentence description\n- Button: \"Play data flow\" -- animates a small pulse traveling from Wearable Device through to Telehealth Visit at a fixed pace, pausing at each node long enough for the infobox to display\n- Zoom and pan enabled\n\nInstructional Rationale: The objective is Understand-level (explain, classify), so per the interaction-pattern guidance this specification favors staged data reveal and concrete values over continuous animation. Showing the actual threshold rule and the specific reading that crosses it (Stage 3) is what lets a learner explain *why* an alert fired rather than simply seeing that one did, and separating the two origin paths (device vs. portal/PRO) supports the classification half of the objective.\n\nImplementation: vis-network JavaScript library with a two-branch layout radiating from the central Patient node; side panel rendered as fixed-position HTML updated via vis-network's click event."
}