EHR/Health Endeavors Integration Options
Quality Measures via
Single/Spec File
Client Upload to Health Endeavors
Quality Measures Extract, Transform & Load (ETL)
Continuity Care Document (CCD)
Secure File Transfer Portal (SFTP)
Application Program Interface (API)
Quality Measures Extract, Transform & Load (ETL)
Business Requirements Document (BRD)
Secure File Transfer Portal (SFTP)
Application Program Interface (API) Claims Data display
in EHR via Patient Match
(API/SSO)
Patient Profile
Patient Chart
Patient Gaps in Care
Patient Care Coordination Events
Care Coordination Tool
Templates mapping of EHR and
Claims data.
Secure File Transfer Portal
(SFTP)
Application Program Interface
(API)
2
GPRO Central Quality Measure
Repository
Data Imports
Lab File HL7 v2 (parsed with multi
delimiters) and HL7 v3 (xml)
Health Endeavors Spec or Spec File
Upload
Manual KeyClaims (CCLF) Data Imports
EHR Extract, Transform, Load
[CCD Automation]
HE Business Requirements
Document (EHR BRD) Builds
(xlx, xlxs, txt, csv)
3
Quality Measures
QM 2017 IMPORT CHART
Preferences, Data Imports & Priorities
January 19, 2017 pg 4
GPRO Central Quality Measure
Repository
Data Imports
Lab File HL7 v2 (parsed with multi
delimiters) and HL7 v3 (xml)
Health Endeavors Spec or Spec File
Upload
Manual KeyClaims (CCLF) Data Imports
EHR Extract, Transform, Load
[CCD Automation]
HE Business Requirements
Document (EHR BRD) Builds
(xlx, xlxs, txt, csv)
5
Quality Measures
January 19, 2017 pg 6
January 19, 2017 pg 7
January 19, 2017 pg 8
January 19, 2017 pg 9
January 19, 2017 pg 10
Claims Data display
in EHR via Patient Match (API/SSO)
Patient Profile
Patient Chart Care Coordination Events
Patient Gaps in Care
11
CCLF Data display in EHR - Application Program Interface (API)/Patient Match
EHR – Patient Match Integration
Patient Profile, Patient Chart Summary, View Case Management Events
1/19/2017 12
January 19, 2017 pg 13
January 19, 2017 pg 14
January 19, 2017 pg 15
Display in CCLF Claims data in EHR
Data Field Mapping
Secure File Transfer Portal (SFTP)
Application Program Interface (API)
16
Care Coordination Tool Templates populate from EHR data
January 19, 2017 pg 17
Setup Considerations
• ACO ID
• Template Name
• Event Type
• Care Coordination Partner
Data Dictionary
• Option One: Provide a data dictionary of the fields in excel or csv format (Submit a
Request). Data dictionary should define fields:
Field Name
Field Type: Numeric, Alpha, Date Input, Email Input, Phone Input, Dropdown
Select (one option), Radios/Checkboxes, Text Field
Field Response Options (if applicable)
Length of Field (Characters)
• Example:
Type of Fall Dropdown Select of Level 1/Level 2/Level 3 N/A
Description Field Alpha Numeric Text Input 50 Characters (Text)
Template Build
• Option Two:
• Build Template in Care Coordination Tool (CCT) and match
the EMR export to the fields in the Template.
• EMR Data sent in Excel or CSV
Top Related