Presentation is loading. Please wait.

Presentation is loading. Please wait.

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.

Similar presentations


Presentation on theme: "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."— Presentation transcript:

1 EHR System Function and Information Model (EHR-S FIM based on EHR-S FM R2.0) CPS.9.4 Standard Report Generation aka S in EHR-S FM R1.1 , 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: , Passcode: #  The most current artifacts are at: 11/21/2018 DRAFT WORKING DOCUMENT

2 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

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

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

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

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

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

8 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

9 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

10 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


Download ppt "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."

Similar presentations


Ads by Google