EHR System Function and Information Model (EHR-S FIM based on EHR-S FM R2.0) CPS.9.4 Standard Report Generation aka S.2.2.2 in EHR-S FM R1.1 Stephen.Hufnagel@tma.osd.mil.

Slides:



Advertisements
Similar presentations
DIGIDOC A web based tool to Manage Documents. System Overview DigiDoc is a web-based customizable, integrated solution for Business Process Management.
Advertisements

“Service Framework” workgroup
Initial slides for Layered Service Architecture
FireRMS SQL Audit, Archiving & Purging Presented by Laura Small FireRMS Quality Assurance.
The EHR-S FIM project plans to harmonize the EHR-S FM R2
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review April 9, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Understanding the Vital Records Functional Profile (VRFP) Hetty Khan Health Informatics Specialist Centers for Disease Control and Prevention National.
CONNECT Roadmap Draft version as of February 4 th,
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review April 23, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
Public Health Tiger Team we will start the meeting 3 min after the hour DRAFT Project Charter April 15, 2014.
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
LeToia Crozier, Esq., CHC Vice President, Compliance & Regulatory Affairs Corey Wilson Director of Technical Services & Security Officer Interactive Think.
FEA DRM Management Strategy Presented by : Mary McCaffery, US EPA.
Larry Wolf Certification / Adoption Workgroup May 13th, 2014.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
HL7 Electronic Health Record System (EHR-S) Public Health Functional Profile (PHFP) Project PHDSC Annual Business Meeting November 8, 2012 Hetty Khan Health.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review August 13, 2013 Presented by: Michael Dufel and David Staggs Jericho Systems Corporation.
Clinical Quality Workgroup April 10, 2014 Commenting on the ONC Voluntary 2015 Edition Proposed Rule Marjorie Rallins– co-chair Danny Rosenthal –co-chair.
Data Provenance All Hands Community Meeting February 19, 2015.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review November 5, 2013 Presented by: David Staggs JD, CISSP Jericho Systems Corporation.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
Introduction to the GEOSS Registries: Components, Services, and Standards Doug Nebert U.S. Federal Geographic Data Committee June 2007.
Integrating the Healthcare Enterprise
REDCap New Features LTS 6.15.x
Copyright Scott Bloss, All rights reserved.
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS.3.9 Clinical Decision Support System Guidelines Updates aka S
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.3 Manage Medication List aka DC in EHR-S FM
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS Manage Patient Advance Directives aka DC in EHR-S.
Extended Document Management System (EDMS)
Electronic Health Record
EHR System Function and Information Model (EHR-S FIM) Release 2
Electronic Health Information Systems
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.6.2 Manage Immunization Administration aka DC in EHR-S FM.
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.3.3 Manage Clinical Documents and Notes aka DC in EHR-S FM.
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List aka DC
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS Manage Patient Advance Directives aka DC in EHR-S.
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.6 Manage Immunization List aka DC in EHR-S FM R1.1
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
Distributor Want aka. Dis-WAnt
, facilitator January 21, 2011 DRAFT-A
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) AS.4.1 Manage Registry Communication aka S.1.1 in EHR-S FM R1.1
Electronic Health Record Access Control 7
HingX Project Overview
Bethesda Cybersecurity Club
Overview of Oracle Site Hub
Pam Matthews, FHIMSS Director of Business Information Systems Business Information Systems is focused around administrative and financial information.
, editor October 8, 2011 DRAFT-D
Payroll Services Scenario Overview
HP Quality Center 10.0 The Test Plan Module
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
Payroll Services Scenario Overview
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
Conceptual Data Flow Model Between PHIN Systems
Journey Centric Delivery Day 1 Live Plan
Presentation transcript:

