The ambulatory system now receives electronic summary of ED and hospital stay documentation with concern tracking identifications. System A – Ambulatory Office System Time Event Description Model Action 3/20/2014, Concern ID A.4 new. But, the Create Concern A.4 – 9:40am Hospital Follow Up physician then reads the Merge Concerns electronic discharge documentation from hospital and merges that history. He recognizes the hospital Discharge Dx “Pneumococcal ID B.1) Pneumonia” (concern represents the item on his problem list called “Possible ID A.2). He CAP” (Concern merges “Pneumococcal onto Pneumonia” “Possible HealthConcern is CAP”. His now named “Pneumococcal Pneumonia”. 3/20/2014, the hospitals Type Merge Concerns “Diabetes 1” 9:40am (Concern ID B.2) is his A.1/B.2 Type ID “Diabetes 1” (Concern A.1) 3/20/2014, creates problem A.5 from the Create Concern A.5 9:40am hospital B.5 as a new problem. Merge Concerns This history from the hospital is A.5/B.5 already there 3/20/2014, 10:15 Office Spirometry: Add Event to A.5 am <report> 3/20/2014, EncounterNote.Exam: Concern ID A.2 and/or A.5, Add Event to A.2 10:15am Wheeze depending on how/where he OR records this, provides additional Add Event to A.5 problem (concern) tagging and system function to automatically bind known relevant relationships 3/20/2014, Concern ID A.2 The naming Add Event to A.2 – 10:15am Recent observation looks the same as Pneumococcal the hospital, but this is an Pneumonia. additional time point where this is known state/name of this concern. The observation timing and verification is important for decision support systems to know if the problem is stale.
The ambulatory system now receives electronic summary of ED and hospital stay documentation with concern tracking identifications. System A – Ambulatory Office System Time Event Description Model Action 3/20/2014, 9:40am Hospital Follow Up Concern ID A.4 – new. But, the physician then reads the electronic discharge documentation from hospital and merges that history. He recognizes the hospital Discharge Dx “Pneumococcal Pneumonia” (concern ID B.1) represents the item on his problem list called “Possible CAP” (Concern ID A.2). He merges “Pneumococcal Pneumonia” onto “Possible CAP”. His HealthConcern is now named “Pneumococcal Pneumonia”. Create Concern A.4 Merge Concerns 3/20/2014, 9:40am the hospitals “Diabetes Type 1” (Concern ID B.2) is his “Diabetes Type 1” (Concern ID A.1) Merge Concerns A.1/B.2 3/20/2014, 9:40am creates problem A.5 from the hospital B.5 as a new problem. This history from the hospital is already there Create Concern A.5 Merge Concerns A.5/B.5 3/20/2014, 10:15 am Office Spirometry: <report> Add Event to A.5 3/20/2014, 10:15am EncounterNote.Exam: Wheeze Concern ID A.2 and/or A.5, depending on how/where he records this, provides additional problem (concern) tagging and system function to automatically bind known relevant relationships Add Event to A.2 OR Add Event to A.5 3/20/2014, 10:15am Recent Pneumococcal Pneumonia. Concern ID A.2 – The naming observation looks the same as the hospital, but this is an additional time point where this is known state/name of this concern. The observation timing and verification is important for decision support systems to know if the problem is stale. Add Event to A.2