TB PATIENT MANAGEMENT PROJECT BUSINESS USE CASE SPECIFICATION 108: LEGAL ACTION Version 1.0 02/23/2004 This document has been developed by Science Applications International Corporation (SAIC) under a contract with the U.S. Centers for Disease Control and Prevention Department of Health and Human Services.
VERSION HISTORY Date Version Description Author 0.1 Initial Draft 09/02/2003 0.2 Revision R. Tracy 09/03/2003 0.3 Added Issued R. Tracy 09/24/2003 0.4 Merge UC 424 Initiate Legal Orders into this use R. Tracy case 10/23/2003 0.5 Updated pre-conditions J. Blue 11/10/2003 0.6 Revise Template G. Casdorph 02/10/2004 0.7 Revise from reconciliation of Post-JAD session Use G. Casdorph Cases to Final Use Cases 02/23/2004 1.0 Document baselined per PM CCB. G. Casdorph Revision Date: 02/23/2004 Page 2 of 6
TABLE OF CONTENTS 1 BUSINESS USE CASE 108: LEGAL ACTION... 4 1.1 Brief Description... 4 1.2 Actors... 4 1.3 Activity diagram... 4 1.4 Flow of Events... 4 1.4.1 Pre-Conditions... 4 1.4.2 Triggering Event(s)... 5 1.4.3 Basic Flow... 5 1.4.4 Alternative Flows... 5 1.4.5 Post Conditions... 5 1.4.6 Relationships... 5 1.5 Requirements... 6 1.5.1 Functional Capabilities... 6 1.5.2 Business Rules... 6 1.5.3 Supplemental Requirements... 6 1.6 Sources... 6 1.7 Issues... 6 Revision Date: 02/23/2004 Page 3 of 6
1 BUSINESS USE CASE 108: LEGAL ACTION 1.1 BRIEF DESCRIPTION This business use case will allow a user to gather documentation and initiate legal proceedings for a patient who does not adhere to treatment regimens and/or quarantine protocols. 1.2 ACTORS Health Care Worker (HCW) Health Department Legal Counsel 1.3 ACTIVITY DIAGRAM 1.4 FLOW OF EVENTS 1.4.1 Pre-Conditions 1.4.1.1 The patient requires evaluation or care for TB. 1.4.1.2 The user must have proper security rights to enter legal information. 1.4.1.3 The patient must exist in the system. 1.4.1.4 List of actions legal actions to motivate adherence (letter, court order request, etc) 1.4.1.5 Patient is classified 3-Clinical Case or 5-Suspect Case. 1.4.1.6 Acknowledgement of completion of TB Counseling Form or refusal to complete TB Counseling Form 1.4.1.7 Acknowledgement of completion of Notice of Counseling for DOT form completed or refusal to complete Notice of Counseling for DOT form 1.4.1.8 Documented procedures to give proof of non-adherence 1.4.1.9 Documented procedures for legal escalation are documented. Revision Date: 02/23/2004 Page 4 of 6
1.4.2 Triggering Event(s) 1.4.2.1 Patient does not consent to care while displaying symptoms of active disease. 1.4.2.2 Patient fails to attend Directly Observed Therapy (DOT) appointments or otherwise fails to take medications. 1.4.2.3 Patient fails to attend other appointments (x-ray, sputum, etc.) 1.4.2.4 Patient fails to comply with isolation protocols 1.4.2.5 Patient fails to report to health department for initial enrollment/assessment 1.4.2.6 System Use Case alerts user of patient non-adherence. 1.4.2.7 Patient has not complied with specific state laws. 1.4.3 Basic Flow 1.4.3.1 User selects Legal Action option 1.4.3.2 System displays legal action screen 1.4.3.3 User selects action(s) to show reasonable efforts to motivate adherence (phone call, non-adherence letter, court order, etc.) 1.4.3.4 System generates letter or court order as appropriate 1.4.3.5 User documents action taken within the system by completing a petition and affidavit that contains details of the patient s non-adherence. 1.4.3.6 User completes documentation for approval of the legal action. 1.4.3.7 System saves record 1.4.3.8 Use case ends 1.4.4 Alternative Flows 1.4.4.1 Use case repeats to continue gathering documentation of non-adherence 1.4.4.2 Legal proceedings are commenced to have the patient committed and turned over to the legal system 1.4.5 Post Conditions 1.4.5.1 Legal action documented in system 1.4.6 Relationships 1.4.6.1 UC.311.Document Care Note (to collect non-adherence notes) 1.4.6.2 UC.250.Create Template (for legal pleadings, petitions, affidavits, etc) 1.4.6.3 UC.109.Resolve Barriers (to record resolutions for barriers) Revision Date: 02/23/2004 Page 5 of 6
1.5 REQUIREMENTS 1.5.1 Functional Capabilities 1.5.2 Business Rules 1.5.3 Supplemental Requirements 1.6 SOURCES 1.7 ISSUES # Issue Opened Owner Status mm/dd/yy Revision Date: 02/23/2004 Page 6 of 6