Fundamentals of Health Workflow Process Analysis and Redesign

Transcription

1 Fundamentals of Health Workflow Process Analysis and Redesign This material Comp0_Unit3d was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number IU24OC Learning Objectives. Create a process flowchart for a health care system (or system component) using appropriate ISO 5807 symbols and conventions. (Lecture b) 2. Create context and data flow diagrams for a health care system (or system component) using appropriate Yourdon symbols and conventions (Lecture c) 3. Choose the correct scope and detail level for a process flowchart and data flow diagram (Lecture b, c) 4. Read and interpret Gane-Sarson data flow diagram () 5. Read and interpret an entity relationship diagram in crow s foot notation (Lecture e) 6. Read and interpret UML class, activity, and state diagrams (Lecture f) 2 Topics - Gane-Sarson symbols and conventions for process mapping Reading Gane-Sarson data flow diagrams 3

2 Methods for Diagramming Processes Process Aspects ISO 5807 Yourdon Gane- Sarson Context X X Process steps X X X Data flow steps X X X X UML E-R diagram Information content text text X X Data transformation X X X X Flow control and state X text X Roles involved X X X Table 3.4 Methods for Diagramming Processes. Nahm, M, Background Gane-Sarson notation was introduced in Chris Gane and Trish Sarson s 977 book Structured Systems Analysis: Tools and Techniques Gane-Sarson notation is used for data flow diagrams 5 Use Gane-Sarson data flow diagrams show Movement Transformation Storage of data 6 2

3 Simplified On-line Appointment Scheduling Example Patient Patient Web inquiry Accept / decline request Check appointment availability Inquiry / reply Office schedule 2 Check current patient Inquiry / reply Admin. database 7 Gane-Sarson Symbols Entity Entity Double square Process Rounded rectangle Data flow Data store Arrow Open-ended rectangle Symbols used for Gane-Sarson 8 Entities Patient Entity Nurse Entity Nurse Entities Represent people, organizations, or other things that interact with the system Send or consume information If the same entity is shown more than once in a diagram, a diagonal line is added to the lower right-hand corner to visually distinguish it Medical assistant Entity Entity Medical assistant 9 3

4 Process Assess patient Processes transform data Process should be named or described with: Single word (a verb) Phrase Simple sentence Describing what the process does Similar to other notations, a good name will generally consist of a verb-object phrase such as check availability In some cases, the processes are named for a role, an organization, or a machine that performs the process 0 Flow prescription A data flow is a pipe through which data travel Straight lines indicate flow or movement of information Flow names indicate the meaning of the data that moves along the flow Flow can: Represent only one type of data, e.g., request or reply, OR Consolidate several elementary data flows into one flow, Request and reply The same content may have a different meaning in different parts of the system Every line needs an arrow head to indicate direction of the data flow Data Store EMR Collection of data at rest Can be in computerized or noncomputerized format Stores are passive Processes put data in or read data D Claims database 2 4

5 Entities Instead of Event List Gane-Sarson notation does not use event lists Things that stimulate action from a system are indicated by entities 3 Diagram Levels Diagram levels are Roll-up and drill-down Functional decomposition is used to represent each process in more detailed steps / processes Context diagram is highest level As many lower-levels as needed 4 Conventions Meaningful names Number processes and data stores Make sure the DFD is internally consistent and consistent with any associated DFDs Exceptions are shown on lower-level diagrams 5 5

6 Conventions (continued) Size of the shapes should be consistent throughout the diagram This limits the length of the name Color shading for shapes and arrows may be used to visually show different Entities Processes Data stores Flows Arrows in Gane-Sarson are straight and horizontal or vertical 6 Rules for Correctness Entities may not Send data directly to other entities Send data directly to data stores Get data directly from data stores No spontaneous data creation No black holes 7 Maintenance Gane-Sarson is a set of symbols and conventions named for the people who developed it. There is no formal maintenance organization. Individuals use and adapt it to suit their needs. 8 6

7 Summary Gane-Sarson symbols and conventions for process mapping Reading Gane-Sarson data flow diagrams 9 References References Gane, C., & Sarson, T. (979). Structured Systems Analysis: Tools and Techniques. Englewood Cliffs, NJ: Prentice Hall. Ken Hopkins, Curriculum Council Suggested Standards for Information Systems 2006: 238/7, Newman College, 200 available at: %20Suggested%20Standards.pdfhttp://portal.newman.wa.edu.au/technology/2infsys/html/KWH2003/InfoSys%202008/Information %20Systems%20-%20Suggested%20Standards.pdf Information Systems Teachers, Consensus Meetings (eds.). 2006, January). INFORMATION SYSTEMS, Suggested Standards for Information Systems Tools (Year 2 E238/7R). Retrieved from Trinity College website: Charts, Tables, Figures 3.4 Table. Methods for diagramming processes. Nahm, M, Duke University, 202. Images Slide 7: Simplified on-line appointment scheduling example using Gane-Sarson notation. Nahm M., Duke University, 202. Slide 8: Gane-Sarson symbols. Nahm M., Duke University, 202. Slide 9: Entities symbol in Gane-Sarson notation. Nahm M., Duke University, 202. Slide 0: Process symbol in Gane-Sarson notation. Nahm M., Duke University, 202. Slide : Flow symbol in Gane-Sarson notation. Nahm M., Duke University, 202. Slide 2: Data Store symbols in Sane-Garson notation. Nahm M., Duke University,