EHR System Function and Information Model (EHR-S FIM based on EHR-S FM R2.0) CPS.9.4 Standard Report Generation aka S.2.2.2 in EHR-S FM R1.1 Stephen.Hufnagel@tma.osd.mil , facilitator January 27, 2012, original February 24, 2012, last updated Call for Participation This work is being done by the HL7 EHR Interoperability Work-group, meeting every Tuesday at 4PM ET, dial-in: 1-770-657-9270, Passcode: 510269#  The most current artifacts are at: http://wiki.hl7.org/index.php?title=EHR_Interoperability_WG 11/21/2018 DRAFT WORKING DOCUMENT

CPS.9.4 Standard Report Generation Statement: The purpose of this function is to provide report generation features using tools internal or external to the system, for the generation of standard reports. Description: Providers and administrators need access to data in the EHR-S for clinical, administrative, financial decision-making, audit trail and metadata reporting, as well as to create reports for patients. Many systems may use internal or external reporting tools to accomplish this (such as Crystal Report). Reports may be based on structured data and/or unstructured text from the patient's health record. Users need to be able to sort and/or filter reports. For example: -the user may wish to view only the diabetic patients on a report listing patients and diagnoses -the user may wish to view only male patients over 35 with a complaint of chest pain. Example: (Notional Scenario) Clinical users and Administrators manage report metadata and report filters; so that, they can render various standard reports from structured or unstructured EHR data, using internal or external reporting tools. Audits are kept of all users who use or access the reported data, according to scope of practice, organizational policy and/or jurisdictional law. 11/21/2018 RED: delete, Blue: insert DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CPS.9.4 Standard Report Generation Activities Mapped-to System-Components 11/21/2018 DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CPS.9.4 Standard Report Generation Conceptual Information Model (CIM) Mapped to EHR-S Functions 11/21/2018 DRAFT WORKING DOCUMENT

CPS.9.4 Standard Report Generation Conceptual Data Model (CDM) 11/21/2018 DRAFT WORKING DOCUMENT

CPS.9.4 Standard Report Generation CDM Requirements-Traceability 11/21/2018 DRAFT WORKING DOCUMENT

CPS.9.4 Standard Report Generation Dependencies 11/21/2018 DRAFT WORKING DOCUMENT

Action Verb Hierarches Manage (Data) Capture Maintain Render Exchange Determine Manage- Data- Visibility Auto-Populate Enter Import Receive Store Update Remove Extract Present Transmit Export Analyze Decide De-Identify Hide Mask Re-Identify Unhide Unmask Archive Backup Decrypt Encrypt Recover Restore Save Annotate Attest Edit Harmonize Integrate Link Tag Delete Purge 11/21/2018 DRAFT WORKING DOCUMENT

CPS.9.4 Standard Report Generation Requirements 1. The system SHOULD provide the ability to render reports of structured clinical and administrative data using either internal or external reporting tools. 2. The system MAY provide the ability to extract unstructured clinical and administrative data for inclusion in the report generation process, using internal or external tools. 3. The system SHOULD provide the ability to extract and transmit reports generated. 4. The system SHOULD provide the ability to capture and maintain report parameters, based on patient demographic and/or clinical data, which would allow sorting and/or filtering of the data. 5. The system MAY provide the ability to save report parameters for generating subsequent reports either as integrated component of the system, or an external application, using data from the system. 6. The system MAY provide the ability to edit one or more parameters of a saved report specification when generating a report using that specification either as integrated component of the system, or an external application, using data from the system. The system SHOULD provide the ability to render automated reports as required by industry and regulatory bodies. The system SHOULD provide the ability to extract facility level data at an organizational level in support of organizational initiatives. The system MAY provide the ability to render a cumulative directory list of all personnel who use or access the data. RED: delete, Blue: insert DRAFT WORKING DOCUMENT 11/21/2018

CPS.9.4 Standard Report Generation Dependencies POP.4 Support for Monitoring Response Notifications Regarding a Specific Patient’s Health (DC.2.6.3) POP.8 De-Identified Data Request Management (S.1.5) AS.6.6 Support Patient Acuity and Severity Determination (S.3.6) OVERARCHING: Trust Infrastructure Record Infrastructure