A kick-off meeting will be planned
Appropriate IT staff and identified point person from the site should be present
The implementation kit materials will be provided in advance
During kick-off meeting
Develop a timeline
Review all materials and processes
Site will provide an annotated copy of the File Spec on what they can/can’t report, important notes, etc.
Site will provide a list with detailed descriptions of encounter types
Discussion of specific data elements of interest with sites will occur at the kick off or subsequent meeting
This document outlines roles among DPH, clinical site, Commonwealth Informatics, and Dept of Population Medicine
This document describes which EMR fields are necessary for ESP operation and case reporting, format of variables, and table structure
ESP Field List - FileSpec v2.0 (Latest Version)
ESP Field List - FileSpec v1.10
ESP Field List - FileSpec v1.7
ESP Field List (FileSpec) v1.6
How to Install and Configure ESP 3.5 on Ubuntu and RedHat(RHEL)
How to Install and Configure ESP 3.4 on Ubuntu 18.04-v4.pdf (3.4 is an OLD Version - please install 3.5.x )
How to Install and Configure ESP 3.4 on RedHat 7.6-v3.pdf (3.4 is an OLD Version - please install 3.5.x )
3.4.13 or 3.4.14 to 3.5.2 Upgrade Instructions Note: ESP 3.5 includes updates to Python and Django
This document includes information on how to validate the data load from the clinical site EMR
This document outlines how to map specific clinical site lab test names to abstract lab concepts in ESP
This document describes in detail how DPH and clinical site work together to validate messages and case information sent from ESP into the Massachusetts Virtual Epidemiologic Network (MAVEN)
This document suggests a format on how sites should validate the cases created in ESP
This document describes LOINC and SNOMED mapping to be completed by clinical site within the Health Information Reporting Portal (HIRP)
esphealth.org home page and FAQ