120 likes | 232 Views
Public Health Reporting Functional Requirements Check-In. May 23, 2012. Agenda. Functional Requirements - Approach. Build on previous completed work; focus on steps necessary for creating, validating, sending, and acknowledging report Consolidated use case and scenario templates
E N D
Public Health Reporting Functional Requirements Check-In May 23, 2012
Functional Requirements - Approach • Build on previous completed work; focus on steps necessary for creating, validating, sending, and acknowledging report • Consolidated use case and scenario templates • Data set requirements (including elements, definition, cardinality, and data types) • Information exchange scenarios • Working through user stories and domain custodians to identify functional requirements
Table of Contents 4.0 Functional Requirements 4.1 Information Interchange Requirements 4.2 System Requirements 4.3 Triggers 5.0 Non-Functional Requirements 6.0 Dataset Requirements 7.0 Standards Analysis 1.0 Preface and Introduction 2.0 Initiative Overview 2.1 Initiative Challenge Statement 3.0 Use Case Scope 3.1 Background 3.2 In Scope 3.3 Out of Scope 3.4 Communities of Interest 3.5 Actors and Roles 3.6 Use Case Diagrams 3.6.1 Base Flow Description 3.6.2 Alternate Flow 3.6.3 Activity Diagram Tailored from: 1) Bruegge B. and Dutoit A.H. Object-Oriented Software Engineering. Pearson Prentice Hall. Upper Saddle River, NJ. 2nd edition. 1-172. 2) PHDSC Web-Resource Center: Public Health in HIT standardization. HIT Standards Module. Functional Standards. URL: http://www.phdsc.org/standards/health-information/F_Standards.asp
Activity Diagrams – More Details • http://wiki.siframework.org/file/view/PDF+Process+Flow.pdf • Outlines specific steps in the creation, send, receipt, validation, and acknowledgement of a report • Identifies different steps as in scope for the initiative and initiative phase • i.e. Implementation / Pilot details may influence how a report created (automatically vs. web form)
Functional Requirements - Triggers • Considerations include • Reporting criteria as specified by jurisdictional (e.g., federal, state, local or territorial) legislation, statute or regulation. • Surveillance criteria as specified by an organization (e.g., public health agency, healthcare provider, quality improvement organization, registry, etc.) • Patient observations or other healthcare-related assessments made by healthcare providers or other staff • The presence of specific data or documentation within an EHR that meets reporting criteria.
Non-Functional Requirements • Quality Requirements • Data quality, reliability, performance • Constraints • Privacy / security, operations (e.g. periodicity), service level constraints, etc.
Dataset Requirements / Standards Analysis • Data Harmonization Profile
Activity Diagrams – More Details • http://wiki.siframework.org/file/view/PDF+Process+Flow.pdf • Outlines specific steps in the creation, send, receipt, validation, and acknowledgement of a report • Identifies different steps as in scope for the initiative and initiative phase • i.e. Implementation / Pilot details may influence how a report created (automatically vs. web form)
Functional Requirements Resources • Other S&I Initiatives • http://wiki.siframework.org/LRI+-+FINAL+Use+Case • http://wiki.siframework.org/ToC+-+Functional+Requirements+SWG • FRAD Development Tutorial • Functional Standards. Module 2. Lecture 5. Johns Hopkins OpenCourseWare. Health IT Standards and Systems Interoperability. 315.708.81. URL: http://ocw.jhsph.edu/courses/infstandards/lectureNotes.cfm