Public Health Reporting Functional Requirements Check-In May 23, 2012

Agenda TopicTime Allotted Welcome / Agenda Overview - John Stinn4:00 - 4:05 Introduction / Approach Functional Requirements Update4:05 – 4:15 Functional Requirements Table of Contents Review4:15 – 4:25 Activity Diagram Review4:25 – 4:50 Resources4:50 – 5:00 Adjourn5:00

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 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 Base Flow Description Alternate Flow Activity Diagram 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 Tailored from: 1) Bruegge B. and Dutoit A.H. Object-Oriented Software Engineering. Pearson Prentice Hall. Upper Saddle River, NJ. 2 nd edition ) PHDSC Web-Resource Center: Public Health in HIT standardization. HIT Standards Module. Functional Standards. URL:

PHRI Base Flow (in Use Case)

Base Flow Description (in Use Case) Step #ActorRoleEvent/DescriptionInputsOutputs 1EHR System Generate and Send Report EHR System generates public health report and sends to public health agency system (Note: healthcare provider may verify/certify report prior to send) Public health reporting criteria; report generated/sent when patient/healthcare data meets reporting criteria and appropriate report validation and certification processes are complete. Public health report, including at a minimum all required data elements that meet the specified report type, in standardized structured format 2 Public Health Agency System Receive Report Public Health Agency System receives report Receipt of public health report Program-specific outputs (out of scope for this document) 3 Public Health Agency System Send Acknowledgement Public Health Agency System sends acknowledgement of receipt of report Receipt of public health report Acknowledgement of receipt of public health report 4EHR SystemReceive Acknowledgement EHR System receives acknowledgement of receipt Acknowledgement of receipt of public health report END

Activity Diagrams – More Details +Flow.pdf +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 CEDD object CEDD data element name Referenc e source (C- communc iable diseases, S- syndromi c surveillan ce) CategoryNameDescription Is this mand atory by user story submi tters (Y, N)? Sender Usage/HL 7 Required FormatValue Set CDC Vocabulary Server - VADS Value Set Hyperlink Notes Report Report Date/TimeC, SReportReport date/time Date and time the report is being sent to public health YR Date/Time,, Format:YYYY MMDDHHM M[SS[.S[S[S[ S]]]]] [+/- ZZZZ] HL7 Date/Time Report Alert Creation Date/Time CReport Alert creation date/time For automated systems, date/time detection algorithm created the alert relevant to the condition being reported 1 YRE Date/Time, Format:YYYY MMDDHHM M[SS[.S[S[S[ S]]]]] [+/- ZZZZ] HL7 Date/Time 1-Taken from notes; Reporting SystemCReportReporting system YRETX The sending application/sendi ng facility is required in ELR IG; The sending application and sending facility are included in the MSH segment in v2.x messages, and in whatever control wrapper is used to send the document (which could be a v2.x message).

Activity Diagrams – More Details +Flow.pdf +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 – – FRAD Development Tutorial – Functional Standards. Module 2. Lecture 5. Johns Hopkins OpenCourseWare. Health IT Standards and Systems Interoperability URL: